![]() It may have been true in 1990 (ATM just being born) nowadays, with ⅓-pixel positioning of strokes, this is way out of question. However, AFAIK, this theory is completely bogus. Thanks in You continue to mis-interpret what I said. So please guide me in the right direction. I can adopt it to suit the tool input format if needed. I have all bitmap data, kernings, sizes, etc for that and possible to define kerning pairs in pixels (or other values).glyph overalapping must be supported of course.alpha-maps) must be 1:1 preserved on the display, i.e. must be possible to compile it programmatically, because otherwise I will spend a good.If yes, still I want to note the requirements (so as not to end up in misunderstanding): ![]() Is it possible to generate such Windows-compatible font from my bitmaps (8-bit maps)? There is a TTF 'bitmap strikes' - this info I have found on the FontForge main page.But maybe there is some newer reincarnation of that format? So this option is out, because there is no chance to avoid cutted pixel sides I have read the docs,īut now I am thinking - even if it supports graymaps, then it stillĭoes not support kerning and glyph overlapping (correct me if I am wrong), So it might support graymaps also, I am not sure. I have some of those on my PC,īut they seem to show-up only in 1-bit, though MS docs say: I already have bitmaps, and everything for that. I want to create a bitmap-only font on Windows, so it can be registerd in platform. So I think it is ok to post a question here, and it is merely a general fontĬreation question, but probably you can guide me. (I was about to ask on nabble forum but it seems it's in archive mode) I am new to Fontforge and it's my first post here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |