RE: Latest TortoiseSVN & TortoiseMerge docs - Simplified Chinese

Hi Dongsheng Song,

You wrote:

> I catched the secret. When the DocBook XML encoding is GB18030 and the
> htmlhelp encoding BOTH GB18030, the chm file is OK. Here is the
> sketch:
>
> <target name="chm" description="Create CHM documentation">
> + <if lang="zh_CN">
> + DocBook xml: UTF-8 -> GB18030
> + </if>
> <call target="xsltproc" />
> + <if lang="zh_CN">
> + DocBook xml: GB18030 -> UTF-8
> + </if>
> <exec program="hhc.exe"/>
> </target>
>
> Is it too ugly ?

Hm, I think I understand what you mean, but I'm not sure. How can we solve this in the build process on a western European PC? Is it possible that the docs build correctly on a Chinese PC because the locale is set to zh_CN and this indirectly enforces GB18030 encoding?

The docbook xml files are created by xml2po.py which uses utf-8 encoded translations from poEdit.

In htmlhelp.xsl you set:
<xsl:param name="chunker.output.encoding" select="'GB18030'"/>
<xsl:param name="htmlhelp.encoding" select="'GB18030'"/>
So this converts the utf-8 input to GB18030 output. But if all the files are converted correctly and go into hhc.exe, why is there still a wrong index?

Maybe there is another parameter which sets the output encoding for the index?

Cheers
- Lübbe

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org