Quote:
Originally Posted by enuddleyarbl
So, I'm assuming that in the original epub, that first line immediately after the body statement was:
<br clear="all"/>
Am I missing something? Is there any object anywhere at that point whose bottom margin needs to be cleared?
|
Support for this was recently added into LibreOffice 7.4:
He explains all the weird edge-cases found in documents people create... like multiple left/right floats in the same paragraphs.
Quote:
Originally Posted by Quoth
I've only ever needed <br clear="all"/> in Wordpress to stop text wrapping on an image. Never needed it in an ebook.
|
Yes, <br> is rarely, if ever, needs to be used. I explained it all in "Valid Uses of Line Breaks?" here:
Quote:
Originally Posted by enuddleyarbl
I hope the OP followed Jon's advice and re-downloaded the book from Amazon and re-converted it, because it sure looks odd.
|
Yes, in this case, it would be best to just redownload the latest copy. Most likely, they've corrected/updated this ancient file.
Quote:
Originally Posted by enuddleyarbl
There's the line:
Code:
text-justify-trim: punctuation;
The teeny bit of information I can find on that is it's for languages like Japanese (I have no idea what it even does). |
Looks like it was part of the CSS3 specs back in 2007/2010, but was dropped soon after:
Quote:
7.3. Justification Method: the ‘text-justify’ property
[...]
trim
This keyword specifies that compression is preferred to expansion and enables the trimming of blank space in glyphs where allowed by typographic tradition (for example, in spaces and fullwidth punctuation glyphs). If specified alone, the exact justification algorithm is UA-defined (as for ‘auto’).
[...]
11.3. Changes from the March 2007 CSS3 Text WD
- Added ‘trim’ keyword to ‘text-justify’ as a replacement to ‘text-justify-trim’.
|
As of
today's version (September 18, 2022), text-justify is "at risk":
Quote:
The following features are at-risk, and may be dropped during the CR period:
[...]
- the text-justify property
[...]
“At-risk” is a W3C Process term-of-art, and does not necessarily imply that the feature is in danger of being dropped or delayed. It means that the WG believes the feature may have difficulty being interoperably implemented in a timely manner, and marking it as such allows the WG to drop the feature if necessary when transitioning to the Proposed Rec stage, without having to publish a new Candidate Rec without the feature first.
|
and it now only supports 4 settings:
Code:
auto | none | inter-word | inter-character
Quote:
Originally Posted by enuddleyarbl
Yet, the language is set to "EN-US".
|
Yes, I agree. Usually when that occurs, it's a whole bunch of leftover gibberish from Word documents.
Tons and tons of needless CSS + overrides + every which type of obscure/obsolete CSS + IE-specific crap.
That is definitely not needed in English.