-bytes into
two-bytes starting from 0x, then process them as 2 two-byte inside,
when displaying it, fontenc will look up gb18030.2000-1 to display the
font. There is no conflict whatsoever, just like i said, totally depends
on how to process them inside encoding part.
Yu Shao
Jungshik Shin
Jacky, Lau wrote:
Hi,
Just to clarify this a bit more, the C++ version of ttmkfdir
included in Red Hat Linux is not a part of XFree86 (thank
goodness), but is included in our XFree86 packages as it made
more sense to include it there than in the freetype package as we
have in the past.
Hi Keith,
It seems a typo and I think using FcCodePageSet is always safer?
Shao
diff -uNr fcfreetype.c.orig fcfreetype.c
--- fcfreetype.c.origSun Jul 7 22:25:37 2002
+++ fcfreetype.cSun Jul 7 22:27:49 2002
@@ -365,7 +365,7 @@
if (matchCodePage[i])
{
if
glyphs are missing.
--
Yu Shao
Red Hat Asia-Pacific
+61 7 3872 4835
Legal: http://apac.redhat.com/disclaimer
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
Keith Packard wrote:
Around 14 o'clock on Jun 29, Yao Zhang wrote:
Sure, I will install as many Chinese fonts as possible and get the
fonts.cache for you. But before that, I will show you serveral lines in my
fonts.cache:
I'm afraid the mailers corrupted the rather long lines in those files,
/mailman/listinfo/fonts
--
Yu Shao
Red Hat Asia-Pacific
+61 7 3872 4835
Legal: http://apac.redhat.com/disclaimer
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
