Skip to content

Conversation

jtanx
Copy link
Contributor

@jtanx jtanx commented Aug 31, 2019

All the popup messages were really already gettext localised strings anyway. So this removes the possibility of mistakenly not specifying the gg_utf8_popup flag (see #3877), and removes the need to cast to unichar_t on initialisation

Type of change

  • Bug fix

Copy link
Member

@ctrlcctrlv ctrlcctrlv left a comment

Choose a reason for hiding this comment

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

Working with GDraw often feels like death by a thousand cuts. I approve anything that removes a cut.

@jtanx jtanx merged commit ee08337 into fontforge:master Aug 31, 2019
@jtanx jtanx deleted the gg branch August 31, 2019 09:47
ctrlcctrlv added a commit that referenced this pull request Aug 31, 2019
g->popup_msg = (gd->flags&gg_utf8_popup)
? utf82u_copy((char *) gd->popup_msg)
: u_copy(gd->popup_msg);
g->popup_msg = utf82u_copy(gd->popup_msg);
Copy link
Contributor

Choose a reason for hiding this comment

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

Isn’t popup_msg a char * now? So this should be copy()?

Omnikron13 pushed a commit to Omnikron13/fontforge that referenced this pull request May 31, 2022
 Disallow unichar_t popup messages on GGadgetData initialisation; remove gg_utf8_popup flag
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.

3 participants