Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Fixed compatibility issues with fontpatcher #194

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants
Contributor

upsidedwn commented Aug 9, 2012

I'm new to fonts and stuff so I'm not sure if this is the best way to do
things but here goes.

Fontpatcher was unable to patch the Consolas font. This is due to the fact
that Consolas is 'not' strictly a mono spaced font - it has some glyphs
which are 0 width. The added option '--fix-mono' fixes this issue by
setting all 0 width glyphs to a common width.

Windows does not seem to respect the font family name that fontforge uses.
Using the added option '--fix-win', the script will now set the font name to
be the family name. In this manner, Windows will group these fonts under the
same family. Windows still differentiates between different fonts of the
same name by their weights(italic, bold, etc.), so having fonts of the same
name is not a problem.

FIXED COMPATIBILITY ISSUES WITH FONTPATCHER
Fontpatcher was unable to patch the Consolas font. This is due to the
fact that Consolas is 'not' strictly a mono spaced font - it has some
glyphs which are 0 width. The added option '--fix-mono' fixes this issue
by setting all 0 width glyphs to a common width.

Windows does not seem to respect the font family name that fontforge
uses.  Using the added option '--fix-win', the script will now set the
font name to be the family name. In this manner, Windows will group
these fonts under the same family. Windows still differentiates between
different fonts of the same name by their weights, so having fonts of
the same name is not a problem.
Owner

Lokaltog commented Aug 10, 2012

Nice, thanks!

@Lokaltog Lokaltog closed this in 20ab08c Aug 10, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment