Quote:
Originally Posted by PeterT
The kepub renderer uses another font if there are symbols missing in the font called for. The Epub renderer displays a [] for missing symbols.
|
Well, we all know THAT, you’re just stating the obvious here.
But the average user doesn’t ask or even care WHY there is gobbledygook on their screen. They couldn’t care less about WHY KOBO made that bad of a decision selecting a font that does not cover their or their favorite author’s/publisher’s needs. They just wanna have the experience they are expecting to get when they buy such a proprietary hardware.
Simply because:
• If all their apps on their tablets can render their books correctly so should their eReading device!
• If an .epub on their KOBO device can be rendered correctly so should their .kepubs !
• If tapping a link in one format produces the correct navigation so should a link in the other format on the same device!
We shouldn’t accept or even defend all those excuses for amateurish implementations from a company that pretends to be amongst the leaders of the pack.
As far as I remember complaints about KOBO’s faulty footnote implementation date back to 2015 and nothing has changed whatsoever in 2025.
Maybe YOU are just simply trying to stay on the positive side but there’s a time and place for everything, and in my opinion we are getting screwed over more and more, so I frankly am not willing to join you in your song of praise.
.