Bug 83212

Summary:	Font list on toolbar differs from font list in KWord's font dialog
Product:	[Applications] calligrawords	Reporter:	Dik Takken <kde>
Component:	general	Assignee:	Calligra Words Bugs <calligra-words-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	cfeck, nicolasg
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Dik Takken 2004-06-11 13:05:57 UTC

Version:           1.3.1 (using KDE KDE 3.2.2)
Installed from:    Compiled From Sources
OS:                Linux

The font listing on the toolbar of KWord shows more available fonts than the font list in the < Format -> Font > menu. I guess it's the bitmap fonts that are shown in the toolbar listing, but they are not present in the Font dialog. When I do select a bitmap font like 'terminal' or 'fixed', they seem to be substituted with a sans-serif Type1 font as soon as I try to use it.

Comment 1 Nicolas Goutte 2004-06-14 09:27:36 UTC

Bitmap fonts are not supported by KOffice, as they do not give enough information for WYSIWYG. However the toolbar widget does not allow to restrict the fonts shown.

Have a nice day!

Comment 2 Halla Rempt 2005-10-19 12:41:33 UTC

Then this is a kdelibs issue.

Comment 3 Christoph Feck 2011-07-26 11:57:54 UTC

Indeed. KFontAction and KFontComboBox miss a way to filter the list, as is possible in KFontChooser.

Comment 4 Christoph Feck 2011-08-06 00:24:52 UTC

Actually, KFontAction has a constructor taking a "fontListCriteria" argument, so it could filter out the bitmap fonts the same as the font dialog. I don't know if this is still a problem in Calligra/Words, so I am reassigning back for inspection.

If Calligra uses KFontComboBox, I can add a setFontListCriteria(), so that it can filter not only by fixed fonts, but also by bitmap fonts.

Comment 5 Camilla Boemann 2011-08-06 16:17:36 UTC

we already ask for SmoothScalableFonts

Comment 6 Camilla Boemann 2011-08-06 16:18:40 UTC

and seeing how old the bug i'd say it's fixed

Comment 7 Christoph Feck 2012-09-11 19:35:38 UTC

Not fixed, but newly reported.

*** This bug has been marked as a duplicate of bug 306625 ***