Bug 42264

Summary:	font selection dialog ignores fonts defined in XftConfig
Product:	[Applications] konsole	Reporter:	Siegbert Baude <siegbert.baude>
Component:	general	Assignee:	Konsole Bugs <konsole-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	FreeBSD Ports
OS:	FreeBSD
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Siegbert Baude 2002-05-06 20:25:26 UTC

(*** This bug was imported into bugs.kde.org ***)

Package: konsole
Version: KDE 3.0.0
Severity: normal
Installed from: FreeBSD Ports
Compiler: gcc version 2.95.3 20010315 (release) [FreeBSD]
OS: FreeBSD
OS/Compiler notes: FreeBSD 4.6-PRERELEASE i386

XFree86 4.2.0 with RENDER extension for anti-aliasing
KDE3.0
FreeBSD 4.6-PRERELEASE

The "konsole" program's font selection dialog ignores fonts whose font path is defined in XftConfig. XftConfig is the config file for the AA-RENDER extension of XFree 4.2.0 . The only fonts presented are those directly defined in XF86Config.
This must be somehow a non-KDE and non-QT way of finding fonts as at the same time both "qtconfig" and all other KDE programs show all fonts defined in XftConfig (in addition to those defined in XF86Config of course).

More differences compared to the font handling of other KDE applications:

If the font path of TrueType and Type1 fonts is defined both in XF86Config and XftConfig qtconfig and other KDE applications show each font twice e.g.:
Verdana [Microsoft]
Verdana [Xft]
This probably is a bug in QT and the reason why one wants to define the font path in only one location.
Konsole shows each font only one time. This also indicates that "konsole" ignores the additional font path in XftConfig.

Very strange if in this mode I choose the "konsole" font as some TT/Type1 fixed font (e.g. Lucida Console) save settings and restart X with the relevant font path eliminated in XF86Config the correct TT/Type1 font is still used in konsole but not presented in the font selection. The TT/Type1 "font size options" are however presented i.e. for "Lucida Console" up to 64 point size can be chosen whereas none of the visibly presented fonts actually offers this size.

Also strange the anti-aliasing settings of XftConfig are strictly followed even if the fonts aren't visible in the aforementioned example.

Ciao
Siegbet

(Submitted via bugs.kde.org)

Comment 1 Waldo Bastian 2002-08-06 19:24:48 UTC

Konsole only lists "fixed width" fonts. When it ignores fonts defined in=20
XftConfig it is probably because it fails to detect that those fonts are=20
fixed.

If you are into debugging relevant code can be found in=20
KFontChooser::getFontList() in kdelibs/kdeui/kfontdialog.cpp

In particular this line:
if ((fontListCriteria & FixedWidthFonts) > 0 && !dbase.isFixedPitch(*it))
continue;

Cheers
Waldo
--=20
bastian@kde.org  |   SuSE Labs KDE Developer  |  bastian@suse.com

Comment 2 ddoerflinger 2003-03-06 14:48:01 UTC

This bug starts getting old. Does it still exist in newer Versions of KDE?

Regards,
DD

Comment 3 andy 2003-09-03 20:45:02 UTC

Can you try this with an uptodate FreeBSD/XF86/Fontconfig and let us know 
whether it still applies?

Comment 4 groot 2004-01-01 20:27:52 UTC

Timeout; in addition, relevant X is now 4.3 and Xft is deprecated as far as I know.