[Pkg-fonts-devel] package names

[Adam Borowski]

On Thu, Apr 06, 2017 at 06:31:16PM +0200, Nicolas Spalinger wrote:
> >> How about dropping the first foundry name:  fonts-$fullfontname instead? 
> >>
> >> How does that sound? 
> > 
> > I prefer a naming scheme of "fonts-$name" over "fonts-$foundry-$name".
> > 
> > I prefer that we _not_ include foundry in package name - i.e. that we 
> > use these schemes by default:
> > 
> >   * fonts-$superfamily
> >   * fonts-$family
> >   * fonts-$name
> > 
> > I.e. for a font including the foundry as part of the name but not its 
> > familiy name, use family name in package name, and for a collection of 
> > font families sharing a basename (e.g. Noto) use that "superfamily" name 
> > in package name.
> 
> 
> I agree that for certain fonts it's hard to know what to pick as the foundry name:
> -croscore-? -google-? -adobe-?  Especially when multiple foundries have worked on it.

I'd for one strongly discourage using foundry names when avoidable.  Ie,
let's use them only when they are either engrained in the font's popular
name, or are required to tell a particular implementation of a typeface from
others.

-- 
⢀⣴⠾⠻⢶⣦⠀ Meow!
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second
⠈⠳⣄⠀⠀⠀⠀ preimage for double rot13!