View Single Post
Old 10-15-2008, 07:36 AM   #5
murraypaul
Interested Bystander
murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.
 
Posts: 3,224
Karma: 10210627
Join Date: Jun 2008
Device: Sony PRS505, Nook Color(CM7), iPad3
Quote:
Originally Posted by llasram View Post
Capitalization is relevant[*]. The Reader-internal path is "Data", with just the initial 'D' capitalized. Then created just 'FONT' in the Reader-internal memory and put your font-file there.
[*] But only up through the 'Data' part. It's complicated.
Thanks. That (plus realising I hadn't properly understood what the CSS needed to do) has fixed the problem.

This is pretty impressive, it seems like it might be slightly slower paging forward several pages in a go than LRF or and ePub without a font specified, but it is hard create a fair comparison because there is now a different amount of text on the page.

I hadn't realised how much faster ePub was to open and change text size than LRF either, not having to recalculate the number of pages makes a huge difference, from 10 seconds to open to 1, from 22 seconds to change font size to around 6.
murraypaul is offline   Reply With Quote