On 11/11/16 21:43, Andrea Aime wrote: > On Thu, Nov 10, 2016 at 9:41 PM, Ben Caradoc-Davies <[email protected]> > wrote: >> Are there use-cases in which it is desirable to leave the file.encoding >> property unset? Setting this as the default behaviour would likely improve >> the experience of users with a non-UTF8 default encoding. > > Eh, I'm not sure.
In particular, what happens if -Dfile.encoding=UTF8 is set on platform with a non-US-ASCII Windows code page, and the SLD editor is used to edit an SLD that uses this code page (not UTF-8)? Setting -Dfile.encoding=UTF8 in the Windows startup scripts might break things for some users. A better solution might be for the encoding to be detected from the SLD when it is written. I am not volunteering. I support all encodings ... as long as they are UTF-8: http://utf8everywhere.org/ Kind regards, -- 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
