Bug 141119 - feature requests: display actual font file and path; add a search function; add features like in "gwaterfall" and "gucharmap"; and more
Summary: feature requests: display actual font file and path; add a search function; a...
Status: RESOLVED FIXED
Alias: None
Product: kcontrol
Classification: Miscellaneous
Component: kcmfontinst (show other bugs)
Version: unspecified
Platform: openSUSE All
: NOR wishlist
Target Milestone: ---
Assignee: Craig Drummond
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-03 13:25 UTC by Kurt Pfeifle
Modified: 2011-06-23 15:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kurt Pfeifle 2007-02-03 13:25:30 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    SuSE RPMs

In the last few days I happened to use "kcmshell kcmfontinst" quite a few times, because I'm currently trying to gain more knowledge about printing + fonts (esp. as far as it concerns KDEPrint, CUPS and Ghostscript).

Hence, a few ideas came to my mind, how kcmfontinst could be improved for KDE4 (3.5.x is probably out of scope) by adding a few features.

I admit, if you take all the items in my feature request together, the application will go far beyond a simple "Font Installer", and should more likely be re-named a "Font Manager".

OK, here we go:

"Simple" feature requests: 
--------------------------
 * display actual font file and path for each font name
 * search function (search for names, paths and file names)
 * show alias names of fonts
 * show what "fc-match" would use for a given fontname

"Advanced" feature requests:
----------------------------
 * functionality like is availabe in "gucharmap".
 * functionality like is availabe in "gwaterfall".
 * ability to create groups of fonts which could be easily disabled/enabled at will (also "hiding" of fonts)


There is of course no need to bloat the current UI with all these things. But if they could be made available behind an "Advanced" button (or some similar means), it would be nice.

My need to display the actual font file name+path (as well as the search function) stems from the very often non-obvious mapping of file names to font names to glyph shapes. Or could you say (out of the back of your head), which font hides behind a file name such as bl______.ttf?

Regarding "gucharmap" and "gwaterfall": these are Gtk/Gnome programs. If you don't know them yet, have a look please. A long look, I mean. You really only start to appreciate what these applications can do for you, if you play with them for an hour or more.

gucharmap:
----------
allows you to browse through all the available Unicode characters for all installed fonts. You can display their glyhps, look at their descriptions and Unicode names and invocations (UTF-8 and UTF-16), find their XML entities, and lookup aliases they also may be known as. gucharmap also supports browsing through the Unicode categories of a font and examine their properties in much detail. gucharmap provides a nice and easy way to find any glyph you might only know by its Unicode name or code point. Last, you can copy any glyph into an edit line, and by this means easily construct complex strings consisting of various fonts, scripts and glyphs for further usage.

gwaterfall:
-----------
displays simultaneously a sample of the line "The quick brown fox..." in various sizes (defaults to a range from 5 to 36 points with steps of 1 point -- but range and steps are configurable); allows to enable/disable and change hinting, autohinting, anti-aliasing, subpixel smoothing and aspect, with an immediate display of any change on the screen; Unicode characters are divided into blocks of 128 characters (which can serve as the text sample), so users can browse through each font's Unicode characters as well (or not, if the font is limited to ASCII)..

font grouping/hiding:
---------------------
it would be nice if there was a way to tell an application to only display a set of given fonts (must be configurable) for the current document. It is a pain i.t.a. and very inconvenient to have a few hundred fonts installed, and then work with a document that uses various of them (but only 3 or 4), and you've to frequently select in the dropdown one from the hundreds of fonts...


Anyway, thanks for kcmfontinst so far -- it is a really nice little program. :-)
Comment 1 Craig Drummond 2007-02-07 22:08:08 UTC
The KDE4 font installer already has a "Font Management" mode, which enables 
the creation of "font groups", and the possibility to enable/disable fonts.

> "Simple" feature requests:
> --------------------------
>  * display actual font file and path for each font name


Not sure where to display this. Fontconfig is used to obtain font listings, 
therefore there can be multiple font files for 1 font. I could put this in a 
tooltip? Or a "Properties" dialog.

>  * search function (search for names, paths and file names)


The KDE4 installer already had a search/filter function - it worked on both 
family and style together. I've just (today!)  changed this to have a drop 
down menu to select the filter type - so it can filter on either:
	Family
	Style
	Filename
	File location

>  * show alias names of fonts


How do I get these?

>  * show what "fc-match" would use for a given fontname


Interesting idea - I suppose I could put this in the tools menu...

> "Advanced" feature requests:
> ----------------------------
>  * functionality like is availabe in "gucharmap".


I've updated the large preview section, and the standalone font viewer, to 
allow displaying of unicode blocks and scripts. I'm not 100% convinced about 
the need to display character information - but I will ponder on this.

>  * functionality like is availabe in "gwaterfall".


Don't really see the point. It didn't seem to work very well for me. The only 
control that seemed to have an effect was the "auto hinting" toggle.

>  * ability to create groups of fonts which could be easily disabled/enabled
> at will (also "hiding" of fonts)


Already done! :-)


> My need to display the actual font file name+path (as well as the search
> function) stems from the very often non-obvious mapping of file names to
> font names to glyph shapes. Or could you say (out of the back of your
> head), which font hides behind a file name such as bl______.ttf?


Would the above mentioned search/filter be enough? I dont really want to place 
the file listing in the UI.

> font grouping/hiding:
> ---------------------
> it would be nice if there was a way to tell an application to only display
> a set of given fonts (must be configurable) for the current document. It is
> a pain i.t.a. and very inconvenient to have a few hundred fonts installed,
> and then work with a document that uses various of them (but only 3 or 4),
> and you've to frequently select in the dropdown one from the hundreds of
> fonts...


Per app/document? Not sure how that would be done. I've got a patch that adds 
a font group list to KDE's font dialog. Using the current font installer, you 
can place font families int groups. The KDE font dialog then reads this list 
of groups in, and allows filtering based upon the group. Is this what you 
mean?


You really should check out the KDE4 font installer - I would be very 
interested in your opinion.
Comment 2 Kurt Pfeifle 2007-09-05 16:07:49 UTC
I'll soon have Linux system with a GUI again (and will install openSUSE on it to take advantage of their KDE4 build service). Looking forward to see your KDE4 font installer in action then... :-)
Comment 3 Craig Drummond 2011-06-23 15:25:50 UTC
KDE4 font installer already contains most of these requested features.