Summary: | README.fonts needs update for fontconfig multi-file configurations | ||
---|---|---|---|
Product: | xorg | Reporter: | Alan Coopersmith <alan.coopersmith> |
Component: | Documentation | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED MOVED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | minor | ||
Priority: | medium | CC: | jch, jesserayadkins |
Version: | 6.8.99.904 (6.9 RC4) | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | 2011BRB_Reviewed | ||
i915 platform: | i915 features: |
Description
Alan Coopersmith
2005-12-19 14:20:10 UTC
Moving to 7.1 doc tracker. Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. Haven't blocked a release on this yet, so clearing the status. I can't find this file anywhere in xorg-docs, xserver, or...anywhere. I'm assuming that the file is gone, and thus the issue fixed. If I'm wrong, can someone point me to where this is so I can try to fix this? The source file (as of last night when I renamed it) is: http://cgit.freedesktop.org/xorg/doc/xorg-docs/tree/general/fonts/fonts.xml The formatted output generated for X11R7.5 last year is at: http://www.x.org/releases/X11R7.5/doc/fonts/fonts.html How about : Fontconfig's behaviour is controlled by a system-wide configuration directory, and by a user specific file. The system-wide configuration directory is located at `/etc/fonts/conf.d'. Fontconfig will scan all files inside of this directory that start with a number (0-9). The files are parsed in descending order (so 0.conf would be parsed before 1.conf, which is before 2.conf, and so on). The user-specific file named `.fonts.conf' is in the user's home directory (but can be overridden by the `FONTCONFIG_FILE' environment variable). (In reply to comment #6) > How about : > > Fontconfig's behaviour is controlled by a system-wide configuration directory, > and by a user specific file. The system-wide configuration directory is located > at `/etc/fonts/conf.d'. Fontconfig will scan all files inside of this directory > that start with a number (0-9). The files are parsed in descending order (so > 0.conf would be parsed before 1.conf, which is before 2.conf, and so on). The > user-specific file named `.fonts.conf' is in the user's home directory (but can > be overridden by the `FONTCONFIG_FILE' environment variable). Sounds pretty good - but isn't /etc/fonts/fonts.conf also still used in addition to the conf.d files? Also, 0, 1, 2,... sounds like ascending order, not descending order, to me. (In reply to comment #7) > (In reply to comment #6) > > How about : > > > > Fontconfig's behaviour is controlled by a system-wide configuration directory, > > and by a user specific file. The system-wide configuration directory is located > > at `/etc/fonts/conf.d'. Fontconfig will scan all files inside of this directory > > that start with a number (0-9). The files are parsed in descending order (so > > 0.conf would be parsed before 1.conf, which is before 2.conf, and so on). The > > user-specific file named `.fonts.conf' is in the user's home directory (but can > > be overridden by the `FONTCONFIG_FILE' environment variable). > > Sounds pretty good - but isn't /etc/fonts/fonts.conf also still used in > addition > to the conf.d files? Also, 0, 1, 2,... sounds like ascending order, not > descending order, to me. I get those mixed up sometimes. Ascending it is then. As for being used in addition to conf.d files, I assume so. So let's try... Fontconfig's behaviour is controlled by a system-wide configuration directory, and by two files. The system-wide configuration directory is located at `/etc/fonts/conf.d'. Fontconfig will scan all files inside of this directory that start with a number (0-9). The files are parsed in descending order (so 0.conf would be parsed before 1.conf, which is before 2.conf, and so on). The first file is a system-wide file named `/etc/fonts/fonts.conf'. The second is a user-specific file named `.fonts.conf' is in the user's home directory (but can be overridden by the `FONTCONFIG_FILE' environment variable). It seems like this has a fix. Was it never pushed or the bug never closed? -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/doc/xorg-docs/issues/1. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.