I checked this with Chrome 54.0.2840.27 beta (64-bit) and Firefox 48.0.1 on Linux, and was able to reproduce the problem on Firefox. It seems Chrome is defaulting to UTF-8 in the absence of any other declaration these days.
Great catch Eva! This is a fix we want as well; I've gone ahead and created a branch at http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbs/lp1624846_print_charset_header that implements the fix.
I checked this with Chrome 54.0.2840.27 beta (64-bit) and Firefox 48.0.1 on Linux, and was able to reproduce the problem on Firefox. It seems Chrome is defaulting to UTF-8 in the absence of any other declaration these days.
Great catch Eva! This is a fix we want as well; I've gone ahead and created a branch at http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ dbs/lp1624846_ print_charset_ header that implements the fix.