Quote:
Originally Posted by m00min
I don't know why you insist on referring to me as a publisher, I'm not. I just tweak my ebooks
|
That makes you a publisher, sorry. Arguing about the semantics of "publisher" would be splitting hairs.
Quote:
Originally Posted by m00min
I'm not conflating anything. Read my posts again, I've been quite clear. Changing my theme knocks out all of my margin settings
|
You've been anything
but clear. See your statement just quoted above. Changing a theme in Marvin
never knocks out anything, least of all margin settings. What you, improperly and confusingly, call "changing a theme", is constantly moving between "Publisher's Settings" and "Marvin's formatting", something that a regular Marvin user would be extremely unlikely to do. They would choose
one of the two modes, and stick to it. However, "Publisher's Settings" in Marvin currently do
not support any themes, font or color customisations. It's something you would need to request from Kris, so that they are supported even in "Publisher's Settings".
Quote:
Originally Posted by m00min
There is a big difference between 0 and 0.75em; it's 3/4 of the total line-height of the text. Assuming a base apparent size of 16 pixels (this is what web browsers default to) and a line-height of 1.5em, 0.75em would be the equivalent of 18 pixels. In other words taller than the cap height.
I don't know where you would be using points in CSS.
|
Nowhere. But I have noticed that when you don't specify font and paragraph attributes in HTML in any way, the font that tends to come out in browsers appears to correspond to a 12-point font in a word processor, and the default paragraph spacing seems to correspond to one half of that, or 6 points. You can talk about "cap heights" and "base apparent sizes", but only 1 out of 100000 people would understand what you mean, whereas anyone can imagine a 12-point font in a word processor.
I think I know where the root of all of your struggles lies, m00min: you use reading devices from various platforms, and wish that your books would display pitch-perfect on every platform, even when they are so wildly different as iOS, Nook, and Sony. Good luck with
that effort.
I'd just give up instantly, choose the preferred platform for me from among the 3, and abandon the other 2, because it's just not worth the struggle. It actually
is what I did: I gave away all my Kindle devices after Marvin was released, so that I could switch to reading e-books in Marvin "full-time", instead of struggling with idiosyncracies of the various conflicting platforms.
All of that said, m00min, if you do feel strongly about having to readjust paragraph spacing manually, visit
GitHub and request Kris to add a switch among Marvin's advanced settings:
Always override publisher's paragraph spacing when launching new books? YES/NO
It would be an advanced setting that could potentially produce ugly results (as Kris explained), but then again: the damage would be "self-inflicted" by anyone who voluntarily selected YES in that switch. And if YES was selected, you would never again need to re-adjust paragraph spacing, either, when using "Marvin's formatting", which is what you wish to achieve, right?
My general advice is to forget about Marvin's "Publisher's Settings" switch because, as you can see, it can create lots of confusion. At this moment, I don't think that books as displayed by Marvin with the "Publisher's Settings" activated, are "fit for reading". There really is no way of customising that view -- and if you
did customise it, would those truly be
publisher's settings any longer?
Again, you might request from Kris to make it possible, as an option among Marvin's advanced settings, to adjust font types and colours and Night Mode (but nothing else) even while viewing "Publisher's Settings" in Marvin... but then someone else might arrive, requesting even
more customisable features to be enabled in alleged "Publisher's Settings"... and the difference between "Publisher's Settings" and "Marvin's formatting" would get blurred, and gradually all but disappear.