Regular and slashed variants: can't be packaged together due to using same name

[dtzWill]

Hi!

I package this font (for a linux distribution), and when updating was excited to include the slashed variants (I like base agave but have often enjoyed the slashed zero in other fonts in the past).
Unfortunately since the fonts use the same font name, they can't both be included in the default agave package (well they could but users wouldn't have a good way to select which they want to use in applications/etc).

Even putting them in separate packages only works really as long as a user only installs one of them, which isn't ideal.

Instead, could these be merged into a single font with stylistic sets used to select the preferred variant? This might mean using fontconfig snippets to force a particular variant for terminals/programs that don't let this be specified, however.

Or perhaps more simply, name the latter "Agave-Slashed" or something? This might get messy as variations grow...

Not sure how to best handle it, but those are ways I've seen this handled in other fonts.

Just a thought, thanks! Glad to see this font still growing and improving! 👍

[blobject]

Thanks for reporting, and again thank you so much for packaging agave for nixos.

I was shortsighted in offering the variants in the current way; I assumed the user would download the variant they want and not bother with the other. But this is not a useful assumption in terms of packaging.

I guess the stylistic set method is the more proper way of dealing with this, letting zero be unslashed by default. I'll get to fixing this, hopefully soon.

todo:

• make slashed zero a stylistic variant thing
• document style switching for end user
• test in app (editor, font viewer, css)

[blobject]

influences auto-generation: #62