Around 15 o'clock on Jul 8, Roger So wrote:
A guy from the IT department of the HK Government was in the discussion,
and he stated that the official plan is to provide support for the PUA
entries as an interim measure, until the whole system is ready to
migrate to use non-BMP entries:
...
On Mon, 8 Jul 2002, Edward Lee wrote:
There are `two' Traditional Chinese fonts here. In zh-tw the
radical/stroke of some glyphs are differrent with the TC glyphs
in GB18030 fonts.
Could you give Unicode code points of a few of those characters?
Have you checked them out at your own
On Mon, Jul 08, 2002, Jungshik Shin wrote:
On Mon, 8 Jul 2002, Edward Lee wrote:
There are `two' Traditional Chinese fonts here. In zh-tw the
radical/stroke of some glyphs are differrent with the TC glyphs
in GB18030 fonts.
Could you give Unicode code points of a few of those
On Sun, 7 Jul 2002, Keith Packard wrote:
http://www.info.gov.hk/digital21/eng/hkscs/download.html
Thanks. I notice that the newest part of this table references quite a
few symbols beyond the BMP; would you suggest that I use the older
entries? Or should I use the non-BMP entries and
On Mon, 2002-07-08 at 16:30, Keith Packard wrote:
Let me rephrase the question in the context of this discussion -- in
attempting to identify which languages a given font is suitable for, I
believe I shouldn't expect fonts designed for HKSCS to support the non-BMP
encodings, and so
On Mon, 2002-07-08 at 19:18, Edward Lee wrote:
The examples are U+89D2(Big5 0xa8a4), U+904E(Big5 0xb94c),
U+9AA8(Big5 0xb0a9), U+5433(Big5 0xa764),
...
Thanks; I wasn't aware of the difference. (Our font supplier didn't
supply us with a true GB18030 font
I forgot to post this announcement to here ;-O).
One of the goals is to replace the Xlib side Local IM and Compose file
which is so limited in functionality and flexibility(such as all
Cpmpose rule is static)
---
Subject:
Keith Packard [EMAIL PROTECTED] writes:
Much as I hate the C locale model, I'm wondering if I shouldn't use the
current locale as a language hint where applications don't provide
explicit language information when selecting fonts. This would make
the generic aliases (like sans-serif)
Owen Taylor wrote:
+locale = (FcChar8 *)setlocale (LC_CTYPE, NULL);
+result = malloc (strlen (locale + 1));
Should be strlen(locale) + 1.
Erik
___
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
Keith Packard [EMAIL PROTECTED] writes:
Around 14 o'clock on Jul 8, Owen Taylor wrote:
+locale = (FcChar8 *)setlocale (LC_CTYPE, NULL);
Don't you mean LC_MESSAGES? If so, I think we should be able to use this
return value almost raw; stripping out the language and territory codes
On Mon, 8 Jul 2002, Keith Packard wrote:
Around 14 o'clock on Jul 8, Owen Taylor wrote:
+locale = (FcChar8 *)setlocale (LC_CTYPE, NULL);
Don't you mean LC_MESSAGES?
I believe it should be LC_CTYPE. Some people like me
have the following because English menu and (error) messages
On Mon, 8 Jul 2002, Jungshik Shin wrote:
On Mon, 8 Jul 2002, Keith Packard wrote:
Around 14 o'clock on Jul 8, Owen Taylor wrote:
+locale = (FcChar8 *)setlocale (LC_CTYPE, NULL);
Don't you mean LC_MESSAGES?
I believe it should be LC_CTYPE. Some people like me
...
Around 16 o'clock on Jul 8, Jungshik Shin wrote:
Don't you mean LC_MESSAGES?
I believe it should be LC_CTYPE. Some people like me
Check. LC_CTYPE it is. Sometimes life in en_US is so insular...
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
13 matches
Mail list logo
