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

Don't write disabled feature prefixes #762

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

simoncozens
Copy link
Collaborator

Fixes #761.

@anthrotype
Copy link
Member

I suppose that this will not roundtrip when ufo2glyphs, am I right? How important that would be?

@simoncozens
Copy link
Collaborator Author

I think we already have that situation with disabled features.

@anthrotype
Copy link
Member

actually we seem to have code to parse that special comment, see DISABLED_RE = re.compile("^# disabled$") in builder/features.py

Could you add a test to see if that also works for featurePrefixes?

@schriftgestalt
Copy link
Collaborator

And don’t forget the classes. They can be disabled, too.

# Not even feature code

"""
)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Could you check that when going back to Glyphs.app the commented-out feature prefix comes back uncommented? = in the same situation before going to UFO (if that sounds like a reasonable thing to have)

Copy link
Member

Choose a reason for hiding this comment

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

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.

Support "disabled" feature prefix code
4 participants