You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
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:
@benkiel @LettError @justvanrossum @anthrotype Do you have any thoughts? Do you know of any other issues that should be addressed?
The text was updated successfully, but these errors were encountered: