Keith Packard wrote: > > I've had a request to consider how to "group" fonts as seen in Macintosh > interfaces -- that interface permits the list of available fonts to be > trimmed down to elide infrequently used fonts or to limit the display to > only a few fonts selected for a particular project.
When you say "limit the display", do you mean in a document, or in the list of available fonts? > This message is just a starting point for discussion, I want to see if I'm > going in a reasonable direction as the underlying requirements aren't all > that clear to me yet. It would be nice to get a firmer idea of the requirements, or at least an example or three of where this would be used. > Here's what I'm thinking this evening: > > 1) Create groups of font families; each family can be in zero or more > groups. These groups are part of the global configuration (either > system-wide or per-user). These are a part of the font pattern. When it's system-wide, I can understand the term "global configuration", but when it's per-user, are you still calling it "global"? If so, is there also a "local" configuration? (I haven't been following your work very closely. Please point me in the right direction to find out more. Thanks.) > 2) Add a new mode for <match> elements. Currently, <match> works on > either pre-match patterns or post-match font names. Make it work > on pre-list patterns as well. This permits changing the pattern > provided to list fonts. > > 3) Use the group as a part of the font matching property list. > I'm not sure precisely where in the list it should fall. > > Now the configuration can contain elements like: > > <group name="laserwriter"> > <family>times</family> > <family>courier</family> > <family>helvetica</family> > <family>symbol</family> > </group> > <match target="list"> > <edit group="laserwriter"> > </match> > > Now font listing would show only fonts from the "laserwriter" group, while > font matching would still use all available fonts. I don't know if this example is just an example, or a real need. It looks like it's trying to limit the font list to fonts that also reside in the printer (the Laserwriter). This makes me wonder, are we doing this because we want the user to use only those fonts that are in the printer? Can we not send glyphs from the computer to the printer? Or do we also have other purposes in mind, such as limiting the user to a set of fonts that are likely to be found on all Internet users' clients (for example)? > Add: > > <match target="pattern"> > <edit group="laserwriter"> > </match> > > and now font matching would prefer fonts from the "laserwriter" group, > although, depending on the precedence of "group", it might still match > fonts outside of the group. > > I'm not sure I like the notion of placing the group selection into the > global configuration, but I'm not sure where else it should go. Should > there be API support to set/query the current groups? What do you mean by "group selection"? The <group> element above? One of the <match> elements? Which one? Erik van der Poel _______________________________________________ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
