[GUI Plugin] Hyphenate This!

[Ptitprince]

Hello SauliusP,

Is it possible to put your plugin on transifex like other plugins? I'll be glad to translate it into french.

Regards

[bart86]

Hi all,
I have problem that is not directly related to this plugin. After sending books by mail some of them are not hyphenated even if converted mobi files (Calibre) are all ok. It is a bit frustrating and I don't want to go back to upload files by usb. The problem is related to Amazon servers but I thought that maybe someone has similar problem before and found some solution. Thank you.

[Ruskie_it]

Originally Posted by bart86

Hi all,
I have problem that is not directly related to this plugin. After sending books by mail some of them are not hyphenated even if converted mobi files (Calibre) are all ok. It is a bit frustrating and I don't want to go back to upload files by usb. The problem is related to Amazon servers but I thought that maybe someone has similar problem before and found some solution. Thank you.

I am sorry I can't help. I never use send books by email because I really really hate (and find uncomfortable) the send by mail to my Kindle.
First, it forces me to turn on wireless, wich apart from battery consumptions exposes me to unwanted firmware updates.
Second, if I'm not mistaking, it is limited to mobi, and mobi is an inferior format (it lacks for example page count and I think also the kindle reading time doesn't work with mobi).

That said, it seems really strange to me that sending it via mail breaks hypenation: infact, hypens are written directly into the text of the book, the html changes, it's not some "extra file" or a suffix of the mobi file that could be stripped down in a transfer, it would require active and explicit tampering of a text processor, and it seems unlikely to me that something does this.

Edit: I have looked around, and if you look carefully at first post in this thread, hypenate this! does not support mobi files:

Supports EPUB and AZW3 formats (no MOBI, even with KF8 inside, convert instead).
[...]
Note, that if you hyphenate EPUB or AZW3 and convert to "old" MOBI, hyphenation won't work.

[shamanNS]

@Ruskie_it: If you hyphenate epub and then convert it to "dual mobi" /"combo mobi" (contains both "old mobi" and "KF8" sections in one file with .mobi extension, and KF8 portion has soft hyphens) and send that to Amazon usually azw3 file gets delivered to your Kindle and all is good.
I'm guessing that @bart86 is using that workaround (because Amazon's PDOCs service doesn't accept KF8-only books) and for some reason for certain books ends up with "old mobi" being delivered.

Also you're wrong : Reading Time feature work with "old mobi" format since it only needs .NCX to "know" what constitutes a chapter.

[JSWolf]

Originally Posted by shamanNS

Also you're wrong : Reading Time feature work with "old mobi" format since it only needs .NCX to "know" what constitutes a chapter.

Then it's not possible for Reading Time to work with with Mobi because Mobi does not support NCX. KF8 doesn't support NCX as well. It's all an HTML ToC.

So however Reading Time does work, it's not based on an NCX ToC.

[Ruskie_it]

Originally Posted by shamanNS

@Ruskie_it: If you hyphenate epub and then convert it to "dual mobi" /"combo mobi" (contains both "old mobi" and "KF8" sections in one file with .mobi extension, and KF8 portion has soft hyphens) and send that to Amazon usually azw3 file gets delivered to your Kindle and all is good.
I'm guessing that @bart86 is using that workaround (because Amazon's PDOCs service doesn't accept KF8-only books) and for some reason for certain books ends up with "old mobi" being delivered.

Also you're wrong : Reading Time feature work with "old mobi" format since it only needs .NCX to "know" what constitutes a chapter.

I see, I didn't know about this complex behaviour while sending docs to Amazon. Yet I find this much more unpractical than using usb cable. 😊

Regarding mobi, perhaps I remember it wrong, but I am write sure it does not support page numbering at least. But if you say that an azw3 is delivered anyway, this doesn't matter as well.

Inviato dal mio SM-G935F utilizzando Tapatalk

[mgrmgrde]

Let me ask my questions from March once more:

1. Can you change the type of the custom field from text to a Y/N field? I think the three states of Yes/No/undefined are a better selection than text column.

2. As I use sigil as my e-book editor: can you replace the hex-code  with another &x....; sequence so I can edit a book in sigil too without a lot of spelling marks.

I think that would make this fabulous plugin a bit (for me a lot) better

TIA for considering these suggestions

[shamanNS]

Originally Posted by JSWolf

Then it's not possible for Reading Time to work with with Mobi because Mobi does not support NCX. KF8 doesn't support NCX as well. It's all an HTML ToC.

So however Reading Time does work, it's not based on an NCX ToC.

Wrong & wrong.
If you've ever owned a Kindle you would know the following:

