Encoding of special (German Umlaut) characters in html backend

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Encoding of special (German Umlaut) characters in html backend

ChrLipp
Hello!

I am aware of this thread: http://discuss.asciidoctor.org/German-special-Characters-incompatible-character-encodings-CP850-and-UTF-8-td175.html and therefore create my *.adoc files encoded in UTF-8 without BOM.

When I use the HTML backend I noticed (when looking at the source of the HTML) that the German Umlaut characters (ä, Ä, ö, Ö, ü, Ü, ß) are included in the HTML without any processing.
But in my opinion the chars should be transformed, e.g. ä should become &a uml;  (without the space, see http://www.w3schools.com/tags/ref_entities.asp)

In my opinion the transformation should also performed within the docbook backend (since this is XML).
What do you think?

Kind regards, Christian
Reply | Threaded
Open this post in threaded view
|

Re: Encoding of special (German Umlaut) characters in html backend

LightGuardjp
Administrator
If the generated files are UTF-8 encoded, why does it matter if they're transformed with the different entities? The whole idea of the different entities is so you can include characters from a different character set in something more restrictive.


On Mon, Sep 9, 2013 at 2:32 AM, ChrLipp [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Hello!

I am aware of this thread: http://discuss.asciidoctor.org/German-special-Characters-incompatible-character-encodings-CP850-and-UTF-8-td175.html and therefore create my *.adoc files encoded in UTF-8 without BOM.

When I use the HTML backend I noticed (when looking at the source of the HTML) that the German Umlaut characters (ä, Ä, ö, Ö, ü, Ü, ß) are included in the HTML without any processing.
But in my opinion the chars should be transformed, e.g. ä should become &a uml;  (without the space, see http://www.w3schools.com/tags/ref_entities.asp)

In my opinion the transformation should also performed within the docbook backend (since this is XML).
What do you think?

Kind regards, Christian


If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Encoding-of-special-German-Umlaut-characters-in-html-backend-tp548.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Reply | Threaded
Open this post in threaded view
|

Re: Encoding of special (German Umlaut) characters in html backend

ChrLipp
You are right, my mistake.
I missed the

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

in the generated HTML.

Thanks for your answer.