CSS margin instead of margin-top, etc.

[icallaci]

I don't usually convert ebooks with Calibre, but every once in a while it solves a problem for me, fast. I did an epub to epub conversion recently, and I noticed that instead of margin-top, margin-bottom, margin-left and margin-right in the CSS, I now see one single margin property or class (or whatever it's called), which I HATE. Is there a setting somewhere that will force Calibre to use margin-top, margin-left, etc. when converting? Apologies if this has been covered previously, but I couldn't find anything about it. A link to another thread would be fine. Thanks.

[theducks]

Originally Posted by icallaci

I don't usually convert ebooks with Calibre, but every once in a while it solves a problem for me, fast. I did an epub to epub conversion recently, and I noticed that instead of margin-top, margin-bottom, margin-left and margin-right in the CSS, I now see one single margin property or class (or whatever it's called), which I HATE. Is there a setting somewhere that will force Calibre to use margin-top, margin-left, etc. when converting? Apologies if this has been covered previously, but I couldn't find anything about it. A link to another thread would be fine. Thanks.

margin: 1em 16pt 1em 2pt;

is the short form version
I have never seen Calibre use that in calibre# styles.
I tend to use those to show I have edited a conversion

I also don't believe Calibre ever changed a defined class that DID ise the short form.

The form is easy to remember
margin: 1em =All margins are 1em
margin: 1em 2em = top and bottom 1 em, right and left 2em
margin: 1em 16pt 1em 2pt; =(top, right, bottom, left) Clockwise starting at the top

[Purple Lady]

Originally Posted by theducks

margin: 1em 16pt 1em 2pt;

is the short form version
I have never seen Calibre use that in calibre# styles.
I tend to use those to show I have edited a conversion

I also don't believe Calibre ever changed a defined class that DID ise the short form.

The form is easy to remember
margin: 1em =All margins are 1em
margin: 1em 2em = top and bottom 1 em, right and left 2em
margin: 1em 16pt 1em 2pt; =(top, right, bottom, left) Clockwise starting at the top

Maybe this is because of a 1.4 change. From 1.4 change log:
EPUB/AZW3 Output: Use shorthand forms for margin, padding and border CSS properties, where possible

[theducks]

Originally Posted by Purple Lady

Maybe this is because of a 1.4 change. From 1.4 change log:
EPUB/AZW3 Output: Use shorthand forms for margin, padding and border CSS properties, where possible

Good catch
I have not yet done/fine tuned a 1.4+ conversion

To me they are the same and produce a shorter MULTI-LINE, but still easy-to-read CSS

[Purple Lady]

Originally Posted by theducks

Good catch
I have not yet done/fine tuned a 1.4+ conversion

To me they are the same and produce a shorter MULTI-LINE, but still easy-to-read CSS

I've never liked the short version because I could never remember what was where. But I think I can remember what you said above - (top, right, bottom, left) Clockwise starting at the top

[icallaci]

There is also a version with 3. So we have:

•margin:10px 5px 15px 20px - top, right, bottom, left
•margin:10px 5px 15px - top, right & left, bottom
•margin:10px 5px - top & bottom, right & left
•margin:10px - all margins

I can NEVER remember these, and have to look it up every time. Is there any way to get Calibre to use separate top-margin, right-margin, etc.?

[DoctorOhh]

Originally Posted by icallaci

Is there any way to get Calibre to use separate top-margin, right-margin, etc.?

Not since the update performed in version 1.4.

I agree that it is easier to edit the epub if the margins are separate. Maybe you can ask Kovid to add a tweak to avoid this outcome.

[icallaci]

Originally Posted by DoctorOhh

I agree that it is easier to edit the epub if the margins are separate. Maybe you can ask Kovid to add a tweak to avoid this outcome.

Thanks, I will ask Kovid and hope it's an easy thing for him to do.

[PatNY]

I also find the new way margins are specified makes it harder to edit a stylesheet. The convention of having a variable number of values is very confusing and I would not have known what they meant if I hadn't seen this post. I cannot remember them easily either.

If possible, a tweak to use the older style would be appreciated.

--Pat

[icallaci]

Just received a notice that the ability to choose separate margin properties will be in this Friday's Calibre release. Thank you, Kovid!

[Purple Lady]

Originally Posted by icallaci

Just received a notice that the ability to choose separate margin properties will be in this Friday's Calibre release. Thank you, Kovid!

Great! Thanks Kovid.

[PatNY]

TYVM, Kovid. Hope you had a wonderful vacation.

[gbm]

Originally Posted by icallaci

Just received a notice that the ability to choose separate margin properties will be in this Friday's Calibre release. Thank you, Kovid!

The Nook dose not like the css shorthand form for margins. Will do more tests later this week.
Maybe the long form should be set as the default.
bernie

[DoctorOhh]

Originally Posted by gbm

The Nook dose not like the css shorthand form for margins.

Either version of setting margins is perfectly acceptable standard html. I highly doubt that the Nook has problems with standard html code. Exactly why do you think there is a problem?

Originally Posted by gbm

Will do more tests later this week.

It would be interesting to hear what your tests reveal.

Originally Posted by gbm

Maybe the long form should be set as the default.

Six of one half a dozen of the other. Both versions are absolutely standard html.

[theducks]

@gbm
using the short form has to be done correctly (precisely on many fussy devices ). lack of whitespace, punctuation marks in the wrong place are a few I have messed up (many of the same type mess ups done anywhere in the CSS) Validate your CSS at W3C