Hi,

On Sat, May 06, 2017 at 11:06:09PM +0200, Holger Wansing wrote:
...
> > The reason for the used fonts in installation-guide is probably historical
> > ones, nothing really intended.
...

I also use installation-guide as a good guidance.

> That's why I did changes on the xetex_param.xsl file:
> If build has worked fine with the status I found before, I wouldn't have
> changed anything.

I see.

Somehow, IPA fonts chokes on many characters producing PDF with many
dropped characters for many characters, most notably for +U30FC.  I can
guess this may be due to encoding problem but ... let's leave this
problem for now.

So VL-fonts seems to be better choice.  With your xetex_param.xsl,
this doesn't happen and remaining problems are few awkward characters:

Build stdin.pdf
Character U+2194 (↔) not in font '[lmroman10-regular]:mapping=tex-text;'
Character U+21D4 (⇔) not in font '[lmroman10-regular]:mapping=tex-text;'
Character U+2500 (─) not in font '[lmroman10-regular]:mapping=tex-text;'

As for Chinese, your xetex_param.xsl causes:
Build stdin.pdf
Character U+2194 (↔) not in font '[lmroman10-regular]:mapping=tex-text;'
Character U+21D4 (⇔) not in font '[lmroman10-regular]:mapping=tex-text;'
'debian-reference.zh-cn.pdf' successfully built

Oh, with my old xetex_param.xsl, chinese zh-cn and zh-tw have problem
handling ndash (+U2013) with arphic fonts.  (It's missing in that font)

Above mentioned problem of installation-guide way can be fixed by moving
out following from  <xsl:choose>

        <xsl:text>\setmainfont{FreeSerif}&#10;</xsl:text>
        <xsl:text>\setsansfont{FreeSans}&#10;</xsl:text>
        <xsl:text>\setmonofont{FreeMono}&#10;</xsl:text>

So installation-guide seems better choice as baseline.  My concern is
that GNU Free fonts is not as easy to distinguish O and 0.  I will try
both to check how they come out.

Also, I remember CJ people like SanSerif for their main text of the CJK
character.

As for pt, I think I need to do divide and find to the offending string
in PT PO file.  If I reset PT into no PO string, it creates proper PDF.
This needs a bit more work.

Other problem is "-mark.  It used to look ``...'' but now ''...''.

Regards,

Osamu

Reply via email to