View Single Post
Old 11-28-2021, 10:48 PM   #495
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 Buhaj47 View Post
I have loaded a Polish hyphenation dictionary on my Kobo, and the plugin has an option to Hyphenate Files that can be selected. Hope someone can confirm:
  • will hyphenation be active if that option is not selected? (with the hyphenation dictionary installed on Kobo);
  • what if I have different number of minimum left and right characters set in the dictonary file on Kobo and the plugin itself - which is then used?
The hyphenation option adds CSS to either force hyphenation on or off. If neither option is selected, then whatever is already in the book is used. And if there is no hyphenation CSS in the book, it goes to the device. And that is basically if you use justification, then hyphenation will happen. If you use ragged-right alignment, then hyphenation won't be done.

As to which values are used. I don't know. I don't like the way the devices do hyphenation, so I remove the justification from the books and use ragged-right alignment on the device.
Quote:
PS. The default option is to split files larger than 260 KB - any issue if this is increased? I have a book where where one xhtml file is larger than that, and don't want to split it so that chapter page count displays correctly.
It doesn't matter. The conversion to kepub is basically a conversion to kepub plus adding Kobo specific things. That option is for Adobe RMSDK based ereaders (used in lots of places but used for ePubs on Kobo devices). It has issues with files larger than this. The renderer used for kepubs does not have this issue. You can go bigger, but, you might hit performance issues if you go past a couple of megabytes. It's been a while since I have bothered testing, so I don't know where it is likely to happen.
davidfor is offline   Reply With Quote