<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Morning,<br>
<br>
<blockquote cite="mid:512D518F.8070108@gmail.com" type="cite">
<blockquote cite="mid:512CF61E.7050106@byte-consult.be"
type="cite"> flyer_vertaling.txt: ISO-8859 English text, with
CRLF line terminators<br>
</blockquote>
No, displaying an ISO-8859-1 encoded file as if it were UTF-8
encoded gives a wrong display.<br>
é (e-acute)<br>
</blockquote>
Oh, I didn't spot a e-acute in there, I just quickly glanced at the
content, that one would indeed backfire. I looked ok at first. <br>
<blockquote cite="mid:512D518F.8070108@gmail.com" type="cite"> ISO
8859-1 : E9 (invalid under UTF-8 decoding)<br>
UTF-8 : C3A9 (displays as é under ISO-8859-1 decoding) <br>
That's because <a moz-do-not-send="true"
href="http://en.wikipedia.org/wiki/UTF-8#Description">UTF-8 uses
the two high order bits as flags</a>.<br>
<br>
To have no problems, use UTF-8 everywhere.<br>
</blockquote>
<br>
I totally agree here. I wished we had like 1 character set
covering them all (=irony) including kanji and big5<br>
<br>
<blockquote cite="mid:512D518F.8070108@gmail.com" type="cite">
<blockquote cite="mid:512CF61E.7050106@byte-consult.be"
type="cite">
<blockquote cite="mid:512CF01B.8030405@gmail.com" type="cite"> I
still think that Apache is not doing its .ext->mimetype
job, there, but it may be a user config pb.<br>
</blockquote>
<br>
What do you mean exactly ?<br>
</blockquote>
that Apache indicated text/plain when transmitting the .SVG file;
same for other files.<br>
</blockquote>
I did misunderstand the text/plain point you made. It would be easy
to fix that in the SVN props, any svg capable browser would then
display it directly once that is corrected.<br>
<br>
Glenn<br>
</body>
</html>