View Single Post
Old 09-28-2019, 09:23 AM   #1
Alanon
Connoisseur
Alanon is clearly one to watchAlanon is clearly one to watchAlanon is clearly one to watchAlanon is clearly one to watchAlanon is clearly one to watchAlanon is clearly one to watchAlanon is clearly one to watchAlanon is clearly one to watchAlanon is clearly one to watchAlanon is clearly one to watchAlanon is clearly one to watch
 
Alanon's Avatar
 
Posts: 76
Karma: 10742
Join Date: Jul 2017
Location: Serbia
Device: Kobo Aura One
Font Forge and adding font weight for Kobo?

I've been on the lookout for nice fonts since the day that I got my Kobo. 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 like some serif goodness in my fonts, but an occasional slab can also be appealing. 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. 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.

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. Though not nearly as bad as Adobe's Garamond or Jenson (perfect, beautiful fonts, if only they were not so... spidery on my Aura One), they are still a bit on the thin side. The heavier fonts like Galliard could use about 10-15% more weight to reach perfection. To top it off, about half of the fonts had bad PANOSE settings, which was apparent in the selection menu. So I set out to learn how to fix these things. 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. (Note, this might have been a consequence of different Font Forge versions - to be certain that the scripts would work, I used the 2015 and 2016 versions respectively, as those were the versions active when the scripts were written.)

Finally, 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. Oh boy, what a garbled mess that thing is. I was able to correct the PANOSE settings, but again the added weight did not work. 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. Besides this, the only things I've touched were the font names and PANOSE settings - all other errors were usually ignored. I saw the glyphs become heavier while they were processing, and the files ultimately generated properly. 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. The regular font remained the same weight, and the italic font became regular bold. (Throughout this process, I made sure to check for leftover Kobo font or reading settings, custom sharpness or weight values.)

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. I've tried experimenting with removing the errors, auto correcting and ignoring them, to no avail.

Spoiler:
The following table(s) in the font have been ignored by FontForge
Ignoring 'ADFH'
Ignoring 'DSIG' digital signature table
Ignoring 'VDMX' vertical device metrics table
Ignoring 'hdmx' horizontal device metrics table
This font contains both a 'kern' table and a 'GPOS' table.
The 'kern' table will only be read if there is no 'kern' feature in 'GPOS'.
Warning: Mac and Windows entries in the 'name' table differ for the
Fullname string in the language English (US)
Mac String: Galliard eText ITC ITC
Windows String: Galliard eText ITC
The glyph named Omega is mapped to U+03A9.
But its name indicates it should be mapped to U+2126.


After modifying the weight, I would also get errors in some of the font points citing "You have changed the point numbering of glyph XY... Instructions in this glyph (or one that refers to it) have been lost".

When generating the font, I'd get "Self Intersecting, "Missing points at Extrema", "Wrong direction", "Non-integral coordinates", and "Bad Point Numbering" errors, that I ignored.

Based on my random tinkering, not ignoring some of these completely garbles question marks and the like.


I've no idea what these errors mean or if they're critical or not. I have no clue what to try next and I'm very close to throwing in the towel and using Galliard as-is, which leads me to the question for all you knowledgeable font nerds around here. Am I doing it wrong? Is there some additional step in Font Forge that I missed, which might cause the changes to go wonky? The errors I've tried to describe might mean something to someone, at least enough to point me in the right direction.

I appreciate you sticking with my long-winded narrative, and I'd also appreciate any thoughts you might have on where to go from here!


As an aside, I've included screenshots of all the eText fonts I have installed. In case you were thinking of, or still considering, getting any of them, you can see if they're worth it. One thing I can say, they look substantially... more substantial on the screenshots than on the device itself. Note that there are more fonts in the pack (like Amasis, Malabar, Caecillia, etc.), but they overlap with what comes default with Kobo, and there seems to be some interference there, so I can tell you nothing about them.
Attached Thumbnails
Click image for larger version

Name:	Baskerville.png
Views:	439
Size:	147.0 KB
ID:	173767   Click image for larger version

Name:	Dante.png
Views:	432
Size:	148.4 KB
ID:	173768   Click image for larger version

Name:	Didot.png
Views:	378
Size:	143.5 KB
ID:	173769   Click image for larger version

Name:	Galliard.png
Views:	402
Size:	157.3 KB
ID:	173770   Click image for larger version

Name:	Halesworth.png
Views:	403
Size:	155.5 KB
ID:	173771   Click image for larger version

Name:	Palatino.png
Views:	351
Size:	150.4 KB
ID:	173772   Click image for larger version

Name:	Sabon.png
Views:	350
Size:	151.0 KB
ID:	173773   Click image for larger version

Name:	Tipperary.png
Views:	369
Size:	139.9 KB
ID:	173774   Click image for larger version

Name:	Ysobel.png
Views:	355
Size:	139.8 KB
ID:	173775  
Alanon is offline   Reply With Quote