Thread: Page break at sentence....?
View Single Post
Old 05-19-2022, 10:43 PM   #14
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 se1961 View Post
That is too much, even for me! I guess I will stick with my DOCX workaround. I'm surprised there's no way to set the "keep lines together" formatting command when converting to DOCX in Calibre..

I think from your section post that you were saying you couldn't get "Natural Reader Online" to work with epubs-- it did work for me, when I created the epubs in Calibre. But it was almost useless, because NRO then generates a PDF with completely unusable settings (teeny tiny fonts, etc..) If you want to test it out, I think it make the most sense to create a PDF the way you like it, and then import the file to NRO-- since it doesn't do any conversion to a PDF, I presume it would import without error.
What that says is that the problem is in "Natural Reader Online". This demonstrates that they have taken a cheap solution, convert to PDF and use someones TTS solution without truly knowing who it works. Have you tried using calibre to convert the epub to PDF and then running the TTS that is on your computer? I suspect you will get the same pause at the end of a page.

But, you have missed something that was sort of suggested. A mention was made of widows and orphans. These are used to keep parts of a paragraph together over the end of a line. The default is 2 or 3. Most people want 1 as that fills the screen as much as possible. Using a much higher number will mean less paragraphs get split over a page. If you use a number that is more than half the number of lines in the longest paragraph, then the paragraphs won't get split (unless they are longer than a page). That has worked for someone on an ereader where they wanted this. I don't know if it will work for the PDF render that the tool is using. If they actually said what backend tools they use, you could get an idea of whether it would work or not.

And for the record, it didn't. And I wasn't impressed with the handling of some of the text. The test case I used has a heading for "Chapter n" and the first letter of the first paragraph after this is a drop-cap. After processing the file, it read that first letter, then the heading and then the rest of the first word. That's pretty crappy behaviour and make me question what else they get wrong.
davidfor is offline   Reply With Quote