[Fontconfig] Marking glyphs as deliberately blank, per font

Nicolas Mailhot nicolas.mailhot at laposte.net
Fri Nov 27 00:53:02 PST 2009



Le Ven 27 novembre 2009 01:10, Nicolas Mailhot a écrit :

> To keep syntax consistent with A. and have a reliable rule the packager
> understands, it should have been
>
> <alias>
>   <font>
>     <family>[genericname]</family>
>     <lang>[loc]</lang>
>   </font>
>   <prefer>
>     <font>
>       <family>[fontname]</family>
>       <lang>[loc]</lang>
>     </font>
>   </prefer>
> </alias>

Actually, it should have been something like:

 <alias>
   <font>
     <family>[genericname]</family>
     <langrequest>[loc]</langrequest>
     <langcover>[loc]</langcover>
   </font>
   <prefer>
     <font>
       <family>[fontname]</family>
     </font>
   </prefer>
 </alias>

to distinguish between lang as "the language I'm rendering for" and lang as
"the glyphs associated with the foo .orth"

Many many CJK fontconfig configuration bugs occur because lang (as a rendering
context) is confused with lang (as specific glyphs in a font)

-- 
Nicolas Mailhot




More information about the Fontconfig mailing list