Drop Bitstream Vera fonts from 60-latin.conf
Bitstream Vera fonts seems broken so dropped them there. Fixes fontconfig/fontconfig#26
-
mentioned in issue #241
-
mentioned in issue #268 (closed)
-
Does Bitstream Vera need to be dropped from 45-latin.conf too?
-
Author Owner
No, this the kind of configuration is used to decide what the generic family the targeted family name should be fall back. this is helpful if they don't have their fonts installed but it was specified by applications. e.g. fontconfig will find out a fallback font like "Bitstream Vera Serif" -> "serif" -> "something else serif fonts installed".
-
OK, should the order be changed if it plays a role? Dejavu before Bitstream Vera. The idea is to always prefer Dejavu to Bitstream Vera if both are installed.
-
Author Owner
For what? let me rephrase. this config is to let fontconfig know those "Bitstream Vera" fonts are supposed to be fallback to the generic family, such as "sans-serif", "serif", and "monospace". Without this config, when you ask "fc-match :family=Bitstream Vera Serif" for example, they will return any sans-serif font because of 49-sansserif.conf even though we expect it will be fallback to any serif fonts.
The order of such config isn't a big deal.
-
Thanks for the explanation. What I meant is if both Bitstream Vera and Dejavu are installed on the system, applications and the desktop environment should always present their text using the Dejavu family when they request the system for the default sans-serif, serif, or monospace font. So Dejavu should always take precedence over Bitstream Vera.
The overall picture is to force Bitstream Vera out of the picture, as it is very obsolete, looks worse than Dejavu and sometimes, as a negative side effect, it takes over as a default font when installed.