Right now, we install a pile of configuration examples to /etc/fonts/conf.d. I don''t think that''s a good plan. There are two obvious alternatives -- the first is to just stick them in /usr/share/doc/fontconfig/examples and let people pull the ones they want into /etc/fonts/conf.d. That would allow us to ship a lot more examples and catagorize them as appropriate. It would, however, make it harder for us to maintain those configuration files and update them in future releases. The second alternative is to stick them in /etc/fonts/conf.available and then let people symlink the desired ones into conf.d. Both of these approaches would let us prescribe suitable numeric prefixes for the filenames, something the current system lacks. And, both would let us catagorize the examples by function. Perhaps a mix of the two approaches where the ''officially supported'' snippets live in /etc/fonts and the ''examples'' snippets live in /usr/share/doc/fontconfig/exmaples? -- keith.packard@intel.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.freedesktop.org/archives/fontconfig/attachments/20060902/b567fe32/attachment.pgp
Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.freedesktop.org/archives/fontconfig/attachments/20060906/40f9c274/attachment-0001.pgp
On Wed, 2006-09-06 at 00:47 -0400, Behdad Esfahbod wrote:> ++. In particular, the current practice of only including files > starting with a digit should be removed.No. This provides an ordering to the configuration file loading which is often important. A separate discussion about how to fix this load order dependency on the configuration might be interesting though.> Also, lets clean up the configs as much as possible. Breaking down > fonts.conf into separate files is good. We also patch the default > config to add lots of aliases. Attaching. Ideally we want to break > this down to something per-language or -script, like for example the > fonts-persian.conf file is currently doing. Separating all Indic stuff > for example.Alising generics to specifics should be family dependent; to a great extent, we should split these across font package boundaries instead of languages though. For fonts which ''commonly'' ship on free software platforms, I''m comforatble putting those into the default configuration mechanism. We should also include other widely used, even if non-free, fonts (like the MS web fonts, and the Adobe standard fonts).> We also have a 40-blacklist-fonts for blacklisting some fonts that > FreeType cannot handle correctly, and 50-no-hint-fonts for disabling > hinting and embedded bitmaps on our Indic and a couple other fonts.Those would be great to have.> Another config file I have in Fedora is for making DejaVu Sans LGC an > alias for DejaVu Sans, and turning off hinting for DejaVu in small sizes > (like we do for Vera). These can go upstream too I guess. Attaching > that too.Yes, these are all useful and should be in the default configuration.> Finally, I like to suggest we start providing two more generic families > that are in CSS but currently not fontconfig: cursive and fantasy. For > cursive, URW Chancery L can be aliased. I''m sure there is a font to map > fantasy to too. This is needed for proper support of these in Firefox.I don''t know why I didn''t do this a long time ago; all of the CSS generics should be generic in fontconfig as well. But, at this point, I''m interested in seeing us get to a more comprehensive upstream configuration that will reduce the differences in downstream packaging, so please focus on patches that are obviously correct (like the above list) and getting those merged into the distribution. -- keith.packard@intel.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.freedesktop.org/archives/fontconfig/attachments/20060906/d69971d8/attachment.pgp
Le Mer 6 septembre 2006 06:47, Behdad Esfahbod a ?crit :> On Sat, 2006-09-02 at 09:02 -0700, Keith Packard wrote: >> Right now, we install a pile of configuration examples >> to /etc/fonts/conf.d. I don''t think that''s a good plan. >> >> There are two obvious alternatives -- the first is to just stick them >> in /usr/share/doc/fontconfig/examples and let people pull the ones they >> want into /etc/fonts/conf.d. That would allow us to ship a lot more >> examples and catagorize them as appropriate. It would, however, make it >> harder for us to maintain those configuration files and update them in >> future releases. >> >> The second alternative is to stick them in /etc/fonts/conf.available and >> then let people symlink the desired ones into conf.d. >> >> Both of these approaches would let us prescribe suitable numeric >> prefixes for the filenames, something the current system lacks. And, >> both would let us catagorize the examples by function. >> >> Perhaps a mix of the two approaches where the ''officially supported'' >> snippets live in /etc/fonts and the ''examples'' snippets live >> in /usr/share/doc/fontconfig/exmaples?Just stuff everything in /usr/share/doc/fontconfig-foo/, using subdirs to distinguidh between categories> ++. In particular, the current practice of only including files > starting with a digit should be removed.Agreed, it is very confusing to users. Current Red Hat/Fedora practice seems to do the test on the .conf extension, as rpm will rename old/new files as oldname.rpm{new,save}> > Also, lets clean up the configs as much as possible. Breaking down > fonts.conf into separate files is good. We also patch the default > config to add lots of aliases. Attaching. Ideally we want to break > this down to something per-language or -script, like for example the > fonts-persian.conf file is currently doing. Separating all Indic stuff > for example. > > We also have a 40-blacklist-fonts for blacklisting some fonts that > FreeType cannot handle correctly, and 50-no-hint-fonts for disabling > hinting and embedded bitmaps on our Indic and a couple other fonts. > > Another config file I have in Fedora is for making DejaVu Sans LGC an > alias for DejaVu Sans, and turning off hinting for DejaVu in small sizes > (like we do for Vera). These can go upstream too I guess. Attaching > that too.And here are the current conf files for the Fedora Extras DejaVu full package (main families and experiental ones) http://cvs.fedora.redhat.com/viewcvs/devel/dejavu-fonts/dejavu-fonts-fontconfig.conf?root=extras http://cvs.fedora.redhat.com/viewcvs/devel/dejavu-fonts/dejavu-fonts-experimental-fontconfig.conf?root=extras Regards, -- Nicolas Mailhot
Le Mer 6 septembre 2006 21:00, Keith Packard a ?crit :> On Wed, 2006-09-06 at 00:47 -0400, Behdad Esfahbod wrote: > >> ++. In particular, the current practice of only including files >> starting with a digit should be removed. > > No. This provides an ordering to the configuration file loading which is > often important. A separate discussion about how to fix this load order > dependency on the configuration might be interesting though.Not filtering on number prefix does not mean people won''t use number prefixes. If they don''t want to bother selecting the right priority number, forcing them to pick up a random one won''t help at all. Regards, -- Nicolas Mailhot
On Thu, 2006-09-07 at 12:53 +0200, Nicolas Mailhot wrote:> Not filtering on number prefix does not mean people won''t use number > prefixes. > If they don''t want to bother selecting the right priority number, forcing > them to pick up a random one won''t help at all.Which is why I wanted to come up with a policy for the numbering. Something simple like: 10: font directories 20: selectfont (white/black listing) 30: system rendering defaults 50: 50-user.conf 60: local default configuration 70: font aliases (75-dejavu.conf, 75-vera.conf, etc) 99: local fixups (overriding user configuration if necessary) I think a bit of documentation (in conf.d/README) will make this workable. -- keith.packard@intel.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.freedesktop.org/archives/fontconfig/attachments/20060907/f8e93ca9/attachment.pgp
On Thu, 2006-09-07 at 09:12 -0700, Keith Packard wrote:> On Thu, 2006-09-07 at 12:53 +0200, Nicolas Mailhot wrote: > > > Not filtering on number prefix does not mean people won''t use number > > prefixes. > > If they don''t want to bother selecting the right priority number, forcing > > them to pick up a random one won''t help at all. > > Which is why I wanted to come up with a policy for the numbering. > Something simple like: > > 10: font directories > 20: selectfont (white/black listing) > 30: system rendering defaults > 50: 50-user.conf > 60: local default configuration > 70: font aliases (75-dejavu.conf, 75-vera.conf, etc) > 99: local fixups (overriding user configuration if necessary)Sounds good. But make sure you allow more than two digits there, just in case. Before I forget, the current autohint.conf, sub-pixel.conf, etc in conf.d are completely broken as they override any configuration. They should be checking whether those Also see this relevant bug in Red Hat bugzilla: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179815> I think a bit of documentation (in conf.d/README) will make this > workable.Yeah yeah. A README right there does the job. -- behdad http://behdad.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.freedesktop.org/archives/fontconfig/attachments/20060907/7caa7187/attachment.pgp