View Single Post
Old 11-03-2020, 06:46 PM   #22
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by james_ View Post
Thanks David for all your investigation. I'm going to ask the people producing the tickets to fix it, as clearly this isn't a "Kobo" problem.

However, clearly Kobo have a particularly inept programming team. If pretty much every other device out there can read this PDF then you have to ask why Kobo have such a badly written PDF parser that it drops dead at the slightest sign of trouble.
It is inept to follow well published standard? Sorry, but no. Producing files that don't follow the standards is inept. Handling files that don't follow the standards without even a warning, again, inept. But, making sure your system works even when crap is thrown at it, not inept. And deciding to throw away the crap rather than take a guess at how to handle it, again, not inept. Especially when doing this in a resource constrained environment.
davidfor is offline   Reply With Quote