On Thu, Sep 22, 2016 at 02:26:02PM -0500, rhubarbpie...@gmail.com wrote: > > I thought fontconfig creates /etc/fonts/fonts.conf and the files differ > between 7.9 and 7.10. In fact they differ significantly in size. It seems > compiling fontconfig is pretty straightforward but I guess there could have > been an error I missed. Replacing my BadFonts_7.10 /etc/fonts with my 7.9 > version does fix the problem. > I've just had the opportunity to compare /etc/fonts/fonts.conf in 7.9 and 7.10. Yes, they do differ in size by about 3.5K. The reason is that the table of valid blank characters almost at the end of the file has been removed.
Previously I came across a reference to this table in the context (some years and versions ago) of one of the Source Sans fonts being treated by fontconfig as not usable for English (in that case, I think it was missing both the caret and the back-tick, which I interpreted to mean they were ostensibly present, but blank). I'm puzzled why the absence of that table would alter things for an English speaker running LFS - unless you are trying to use some uncommon font (e.g. in your browser's preferences, if the browser is where you noticed this) which used to be ignored because some other characters were blank, but is now in use. But diagnosing what happens in fontconfig seems to be painful. The link I found was, I think, in https://eev.ee/blog/2015/05/20/i-stared-into-the-fontconfig-and-the-fontconfig-stared-back-at-me/ which also talks of using fc-match and pango-view to see which font will be used for a particular codepoint, based on the font name you pass and what is installed. Unfortunately, I think the examples used a smiley or other graphic character. But perhaps the process may be useful if you have both the 7.9 and 7.10 systems available. ĸen -- `I shall take my mountains', said Lu-Tze. `The climate will be good for them.' -- Small Gods -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
