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
Axis Tags must be uppercase #17
Comments
Thanks, Dave. Upper-casing the tags would bring them into conformance with the spec.
|
Here's the ttx dump of the current
|
These changes would make the tags conform to the spec: Wrt xHeight, could you envisage that becoming a registered axis in the future? (It's an axis I've seen used as an example more than once.) If so, any thoughts on a scale for that axis that would make sense across any fonts using the axis? (E.g., per-mille of em height?) If so, you might use that for your XHGT scale. (Same would be true for other custom axis scales, but I call that out just because I've seen x-height called out so often as a example.) |
Thanks for the suggestions, we are planning to change all the tags in
Amstelvar to a different system, where the lowercase and uppercase issues
will be resolved.
Lowercase x height is part of our "y transparent" axis, which is almost
all available in any font's vertical metrics data, so we left it out of
Amstelvar, except x ht, because we were changing it.
…On Fri, Mar 24, 2017 at 4:24 PM, Peter Constable ***@***.***> wrote:
These changes would make the tags conform to the spec:
"cntr" -> "CNTR"
"grad" -> "GRAD"
"prwd" -> "PRWD"
"prwg" -> "PRWG"
"srfr" -> "SRFR"
"xhgt" -> "XHGT"
Wrt xHeight, could you envisage that becoming a registered axis in the
future? (It's an axis I've seen used as an example more than once.) If so,
any thoughts on a scale for that axis that would make sense across any
fonts using the axis? (E.g., per-mille of em height?) If so, you might use
that for your XHGT scale. (Same would be true for other custom axis scales,
but I call that out just because I've seen x-height called out so often as
a example.)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB3ajp3UoiSSK_QPKazbpLHYI_hzQOtwks5rpCZkgaJpZM4L8qvI>
.
|
Fixed with commit a879f3f |
Excellent, thanks. I would rather "AmstelvarAlpha-VF-2017-01-23" not cause any confusion and be in an old fonts folder or something, so just "AmstelvarAlpha-VF" is there? |
I'll take care of this with git tags |
tag on! thanks.
…On Mon, Mar 27, 2017 at 4:16 PM, Dave Crossland ***@***.***> wrote:
I would rather "AmstelvarAlpha-VF-2017-01-23" not cause any confusion and
be in an old fonts folder or something, so just "AmstelvarAlpha-VF" is
there?
I'll take care of this with git tags
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB3ajnKTYm4J4OypQW6FxbvWJeHNq7Utks5rqBkhgaJpZM4L8qvI>
.
|
Thanks! :-) |
Over in http://typedrawers.com/discussion/comment/25823/#Comment_25823 @PeterCon said,
I'd like to request that
abcA
andxyz2
can be changed toABCA
andXYZ2
in order to conform to the spec's requirements.(This is the same as googlefonts/decovar#2)
The text was updated successfully, but these errors were encountered: