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 ?
2007/4/11, Lübbe Onken <l.onken@rac.de>:
> Hi Dongsheng Song,
>
> You wrote:
> > These files looks good!
> >
> > http://l10n-zh.googlecode.com/files/TortoiseSVN_zh_CN_r9140.chm
> > http://l10n-zh.googlecode.com/files/TortoiseMerge_zh_CN_r9140.chm
>
> Yes, they really look good :)
>
> Now please tell me the secret how you built them. If I update my sources and
> build the chinese docs on my PC, the index of the chm help still looks
> broken. It now looks different than before you changed the output encoding
> from utf-8 to GB18030, but it's still broken.
>
> The html files created in doc\output\TortoiseMerge_zh_CN look good to me,
> but they have utf-8 encoding. Where's the trick? Do you have a different
> version of hhc installed than I have?
>
> Cheers
> -Lübbe
>
Received on Tue Oct 30 05:27:26 2007