View Single Post
Old 12-08-2010, 10:40 PM   #5
NASCARaddicted
Addict
NASCARaddicted herds cats with both ease and graceNASCARaddicted herds cats with both ease and graceNASCARaddicted herds cats with both ease and graceNASCARaddicted herds cats with both ease and graceNASCARaddicted herds cats with both ease and graceNASCARaddicted herds cats with both ease and graceNASCARaddicted herds cats with both ease and graceNASCARaddicted herds cats with both ease and graceNASCARaddicted herds cats with both ease and graceNASCARaddicted herds cats with both ease and graceNASCARaddicted herds cats with both ease and grace
 
Posts: 340
Karma: 43106
Join Date: Apr 2009
Location: Germany
Device: BeBook One, Pocketbook Touch, Pocketbook Touch HD
I haven't had very much problems with ADE, but from wha I have seen so far, I believe, that most of the bugs that everyone mentions appear on handheld devices. And I think the majority of the readers uses the ADE parser. At least Sony and Hanlin (and all it's clones like Bebook) uses ADE.

One bug that I experienced is this: I have this one ebook. There are 3 "special" (hebrew) characters in the ebook. I found them in the unicode table so I just added them to my ebook. I cheched my base file (the html file) with Firefox and the hebrew letters showed up. Then I converted it with Calibre and looked at it with the Calibre ebook-viewer and the hebrew letters showed up. Then I copied the epub on my ebook and looked at it - and instead of the hebrew letters, I ended up with "?". And as far as I know, this is one of the bugs - no full support of all unicode characters.
NASCARaddicted is offline   Reply With Quote