Quote:
Originally Posted by doubleshuffle
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.
|
I've never seen any font where the font family name included bold, italic, bold italic variants though I have seen several that used thin, black, etc. See the sample below from FontForge for DejaVuSerif-BoldItalic. The font family (what Windows font viewer calls the font name) is DejaVu Serif. To use this on my Kobo, I needed to rename the files for the four variants as:
DejaVu Serif-Regular.ttf
DejaVu Serif-Bold.ttf
DejaVu Serif-BoldItalic.ttf
DejaVu Serif-Italic.ttf
The -Regular is not actually needed but keeps the font names consistent.
With the font files correctly named, all I need to do is to copy the 4 files over to the fonts directory in the root of the Kobo's internal storage, power cycle the ereader and that font is ready to be used.
Quote:
Originally Posted by doubleshuffle
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."
|
Kobo does have other priorities -- the ACCESS NetFront BookReader renderer is likely to be more important to future corporate plans. Even Datalogics who now support the Adobe Reader Mobile SDK are waiting for the Readium project to produce their epub3 code which Datalogics is then going to wrap with Adobe's ADEPT DRM code.
The Aura works quite well with epubs other than a few glitches such as the very long paragraph bug. Overall, I've been very happy with my Kobos and I have used several other brands of ereader.
The font naming issue has been there since Kobo first introduced the ability to sideload fonts. I don't feel that having to specify the font file names is that big an issue. 3 of Kobo's internal fonts have issues with bold/italic and epubs but since I rarely use them, it's not a major issue for me. It is an issue (and a known one) with the Adobe Reader Mobile SDK from some digging I did a while back. I've never had any issues with add-on fonts since I first started using the correct file names.
Regards,
David