Difference between revisions of "Talk:Font configuration"

From ArchWiki
Jump to: navigation, search
(Softlinks: Note about "cd")
(Remove closed discussions.)
(22 intermediate revisions by 8 users not shown)
Line 1: Line 1:
== Troubleshooting section revision ==
+
== freetype2 config changes ==
  
I'm attempting to rewrite this to a more formal English while also doing some reorganization. This will take some time. I know I'll make some mistakes and any corrections, rewordings, and edits are appreciated.
+
freetype2 no longer uses local.conf (same with infinality) and has switched to /etc/fonts/conf.d/* config files symlinked to /etc/fonts/conf.avail/*. I'm happy to update this page but don't want to step on the plans of someone more informed than I. If I don't hear back in a week or so I'll go ahead and add some minor changes to reflect this new configuration setup.
:--[[User:Thisoldman|Thisoldman]] 08:47, 25 November 2009 (EST)
+
:Freetype2 has had conf.avail and conf.d for a while. One of the files in conf.d is "51-local.conf" and that lets you use /etc/fonts/local.conf for your own local settings. The freetype2-infinality package just now installs the default non-customized Infinality config to conf.avail so people know it exists without reading the documentation. [[User:Thestinger|thestinger]] 13:18, 30 November 2011 (EST)
  
: The whole Troubleshooting section in a FAQ format didn't really fit in, pretty informal too.  I'm also thinking that the 'Missing Characters' section can be removed (mostly this has to do with special language [not in unicode best way to put it?] fonts.
+
== Contradictory recommendations? ==
: Any thoughts about the GTK and QT section?  Not sure if these are being used anymore.
+
: Nice work thus far.
+
: --[[User:Gen2ly|Gen2ly]] 18:18, 25 November 2009 (EST)
+
  
:: Installing missing fonts are the solution for the Mozilla Apps problems too. I'll leave both sections in for now. They're frequent problems judging from the forums. Perhaps there will be future article: ''Text, Fonts and Unicode''
+
I'm not familiar with fontconfig - I've configured it rarely and a long time ago for a different OS. So I'm not sure if something is just not clear to me but as I read the article, it is giving me contradictory instructions:
:: I am removing the ''GTK and QT'' section. The change can be reverted, if we're mistaken.
+
* early on, it suggests enabling both the autohinter and subpixel rendering to improve appearance after installing msfonts
::--[[User:Thisoldman|Thisoldman]] 22:26, 25 November 2009 (EST)
+
* later on, it says that the autohinter should not be used with subpixel rendering
 +
I realise that the methods used to enable these are different in the two cases (one sets up symlinks in conf.d; one adds sections to local.conf) but if this explains the apparent inconsistency, it would be really good to explain why there's no conflict in this case. --[[User:Margali|Margali]] 19:07, 4 March 2012 (EST)
  
Removed The Mozilla apps section. Added the default MS-Windows font settings to the [[Firefox]] article. Noted Trebuchet Bold is missing from ttf-ms-fonts package in [[Fonts]].
+
== Autogenerating missing shapes and weights ==
:--[[User:Thisoldman|Thisoldman]] 15:05, 26 November 2009 (EST)
+
  
== Comments ==
+
Since the article is about improving the appearance of fonts, I would suggest qualifying the section which explains how to have fontconfig generate italics and bold/bolder fonts on the fly. I doubt very much that it is faking italics. I assume it fakes slanted versions (which are not the same as italics). Moreover, it is unlikely that the results of autogeneration will be especially pleasing. Font designers would abhor such things and not, I think, because they need the work! Faked versions can be acceptable but they will not look as good - the spacing will not be optimal, the shapes of the glyphs and the metrics will not be quite right as good fonts vary these things appropriately for different weights, shapes and sizes. --[[User:Margali|Margali]] 19:13, 4 March 2012 (EST)
  
Saw your almost-complete re-write here and on the [[Fonts]] page.  Very nice work Manolo.
+
== Configuration confusion ==
: --[[User:Gen2ly|Gen2ly]] 00:39, 12 November 2009 (EST)
+
  
:Thanks. In all fairness, I didn't contribute any content. [[User:Manolo|manolo]] 17:16, 12 November 2009 (EST)
+
As currently set out, I'm not clear what the relationship is between configuration via symlinks in conf.d (adding to conf.avail as needed) and via local.conf. Should these be used for different aspects of configuration? Or are they equivalent/interchangeable?
  
:: :rolleyes: --[[User:Gen2ly|Gen2ly]] 17:46, 12 November 2009 (EST)
+
I also don't quite understand about the numbering. It looked to me as if higher numbered files under conf.d were more specific than lower numbered ones. I assumed this was so that e.g. config specific to a particular font overrode general, default config for all fonts. But the article suggests that is wrong. So should I be renumbering the files there in order to get this behaviour?
  
::: lol i just moved stuff around, didnt add anything. [[User:Manolo|manolo]] 17:51, 12 November 2009 (EST)
+
e.g. Will the font-specific set up in 20-unhint-small-dejavu-sans-mono.conf get overridden by 10-bcihint.conf (a file I created with the section for BCI hints from the article)? I used 10- because that's the number for the autohinter file under conf.avail so I assumed that number was about right.
  
=== Softlinks ===
+
--[[User:Margali|Margali]] 19:23, 4 March 2012 (EST)
They shouldn't be done in relation to {{Filename|/}}; i.e., {{Codeline|ln -s /dir/dir2/file file}}. These are dangerous when cleaning a chroot, or deleting a mounted file-system in general. [[User:Time|Time]] 21:31, 5 December 2009 (EST)
+
 
+
And the seemingly superfluous {{Codeline|cd}} is added for ease of use with auto-complete. [[User:Time|Time]] 21:36, 5 December 2009 (EST)
+
 
+
== Suggestions ==
+
 
+
Suggestions for edits to this page.
+
 
+
=== xtt ===
+
 
+
The word "xtt" is used at the beginning but not defined.  I must admit that I'm unfamiliar with it.  - [[User:KitchM|KitchM]] 10:29, 23 August 2009 (EDT)
+
 
+
=== Bitmap fonts ===
+
 
+
fontconfig (2.8.0-1) does ''not'' disable bitmap fonts by default. It does not place the 70-no-bitmaps.conf softlink that the [[Font Configuration#Enable]] section suggests removing. [[User:Time|Time]] 21:25, 5 December 2009 (EST)
+

Revision as of 05:38, 20 March 2013

freetype2 config changes

freetype2 no longer uses local.conf (same with infinality) and has switched to /etc/fonts/conf.d/* config files symlinked to /etc/fonts/conf.avail/*. I'm happy to update this page but don't want to step on the plans of someone more informed than I. If I don't hear back in a week or so I'll go ahead and add some minor changes to reflect this new configuration setup.

Freetype2 has had conf.avail and conf.d for a while. One of the files in conf.d is "51-local.conf" and that lets you use /etc/fonts/local.conf for your own local settings. The freetype2-infinality package just now installs the default non-customized Infinality config to conf.avail so people know it exists without reading the documentation. thestinger 13:18, 30 November 2011 (EST)

Contradictory recommendations?

I'm not familiar with fontconfig - I've configured it rarely and a long time ago for a different OS. So I'm not sure if something is just not clear to me but as I read the article, it is giving me contradictory instructions:

  • early on, it suggests enabling both the autohinter and subpixel rendering to improve appearance after installing msfonts
  • later on, it says that the autohinter should not be used with subpixel rendering

I realise that the methods used to enable these are different in the two cases (one sets up symlinks in conf.d; one adds sections to local.conf) but if this explains the apparent inconsistency, it would be really good to explain why there's no conflict in this case. --Margali 19:07, 4 March 2012 (EST)

Autogenerating missing shapes and weights

Since the article is about improving the appearance of fonts, I would suggest qualifying the section which explains how to have fontconfig generate italics and bold/bolder fonts on the fly. I doubt very much that it is faking italics. I assume it fakes slanted versions (which are not the same as italics). Moreover, it is unlikely that the results of autogeneration will be especially pleasing. Font designers would abhor such things and not, I think, because they need the work! Faked versions can be acceptable but they will not look as good - the spacing will not be optimal, the shapes of the glyphs and the metrics will not be quite right as good fonts vary these things appropriately for different weights, shapes and sizes. --Margali 19:13, 4 March 2012 (EST)

Configuration confusion

As currently set out, I'm not clear what the relationship is between configuration via symlinks in conf.d (adding to conf.avail as needed) and via local.conf. Should these be used for different aspects of configuration? Or are they equivalent/interchangeable?

I also don't quite understand about the numbering. It looked to me as if higher numbered files under conf.d were more specific than lower numbered ones. I assumed this was so that e.g. config specific to a particular font overrode general, default config for all fonts. But the article suggests that is wrong. So should I be renumbering the files there in order to get this behaviour?

e.g. Will the font-specific set up in 20-unhint-small-dejavu-sans-mono.conf get overridden by 10-bcihint.conf (a file I created with the section for BCI hints from the article)? I used 10- because that's the number for the autohinter file under conf.avail so I assumed that number was about right.

--Margali 19:23, 4 March 2012 (EST)