Skip to content

Always set usDefaultChar to 0 (.notdef)#5242

Merged
skef merged 1 commit intofontforge:masterfrom
dscorbett:usDefaultChar-0
Jan 28, 2024
Merged

Always set usDefaultChar to 0 (.notdef)#5242
skef merged 1 commit intofontforge:masterfrom
dscorbett:usDefaultChar-0

Conversation

@dscorbett
Copy link
Copy Markdown
Contributor

usDefaultChar is the code point to use for a default glyph for an unsupported code point. If it is 0, the font uses glyph 0 (.notdef), which is always what you want instead of FontForge’s current behavior of defaulting to U+0020 SPACE.

Type of change

  • Non-breaking change

@iorsh
Copy link
Copy Markdown
Contributor

iorsh commented Jan 28, 2024

@dscorbett, could you please rebase to the latest fontforge:master?

This generally looks safe to me. I couldn't see any specific Linux software incorrectly using "space" as a default character, but I recall such behavior in Windows. I agree that ".notdef" is better than "space", since it allows missing characters to stand out when displayed, instead of being quietly replaced with space.

@iorsh
Copy link
Copy Markdown
Contributor

iorsh commented Jan 28, 2024

Per GW (224315a) is was a guess, so probably safe to sacrifice.

Copy link
Copy Markdown
Contributor

@skef skef left a comment

Choose a reason for hiding this comment

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

This seems good

@skef skef merged commit cd36c82 into fontforge:master Jan 28, 2024
@dscorbett dscorbett deleted the usDefaultChar-0 branch January 28, 2024 22:05
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