MobileRead Forums - View Single Post

brewt · 12-31-2008, 02:59 PM

Man, this has been just stumping me - thank you.

Would it be oh-too-much-to-ask to suggest some kind of an output report from epub-making that would warn of pieces in the epub being bigger than 300k? I've been beating my head against the wall for some a week (a whole week!) now, as it is the reading devices that have the problem with the 300k limit, not the reading softwares on the computers.

Epubcheck doesn't pipe output to a file, so if I've got a gazillion warnings, it's hard to catch the over-sized-edness of a piece in a dos window.

I've got one file that has 1200+k in a css, for example. (Converted from an pdf-then-rtf file that was destined for print, and whoever made that, made it totally beautiful for print, with oodles of individual styles for individual lines. No darn good for electro-reading, but great for paper.)

Thanks again for your help and consideration.

-bjc

12-31-2008, 02:59 PM	#3
brewt Boo-Frickety-Hoo-Erizer Posts: 251 Karma: 686 Join Date: Oct 2007 Device: Kobo Glo HD!	Man, this has been just stumping me - thank you. Would it be oh-too-much-to-ask to suggest some kind of an output report from epub-making that would warn of pieces in the epub being bigger than 300k? I've been beating my head against the wall for some a week (a whole week!) now, as it is the reading devices that have the problem with the 300k limit, not the reading softwares on the computers. Epubcheck doesn't pipe output to a file, so if I've got a gazillion warnings, it's hard to catch the over-sized-edness of a piece in a dos window. I've got one file that has 1200+k in a css, for example. (Converted from an pdf-then-rtf file that was destined for print, and whoever made that, made it totally beautiful for print, with oodles of individual styles for individual lines. No darn good for electro-reading, but great for paper.) Thanks again for your help and consideration. -bjc