Added characters for c0 and c1 codes #83
Conversation
|
It's not clear to me that it is desirable to have visible glyphs assigned to all the C0 and C1 code positions (or indeed to any of them -- what is the intended use case for these?). In particular, in TrueType fonts several of these characters are expected, according to Microsoft recommendations[1], to have blank glyphs. Note also that visible representations of C0 control codes (and a few others) are encoded separately in Unicode; see the Control Pictures block at U+2400. The control codes themselves are not expected to have visible glyphs. I'm not sure how these .ufo files were created, but when imported into Glyphs.app they look like the outlines are somewhat broken -- it looks like many of the curved outlines are not closed correctly, and end up finishing with a straight line where a curve would be expected. (I suspect this may be a Glyphs bug rather than an error in the files, but have not investigated more deeply.) But when I tried to import them into FontForge for comparison, it crashed.... In any case, these glyphs are fundamentally unsuitable for Fira Mono because they do not have the correct (monospaced) width to be compatible with the font. |
The purpose was to use this fonts in debug output and web IDEs to have more control over output.
this block in fact contains another characters, you cannot just copy them and get what they really meant to be
They were created in fontforge. At first I created a prototype font with these chars (validated, so there musn't be such things as unclosed contours) and tested it. (and the font was exported correctly, without crash). Then I just exported that font into .ufo and manually merged with fira mono (just copied files and copied some rows into contents.plist) because I haven't managed to copy them from font to font using fontforge (instead of this fontforge replaces the last glyph), maybe this caused the crash
They were inspired by Notepad++ ones. I can try to fix them. Would it be OK if they were twice as wide as regular chars? Also would it be OK, if I replaced space glyph with a dot and tab one with an arrow? |
|
On 16/5/15 19:31, KOLANICH wrote:
Some rendering systems will not display control codes using glyphs from
I don't think so. If there are glyphs that have a different advance
Not as their default rendering; if anything, that could be done as an But in general, software that supports "show invisibles" or similar |
|
|
On 17/5/15 13:58, KOLANICH wrote:
Yes, I know; I recently implemented that change in Firefox. Though note Before this can be considered, though, the issue of the glyph widths |
|
@KOLANICH Thanks a lot for this pull request. I would love to use this font, since I'm working on a hex editor. I can't find any way to build the OTF fonts from the UFO sources though, |
|
@mickeyl, I used FontForge (if I remember right - with some plugin for importing ufo). Unfortunately currently I don't have the access to the prebuilt version. |
|
Ok, thanks anyways. Unfortunately FontForge complains about a lot of errors in the |
Hello, here is the glyphs for C0 and C1 codes.