View Full Version : TOC causes PRS-505 reboot


rijidij
03-01-2009, 03:20 PM
Hello all,

This is my first post, so please excuse me if this has been covered before.

I have just tried converting a text file to ePub using Calibre, and selecting the Table Of Contents causes my eReader to reboot.
Has anyone else experienced this?

Here is my procedure for creating the ePub document.

Open the text file in OpenOffice Word Processor. Set document title style to Heading1, author name to Heading2, and chapter titles to Heading3.
Save document as HTML format.
Open HTML file in jEdit and add "page-break-before:always" to CSS for H3 tag.
Add HTML book to Calibre library, and convert to ePub.
Upload to PRS-505


I can read the document and view the TOC with no problems using the Calibre built-in reader.
On my eReader it is very slow to change between chapters, and when I select the TOC, the spinning arrow appears and then, some time later, the reader reboots.
The TOC menu shows the correct number of items.

Also, accented characters appear as "?" in both readers.

Advice and suggestions gratefully received.

Thanks,
Craig

dschill
03-01-2009, 03:29 PM
I had a article ready to paste to you but when i looked it must have been deleted from my favorites somehow im sorry http://photosnag.com/img/3045/y09w0131xdtc/82(2).gif

kovidgoyal
03-01-2009, 06:16 PM
This usually happens if the the generated epub file has markup too complex for the reader to process and it runs out of memeory/crashes and reboots. For the ? issue use the correct encoding option in calibre for the conversion. The encoding must match the encoding of your txt file

rijidij
03-02-2009, 12:01 PM
Thanks for your replies.
I'll try simplifying the HTML and re-converting it.
Although I'm not sure what else can go..? It's not much more than <P> & <H> tags...

Thanks again,
Craig

kovidgoyal
03-02-2009, 12:47 PM
If you can'r figure ti out open a aticket and attach thext file and I'll have a look

rijidij
03-02-2009, 05:43 PM
I just had another go at this.
I deleted all the inline style dross that the Word Processor insisted on inserting, and ran it again.
It parsed in 17 seconds flat! And it runs like a dream. Chapters, TOC, the lot!

Thanks again for your help.
Craig