On Fri, 07 Jan 2011 18:56:37 -0500 Jerry Casiano <jerrycasiano@xxxxxxxxx> wrote: >On Fri, 2011-01-07 at 14:45 +0900, suzuki toshiya wrote: > >> During the registration of them to tricky font lists, >> I found that these fonts lack ASCII family name. Their >> name tables are for MacJapanese (ShiftJIS) and Microsoft >> Unicode. In both names, the family names are in Japanese, >> not English. >> In such case, current FreeType2 replaces non-ASCII >> character in non-ASCII family name by "?". Thus, >> FT_Face->family_name is set by broken string. There >> is a possibility that the different fonts will have >> same broken family name. However, the PostScript name of >> the fonts I found are still in ASCII. > >This happens with a lot of fonts. I think the issue is that you're using >FT_Face->family_name by default rather than as a last resort. At least >that was my mistake. ;-) > >I'm not sure what you're trying to do or what your requirements are but >wouldn't it be better to get the info you need directly from FontConfig? >or at least as much of it as possible. Ah, I'm sorry for poor explanation. What I'm trying to do is: a patch for FreeType2 library to change the default FT_Face->family_name when a TrueType/OpenType font without ASCII family name is given. My concern was that such change may have any bad impact to fontconfig. But, as Behdad and you told, it seems that the names handled by fontconfig are copied from "name" table and not a copy of FT_Face->family_name. So, I understand as there is no impact at all. It is good news! I have to check other applications which write FT_Face->family_name as a persistent font identifier into their output files. Regards, mpsuzuki _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
