03-24-2017, 02:18 AM | #31 |
Wizard
Posts: 3,305
Karma: 10259306
Join Date: May 2016
Device: kobo forma, Kobo Libra, Huawei media Tab, fire HD10, PW3 HDX8.9,
|
ok - the OP talked only of having his entire personal register in 2 columns, not an extract.
anyway, that can partially be done because some of the apps/ readers base their decision on when to show 2 columns, based on font and windows size, not CSS, Thus a small font for the extract may make it happen. for only a smell extract, an embedded image may be the quickest / simplest fix |
03-24-2017, 09:19 AM | #32 |
Wizard
Posts: 1,539
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
Suppose you want to write an ebook in two languages, one language at the side of the other, paralell columns, so the text doesn't flow from one column to another. You could do it with a table, but a table has many issues with ereaders. In cases like that, a two columns layout is the best option.
|
03-24-2017, 04:17 PM | #33 |
Head of lunatic asylum
Posts: 349
Karma: 77620
Join Date: Jun 2012
Location: UTC +1
Device: Tolino Vision 3HD
|
I don't want to let you wait for Monday. But I had to become clear about some issues.
First! User devices dependent ePubs could be done by producing different versions, e.g. a version for Kindle, for KF8, for 'pure' .epub readers, and so on. Or to use one stylesheet, fitting all, or let's better say some different users devices via media queries: I read some info (a bit theoretical) and the w3 schools page. To understand it right: A Kindle looks in the Styles list for the Kindle reserved stylesheet and uses automatic that one, a KF8 auto-detact the KF8 stylesheet and so on? Fine! But there is a very real other problem: I couldn't test these versions, as I got only my Tolino 3HD. Standard lists in <li> tags. By the time @Tex2002ans thought about (#28), they were already done. A personal register (1030) plus a title register (1190 entries). Especially in regard to the latter and to the size of a Kindle PW or Tolino reader (6 inches), a two columns register seems me not so useful anymore. The book Werke comes in 6 volumes, but these registers only reference the journalistic work of Joseph Roth, Volume I, II & III. The roman numerals in the register entries indicate these volumes, followed by latin numbers indicating the page numbers. As there are no page numbers in an ePub, the registers introduced to the ePub as a visual copy only would be of limited use/value, while they only would indicate the 'zone', where is to find something (e.g. in beginning, middle or at the end). To make the entries valueable it means making them functionable/clickable. And that would mean an intensive work of months, maybe years. Just now I don't know if I want to do that. That would mean (a more detailed assessment is done): about 6000 links. I would have to insert both registers to each volume, ... or making one volume out of three with 3225 (1115/1030/1080) closely printed paper book pages. Scaling the ereader to 22 or 25 lines per screen page, the ePub would got about 6000 to 7000 screen pages. Is that anymore to handle ... by humans and/or the ereader? Blaming God and ourself! Last edited by chaot; 04-05-2017 at 01:08 PM. Reason: removed issues, rough estimate about up to 10000→ (a more detailed assessment is done) |
04-05-2017, 01:05 PM | #34 |
Head of lunatic asylum
Posts: 349
Karma: 77620
Join Date: Jun 2012
Location: UTC +1
Device: Tolino Vision 3HD
|
Hi!
I could just say I was stoned/pissed when I thought about 'languages', or generally understanding problems (and published it). It's not so easy - explaining it's even more complicated, and awkward. So I will leave it alone. I got very recently a PM (out of the forum) what showed me, how serious some, when not all off you guys, acting here. Let me gain and retain your favour again. Thanks! Last edited by chaot; 04-06-2017 at 06:38 AM. Reason: add: just, (from somebody here)→(out of the forum), del: with me |
04-06-2017, 04:28 AM | #35 | |||
Wizard
Posts: 2,297
Karma: 12126329
Join Date: Jul 2012
Device: Kobo Forma, Nook
|
Quote:
Besides that minor use-case, I would heavily scrutinize all of the reasons why multi-column text was chosen for a given section... In physical texts, almost all of the reasons boil down to:
In digital text, these decisions almost always fail because the variables can be vastly different:
Side Note #1: Also, in the case of digital text/ebooks, the horizontal (left/right) width is typically our limiting factor, while vertical (up/down) is "infinite". I discussed this somewhat in Tables in an epub? with an example: Tables often designed to be "horizontal": Attachment 111743 where in ebooks, we might "verticalize" them (13x3 -> 3x13): Attachment 111748 or you may completely reformat: Spoiler:
so that they play much nicer with massive font size and/or tiny screen size. Side Note #2: Another purely typographical decision that was only made to save space/paper are Indexes that are laid out as block paragraphs instead of indented: Spoiler:
could easily be updated to: Spoiler:
Again, in an ebook there are zero limits on how "vertical" the text can be. Same exact information, just displayed in a slightly different way. Side Note #3: I also ran into another case of "columns". Sometimes they occur when the book is full of very short footnotes: I believe most of us would agree it would be absurd to carry these purely typographical decisions over into the ebook. The only reason it was designed that way in the print book was to save pages/space. Quote:
Code:
<p>This is a sample<a id="pageII-670"></a> sentence.</p> https://www.mobileread.com/forums/sh...d.php?t=266120 Then you wrap up your Index using whatever methods (Regex): Code:
<p class="index">Aischylos <a href="../Text/II-Chapter10.xhtml#pageII-670">II, 670</a></p> https://www.mobileread.com/forums/sh...02#post3404302 One method is obsolete, the other is EPUB2, and the other is EPUB3. Quote:
Sick of Amazon Kindle books without Page Numbers... Real Page Numbers for Reflowable Kindles |
|||
04-12-2022, 03:24 PM | #36 | ||
Member
Posts: 21
Karma: 10
Join Date: Aug 2013
Device: Kindle Voyage
|
Quote:
Quote:
If anyone could share a sample EPUB - either epub2 or epub3 with the code - I'd really appreciate. |
||
04-12-2022, 03:40 PM | #37 |
Bibliophagist
Posts: 35,307
Karma: 145435140
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
The only multicolumn epubs I've seen that looked good used epub3 fixed layout where every bloody letter on the page is absolutely positioned so throw out all the epub features like reflowable text.
|
04-13-2022, 06:12 AM | #38 |
the rook, bossing Never.
Posts: 11,092
Karma: 85874891
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper11
|
Not possible on a proper reflowable ebook that suits different screen sizes of Kindle and font size changes for the user.
Multicolumn was invented for newspapers. The only books that commonly use it are bibles. Fortunately you can get single column bibles. Multicolumn is ghastly on a small screen or small paper page. |
04-13-2022, 05:17 PM | #39 |
Resident Curmudgeon
Posts: 73,897
Karma: 128597114
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
I can get multi-column in RMSDK but that's it.
: 2 In body, use oeb-column-number: 2; |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
i cant see html or css | AnisioLemos | Sigil | 12 | 12-15-2016 07:12 PM |
HTML and CSS for Dummies | Sablerose | Workshop | 21 | 01-21-2014 03:48 AM |
Nesting Function arguments in custom columns | da_jane | Calibre | 1 | 11-21-2012 02:48 PM |
CSS/HTML question | ElMiko | Sigil | 54 | 10-23-2012 12:39 PM |
HTML and CSS for Dummies | weedfreak | Sigil | 17 | 01-07-2010 09:34 PM |