What is the character encoding used by your GeoServer instance? Is your server using UTF-8?
Text files containing UTF-8 byte sequences that are written to a server that does not support these UTF-8 byte sequences might be corrupted when unsupported characters are replaced with other bytes as placeholders. This could make files valid for the server encoding but invalid UTF-8. If I open your SLD in Firefox 49, it correctly detects the encoding as UTF-8 but reports the following error: http://osgeo-org.1560.x6.nabble.com/file/n5294270/BaftFarsoode.sld XML Parsing Error: not well-formed Location: http://osgeo-org.1560.x6.nabble.com/file/n5294270/BaftFarsoode.sld Line Number 14, Column 18: <Title>���� ������</Title> -----------------^ This is consistent with the exception you report (copying from Nabble as I do not see the log in the mailing list email): INFO | jvm 1 | 2016/11/04 22:49:36 | java.lang.RuntimeException: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 2-byte UTF-8 sequence. INFO | jvm 1 | 2016/11/04 22:49:36 | at org.geotools.styling.SLDParser.parseSLD(SLDParser.java:430) Kind regards, Ben. On 05/11/16 08:26, am2222 wrote: > This is the log File when I save style with unicode characters. Any > suggestion? -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
