-
Notifications
You must be signed in to change notification settings - Fork 24
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
Use font spec names for scalar types in codegen inputs #84
Comments
thinking about this a bit more:
Does this bother us? it does not especially bother me in a world where these inputs really are some sort of language-agnostic schema, but if we are treating these inputs as a project-specific shorthand for what we're generating, then I don't love it. |
I would argue the codegen inputs are incrementally moving closer to being a language-agnostic schema, that that is desirable, and that this is a clear step in that direction |
This was addressed in #81 |
Today, with the exception of Uint24, we use Rust type names for scalars. Use the names given in https://learn.microsoft.com/en-us/typography/opentype/spec/otff#data-types instead, e.g.
uint16
instead ofu16
, etc.The text was updated successfully, but these errors were encountered: