-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was scanning the archive of this list and a number of people seem to have commented on the problem I have been chasing for a while - Why are the console fonts on kde konsole looking wrong.
I have got half an answer - and that is why the wrong font is displayed. (The other half - why are the fonts displayed at other widths I haven't tracked - but there seem to be some messages here about that). Basically there are two bugs - one in freetype (now fixed I am told) that caused it to report gzipped font files as the wrong format. This caused fc-cache to put the wrong font "family-name" in the fonts.cache-1 file (basically it was putting the filename instead). When fontconfig was then matching the requested font name it was not finding "console" and was therefore using the style hint to find something from the sans-serif set in /etc/fonts/fonts.conf. Even if the bug is fixed fc-cache still doesn't put the correct family name in the fonts.cache-1 file because the freetype library is looking in the font file for a property called FAMILY_NAME and the "console" font shipped with kde only has a property called FAMILY. I have been looking on the net for a specification of the pcf file format. The only reference I can find is one which says that the code for pcfread.c and pcfwrite.c on XFree86.org cvs is the only definative statement of the format. I have scanned both files and neither makes any reference that I can see to FAMILY or FAMILY_NAME. How can I see what is correct? - -- Alan Chandler [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+VTqauFHxcV2FFoIRAvZ2AJ9Lh6GU/fDvQLKSsvZX65G08Hl5IwCglPfE dE37F6PijD6QTR0taxaRKm4= =5leP -----END PGP SIGNATURE----- _______________________________________________ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
