Thread: Bible Framework
View Single Post
Old 12-15-2015, 08:58 PM   #38
ProDigit
Karmaniac
ProDigit ought to be getting tired of karma fortunes by now.ProDigit ought to be getting tired of karma fortunes by now.ProDigit ought to be getting tired of karma fortunes by now.ProDigit ought to be getting tired of karma fortunes by now.ProDigit ought to be getting tired of karma fortunes by now.ProDigit ought to be getting tired of karma fortunes by now.ProDigit ought to be getting tired of karma fortunes by now.ProDigit ought to be getting tired of karma fortunes by now.ProDigit ought to be getting tired of karma fortunes by now.ProDigit ought to be getting tired of karma fortunes by now.ProDigit ought to be getting tired of karma fortunes by now.
 
Posts: 2,553
Karma: 11499146
Join Date: Oct 2008
Location: Miami FL
Device: PRS-505, Jetbook, + Mini, +Color, Astak Ez Reader Pro, PPW1, Aura H2O
Quote:
Originally Posted by Toxaris View Post
Depends on your target audience. In general smaller HTML files will result in snappier ePUB's, since they have to load less in memory each time. Older readers (and yes, they still exist) will choke on HTML files larger than 285kb.
Readers usually don't have much memory and top of the line CPU.
I have tested several bibles on my Sony PRS-505. From what year would you say readers are considered 'older'?

The 2008 PRS-505 did a good job with a nearly 3MB HTML file (if memory serves me correctly). The only problem it had, was it sometimes didn't follow all the html links correctly, probably a memory issue.

I'm thinking to indeed do each book separate, 66 separate html files, and use internal linking to the chapters.

Last edited by ProDigit; 12-15-2015 at 09:00 PM.
ProDigit is offline   Reply With Quote