1) Even Kindle 2 & 3 used NCX ToC in "old mobi" format to display chapter markings on progress bar and for skiping to next/previous chapter via D-pad right/left buttons. Those Kindle models (or to be more precise firware 2.x & 3.x branches) used HTML ToC for "Go To" menu (as in no HTML Toc inside book = disabled "Go To" menu option". So books in old mobi format had and used (for different things, as stated above) both "inline" (= HTML) and "logical" (NCX) ToCs.

2) Newer Kindles using firware 5.x use NCX ToC for everything. As in it parses NCX ToC and populates "Go To > Contents" menu (just like it parses apnx for page numbers and ads that info beside each chapter title). HTML ToC is there only for legacy. Reading time feature just replaced the role chapter marking and progress bar of older Kindles when Amazon removed the progress bar, and thus also/still uses NCX file to "know" chapter borders.

No idea where Kindle 4 (firmware 4.x) devices stood, since I've never owned one.


One notable difference is that older Kindles didn't support multilevel (nested elements) elements in NCX and fw 5.x Kindles do support it (but the parsing logic has a known bug on all newer firmware build since 5.3.x build for PW1, that the first element of NCX can't be nested or it will not be expandable = you only get the top most elements title, child elements are missing).


I find it very strange that you're known for using KindleUnpack (I recall you being very annoying when reporting bugs on forum thread) and yet apparently you never spent time to learn what unpacking old mobi files gets you. But that didn't stop you from commenting here and spreading incorrect information (with air of authority) ...

@Ruskie_it: I haven't used old mobi format books in ages but I think I remember Calbre generated .apnx files working just fine with old mobi format books. You're correct in that you can't email those extra files...

[JSWolf]

How do you make an NCX for Mobi? Mobi doesn't use NCX. If your source file is a Word document or an HTML file, where's the NCX?

[Ruskie_it]

Originally Posted by shamanNS

@Ruskie_it: I haven't used old mobi format books in ages but I think I remember Calbre generated .apnx files working just fine with old mobi format books. You're correct in that you can't email those extra files...

I'm sorry I'm not as technical as you are for what concerns inner file formats details: are you implying that page numbering works with mobi files as well (as long as they have been converted to mobi from another format and transferred to kindle via calibre)?



Inviato dal mio SM-G935F utilizzando Tapatalk

[shamanNS]

Yes, but the information/mappings that Kindle uses for page numbers are not part of the book itself (not inside a mobi file) nor is Kindle doing calculations like epub readers using Adobe reading software are doing... the info is contained within ".apnx" file which for Amazon bought books gets downloaded alongside the actual book (and contains "real page numbers" = mapped to certain printed edition) and for converted book Calibre can generate "fake page numbers" (as in approximation of number of pages based on chosen algorithm) and send it to Kindle over USB when it's sending the book itself. I don't recall if Calibre does that by default nowadays or if you must first turn that option on. See the screenshot below to where to find that option:




I'm using "Count Pages" Calibre plugin to calculate number of pages based on number of characters per page and put it in custom column "#pages" and I've set Kindle device plugin to use that column value when creating .apnx file.

[Hammond]

Hi,

First, I would like to thank you for this excellent plugin. I have one quasetion. Is there any option or way to limit the maximum number of following lines end with hyphenate? Now there is often situation when I have for example 4 lines with hyphen. The limit should be (in my language – czech) max 3 following lines and than min one line without it.

Thank you

[JSWolf]

Originally Posted by Hammond

Hi,

First, I would like to thank you for this excellent plugin. I have one quasetion. Is there any option or way to limit the maximum number of following lines end with hyphenate? Now there is often situation when I have for example 4 lines with hyphen. The limit should be (in my language – czech) max 3 following lines and than min one line without it.

Thank you

It's not possible to limit the number of consecutive lines with hyphens. There is no way for the plugin to know anything about how the hyphens will end up and where.

[Csabi]

Hi Guys!

First of all, I would like to thank for this plugin. This is really I was looking for.
My native language is hungarian and I read hungarian novels most of the time.
I downloaded this dictionary for the hyphenate plugin:
http://extensions.openoffice.org/en/...-pack-20101019


I noticed some strange spellings after hyphenating my books. Let's see some example.
After hyphenation:
"vissza" becomes "viszza"
"mennyi" becomes "menynyi"


I don't know is it a hyphenate bug or just a dictionary issue?

Thank you for your help!

[shamanNS]

@Csabi: The problem with hyphenation of hungarian language is mentioned several times in this thread. Do a search (by clicking on "Search this thread" link on the top of the page) for "hungarian" and you will find those posts.

To me the most informative post looks to be this one:
https://www.mobileread.com/forums/sh...&postcount=211