Osamu Aoki <os...@debian.org> wrote:

> Package: dblatex
> Version: 0.3.1-2
> Severity: normal
> X-Debbugs-CC: "W. Martin Borgert" <deba...@debian.org>
>
> While I was trying to build Japanese PDF for debian-reference using
> "dblatex -b xetex ...", I faced build problem.   As I investigated its
> problem with simpler shorter texts to pin-point the source of the
> breakage, I found few irregularities.

Hi Osamu,

thanks for your report, however due to the multitude of the included
topics I have some problems understanding what your problem(s) actually
is/are.  This is what I have understood respectively tested:

I agree that it is a problem if a failed transformation doesn't get
signaled by an exit code ≠ 0, especially when dblatex is embedded into
another program that relies on its exit code.  I will further
investigate this.

However for me your two examples manual-ja-(good|bad).dbk get
transformed successfully with the XeTeX backend, for native as well as
for db2latex style.  In order to get a setup as simple as possible, I
have stripped down your XSL user file to [1] and called dblatex on the
command line:

$ dblatex --backend=xetex --xsl-user=xetex_param.xsl --style=db2latex 
manual-ja-bad.dbk

When replacing 'lang="en"' by 'lang="ja"' (seems logical for a japanese
document), a potential issue arises with the author name:

"青木 修 [FAMILY Given]" looks somewhat peculiar, the corresponding
documentation from the dblatex file common.xsl is:

<!-- The family-given style applies a convention for identifying given -->
<!-- and family names in locales where it may be ambiguous -->

The family-given style is explicitly set in dblatex file ja.xml, thus I
assume it is appropriate, although it could be an enhancement if the
string "FAMILY Given" would be translated.

Thus to me it looks like dblatex with the XeTeX backend is able to
handle japanese documents properly.  From where do the problems you
experienced arise?

Should I have neglected other topics mentioned in your report that are
important to you, please tell.  At the moment from my perspective it
boils down to the misleading exit code.

[1] 

Attachment: xetex_param.xsl
Description: XSL user file

Regards, Andreas
-- 
Andreas Hoenen <andr...@hoenen-terstappen.de>
GPG: 1024D/B888D2CE
     A4A6 E8B5 593A E89B 496B
     82F0 728D 8B7E B888 D2CE

Attachment: pgpjB4rTXTWER.pgp
Description: PGP signature

Reply via email to