View Single Post
Old 11-07-2009, 05:20 AM   #52
GeoffC
Chocolate Grasshopper ...
GeoffC ought to be getting tired of karma fortunes by now.GeoffC ought to be getting tired of karma fortunes by now.GeoffC ought to be getting tired of karma fortunes by now.GeoffC ought to be getting tired of karma fortunes by now.GeoffC ought to be getting tired of karma fortunes by now.GeoffC ought to be getting tired of karma fortunes by now.GeoffC ought to be getting tired of karma fortunes by now.GeoffC ought to be getting tired of karma fortunes by now.GeoffC ought to be getting tired of karma fortunes by now.GeoffC ought to be getting tired of karma fortunes by now.GeoffC ought to be getting tired of karma fortunes by now.
 
GeoffC's Avatar
 
Posts: 26,947
Karma: 17036296
Join Date: Mar 2008
Location: Scotland
Device: Cybook Gen3 , Pocketbook 302 (Black) , Nexus 10: wife has PW
Quote:
Originally Posted by quillaja View Post
To make columns in an ePub, use the following CSS property on any block element, such as "body" or "div":

Code:
oeb-column-number: [integer] | auto;
from the ePub OPS specification:



Anyway, I tested "2" and "auto" on my prs-600 and in ADE. Both worked, although the prs-600 "decided" just to use 1 column. I had to make the font size very small in ADE to make AUTO display as 2 columns. However, hard-coding 2 into the CSS made 2 columns display on the sony reader.

Pretty cool! =)
Creating two columns may be a useful ploy with poetry, there is nothing worse than having a verse split at the screen base. But this as a solution raises the question as to whether there is sufficient width in reading devices for it to work satisfactorily.

Do you have any screenshots of the Sony to 'see' how it looks ?
GeoffC is offline   Reply With Quote