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

Clarify input vs output in location units? #7

Open
tiroj opened this issue Oct 15, 2024 · 1 comment
Open

Clarify input vs output in location units? #7

tiroj opened this issue Oct 15, 2024 · 1 comment

Comments

@tiroj
Copy link

tiroj commented Oct 15, 2024

I suspect this may be confusing to some font developers

u indicates the number is expressed in "user" units—the "input" values in a variable font's designspace axis map. d indicates the number is exprssed in "design" units—the "output" values in a variable font's designspace axis map.

because ‘input’ and ‘output’ depend on perspective. From a font maker perspective, the design units are in the input from the font and the user units are the output to the client software. From a user perspective, the user units are the input from the client software and the design units are the output from the font.

I think the latter is what is implied by the use of input and output in the variable location spec, but maybe clarify this in some way?

@skef
Copy link
Contributor

skef commented Oct 15, 2024

Ah, that part of the discussion was meant literally and refers to designspace file map elements:

https://fonttools.readthedocs.io/en/latest/designspaceLib/xml.html#map-element

So yes, abstractly, one could consider the mapping (and probably many mappings) to run in either direction, those terms refer to specific XML properties that aren't ambiguous in that way.

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

2 participants