First of all, sorry as this is going to be a very verbose post (any longer post, guys?!) and sorry
ixtab in particular for gradually swaying your thread
Quote:
Originally Posted by NiLuJe
Like I said, FT's not in charge of the layout, which seems to be the issue here  . |
Yes sir. Confirmed. I was about to say that 6.8.1 is the reason alphabets are separated but to my great surprise I opened an article which had them connected! So I'm confused myself too!!! AZW3 reader is just buggy I think.
Quote:
Originally Posted by NiLuJe
Is this the only file you have an issue with in Persian? Or is it always broken? I'm not sure I understood if it's working correctly in mobi6, or if it's only 'working', but LTR?
|
No, issue is all over place, many books don't show up or if show up after a while they crash. Please read further.
Sorry to be confusing (as I'm too). So I'll try to make it clear, dissect and explain the issue here:
Spoiler:
TERMINOLOGY: mobi6 = mobi, mobi8 = KF8 = azw3 (right?!)
1. mobi documents:
With libfreetype.so.6.8.1: they're disconnected (
for sure).
With older libfreetype.so.6: fine.
(and in both case, obviously as mobi doesn't store RTL tags, words are from LTR
)
2. azw3 documents:
In both cases, RTL is fine. (so @
geekmaster: please discard my pm and previous posts.)
Very unstable results in both cases, so can't say anything as it's flaky, for some documents 6.8.1 shows them connected, for some disconnected. With older libfreetype, it's always connected as far as I have tried!!! So regardless of version of libfreetype, some azw3 documents show great, some are full white or full black pages.
Funny example:
When opening Persian_Sample_Article.azw3, first time, it shows the crash dialog that geekmaster talked about. Try to open it again... it opens a blank screen, but when you go to next pages (it takes forever, so be patient). You have to swipe a lot of times, and if you monitor it with "showlog -f" you'll see crazy amount of errors... continue swiping until it goes to location 18% or so and you'll see a page.
INTERESTING finding:
1. Try to Go To End page and you'll see a dialog that says "Before you go" Rate this book and share!!! I've never seen this for regular books!!! I don't know! Is this something Calibre adds to the book?
When swiping to next page:
2. Even after closing the bookreader, cvm has locked the azw3 books as when I try to delete it, it gives a .fuse file! gross.
Errors when reader crashes:
AZW3 Reader is crazy:
After opening first article, I opened Persian_Sample_Article_2.azw3 and after swiping back the reader showed me pages of Persian_Sample_Article.azw3 ?!!!
Reader crashes even after successfully rendering some pages! I'm sure it's not a memory full error as I checked it. It's just that AZW3 reader is not ready on KT yet.
Summary: @NiLuJe and @ixtab: As Kovid said AZW3 renderer of Kindle Touch is crap. It's very flaky, sometimes it opens the 2 sample files that I attached and sometimes not. The issue seems to be neither of marvelous FontHack plugin nor libfreetype, but AZW3 reader in KT.
I chose to let FontHack stay but with old libfreetype.
Anyways... until Amazon deals with AZW3 RTL languages, I'm going to convert to PDF or save as HTML and read it with CoolReader3. (Should find a way for HTML files to be shown on the home screen and put them in a collection with Collection Manager)
Quote:
Originally Posted by NiLuJe
Thanks for checking, though . (And check the log on the SVN stuff, I never delete anything, so there's stuff in there that I haven't used in a couple of years, if not more, so some stuff might be outdated ). |
I sure will... It's treasure. Keep it up baws (i.e. boss
).