Conversion of special characters to entities

[Tobias Gruetzmacher]

Hi,

Lasar Liepins schrieb:
> Apparently MarkDown does not convert special characters that possess
> HTML entity equivalents. Examples are German Umlauts (ä becomes ä
> etc), which often come up in my documents, with me being German and all
> that. Of course I can do this with an additional script after or before
> running MarkDown over my documents, but since for example the ampersand
> is converted to &, I was wondering why such characters are not
> replaced by their respective entities.

If the character encoding of your documents is correctly declared
everywhere (I suppose you use ISO-8859-1 or ISO-8859-15) using the

     Content-Type: text/html; charset=iso-8859-1

HTTP Header or (if you have no control over your web server) the
corresponding meta attribute:

     <meta http-equiv="content-type"
     content="text/html; charset=ISO-8859-1">

then using entities should not be necessary. I don't think there are any
browsers out there which don't honour this specification.

Greetings Tobi

--
GPG-Key 0xE2BEA341 - signed/encrypted mail preferred
My, oh so small, homepage: http://portfolio16.de/
http://www.fli4l.de/ - ISDN- & DSL-Router on one disk!
Registered FLI4L-User #00000003
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://six.pairlist.net/pipermail/markdown-discuss/attachments/20050309/03746ef3/signature.bin