![]() I saw the glyphs become heavier while they were processing, and the files ultimately generated properly. Besides this, the only things I've touched were the font names and PANOSE settings - all other errors were usually ignored. To add the weight, I simply selected all the glyphs and added some weight in the Element - Style - Change Weight - Embolden by, and left everything else alone. I was able to correct the PANOSE settings, but again the added weight did not work. Oh boy, what a garbled mess that thing is. (Note, this might have been a consequence of different Font Forge versions - to be certain that the scripts would work, I used the 20 versions respectively, as those were the versions active when the scripts were written.)įinally, I gave up on the scripts, opened up the latest release of Font Forge for the very first time and decided to do it all manually. I tried Koboify Fonts 0.3.1 and the latter Readify Font scripts - both refused to embolden the fonts, and in some cases even failed to alter PANOSE settings. So I set out to learn how to fix these things. To top it off, about half of the fonts had bad PANOSE settings, which was apparent in the selection menu. The heavier fonts like Galliard could use about 10-15% more weight to reach perfection. ![]() spidery on my Aura One), they are still a bit on the thin side. Though not nearly as bad as Adobe's Garamond or Jenson (perfect, beautiful fonts, if only they were not so. While I actually love the look and feel of all the fonts - spacing, line height, etc, I honestly wouldn't change any of it - the weight leaves something to be desired. From the marketing spiel, I was hoping that they would be almost ideal for eInk, due to the "super special" technology that was supposedly used in crafting them. Anyway, after harassing my friend well and good, I managed to badger him into giving me the full set of those nice-looking "eText" font redesigns that were released a few years back. I like some serif goodness in my fonts, but an occasional slab can also be appealing. I've pretty much been on the excellent ChareInk since the moment I discovered it, but I still enjoy looking up and testing fonts that seem promising. The final guide I wanted to add was the top of the innermost letter, and that was at 108 pixels up.I've been on the lookout for nice fonts since the day that I got my Kobo. ![]() The most important line in the typeface was the line that threads all the letters together, and I could see this was centred at 40 pixels up, so that was another guide. So I added two vertical guides at 102 pixels apart. Now I could work out the width of the letter a, which turned out to be 102 pixels. So I created two horizontal guides, 120 pixels apart, then scaled the scan of the font so that the letter a was also 120 pixels tall. So I decided to draw my characters at 120 pixels high in Inkscape as I thought that would mean I would have a good chance that if I did the various elements of the font would sit on nice round numbers. The letter a was 96pt which, on a 90dpi display, is 120 pixels. The first thing I decided to do was base my drawings on the large, clear 96pt letter 'a' at the top right of the scan. In a moment of madness, I decided it might be a nice exercise to try and draw the font myself using my old friends Inkscape and FontForge 2.0.
0 Comments
Leave a Reply. |