View Single Post
Old 01-26-2017, 05:42 AM   #7
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,911
Karma: 146918083
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by pdurrant View Post
While I applaud the responsiveness, is this really a good change? There's already an option that prevents this happening, if people don't want it. Why add a special option for AZW3 that stops the automatic tidy of CSS with no way to override?

(As far as I know, Kindle does not require that the CSS margins be given separately.)
Problem is that the editor converts long form CSS to short form CSS even if expand CSS is selected. When I have expand CSS selected, with ePub, the margins are left as is. Should they be expanded on save? Even with expand CSS not selected, the ePub margins are left as they are on save. They are not changed at all.

Having expand CSS checked makes no difference to how the edtior handles CSS when it save. ePub margins stay the same and KF8 margins become short form if they are in long form.
JSWolf is offline   Reply With Quote