[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Freetype] Re: [Fonts]New versions of mkfontscale and FreeType 2 backend
From: |
Juliusz Chroboczek |
Subject: |
[Freetype] Re: [Fonts]New versions of mkfontscale and FreeType 2 backend |
Date: |
26 Apr 2002 17:16:45 +0100 |
CC'd to Freetype.
Rui-Xiang Guo <address@hidden>:
RG> - "jisx0212.1190-0", "big5.eten-0", "gb2312.1980-0",
RG> + "jisx0212.1990-0", "big5-0", "gb2312.1980-0",
Okay, in next version. Thanks.
RG> (I tested it with Arphic TTF which be distributed with most Linux
RG> distributions and all *BSD.)
Hmm, there may be problems with this font; I'm told it has bugs.
Maybe the FreeType folks can comment?
RG> It seems the problem of FT_Get_Char_Index() in checkEncoding().
RG> - if(FT_Get_Char_Index(face, c) == 0) {
RG> + if(face && face->charmap) {
RG> + ttcmap =
&((TT_CharMap)face->charmap)->cmap;
RG> + if(ttcmap->get_index)
RG> + /* if(ttcmap->get_index(ttcmap, c) ==
0)
RG> + return 0; */
RG> + return ttcmap->get_index(ttcmap, c);
Very curious. I'll try to understand what's going on.
RG> 3) Besides that, I need to fix the spacing value 'p' to 'c' because the
RG> value 'p' will cause delay in several seconds when start-up rxvt.
Again, that's a font bug; mkfontscale tries to work out which fonts
are proportional. On the other hand, it doesn't yet implement a
heuristic to distinguich monospaced (-m-) from charcell (-c-) fonts.
I guess a suitable heuristic would be to decalare all monospaced fonts
in East-Asian encodings to be charcell.
RG> Would it be merged into next XFree snapshot?
I hope so.
Thanks,
Juliusz