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: Re: [docbook-apps] htmlhelp.encoding="windows-932" and Saxon


"David Cramer (Tech Pubs)" <dcramer@motive.com> wrote on 08/28/2003 
04:17:17 PM:

> I'm using htmlhelp xsls and saxon to produce Japanese chms. The .hhc
> and .hhk files come out as Unicode files, even though htmlhelp.
> encoding is set to Windows-932. The result is that in the toc and 
> index panes, the Japanese is mangled. If I open the .hhc and .hhk 
> files on a Japanese OS, save as ANSI, and recompile, all is well. 
> Does anyone have any experience with a problem like this?

Try:

  <xsl:param name="htmlhelp.encoding" select="'Shift_JIS'"/>
  <xsl:param name="default.encoding" select="'Shift_JIS'"/>
  <xsl:param name="saxon.character.representation" select="'native'"/>
  <xsl:param name="chunker.output.encoding" select="'Shift_JIS'"/>

in your customization layer. I'm using xsltproc, but I remember trying 
Saxon earlier on. I think it worked with Saxon as well.

Incidentally, for Japanese help, I also have the following set:

  <xsl:param name="l10n.gentext.language" select="'ja'"/>
  <xsl:param name="l10n.gentext.default.language" select="'ja'"/>


-Taro


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