[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Fwd: Re: [Devel] Fw: Freetype, fontconfig,Xft, Mozilla and Non-BMP char
[Fwd: Re: [Devel] Fw: Freetype, fontconfig,Xft, Mozilla and Non-BMP char. support]
Wed, 04 Dec 2002 23:55:42 +0100
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530
Another message from Jungshik Shin, which I forward for the
enlightment of all the readers.
-------- Missatge original --------
Assumpte: Re: [Devel] Fw: Freetype, fontconfig,Xft, Mozilla and Non-BMP
Data: Wed, 4 Dec 2002 15:09:59 -0500 (EST)
De: Jungshik Shin <address@hidden>
A: Antoine Leca <address@hidden>
On Tue, 3 Dec 2002, Antoine Leca wrote:
Thank you for the quick fix.
> Antoine Leca wrote on 2002-12-02 00:10 +0100:
> > > On Thu, 28 Nov 2002, Jungshik Shin wrote:
> > The initialisation code
> > (in open_face, around line 770) does the right thing, and scans *all* the
> > available charmaps before returning.
> Now, this is utterly wrong! In fact, the code in open_face() is as
> buggy as the one in FT_Select_CharMap(), even if they are slighty
> different (and since they do more or less the same thing, something
> is not perfect here.)
Yeah, that's what I thought I had found in the source
when I wrote my original report. Then you wrote that it's fine and
I beleived you thinking that I had yet another instance of memory
> On a minor way, ftview need to be enhanced: presently the character set
> is limited to U+FFFF. I will enhance it later this week.
> I have enhanced ftstring: now, the "message" could be encoded in UTF-8.
> This means that one can look at the Gothic characters of Code2001,
> without requiring a full download of Mozilla (very nice when like me,
Wow, that will be nice.
> OK, I have updated the CVS, please check. The (relevant) changes are all
> in src/base/ftobjs.c, if you mind. Please note that I did not check if
> it works with Linux (nor even gcc), only a short test on Win32.
I've just checked it under Linux with my test program and CODE2001
font and it worked fine. The default Cmap selected was 3.10 and
FT_Select_Charmap with FT_ENCODING_UNICODE correctly selected 3.10 as well.
BTW, I heard that MacOS X has a Japanese font (Hi??) with hundreds of
Plane 2 characters. I guess this font has two UCS-4 Cmaps (Apple's and
MS') and your concern is justified :-) I was also told that Chinese
version of MS Office XP includes Simsun (founder extended?) font with
thousands of characters in Plane 2.
> And many thanks to Jungshik Shin to draw our attention on this point.
You're welcome and thank you.