[OSM-talk-be] OSM promo

[Glenn Plas]

Morning,

>> flyer_vertaling.txt: ISO-8859 English text, with CRLF line terminators
> No, displaying an ISO-8859-1 encoded file as if it were UTF-8 encoded 
> gives a wrong display.
> é (e-acute)
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.
> 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 
> <http://en.wikipedia.org/wiki/UTF-8#Description>.
>
> To have no problems, use UTF-8 everywhere.

I totally agree here.   I wished we had like 1 character set covering 
them all (=irony)  including kanji and big5

>>> I still think that Apache is not doing its .ext->mimetype job, 
>>> there, but it may be a user config pb.
>>
>> What do you mean exactly ?
> that Apache indicated text/plain when transmitting the .SVG file; same 
> for other files.
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.

Glenn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-be/attachments/20130227/c454fe5b/attachment.htm>