Quoting Axel Beckert (firstname.lastname@example.org): > fonts-$foundry-$fontfamilyname sounds way more sane to me for source > packages, yes. I just wrote in an ITP that we could probably go this way for wheezy. So if that font is not intended for squeeze, I'd say "let's choose 'fonts-yanone-kaffeesatz'" for the source package. How about using "ttf-yanone-kaffeesatz" and "otf-yanone-kaffeesatz" if two binary packages do provide the separated TTF and OTF versions?
Description: Digital signature