Re: How to use Japanese True Type fonts?

[Mike Fabian <mfabian@example.com>]

"Stephen J. Turnbull" <turnbull@example.com> writes:

> >>>>> "Mike" == Mike Fabian <mfabian@example.com> writes:

[...]

>     >> export jisx0208.1983 if it still does.  What is the
>     >> UNSTRAPLIMIT (compile-time variable) for 4.0?
> 
>     Mike> UNSTRAPLIMIT (compile-time variable of xfstt) is 10500U.
> 
> Oops.  CJK Symbols start at U+3000, ie, 12288U.  Everything else is
> above that....

When I look at some Japanese bitmap font, for example

    xfd -fn "-watanabe-fixed-medium-r-normal--32-300-75-75-c-320-jisx0208.1983-0"

I see some Japanese symbols in the very first page (0x2121 - 0x747e),
for example "仝" therefore I thought xfstt should show me something
like that as well with the default UNSTRAPLIMIT. But it doesn't.

>     Mike> To test this I must first find a ttf Unicode font containing
>     Mike> Japanese ... 
> 
> The watanabe font should do.  AFAIK all ttf fonts are Unicode, it's
> the font server that converts from Unicode CIDs to JIS code, etc.

I see. I increased xfstt's UNSTRAPLIMIT to 65535U, but that didn't
work either. As soon as I try to display a True Type font now, xfstt
starts to use 100% CPU time, never stops doing that and never delivers
a font to display ("xfd -fn some-font" just waits and does
nothing). The X-server doesn't crash though.  I tried this with the
Watanabe fonts and with a Cyberbit.ttf font.  The behaviour is the
same with both fonts.

-- 
Mike Fabian   <mfabian@example.com>