OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: problem with HTMLHelp and Turkish content

I'm having a problem building HTML Help output with Turkish content 
(lang="tr").   I'm hoping someone has more experience with this issue.

Turkish requires using windows-1254 encoding instead of windows-1252.  The 
xsltproc processor handles 1254, so I am able to customize the XSL to 

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

into the HTML files, and compile them using HTML Help Workshop.  The text 
displays correctly in the main window and in the TOC.

The one problem remaining is that the Index window contains some incorrect 
characters.  The  index includes indexterm elements and the document 
titles.  It is clear when comparing the 1254 and 1252 encodings that the 
incorrect characters are coming from the codepoints in 1252 instead of 
1254.  For example, "small dotless i" (0xFD in Windows 1254) is replaced 
with "small y acute" (0xFD in Windows 1252).

The help index comes from param elements like this contained in <object> 
elements in the HTML output:

<param name="Keyword" value="My turkish title">

It seems when the help compiler collects this data, it loses the connection 
with the windows-1254 meta information that was at the top of the HTML file 
it came from.   I have not found a way to specify that the keyword index 
should be handled in the 1254 encoding.

Has anyone else seen this problem, and found a solution?

Bob Stayton
Sagehill Enterprises
DocBook Consulting

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]