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

Replace master word in designspace document files #2904

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

pnemade
Copy link
Contributor

@pnemade pnemade commented Nov 23, 2022

This PR is an attempt to fix some master word entries in fonttools/Doc/source/ directory files.
Please review this PR and do suggest if needed any changes.

This PR is created to fix issue #2896

# locations. It's a miniature designspace.
# Remember the "name" attribute we assigned to the sources?
glyphData['masters'] = [
dict(font="master.thin",
glyphData['sources'] = [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here you may need to change the matching code that expects this dictionary key

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are you suggesting to change the occurrences of glyphData['masters'] with glyphData['sources'] in Lib/fontTools/designspaceLib/* source files?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes basically, however I'm not familiar with that part of the designspace spec, maybe @LettError and others can advise. I think maybe font editors who rely on the format would need updating as well if the key changes from "masters" to "sources", that is, code outside this repository would need to adapt. But I'm not sure 100%.

@LettError
Copy link
Collaborator

I don't think there are any tools left that need these glyph-specific designspaces.

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

Successfully merging this pull request may close these issues.

None yet

3 participants