[galax]

It gets a bit more complicated.

Koreader actually is able to render rotated rows as columns with some changed in the settings.

The following render choices are available:

Legacy
Flat
Book
Web

And this is the description in the handbook:

RENDER MODE: This option determines how your document is rendered by KOReader. Default is WEB and generally you don’t need to change this setting. When a book (or saved web page) is very complicated (specified widths or margins, negative margins, floats etc.) and layout looks bad or overflow the screen, you can try other rendering modes.

So the 'column' css syntax instead of rows:

tr { display: block; float: left; }
th, td { display: block; }

in Koreader does render properly in "LEGACY" mode but not in "WEB" mode which is the one the handbook recommends using.

It's interesting to note that Kobo does render the above css snippet correctly.

A search online about epub and tables there's some official specs about the matter:

https://epubknowledge.com/docs/tables

All tables should have the epub:type="table" applied to the table tag, example:

Not much more, it only gives examples of data in rows.

Now comes the difficult part on deciding WHAT TO DO for writing the ebook! It takes some time and effort to create content and with so many choices I'd rather avoid using the wrong format for the epub.

a - Use 'css' column rows AND use koreader in "LEGACY" mode.
b - Or use official epub table specs and force column data into unnatural row html syntax.

I need help. What's the general consensus on the issue???

Thanks in advance.