Around 2 o'clock on Jul 14, Pablo Saratxaga wrote:
> Yes, both localized names and ascii-only names are usefull. Maybe the same
> api could be used for both cases, trough a paremeter telling which
> localized language is requested (if "C", then ascii-only names are given).
Ok, I'm adding localized names to fontconfig. To allow applications to
continue working with a single name, I'm actually listing the localized
names in the FC_FAMILY value using a new datatype (FcTypeLangString).
Ask for a string, and you'll get back just the family name, but ask for a
LangString and you'll get both.
A couple of questions:
1) Macintosh names are encoded in weird Macintosh text encodings,
is it OK to ignore the non-Apple Roman names here? I can't see
embedding conversion tables for all of the weird encodings.
2) Should I use the current locale to select a family from those
listed when an application requests a string for FC_FAMILY?
That would mean returning different values depending on the
locale. All of the return values would map to the same
font. The reason for this is so that simple apps continue
to work in a simple fashion. The alternative is to force
apps to use a new API which includes an explicit lang; when
that is NULL, I could use the current locale.
You'll get localized names for family and style; there aren't any other
obviously useful string values in the current set of font name elements.
Keith Packard XFree86 Core Team HP Cambridge Research Lab
_______________________________________________
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
