Re: State of xfstt

[ISHIKAWA Mutsumi <ishikawa@linux.or.jp>]

>>>>> In <[🔎] 20020125115804.GA4439@firewall.iesi.ba.cnr.it> 
>>>>>	"Francesco P. Lovergine" <frankie@debian.org> wrote:
>> On Thu, Jan 24, 2002 at 11:20:39AM -0600, Colin Watson wrote:
>> > On Thu, Jan 24, 2002 at 08:36:49AM -0800, elf@florence.buici.com wrote:
>> > > While I haven't verified it, I read that there is no need for xfstt
>> > > since the functionality has been added to XFree86.
>> > 
>> > We will still be including XFree86 v3 in woody, though.

>> Consider xfs-xtt, equivalently (I think). 

 We have 3 font servers.

 1) xfs (normal one)
 2) xfs-xtt
 3) xfstt

 All of these can provide TrueType font rendering.
 Yes, xfs 4.0 or above can handle TrueType font.

 XFree86 have 2 different TrueType font rendering engines, FreeType
engine and X-TT engine. xfs and xfs-xtt use same code base, but xfs
uses FreeType engine to render TrueType font, xfs-xtt uses X-TT
engine.

 Please refer to /usr/share/doc/xfree86-common/README.fonts.gz about
the difference between FreeType engine and X-TT engine.

 Both xfs and xfs-xtt use same rendering engine for  X bitmap, Type1,
Speedo and so on. They can handle X bitmap, Type1, CID, Speedo and
TrueType. Both of them support CJKV.

 xfstt is written from scratch (useing C++), and only can handle
TrueType font. It can not ahdnle X bitmap, Type1 and so on.
 And it does not support CJKV.

-- 
ISHIKAWA Mutsumi
 <ishikawa@linux.or.jp>, <ishikawa@debian.org>, <ishikawa@netvillage.co.jp>