![]() |
#16 |
Sigil Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 8,089
Karma: 5450184
Join Date: Nov 2009
Device: many
|
Jon, please stop attacking everything that is epub3. CSS3 is valid in epub3 and rem is different than em in epubs that use different font sizes in different places as it always references the size of the font in the root (html) element.
Epub2 is now totally dead. Deprecated almost 15 years ago (first approved epub3 spec was dated, October 11, 2011). Nothing new should ever be created in epub2. Good, spec compliant Epub3 readers are now broadly available and making epub3 backwards compatible with the old epub2 spec is possible. This forum's love and support for a long dead specification is really misguided. Fair warning: At some point, Sigil will eventually drop support for creating new epub2s and when asked to load one, it will eventually use integrated code (based in my ePub3-itizer plugin) to generate an epub3-only version for editing and saving. Last edited by KevinH; 08-07-2024 at 11:50 AM. |
![]() |
![]() |
![]() |
#17 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 5,635
Karma: 23191067
Join Date: Dec 2010
Device: Kindle PW2
|
Quote:
You can test this yourself with the online validator: https://jigsaw.w3.org/css-validator/ If you're working on epub3 books, you'll need to change the following plugin preferences: Code:
"css_epub2_validation_spec": "css21", "css_epub3_validation_spec": "css3", |
|
![]() |
![]() |
![]() |
#18 | |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 75,787
Karma: 134321338
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
If you are creating an ePub for sale, it could get read on a Kobo as ePub and rem will not work. It could get read on a nook or an old Sony Reader where rem does not work. So if you want to make sure you eBook does not break us em. ePub 3 should be made as backwards compatible as possible and rem is not going to help do that. Last edited by JSWolf; 08-07-2024 at 06:38 PM. |
|
![]() |
![]() |
![]() |
#19 |
Sigil Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 8,089
Karma: 5450184
Join Date: Nov 2009
Device: many
|
Old readers that do not support epub3 and css3 are a dying breed, just like B&W TVs, followed by Colour, followed by LCD, followed by .... Tying yourself to old dead epub2 only e-readers is not the solution. As more and more epub3s are generated, the old readers wll just get the junk pile.
Using epub3 with full css support is the present and future. |
![]() |
![]() |
![]() |
#20 | |
A Hairy Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,165
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:
Code:
p.largetext { font-size:2em; font-size:2rem } The coder who builds the epub should code for epub 3.x/css3.x but provide fallback coding if their target market has some ancient relic devices still in their inventory. These are VERY basic concepts. There are more advanced techniques where you can even check if a property is supported (@supports) or if the device has specific properties (@media). Your assumption that an epub coder MUST only use ePub2/css2 to be backwards compatible is just plain incorrect. Last edited by Turtle91; 08-07-2024 at 09:44 PM. |
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
W3C Validator | JustinThought | Sigil | 2 | 08-21-2018 09:33 PM |
Offline CSS Validator? | odamizu | ePub | 9 | 04-13-2016 01:09 AM |
validate with W3C Validator question | Capricorn | ePub | 12 | 03-09-2016 03:25 PM |
W3C css Validator problem? | pete6055 | Sigil | 14 | 02-28-2013 09:19 AM |