Quote:
Originally Posted by Uncle Robin
If the three fonts are the ones in the attached screenshots, then yes, they too fail.
|
Yes, those are the ones. And I'm not surprised they didn't work properly. That's why I added the extra bit on my post as I realised they probably wouldn't be any different.
Quote:
|
Arial Unicode MS and Noto Sans both display perfectly. Perhaps the publisher should have embedded a suitable font, but I still feel that a customer should be able to expect that when they a book from from Kobo, they will be able to read it as is on any Kobo, without need of sideloaded fonts.
|
But, on the other hand, the publisher should know the likely limitations of the readers and apps. They should not be assuming that some esoteric (to most of use) glyph is supported. That the book worked elsewhere is almost a fluke. They worked because those applications fell back to other fonts installed elsewhere. They might have used system supplied fonts that are much larger than practical on a resource constrained device like an ereader. Or they might have used a font you installed because you knew you would need it.
Kobo does tell publishers about this.
https://github.com/kobolabs/epub-spec#supported-fonts has information about font handling and different languages. It recommends embedding a font if there are any concerns.
For me, the biggest issue here is that there is no real indication that something is missing. In this case, there appears to be some extra spaces, but, it isn't always obvious when a something is missing. It would be much better to have something indicating this.