Font packages

[Kevin E Martin]

On Tue, May 24, 2005 at 09:43:44AM -0400, Leon Shiman wrote:
> on Tue, 24 May 2005 02:13:44 -0400 Kevin E Martin wrote:
> >
> >I've been working through the fonts today, and there are several methods
> >that could be used to package them:
> >
> >1. Create packages similar to the ones in the monolithic tree (100dpi,
> >   75dpi, misc, cyrillic, ...)
> >2. Create packages per family (charter, courier, helvetica, ...)
> >3. Create packages per foundry (Adobe, B&H, Bitstream, ...)
> >4. Create packages using some combination of these options
> >
> >I'm leaning toward using a combination (e.g., font-adobe-courier-75dpi,
> >font-bitstream-charter-100dpi, etc.) it would give our users the
> >clearest indication of exactly what's contained within the package and
> >it allows more fonts to be added to the font module without conflating
> >the official XOF packages.  This breakdown also has a nice side effect
> >of not having to deal with multiple font licenses in the same package.
> >I'll go ahead with this scheme unless someone comes up with a better way
> >to group fonts.
> 
> Strong plan - and a significant "side effect".
> 
> I strongly urge that your cases below be withheld pending clarification... 
> to be raised with SFLC attorneys.

Both of the fonts are already in source tree (and have been since 1994
or earlier).  The current development effort in the modular tree does
not add new files or move them around, so these fonts won't affect the
build system work that we are doing.

Kevin