On #2887064: Cannot build PDF files for right-to-left languages, comments #18 and #22, it was noted that the Mobi format is not working for Persian/Farsi, a right-to-left language.

This is the same issue as:
https://bugs.launchpad.net/calibre/+bug/1073414

That issue says to use the AZW3 format instead of Mobi. Mobi is an old format that doesn't support RTL languages, but the newer AZW3 format (which includes Mobi as a fallback) does.

However, I tried building AZW3, and it still seemed to be backwards... it could be the reader though.

So, on this issue, we need to:

a) Try building AZW3 again.
b) Look at the output on a newer Kindle device or Kindle app that supports AZW3. I think the generic ebook reader on Ubuntu may not.
c) If this output is fine, switch the ebook scripts to build AZW3 files instead of, or in addition to, MOBI.

Comments

jhodgdon created an issue. See original summary.

  • jhodgdon committed 3104d87 on 8.x-3.x
    Issue #2901068: MOBI format not working for right-to-left languages
    
jhodgdon’s picture

Status: Active » Needs review

OK, I've created AZW3 files...

I am unable to tell whether they are working or not. Using the generic e-reader on my Ubuntu machine, they definitely do *not* look OK for Farsi -- they're an odd mix of RTL and LTR.

So, what I'm going to do is go ahead and commit them to the Git repository. Maybe someone else can test and see if the Farsi output is OK or not?

The .azw3 files can be downloaded from
http://cgit.drupalcode.org/user_guide/tree/ebooks
by clicking on the right-most links that say "plain" in each row of the table.

jhodgdon’s picture

Status: Needs review » Closed (won't fix)

Well, I loaded the Farsi AWZ3 file onto a fairly new Kindle Oasis, and it looked the same as on the Ubuntu e-book viewer: a mix of RTL and LTR. For instance, bullet points are on the left side instead of the right, but I think individual words are written RTL. Very odd.

Anyway... I don't know of anything else I can do to try to create a usable Farsi file for Kindle. It is possible that a Kindle Fire (which seems to be the format that AWZ3 is intended for) would be able to see it successfully, but I don't have one to test on. If someone else can test, great! Otherwise I will just leave the file in the Git repository and close this as "won't fix" I guess...