-
Notifications
You must be signed in to change notification settings - Fork 716
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
Console Windows’ fonts #1410
Comments
OK, I suspect that the solutions looks like this: What http://support.microsoft.com/kb/247815 (apparently) omits, is
To disable these codepages, I needed to insert into
(this overrides the auto-generated value Any more comments (so I may close it)? |
Actually, I myself have a comment: Is not it a FontForge bug that: |
You should be able to edit mscodepage in FF by |
You should be able to edit mscodepage in FF by Element->Font Info->OS/2->Charsets->MS Code Pages. Use ctrl-click to toggle single selection. As I pointed in my message, it was via this menu entry that I discovered what made the crucial working change. However, for my workflow, I have absolutely no interest in interactive fixes. |
For a console font it should specify xAvgCharWidth manually to the width of Latin characters, however Fotnforge always calculate this value on its own. |
(I made a new release of de-rasterized Unifont; see http://ilyaz.org/fonts.) As in all (working ;-) releases, I’m forced to remove Katakana, Bopomoto, and Hangul Jamo from the font — otherwise it is not recognized as a “suitable for Console” font on Windows.
Reading http://support.microsoft.com/kb/247815 again, it says:
Could somebody explain what can this mean in context of FontForge?
BTW, another requirement:
is also not clear in the FontForge context (although judging by the fact that removing about 200 characters out of 15000 makes thing work, this is already covered by my setup). Comments?
The text was updated successfully, but these errors were encountered: