Brian Stell <[EMAIL PROTECTED]> writes:

> For Mozilla I add the "family + language-group" as this seems the
> closest match. The "family (any-language-group)" was added when
> I observed that some X fonts cover larger code sets by 
> "subsetting" a larger font; eg:
> 
>   Helvetica-*-iso8859-1
>   Helvetica-*-iso8859-2
>   Helvetica-*-iso8859-3
>   ...
> 
> This "reassembles" these fonts. This is not perfect for all
> fonts (I still have not found a perfect solution). People have
> found a very interesting way to use this: they make an alias
> that has the fonts they want and the code "reassembles" the
> list for them into a logical font. I have primarily seen this
> in use for Japanese users who want to be able to specify the
> fonts used for JISX0201 and JISX0212.

The old X backend for Pango does exactly the same thing; it
creates "fonts" by default by merging on encoding, and
allows users to configure aliases with more general
patterns - the "sans" alias by default is configured to
be something like:

sans normal normal normal normal \
  "-*-helvetica-medium-r-normal--*-*-*-*-*-*-*-*,\
   -*-gulim-medium-r-normal--*-*-*-*-*-*-ksc5601.1987-0,\
   -*-clearlyu-medium-r-normal--*-*-*-*-*-*-iso10646-1,\
   -*-fixed-medium-r-normal--*-*-*-*-*-*-*-*,\
   -kaist-iyagi-bold-r-normal--*-*-*-*-*-*-johab-1,\
   -*-song ti-medium-r-normal--*-*-*-*-*-*-*-*,\
   -freetype-unitamil-medium-r-normal--*-*-*-*-*-*-iso10646-tam,\
   -*-devanagari-medium-r-normal--*-*-*-*-*-*-iso10646-dev,\
   -*-gujarati-medium-r-normal--*-*-*-*-*-*-iso10646-guj,\
   -*-gurmukhi-medium-r-normal--*-*-*-*-*-*-iso10646-gur,\
   -*-bengali-medium-r-normal--*-*-*-*-*-*-iso10646-bng,\
   -*-kannada-medium-r-normal--*-*-*-*-*-*-iso10646-kan,\
   -*-burmese-medium-r-normal--*-*-*-*-*-*-iso10646-brm,\
   -*-buginese-medium-r-normal--*-*-*-*-*-*-iso10646-bgn,\
   -*-oriya-medium-r-normal--*-*-*-*-*-*-iso10646-ori,\
   -daewoo-mincho-medium-r-normal--*-*-*-*-*-*-ksc5601.1987-0"

<shudder>

It turned out, however, when we got a decent font system,
that this wasn't the right place to put the standard aliases;
merging on encoding isn't needed if fonts can properly export
their encodings.

Instead the font lists for standard aliases went into the
mechanism for CSS2-style font lists.

Regards,
                                        Owen
_______________________________________________
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts

Reply via email to