On Fri, 2006-07-14 at 09:58 +0900, [EMAIL PROTECTED] wrote: > Hi > > On Thu, 13 Jul 2006 15:52:23 -0700 > "Tom Fukushima" <[EMAIL PROTECTED]> wrote: > >What does the last sentence mean? > > Since FreeType2 provides "unified" API for various font formats, > the fundamental API is designed for ASCII font name: because > some font formats cannot include localized font names. > If you want to prioritize localized font names, > you may restrict your application to TrueType variants, > so you cannot use format-independent API of FreeType2. > You should use format-dependent API of FreeType2.
fontconfig also extracts the non-ASCII names and tags them by language, including identifying several common mis-encoding errors: $ fc-list :lang=ja family familylang DFSongStd,華康標準宋體:familylang=en,zh-tw Kochi Mincho,東風明朝:familylang=xx,ja ＭＳ ゴシック,MS Gothic:familylang=xx,en Bitstream Cyberbit:familylang=en Arial Unicode MS:familylang=en As you can see, sometimes it's not able to identify the language of the font name, but much of the time it can, so you can actually display localized family and style names. Many latin fonts provide a huge list of style names for each face. -- [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Freetype mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/freetype
