Hi, JSON RFC [1] says in Section 3 Encoding: "JSON text SHALL be encoded in Unicode. The default encoding is UTF-8." But geoserver's default encoding for json output is taken from global encoding setting, which can be different to UTF-8 and therefor be not unicode. Today, many JSON parsers expect UTF-8 but get for example iso-8859-1 and throw exceptions when handling special characters (german language). But setting global encoding to UTF-8 could break compatibility to existing WFS client apps and is therefor not so good.
Would you accept a patch, that uses hardcoded UTF-8 for JSON output no matter what global encoding has been set? What do you think? [1] http://www.ietf.org/rfc/rfc4627.txt Cheers Rudi ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
