[JSWolf]

Originally Posted by bookman156

You misunderstand, although I'm not quite sure how, probably reading too quickly. That's what I was talking about. I'm talking about people altering the page margin in their own ereader and how that affects your own use of a margin on say an epigraph page, which as padding is unaffected.

The programs that adjust the margins keep the all the margins correct while adjusting the overall L/R margins. Padding isn't used much.

I haven't seen any ereader where setting line-height prevents the reader altering it. Some ereaders ignore what I set anyway, others are benefited because you give access to a line-height that isn't available on the ereader itself.

I have a Kobo. It has the option to adjust the line height. But If you have a line height in CSS, it no longer adjusts.

Do you not use px for a hr rule? I wouldn't use px for anything else in an epub, and pt never, I was simply saying that I have seen it used.

I use em and %.

hr {
  margin-top: 0.9em;
  margin-right: 40%;
  margin-bottom: 0.9em;
  margin-left: 40%;
  border-top: 2px solid;
}

Setting a 0.5em margin on the body does no harm, mostly overridden anyway by the device. Setting to 0 is also 'playing around with margins'. I have pointed out a good reason to use line-height.

On my Kobo, I can change the L/R margins. But I can only increase from what you've set in the eBook. So if you set a .5em margin, I cannot make that any smaller.

I don't use that. That's an InDesign export thing. But margin on body is fine.

Setting a margin on body is fine as long as it's zero.

Don't agree at all. It's just right. It depends on the book, you shouldn't be so dogmatic about aesthetics. Maybe your aesthetic sense is different to mine. If you want to argue which is better, that's a matter for a boxing ring.

It's not just an aesthetic. Think about those that might be reading this on a smallish phone screen. 3em would be too large.

Possibly. But I want a line that isn't over-visible. I frankly don't mind if it isn't very visible at all. It's mainly to hold the space for blind people in screen-readers. Sighted people are seeing the space more than the rule. I could even make it invisible, as recommended by the accessibility experts, but I'm less keen on that. It's a space that is respected, and if you see there is a thin grey faint rule there on your eink screen then good. But you may be reading it on an Android reader and be able to see it in colour. And then 2px is certainly too thick. Swings and roundabouts.

I did try 1px at first. It was too think on a 300dpi eInk screen. 2px is a good size.