![]() Instructions in this glyph (or one that refers to it) have been lost". The glyph named Omega is mapped to U+03A9.īut its name indicates it should be mapped to U+2126.Īfter modifying the weight, I would also get errors in some of the font points citing "You have changed the point numbering of glyph XY. Warning: Mac and Windows entries in the 'name' table differ for theįullname string in the language English (US) The 'kern' table will only be read if there is no 'kern' feature in 'GPOS'. This font contains both a 'kern' table and a 'GPOS' table. Ignoring 'hdmx' horizontal device metrics table Ignoring 'VDMX' vertical device metrics table The following table(s) in the font have been ignored by FontForge I've tried experimenting with removing the errors, auto correcting and ignoring them, to no avail. It may very well be that these fonts have some special tables that prevent the emboldening to appear on my device? I've placed the typical warnings I get when tinkering in Font Forge in the spoiler below, and I've summarised some of the errors that crop up when adding weight. (Throughout this process, I made sure to check for leftover Kobo font or reading settings, custom sharpness or weight values.) ![]() The regular font remained the same weight, and the italic font became regular bold. To make things even more confusing, once I figured out that there was a problem, I tried to substitute a medium and medium italic font for the regular ones by renaming the set properly, hoping that that would result in a change - it did not. 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. I've been on the lookout for nice fonts since the day that I got my Kobo.
0 Comments
Leave a Reply. |