Quote:
Originally Posted by Corpsegoddess
Same thing happens to me, also at least once a book (of any length). I also only read epubs.
|
The sony has it to... long paragraph bug.
It is not a real bug.. the sony has it's internal memory, not the storage one, but the "working" memory.
So I was working with the 550 and I make ebooks myself ( I mean, scanning them from paper from scratch) build the internal HTML files and then make an epub of it with abbyy.
When the HTML was longer then a certain length the 550 just freezed.
It doesn't know how to break a to long chapter into 2 pieces.
Solution was simple, more chapter breaks, more html files, so it would not crash.
Sended the bug report to Sony ( I have some short lines to Sony Netherlands) and in the 600 and 650 the working memory was bigger but the 600 still freezes when the internal html in the ebook was to long to place in the "reading buffer" so starting from the 650 the devices just load until the reading buffer is filled,and if the html file is still to long, it breaks at that place, start filling the buffer, but you see a break,where it doesn't must be.
The third party Sony devices just load into memory but they "look" if there is a "soft coded" chapter break somewhere (where a new chapter begins) and it only reads into memorybuffer to there, and then fills the buffer again so it doesn't wait to the end of the html. ( the real hard coded chapter break)
But I am sure if I make a wrong one,without breaks, long enough, it will crashes or shows a break where it doesn't has to be. (empty the buffer and refill it.)
When I make a book from scatch, I insert a chapter break at every place there is a real one in the book, so every html file, has the exact lenght of a chapter in the real book.
When I have the wrong break at the Kobo and I look into the book,and it's a pre made, I see that sometimes 3 chapters of a book,or even more, don't have a hard coded chapter break in it but only the instruction to leave the rest of the page empty and start at a fresh one, so I edit it with Sigil and insert a real chapter break, so i end the HTML file where the chapter in the book ends...and the second time I read it, there will be no "false" break.
I think that the new 3.5.0. "looks" like the new Sony Generation where a chapter has to end ( there is some code in the book that instructs the device to begin at a new page, but not a real new end or beginning of the html) and it only loads to there into the reading buffer...
But there will be problems,because some "bookmakingprograms" have a hardcoded entry just to make chunks of HTML of a certain length and insert a chapter break from there, they devide a book from 600 pages into 2 chunks of HTML and the break is into somewhere, just in the middle, not at the "real end" of the chapter and if a device uses the old technique, the sony 550 will crash because of the length of the html or the new ones produces a false chapter break.
Don't fill the "reading" buffer until it's full, just fill it where the instruction is to start a new chapter and you will not have the break..until the maker of the book doesn't use chapters at all, or doesn't instruct the device to start at a fresh page but just insert 2 blanc lines and then a new chapter title, then you see a chapter title in the middle of the page with 2 blanc lines and sometimes a graphical devider like ~~ more and more books have this...it is the choice of the writer if he wants to start the chapter at a new fresh page or just use "deviders" but doesn't stop the chapter from there, if then the html is longer then the memory buffer is,you will have the "bug" again...