FontManagement

Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2006-06-16 10:23:18 →
Size: 2333
Editor: dskt6433
Comment:
← Revision 5 as of 2006-06-20 23:56:48 → ⇥
Size: 4991
Editor: lns-bzn-55-82-255-177-114
Comment: completed the spec some more for upcoming discussion at the summit in Paris
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
 * '''Created''':  * '''Created''': By NicolasSpalinger
Line 16: Line 16:
The free desktop has made some amazing progress with system-level font support, now we just need some interface polish to expose and complements some font-related functionnalities.
Line 17: Line 19:

Jeff is a designer with a large collection of fonts and he's much rather be able to group fonts in logical sets and activate/deactivate them when needed rather than spending too much time manually uninstalling the ones he wants out of his way or which are using a script other than his own. His font menu is too way too big and some of his apps have annoying performance problems enumerating big font lists. He needs a better way of handling fonts.

Jane has just installed a new font package from the archive and finds the font really beautifully designed. She goes into the font folder and wants to learn more about the font by looking all the font metadata in the properties tab. She wants to know if that font has smart features for a specific writing system. She can easily see the features of the font, the history of the project, what inspired the design of that particular font family, etc by simply using the context menu. She can also quickly see the license of the font and may choose to contact the designer to extend the font for her.

Jack has bought a font from a renowned foundry and would like to install it manually. He does not want to use the command line and does not care about fontconfig caches and xml configuration. He wants to drap&drop and play with cursors and menus to adjust all the font settings. He needs a nice responsive GUI to install/remove his proprietary font and configure it.

Ric would rather just run Free Software on his laptop. He wants to be able to visually distinguish the free/libre/open fonts he has installed from the few restricted fonts he still needs to use. He taggs his fonts with emblems and they automatically get grouped together. He has a dynamic set listing all fonts from a foundry whose open fonts he really likes, when this foundry releases a new fonts and he gets it from the archive, it automatically joins the set.
Line 25: Line 35:
     * creating a properties tab for fonts metadata      * creating a properties tab for fonts metadata (the binary fields showed by ftinfo -a font.ttf)
Line 29: Line 39:
     * in the font preferences panel, allow change of font family and size of all four fonts at the same time.
Line 32: Line 43:
 * provide a way to adjust the priority of overlapping glyphs from various fonts
Line 34: Line 46:

Yes, hopefully once the ability to create font sets and activate/deactivate them easily is there.
Line 38: Line 54:
Possible inspiration Possible inspiration:
Line 42: Line 58:
 * the GNOME [http://live.gnome.org/SummerOutreachProjects Summer Outreach Projects] entry
Line 60: Line 77:
Look at defoma and it's use cases vs. the use of fontconfig.
Line 61: Line 80:

discussion of related specs: FontDesignToolkit OpenFonts

Summary

Polishing existing font management infrastructure and adding extra components to make handling fonts very easy and user-friendly in GNOME

Picking up some ideas left over from ["UbuntuDownUnder/BOFs/FontHandling"].

Rationale

The free desktop has made some amazing progress with system-level font support, now we just need some interface polish to expose and complements some font-related functionnalities.

Use cases

Jeff is a designer with a large collection of fonts and he's much rather be able to group fonts in logical sets and activate/deactivate them when needed rather than spending too much time manually uninstalling the ones he wants out of his way or which are using a script other than his own. His font menu is too way too big and some of his apps have annoying performance problems enumerating big font lists. He needs a better way of handling fonts.

Jane has just installed a new font package from the archive and finds the font really beautifully designed. She goes into the font folder and wants to learn more about the font by looking all the font metadata in the properties tab. She wants to know if that font has smart features for a specific writing system. She can easily see the features of the font, the history of the project, what inspired the design of that particular font family, etc by simply using the context menu. She can also quickly see the license of the font and may choose to contact the designer to extend the font for her.

Jack has bought a font from a renowned foundry and would like to install it manually. He does not want to use the command line and does not care about fontconfig caches and xml configuration. He wants to drap&drop and play with cursors and menus to adjust all the font settings. He needs a nice responsive GUI to install/remove his proprietary font and configure it.

Ric would rather just run Free Software on his laptop. He wants to be able to visually distinguish the free/libre/open fonts he has installed from the few restricted fonts he still needs to use. He taggs his fonts with emblems and they automatically get grouped together. He has a dynamic set listing all fonts from a foundry whose open fonts he really likes, when this foundry releases a new fonts and he gets it from the archive, it automatically joins the set.

Scope

Design

  • improving the various font bits in nautilus
    • exposing the font:/// folder more
    • improving gnome-font-viewer
    • creating a properties tab for fonts metadata (the binary fields showed by ftinfo -a font.ttf)
    • allowing i18n modifiable pangrams
    • visually distinguishing (manual grouping? tags? emblems?) system-wide fonts (/usr/share/fonts/) from personal ones (~/.fonts) as well as restricted/proprietary fonts from free/libre/open ones when browsing fonts:///
    • adding contextual menu actions related to fonts
    • in the font preferences panel, allow change of font family and size of all four fonts at the same time.

  • creating a smarter font menu: [http://unifont.org/fontdialog/ Font selection widget proposal]

  • providing a GUI to set more fontconfig parameters for a user's fonts.conf
  • provide a way to adjust the priority of overlapping glyphs from various fonts

RaphaelBosshard: Would it be possible to sort fonts into multiple categories? Like "Design", "Handwriting", "Futuristic", "Western", and so on?

Yes, hopefully once the ability to create font sets and activate/deactivate them easily is there.

Implementation

Possible inspiration:

Some time ago, before dapper change from 6.04 to 6.06 I made some changes to gnome-font-viewer. It works, but I don't know to integrate it in the source package control-center. I redesigned the ui and used libglade. It is very similar to the old viewer, but it allows to install fonts (it is the same as dnd in fonts:///) I had forgotten it, when I read this spec. I think it could be usefull.

Code

Data preservation and migration

Outstanding issues

Look at defoma and it's use cases vs. the use of fontconfig.

BoF agenda and discussion

discussion of related specs: FontDesignToolkit OpenFonts

CategorySpec

FontManagement (last edited 2010-03-16 11:33:47 by S0106005004cfbeb6)