![]() |
#16 |
the rook, bossing Never.
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 12,238
Karma: 89531599
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper11
|
I read on a Kobo. I use their "not for Kobo" epub2 files. Occasionally I have to fix them. I do convert them to epub2 with some filters / settings I also use for Gutenberg.
A decently done epub works on any epub reader, any Kobo and "Send To Kindle". A Calibre "Dual Mobi" seems to work on every kindle via USB (K3, DGX, PW1, old Basic, PW3, Oasis 2) all tested and is old mobi and azw3 in one file. A standard epub2 works on "Send to Kindle" or KDP, if it's done correctly. I don't know why they give themselves so much work for zero value. It's 99.99% novels, not journals or text books that might need more complex stuff (and then a PDF serves best). |
![]() |
![]() |
![]() |
#17 | |
A Hairy Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,160
Karma: 18843349
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
Quote:
I'm not sure what you mean by 'ridiculously convoluted code'?? ![]() This is as simple as it gets: Code:
.first::first-line {font-variant:small-caps} <p class="first">Betsy said, 'I love the simplicity of this first paragraph in a new chapter.'</p> Code:
.first {font-size:.8em; text-transform: uppercase;} .large {font-size:1em} .small {font-size:.9em} <p><span class="first"><span class="large">B</span><span class="small">etsy said, ' </span><span class="large">I</span><span class="small"> love the simplicity</span></span> of this first paragraph in a new chapter.'</p> |
|
![]() |
![]() |
Advert | |
|
![]() |
#18 |
the rook, bossing Never.
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 12,238
Karma: 89531599
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper11
|
Even simpler is no drop caps and no small caps. They impair reading comprehension and add nothing to the story.
|
![]() |
![]() |
![]() |
#19 | |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 75,686
Karma: 134319572
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
But seriously, why do they need @media queries? At least one breaks in older RMSDK. And they are not needed anyway. Other then Kindle @media queries, I've never seen any in a novel other then from Standard eBooks. |
|
![]() |
![]() |
![]() |
#20 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 75,686
Karma: 134319572
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
@Turtle91 have a look at my modified CSS vs StandardEbooks CSS. The book is McTeague by Frank Norris https://standardebooks.org/ebooks/fr...ad?format=epub
The version I chose is the compatible version which is not compatible. Can you say that their CSS is less complicated? StandardEbooks CSS core.css Spoiler:
local.css Spoiler:
se.css Spoiler:
My CSS Spoiler:
|
![]() |
![]() |
Advert | |
|
![]() |
#21 | ||
A Hairy Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,160
Karma: 18843349
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
Quote:
![]() I actually wasn't trying to make an argument here for small-caps...I was making the argument for pseudo-selectors (the point of this thread). You said that they required 'ridiculously convoluted code'... I was just showing how simple and unconvoluted pseudo-selectors are. Please, don't get thrown off track by the example using small-caps; it could be ANY css used as a example. Quote:
Having said that, media queries started out as primarily a kindle thing, but now they can be used to get the screen size and orientation among other things. Definitely useful on any device that supports queries. Added to the functionality of @media is @supports...that way you can check to see if the device supports a css function before setting it. These two things could be considered 'more convoluted' than basic css...but they aren't really that bad once you get used to them. In any case, they should not be confused with the subject of pseudo-selectors. |
||
![]() |
![]() |
![]() |
#22 | |
A Hairy Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,160
Karma: 18843349
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
Quote:
![]() I don't care for a book with no style. I am not impaired in any way, shape, or form by having drop-caps and small-caps. I LIKE the way it looks, if it is done correctly. I also like changing the font in certain sections for specific reasons...it most certainly CAN help tell the story. Do some authors/publishers mis-use styling functions...you betcha!!...but then they screw up basic paragraphs as well... That doesn't mean we need to throw the baby out with that bathwater! |
|
![]() |
![]() |
![]() |
#23 | |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 75,686
Karma: 134319572
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
They also lie. If it was compatible, they would not have to say it's not compatible with Kobo. |
|
![]() |
![]() |
![]() |
#24 |
A Hairy Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,160
Karma: 18843349
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
Ok… so…
Take a few minutes to understand them. You will be a lot more comfortable with them. They are NOT difficult. Spoiler:
In any case, you can’t recommend others NOT use them just because you aren’t comfortable with them. The customer doesn’t see anything complicated, they just see what looks good. It’s the publisher’s job to make it happen…. Including learning how to do the slightly-more-complicated-than-basic css. Last edited by Turtle91; 04-10-2024 at 07:37 AM. |
![]() |
![]() |
![]() |
#25 | |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 75,686
Karma: 134319572
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
![]() |
![]() |
![]() |
#26 |
A Hairy Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,160
Karma: 18843349
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
Again your argument boils down to: there are still horses in the world so no one can drive cars…
If the publisher does their job then the coding can work on even ancient devices (or non-standards-supportive ones). That does require the publisher to get out of their “coding comfort zone” and learn the new techniques! I have also added an example to my previous post that gives an example of the @media and @supports rules. Very simple! Now, back to the thread topic: pseudo-selectors… Last edited by Turtle91; 04-10-2024 at 07:47 AM. |
![]() |
![]() |
![]() |
#27 | |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 75,686
Karma: 134319572
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
![]() |
![]() |
![]() |
#28 |
A Hairy Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,160
Karma: 18843349
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
Proper use of css will prevent any problems.
Back to pseudo-selectors??? |
![]() |
![]() |
![]() |
#29 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 75,686
Karma: 134319572
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Pseudo-selectors don't work in enough cases. So it's best to use a <span> instead. If this is an eBook for sale, you don't know where it's going to be used so you want the highest level of compatibility.
|
![]() |
![]() |
![]() |
#30 | |
the rook, bossing Never.
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 12,238
Karma: 89531599
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper11
|
Quote:
No, I don't want ebooks with no styles, layouts, formatting, like a Palm PDA has, or PD ebooks had for over 30 years, but there seems to be an increasing trend to over complicate novels as ebooks compared to paper and too much over egg the prettiness. The Typesetting equivalent of purple prose. Been there and done that on paper in 1990s out of ego and ignorance. Sometimes a bit less is better for getting across the content. I know how to do very complex stuff, like needed for a science / Maths text book, or a comic / graphic novel etc. But I chose not to for novels. Having balance is the thing. |
|
![]() |
![]() |
![]() |
Tags |
epub, kepub, kobo, kobo sage, pseudo-elements |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
mangled em-dash as a CSS pseudo-element | sujato | Viewer | 2 | 08-02-2022 05:47 AM |
To cite ePubs: Do you recommend an ID attribute for every single element? | ibu | ePub | 12 | 08-08-2013 05:03 AM |
Default line-height in epubs | Derek R | ePub | 2 | 02-13-2012 11:23 AM |
Touch Problem with all epubs, my epubs, or my kobo? (line clipping) | plague006 | Kobo Reader | 14 | 12-02-2011 11:32 PM |
Command Line Batch Adding of Epubs | nkormanik | Calibre | 6 | 10-19-2010 08:04 AM |