-
-
Notifications
You must be signed in to change notification settings - Fork 25
Bad NS character set 356Q in Classic and Modern ? #1408
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
Comments
In the Google shared drive CHM-PARC there is a folder called "fonts". I'm filling it with all the .DISPLAYFONT files (case insensitive) from the CHM PARC archives. |
there are also .strike files there, and .ac isn't hard to find. We had some ambitions for better fonts #351 |
I wrote some prototype code for reading BDF font files. The next step is to tie it into Medley's font display system. |
I converted Andrew's code to a Medley file, in the package "BDF". I did not make significant changes to the code. And, here's the link to the Adobe Glyph Bitmap Distribution Format document |
I've been looking at the character mappings from Alto fonts to NS fonts. (Some of the entries in the mapping arrays in Interpress don't seem to be correct.)
It appears to me that character set 356Q (Technical Symbol 2) is completely empty at least in size 10 and 12, whereas 357Q is at least spotted with a few characters.
lf someone confirms that this is the case, do we have another source for these bitmaps?
The text was updated successfully, but these errors were encountered: