09-09-2021, 02:05 AM | #31 | |
Grand Sorcerer
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
The answer is you cannot do what you want with the kepub renderer. There is no way to differentiate between justification that can be overriden and justification that cannot. For certain tags, the kepub renderer overrides this not matter what. The rules the RMSDK follows are different. Which is more correct will depend on your viewpoint. And based on my experience here, people will vigorously support both ways of doing it. You might be able to fake it somehow with margins or padding or something. But, I suspect you will not be able to get it working the same on all ereaders or apps. Or font sizes. It is similar to the issues with drop-caps. You can fiddle and get it working perfectly, but, change the font size or font, and it falls apart. |
|
09-09-2021, 02:19 AM | #32 |
Guru
Posts: 873
Karma: 252902
Join Date: Jun 2016
Device: Kobo
|
@davidfor
I wondering why Nook works great with border-radius. It seems that Adobe RMSDK is also used there (not the latest version). And nevertheless, it displays everything perfectly ... It turns out that they fixed it in Nook, but in Kobo they did not do it ... |
Advert | |
|
09-09-2021, 07:04 AM | #33 |
Grand Sorcerer
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
|
09-09-2021, 08:49 AM | #34 |
Wizard
Posts: 2,303
Karma: 9599999
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
|
Here you go. The screenshot that I already posted did have the text-aligns in it that were ignored.
|
09-09-2021, 10:58 AM | #35 |
the rook, bossing Never.
Posts: 11,157
Karma: 85874891
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper11
|
The boxes are centred on Calibre Viewer, otherwise same as screen shot.
|
Advert | |
|
09-09-2021, 11:14 AM | #36 |
Wizard
Posts: 2,303
Karma: 9599999
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
|
Ah, apparently AdobeNativeInterface.setJustified("justify"); throws an !important in.
I got rid of that and just added body {text-align: justify} in my CSS for AdobeNativeInterface.setCustomStyleSheet Now it still justifies books but is amenable to being overriden. This is B&N Glow RMSDK again: |
09-09-2021, 01:15 PM | #37 | ||
Member
Posts: 16
Karma: 10
Join Date: Aug 2013
Device: Kobo Aura HD
|
Quote:
Quote:
|
||
09-10-2021, 01:23 AM | #38 | ||
Grand Sorcerer
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
Quote:
From the point of view of what the two renderers do on the Kobo, different people think more or less should be overridden. Should it just set justify at the body level and let all the tags within decide? Or should it override it at every level? I've seen arguments for both. And people choosing either epubs or kepubs because of it. I have no idea what the correct answer is, unless all of them are as it is a personal opinion. But, I also don't really care. I'm not a fan of how the justification works, so I don't use it. And if edit the book for any reason, I will remove the justification, fonts (if I don't like them), any forced hyphenation and some margin settings from the body text classes. I try not to mess with things were I think this styling is important. If the book has a clear overall style, I try to maintain that. With the above exceptions. |
||
09-10-2021, 05:59 AM | #39 |
Wizard
Posts: 2,303
Karma: 9599999
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
|
If a book annoys you with egregious styling you can always just unzip it, delete all the .css files and zip it again.
This applies to Adobe DRMed books too, without decrypting anything. I don't know Kindle, does this work too? |
09-10-2021, 11:21 AM | #40 |
the rook, bossing Never.
Posts: 11,157
Karma: 85874891
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper11
|
|
09-10-2021, 01:11 PM | #41 |
Wizard
Posts: 2,303
Karma: 9599999
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
|
|
09-10-2021, 03:23 PM | #42 |
Resident Curmudgeon
Posts: 73,974
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
|
09-10-2021, 03:24 PM | #43 |
Resident Curmudgeon
Posts: 73,974
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
|
09-10-2021, 09:51 PM | #44 |
Wizard
Posts: 2,303
Karma: 9599999
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
|
I play it fairly straight with library books, I don't decrypt them.
That's just my quirk. |
09-11-2021, 04:44 AM | #45 |
Grand Sorcerer
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Attached are screenshots from my Kobo Glo with firmware version 4.28.18220. The kepub renderer shows the border-radius and the epub/RMSDK renderer does not. Which is what I expected and matches @DNSB's screenshots. Now I am curious as to why the B&N Glow, with an older version of the RMSDK, supports it.
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Border-radius in pdf not working | kghugo | Calibre | 1 | 07-10-2019 02:35 PM |
ADE 3.0 and RMSDK 10 released | Doitsu | ePub | 14 | 01-24-2014 11:06 AM |
RMSDK | Santanu | ePub | 4 | 05-07-2012 02:02 AM |
RMSDK | Santanu | Android Developer's Corner | 6 | 03-17-2012 12:27 AM |
Renderer resolution with RMSDK | Mark.Vasconcelos | Android Developer's Corner | 1 | 10-05-2011 04:38 AM |