Anthony, and
all gb18030 support interested,
Thanks for your comments.
I seems that support of gb18030 support in glibc level is quite solid, of
course I see many debates. I personally think that our glibc should handle
all code points regardless that they are assigned or not as long as that are
legal. This I believe is worth to continue to discuss.
In X; however, I saw many gb18030 related discussions; however, I did not
see any solid conclusion or finished implementation just by reading mail
threads in xfree86.
My questions as follows still remains unresolved.
DISPLAY of gb18030: For gb18030 two- or/and four-byte characters: (Xlib 4.1,
Glibc 2.2.4)
I can dispplay only after I convert them into utf-8 using iconv and
using unifont.
I tried various settings of XLC-LOCALE along with gb18030 fonts, but all
failed.
Q: How can a gb8030 characters be displayed without conversion with
gb18030 fonts.
LOCALE SETTING for GB18030:
Q: Would modification of XLC_LOCLAE and/or fonts' encoding file be
enough OR
are there more to do ?
Q: Are there an official files for XLC_LCOALE, etc. that XFree86.org
recommend
for gb18030 support ?
Chulkee,
----- Original Message -----
From: "Anthony Fok" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 26, 2002 7:02 AM
Subject: Re: [I18n]XFree86 4.1 gb188030 support
> Hello Chulkee,
>
> The questions you asked about GB18030 are probably all addressed
> already, mainly by James Su and by other developers worldwide. You'll
> probably need to search on various mailing lists and web sites to find
> all the details and information.
>
> On Mon, Mar 25, 2002 at 10:45:12AM -0700, Chulkee Sung wrote:
> > GLIBC:
> > Each time when I use iconv to convert to UTF-8, "invalid gb18030
sequence
> > error", is reported, but when I checked my gb18030 four-byte data, they
> > are all in VALID code points, but I wouldn't know if they are all
> > assigned.
>
> See the discussion at:
>
> http://sources.redhat.com/ml/libc-alpha/2002-01/
>
> Scroll down to "January 15, 2002" and read the thread starting with
> this message:
>
> "New GB18030 gconv module contributed by ThizLinux Laboratory"
>
> At the time, Ulrich and Yu Shao were not willing to put any
> legal-but-unassigned codepoints in gb18030.c, and intentionally put
> NULL in there, hence the "invalid gb18030 sequence" error. Other
> developers and I weren't able to convince them. If you can convince
> Ulrich and Yu Shao otherwise, please do.
>
> Nevertheless, follow the discussion, and you'll find a link to a
> gb18030.c (GB18030<->Unicode gconv module) that is actually complete.
> Make sure you grab the one dated 2002-02-21, which is a few percent
> faster than the 2002-01-15 versions.
>
> Cheers,
>
> Anthony
>
> --
> Anthony Fok Tung-Ling
> ThizLinux Laboratory <[EMAIL PROTECTED]> http://www.thizlinux.com/
> Debian Chinese Project <[EMAIL PROTECTED]>
http://www.debian.org/intl/zh/
> Come visit Our Lady of Victory Camp! http://www.olvc.ab.ca/
> _______________________________________________
> I18n mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/i18n
>
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
