Yves Dorfsman <[EMAIL PROTECTED]> writes:
> On Wed, 6 Sep 2000, Larry W. Virden wrote:
>
> > on what appear at first blush to be irrelevant leads (the Microsoft fonts -
> > how would one use those on X)
>
> xfstt
I tried to use xfstt with Asian fonts, but had no success. As a
default, xfstt only handles the first 255 characters of any font and
discards the rest. It works fine like that for English, but of course
not for languages which use much more characters.
xfstt has a compile time variable UNSTRAPLIMIT, which can be set to
65535U (default is 10500U) to try to get support for CJK symbols. I
tried that and started my X-server with the option '-deferglyphs 16'
as written in the xfstt FAQ.
Then xfstt started to use 100% CPU time as soon as I tried to display
a True Type font, never stopped doing that and never delivered a font
to display ("xfd -fn some-font" just waits and does nothing).
The xfstt FAQ states that many X-servers crash if you increase
UNSTRAPLIMIT, that's the reason why the default is not 65535U. My
X-server didn't crash, but it didn't work either.
I tried this with the Microsoft fonts, the Watanabe fonts and with a
Cyberbit.ttf font. The behaviour was the same with all of them.
It looks like currently xfstt is not useable with CJK fonts.
When I have somewhat more time I'll try to investigate in more detail
what xfstt was doing while burning CPU time.
--
Mike Fabian <[EMAIL PROTECTED]>
