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

Glyph renaming #524

Closed
wants to merge 2 commits into from
Closed

Glyph renaming #524

wants to merge 2 commits into from

Conversation

JoesCat
Copy link
Contributor

@JoesCat JoesCat commented Apr 8, 2013

Khaled has this solution. Please see if it fits what you are looking for.
If yes, please merge.

khaledhosny and others added 2 commits April 8, 2013 15:46
SFGlyphRenameFixup() is too smart that it will, when renaming “f”, it
will search for glyphs that has an “f” component, e.g. “f_f” or “f_f_i”
and rename the component as well. The desirability of this is
questionable, but for now I added a boolean flag to control this and
disable it in Python while keeping the GUI behaviour unchanged.

Commits / fc92548, see issue 523 "Remove the auto glyph renaming feature."
These things can get forgotten later - better highlight a note.
@ghost
Copy link

ghost commented Apr 11, 2013

Doesn't compile for me:

lookups.c:3843: error: conflicting types for 'SFGlyphRenameFixup'
splinefont.h:3126: note: previous declaration of 'SFGlyphRenameFixup' was here

That should be easy to fix (just change the prototype in the header file), and I don't mind doing so myself. I'm not sure if there's an easy way for me to add commits to an existing pull request that is in someone else's space. Should I make a branch of my own in mskala/fontforge? Should I create a branch in fontforge/fontforge, commit to that, and then file a pull request for merging it to the master? What's the protocol?

@ghost
Copy link

ghost commented Apr 11, 2013

See my suggested patch #532. Is it okay to close this one?

@davelab6
Copy link
Member

Yes I think so

@davelab6 davelab6 closed this Apr 11, 2013
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