[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Latest TortoiseSVN & TortoiseMerge docs - Simplified Chinese

From: Dongsheng Song <dongsheng.song_at_gmail.com>
Date: 2007-10-31 03:34:37 CET

Please verify on a western European PC by build svnbook:

svn co http://i18n-zh.googlecode.com/svn/trunk/doc/svnbook
cd svnbook
ant chm

* [1] gettext, xmllint,xsltproc
* python 2.5
* jdk 1.4.2
* ant 1.7
* docbook-xsl-ns 1.73.2
* saxon 6.5(pdf only)
* fop 0.20.5(pdf only)
* hhc(chm only)

[1] http://i18n-zh.googlecode.com/files/gettext_0.16.1_xsltproc_1.1.22.tar.bz2

I think this is a xsl or xsltprocessor bug, the output correct only when:
1. input encoding is GB18030
2. htmlhelp set encoding to GB18030

So I use xmllint convert the xml encoding from utf-8 to GB18030.
Otherwise, it build wrong chm index even if on a Chinese PC.

2007/10/30, Lübbe Onken <l.onken@rac.de>:
> Hi Dongsheng Song,
> 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
Received on Wed Oct 31 03:34:48 2007

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.