sunaku / tamzen-font

💌 Bitmapped programming font, based on Tamsyn
Other
892 stars 29 forks source link

Provide this font in TTF format #7

Closed noscript closed 4 years ago

noscript commented 8 years ago

Where is ttf/ subfolder?

sunaku commented 8 years ago

After many tries, I've abandoned all hope of generating TTFs with FontForge, but this looks promising. :pray:

noscript commented 8 years ago

I will give it a try.

sunaku commented 8 years ago

Well, I gave it a shot but encountered an error: https://github.com/koron/bdf2ttf/issues/1 :grimacing:

sunaku commented 8 years ago

Thanks to @koron, we're finally making progress:

screenshot

See also https://github.com/koron/bdf2ttf/issues/2

noscript commented 8 years ago

Can't wait :smile:

sunaku commented 8 years ago

I've hit a dead end with bdf2ttf :facepunch:, trying FontForge again: https://github.com/fontforge/fontforge/issues/2738 :dizzy_face:

vasili111 commented 8 years ago

Waiting ttf too :)

sunaku commented 8 years ago

Just to clarify: I'm waiting for feedback from FontForge developers in issue https://github.com/fontforge/fontforge/issues/2738. If you're knowledgeable about TTF or passionate about this issue, feel free to help move this forward. :bowing_man:

tobia commented 7 years ago

I managed to convert it very easily using https://github.com/ali1234/bitmap2ttf but I'm having an issue with the space character width.

The reason I'm trying to create a TTF file is that AFAIK Sublime Text does not supports X11 fonts. With the TTF file I created, hard tabs line up correctly with the text, but the space character does not. A single space seems to be rendered 5 pixels wide instead of 8 (using 8x15):

space_width

I get the same results with the Tamsyn PCF files. I'm not sure whether this is a bug in the font definition, in the bitmap2ttf tool, or in Sublime Text. Other editors don't seem to have this bug, using the same TTF file. Does anybody know how to fix it?

sunaku commented 7 years ago

Thanks for the suggestion @tobia! :+1: That tool is generating "blank" SVGs for space characters:

/tmp/tmprKeQ4w/00032.svg:<svg width="500.0" height="1000"><path d="" fill="currentColor"/></svg>
/tmp/tmprKeQ4w/00160.svg:<svg width="500.0" height="1000"><path d="" fill="currentColor"/></svg>

As a result, my fontforge (version 11-Aug-2017) is refusing to process those two "blank" SVGs:

$ fontforge -script /tmp/tmprKeQ4w/Tamzen8x16r.ttf.pe
Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
 with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
 Based on sources from 13:46 UTC 11-Aug-2017-ML-D.
 Based on source from git with hash:
I'm sorry this file is too complex for me to understand (or is erroneous)

It seems your Fontforge did not reject the conversion outright and instead gave you a zero-width blank glpyh for the space character (codepoint 32). That's why you're observing that issue in your screenshot. :sweat_smile:

vasili111 commented 6 years ago

Here guy transformed bitmap to ttf. There are some clues but no tutorial.

vasili111 commented 6 years ago

There is a response in comments about how to convert fonts. https://int10h.org/blog/2018/05/flexi-ibm-vga-scalable-truetype-font/

sunaku commented 4 years ago

Thanks @vasili111, I've applied your suggestion in the issue-7 branch and also added the generated *.ttf files there (under ttf/ folder). Please try it out and let me know if you find any problems.

sunaku commented 4 years ago

Good news, I have verified that the TTF fonts work correctly under Windows 10 build 1909:

2020-05-07 19_52_06-

The fix is now merged into master branch at commit c1664cb26f7b68e736ab1f227abac86ae126e7e1. :tada: Many thanks @vasili111!

vasili111 commented 4 years ago

@sunaku

Thank you very much for creating TTF versions :)