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

Custom axis tags don't conform to OT spec #2

Closed
PeterCon opened this issue Feb 9, 2017 · 5 comments
Closed

Custom axis tags don't conform to OT spec #2

PeterCon opened this issue Feb 9, 2017 · 5 comments

Comments

@PeterCon
Copy link

@PeterCon PeterCon commented Feb 9, 2017

The Decovar font defines axes in the 'fvar' table using these axis tags:

bldA
bldB
sklA
sklB
sklD
trmA
trmB
trmC
trmD
trmE
trmF
trmG
trmK
trmL
wmx2

This doesn't conform to the OT spec requirements for custom axis tags:

"Privately-defined axis tags must begin with an uppercase letter (0x41 to 0x5A), and must use only uppercase letters or digits."

See here for full details on axis tags requirements:
https://www.microsoft.com/typography/otspec/fvar.htm

@dberlow
Copy link
Collaborator

@dberlow dberlow commented Feb 13, 2017

Yes. We are publicly defining them here in an open source font;) Decovar though, so most of them don't matter much as neither the user value, or the name has meaning. As such, visual representation of it is required. wmx2, on the other hand, is shared with Amstelvar, where All of the Axes we have publicly defined in an open source font, have meaningful axes names and values to users and applications, will require interoperability, and should IMO, be registered as well as being public as they now are.

@PeterCon
Copy link
Author

@PeterCon PeterCon commented Feb 14, 2017

@dberlow
Copy link
Collaborator

@dberlow dberlow commented Feb 17, 2017

@djrrb
Copy link
Collaborator

@djrrb djrrb commented Apr 3, 2017

Hi @PeterCon we just committed a new version of Decovar with a new axis-naming scheme. Hopefully these address the concerns you had about the naming of the original axes.

I suppose I can close this issue because I think the original question was resolved, but feel free to reopen and commit should it warrant any more discussion. Thank you!

@djrrb djrrb closed this Apr 3, 2017
@davelab6
Copy link
Collaborator

@davelab6 davelab6 commented Apr 3, 2017

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

Successfully merging a pull request may close this issue.

None yet
4 participants