View Single Post
Old 02-25-2014, 02:45 PM   #38
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by Katsunami View Post
By the way: If I have to specifically edit EPUBs for a particular reader (apart from converting them to another format), while they are otherwise perfect and without problems, then I certainly don't want the device.
Then it's only fair to warn you ... whilst I can see no reason why your existing epubs shouldn't transfer to/open/read on a Kobo, if you want the the font customisation options to work perfectly on every epub then you may need to consider how you normally set your epub css.

For example, when I buy a new book I often see hard-coded font-family and line-height settings on practically every body/p/div/blockquote class in the css file. Letting them remain there in the converted epub is a sure way of making the on-device Kobo font-family menu and line space slider ineffective. In fact, every css attribute, which the Kobo can override (in theory), needs to be used sparingly and with care in your epub's internal css to ensure all font adjustments remain possible.

Last edited by jackie_w; 02-25-2014 at 02:53 PM.
jackie_w is offline   Reply With Quote