Thanks again to Anak for the helpful information. I got
Type light, a free font editor. No idea if it's any good, but it's free and allowed me to change all the font names, so that now everything is hunky dory.
Still, as the owner of "the only premium e-reader on the market" I definitely shouldn't have been required to deal with this problem. (Are you listening, Kobo?)
Quote:
|
The font name used in naming the font file must be the font name (Windows font viewer) or font family (FontForge) embedded in the font file -- if a font is named GillSans-Bold.ttf but the internal name is Gill Sans, the file must be renamed to Gill Sans-Bold.ttf to work on a Kobo ereader. Alternately you can edit the font family name but much easier, in my opinion, to change the font file name.
|
Not true. I've had fonts ending in stuff like "It" or "Reg" or "Med" in their internal names, and then changing the font file name is of no use at all.
Quote:
|
One note is that the Kobo supplied fonts render correctly for .kepub.epub files using the ACCESS NetFront BookReader renderer. To me, this indicates that the issue is with the Adobe Reader Mobile SDK which Kobo does not appear to be enthused about spending time and resources on given their involvement in the Readium project.
|
You're kidding, right? Nobody told me the Aura only works properly with kepubs. It says it's for reading epubs. Since they advertise with some review's phrasing that the Aura is "the Porsche among e-readers", let me draw this parallel: It's like buying a Porsche that only runs smoothly on petrol bought at Porsche's own filling stations. If you buy your petrol somewhere else, you have backfiring and whatnot. When you complain about this you are told: "So what? It runs fine on our petrol. Of course, in theory, it should also work with other petrol, but you know what? We just can't be arsed to fix that, mate. We've got other priorities just now."