On 2013-02-26 18:51, Glenn Plas wrote :
I don't mean that the type of the SVG file should be text/plain, I say that it is; it should be what you say.Unfortunately, SVG type is text/plain, and some png files remain wrong. No, displaying an ISO-8859-1 encoded file as if it were UTF-8 encoded gives a wrong display.dutch_flyer_2013_02/flyer_vertaling.txt seems to be ISO8859-1 and is displayed with UTF-8.Fortunately UTF8 covers the same codepoints as the characters in ISO-8859-1 but not the other ISO-8859-x sets, so in this case it probably will not be a problem. Since there is no entry in the props list(it's not really a prop anyway) , I think UTF8 is the server default for text files, you are correct about the file type, checking the file signature confirms: é (e-acute) ISO 8859-1 : E9 (invalid under UTF-8 decoding) UTF-8 : C3A9 (displays as é under ISO-8859-1 decoding) That's because UTF-8 uses the two high order bits as flags. To have no problems, use UTF-8 everywhere. that Apache indicated text/plain when transmitting the .SVG file; same for other files.I still think that Apache is not doing its .ext->mimetype job, there, but it may be a user config pb. Cheers,
|
_______________________________________________ Talk-be mailing list Talk-be@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-be