Hi,
The intresting part is that I opened sld file in notepad++ and change
Encoding to UTF-8-BOM and it worked fine. thanks
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Right-to-left-language-Arabic-Persian-problem-in-SLD-Legend-tp5294270p5294412.html
Sent from the
GeoServer can always output UTF-8 because Java supports UTF-8. Problems
can arise when GeoServer tries to save files such as your SLD on a
platform with an encoding that does not support all the characters in
the file. This can cause files to be corrupted.
What is the platform on which you
And in answer to your original question, GetLegendGraphic also seems to
work on my UTF-8 system (see attached legend).
Kind regards,
Ben.
On 06/11/16 10:45, Ben Caradoc-Davies wrote:
I am using Linux (Debian unstable) with locale en_GB.utf8 (that is,
UTF-8 as the platform encoding). I tested
Hi Ben,
You did not perhaps notice the mail telling that the SLD file encoding should
be set to UTF-8 with BOM and then it started to work.
I think that it is good to accept BOM but it should not be required.
Jukka Rahkonen
Lähettäjä: Ben
Jukka,
I agree that the BOM should not be required. Looking at the original
email provided by the reporter, the SLD appears corrupt, as it contains
a malformed UTF-8 byte sequence, confirmed by inspection of the actual
byres. Editing this file with Notepad++ likely re-encodes it. I still
