Created attachment 1147 [details]
Example of bad enconding: German umlauts are not correct.
The users handbook is lacking correct informations about its encoding.It need the simple line
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
to get the right encoding. This will go to the HEAD-section of its HTML-code.
this is actually a docbook2html related problem, as the manuals are generated at build time.
Ok. Is there a solution for it?
Otherwise - this sems to be not a new problem with docbook2html. See:
I found this solution but did not know if it will help. See:
Created attachment 1148 [details]
Add SP_ENCODING at html manual generation
Adding SP_ENCODING (patch attached) doesn't help much. I only see some improvement on Spanish uppercase accented letters, which are now properly encoded in output. Other manuals do not use utf-8 encoding (well, English, but has no special chars inside), so the output remains unchanged.
Anyway that doesn't add a proper encoding headers to the final HTML document, so not really a solution.
Created attachment 1149 [details]
Set encoding in generated HTML
The SP_ENCODING=xml appears more promising, as allows generating all output in UTF-8 regardless the input encoding. A bit of sed does the magic for setting the proper meta tag.
Changes related to this bug have been committed.
Please check latest CVS and update the bug accordingly.
You can also get the patch from:
2012-08-24 [mones] 3.8.1cvs35
Keep alphabetic order of hidden options lost
and update Clawsker URL.
Update Clawsker URL.
Sync with English version and update Clawsker URL.
Fix bug 2723 'Missing encoding in generated html manual'