Yep, it's all UTF-8 everywhere but guess what....

I figured out: SLD style ask font-family Arial anec obviously I had no 
Microsoft fonts on the server. Installing them fixed the issue...


Regards, Adam.

________________________________
De : Ian Turton <[email protected]>
Envoyé : lundi 9 juillet 2018 18:21:21
À : Cecile, Adam
Cc : geoserver-users
Objet : Re: [Geoserver-users] Encoding issue when styling ?

What did you set the input encoding to when importing? PostGIS will default to 
UTF-8 I think.

did you set the locale for your server?

Ian

On Mon, 9 Jul 2018 at 16:50, Cecile, Adam 
<[email protected]<mailto:[email protected]>> wrote:

SQL looks ok:


osm=# SELECT id, osm_id, type, name, ref, z_order, class FROM osm_roads WHERE 
name NOT LIKE '' limit 10;
 id | osm_id  |     type      |             name             |   ref   | 
z_order |  class
----+---------+---------------+------------------------------+---------+---------+---------
 19 | 4065573 | primary       | Route de Luxembourg          | N 7     |      
26 | highway
 21 | 4065707 | primary       | Route d'Arlon                | N 6     |       
6 | highway
 24 | 4065736 | primary       | Boulevard Royal              | N 7     |       
6 | highway
 25 | 4065960 | trunk_link    | Rocade de Bonnevoie          | B 3     |       
3 | highway
 28 | 4065877 | motorway_link | Aire d'autoroute de Capellen | A 6     |       
3 | highway
 31 | 4266075 | rail          | Ligne Luxembourg - Oetrange  | Ligne 4 |      
27 | railway
 32 | 4266076 | rail          | Ligne Luxembourg - Oetrange  | Ligne 4 |      
27 | railway
 33 | 4266077 | rail          | Ligne Luxembourg - Oetrange  | Ligne 4 |      
27 | railway
 34 | 4266078 | rail          | Ligne Luxembourg - Oetrange  | Ligne 4 |      
27 | railway
 35 | 4266083 | rail          | Ligne Luxembourg - Oetrange  | Ligne 4 |      
27 | railway


________________________________
De : Cecile, Adam
Envoyé : lundi 9 juillet 2018 17:13:20
À : 
[email protected]<mailto:[email protected]>
Objet : Encoding issue when styling ?


Hello,


Here is what is display when using layer preview. Data source is PostGIS. When 
exporting layer to GeoJSON, labels are ok, so it really seems to be related to 
styling.

Same broken labels appear when querying WMS from VueJS/Openlayers.


Any idea ?


Thanks in advance,


Best regards, Adam.




[cid:08ac2b68-de74-4949-9ccc-add0f3f456c3]


____________________________________________________________________________________

Adam Cecile
ICT Engineer - Software & ICT

HITEC Luxembourg S.A.
5, rue de l'Eglise
L-1458 Luxembourg       Tel: +352 498478 - 775
Fax: +352 401303
www.hitec.lu<http://www.hitec.lu>

        Email: [email protected]<mailto:[email protected]>


Follow us on social media
[http://www.hitec.lu/images/signature/linkedin.png]<https://www.linkedin.com/company/hitec-luxembourg-s-a-/>
 [http://www.hitec.lu/images/signature/facebook.png] 
<https://www.facebook.com/HITECLuxembourg/>  
[http://www.hitec.lu/images/signature/twitter.png] 
<https://twitter.com/HITECLuxembourg>  
[http://www.hitec.lu/images/signature/youtube.png] 
<https://www.youtube.com/channel/UCZKNGXNIkhojWloXtbXUhgg>           
[http://www.hitec.lu/images/signature/logo2.png]         
[http://www.hitec.lu/images/signature/made-in-lux-50.png]  
[http://www.hitec.lu/images/signature/ISO-logo-50.png]    
[http://www.hitec.lu/images/signature/FB.JPG]



Disclaimer: Information included in this email is reserved to named addressee’s 
eyes only. You may not share this message or any of its attachments to anyone. 
Please note that as the recipient, it is your responsibility to check the email 
for malicious software. Finally, the opinions disclosed by the sender do not 
have to reflect those of the company, therefore the company refuses to take any 
liability for the damage caused by the content of this email.

Is it necessary to print this email? If you care about the environment like we 
do, please refrain from printing emails. It helps to keep the environment 
forested and litter-free.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/geoserver-users


--
Ian Turton
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to