docbook v5 customization layer - german umlaute / oxygenxml

[osprofi]

Hello Docbook user

I am writing a customization layer and have 2 questions:

1) I wrote an xml testfile in UTF-8 encoding using german umlaute;
I specified in the customization file for html conversion

Code: Select all

<xsl:output method="html" encoding="UTF-8" indent="yes"/>

the related meta tag

Code: Select all

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

is displayed correctly, but the german umlaute, e.g. ä is written like this: ä

What do I need to adjust so that the correct UTF-8 code for the letter ä will be displayed ?

2) Before using a customization layer for the html transformation Oxygenxml generated an html file which was immediately displayed; Now, using a customization layer for the html transformation the html code is only displayed in the lower window.

What do I need to adjust that the generated html file is displayed straight on ?

Thanks for your help.

regards, peter

[osprofi]

Hello docbook users
question #2 is solved using changing the output parameter in the transformation scenario
regards, peter

[sorin_ristache]

Hello Peter,

1) I wrote an xml testfile in UTF-8 encoding using german umlaute;
I specified in the customization file for html conversion

Code: Select all

<xsl:output method="html" encoding="UTF-8" indent="yes"/>

the related meta tag

Code: Select all

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

is displayed correctly, but the german umlaute, e.g. ä is written like this: ä

What do I need to adjust so that the correct UTF-8 code for the letter ä will be displayed ?

This is caused by the attribute method="html" of the element xsl:output in the XSLT stylesheet. The HTML serializer is imposed by this output method declaration and for the non-ASCII characters it does not guarantee that the Unicode codepoint is used. In particular the German umlaute characters are always represented as entity references (e.g. ä). If you change the method to "xml" you get the ä character.

Anyway the browser displays the character correctly (i.e. ä) regardless of the representation in the HTML file, as the ä character or as the entity reference ä, because all browsers (I think) know how to represent the ä reference. So the exact representation in the HTML file does not really matter if the character is displayed correctly in the browser.


Regards,
Sorin