Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add FAQ #178

Open
typesupply opened this issue Apr 14, 2021 · 2 comments
Open

Add FAQ #178

typesupply opened this issue Apr 14, 2021 · 2 comments
Assignees

Comments

@typesupply
Copy link
Contributor

I think we should add a page to detail answers to the frequent questions/suggestions/complaints/etc. I feel like I'm increasingly answering the same questions and my answers are getting increasingly shorter because of time constraints. I've had a few instances where my responses have been interpreted as being dismissive/gatekeeping. That's absolutely not my intent, but I can understand why they are being interpreted that way. I'd like to try to start compiling these kinds of answers into a spec page that we can point to instead of trying to explain it anew each time.

I'll volunteer to write it. The questions always come from an engineering perspective, so tonally the new page could be the same as the contributing page. Off the top of my head, these are some issues that I think should be addressed:

  • Why is UFO a package?
  • Why property lists and not ?
  • Why aren't there rules about whitespace, attribute order and other normalization issues that make Git diffs noisy?
  • If "no data duplication" is a rule, why is there an exception for kerning?
  • Why are layers at the font level and not at the glyph level?

@benkiel @LettError @justvanrossum @anthrotype Do you have any thoughts? Do you know of any other issues that should be addressed?

@typesupply typesupply self-assigned this Apr 14, 2021
@benkiel
Copy link
Contributor

benkiel commented Apr 14, 2021

I think it would be good to have a history/context bit in there. The idea that UFO is a way of future proofing one's creative work against font editors coming and going is a bit lost these days as the memory of the Fontographer/FontLab change fades.

@LettError
Copy link
Contributor

Fontlab files of your custom fonts as expensive NFTs. Can't do anything with them anymore but they're valuable for sure!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants