[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] problem with HTMLHelp and Turkish content
Rob Cavicchio (rcavicchio@mvps.org) kindly volunteered to test my Turkish HTML Help files on a Windows system set up as a Turkish system. It turns out that when the HTML Help files are compiled on this Turkish system, then the Index and Search window panes display the correct windows-1254 characters, whereas when the same files were compiled on an English Windows system, they displayed some incorrect characters. Fortunately, the CHM file that was compiled on the Turkish system displays correctly on an English system. So if you want a completely correct Turkish HTML Help file, you need to output with encoding windows-1254 and compile it on a Turkish Windows system. Then you can distribute it to any system. Thanks, Rob, for your help on this. Bob Stayton Sagehill Enterprises DocBook Consulting bobs@sagehill.net ----- Original Message ----- From: "Bob Stayton" <bobs@sagehill.net> To: "DocBook Apps" <docbook-apps@lists.oasis-open.org> Sent: Monday, September 24, 2007 3:54 PM Subject: [docbook-apps] 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 > output: > > <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 > bobs@sagehill.net > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]