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

public.postscript.hints confusion #149

Open
yarmola opened this issue Oct 22, 2020 · 1 comment
Open

public.postscript.hints confusion #149

yarmola opened this issue Oct 22, 2020 · 1 comment
Labels
clarification Needed specification clarification.

Comments

@yarmola
Copy link

yarmola commented Oct 22, 2020

I have few questions on the subject.

1 . Spec says:

Each stem string starts with either ‘hstem” or “vstem” and is a followed by a series of white-space delimited stem coordinate values. A stem coordinate value is an absolute coordinate.

while following sample obviously has hint delta stored as relative value:

<string>hstem 11 -21</string>
<string>vstem 30 207</string>

(It references x coordinate of 327 which is a valid coordinate in the contour above)

What option is correct?

2 . Sample references point tags hintSet0000 and hintSet0004 which aren't defined in the contour. Is it just a error or there is a way to encode point index in the hint set tag?

3 . id key — is it required? Building it basically requires to store another copy of the contour which I'd like to avoid. What will happen if there is no id?

4 . Can pointTag be avoided if there is only one hintSetList? That could mean that there is no hint replacement. Generally it would be very nice to assume that first hintSetList is applied from the first point in the current glyph/layer, if not specified otherwise by pointTag.

@benkiel
Copy link
Contributor

benkiel commented Jan 21, 2022

Could @readroberts or @moyogo take a look at this? I don't know this part of the spec well enough to make any calls.

@benkiel benkiel added the clarification Needed specification clarification. label Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Needed specification clarification.
Projects
None yet
Development

No branches or pull requests

2 participants