View Single Post
Old 11-16-2014, 03:59 AM   #406
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 arspr View Post
Nevertheless, as there's a dedicated thread for these issues I suppose we should use that thread instead of this general FW 3.11.
Yes, we should.

Quote:
Adobe is the PARENT of pdf... So I agree with you, if pdf are managed through RMSDK (I really don't know) and the problem is in RMSDK and not in Kobo implementation of it, yes it's should be quite embarrasing for them, because, as Ken Maltby insisted, Koreader has no problem rendering them...
PDFs are handled but the RMSDK. You just need to open one and look in the "Digital Editions" directory for the evidence.

Making the above statement makes me realise I have no idea how the other formats are handled. CBZ/CBR, MOBI, TXT etc. They can all be read on the device, but I've never bothered to look for what is doing it.
davidfor is offline   Reply With Quote