https://bugs.documentfoundation.org/show_bug.cgi?id=163196
Bug ID: 163196
Summary: EPUB export mis-handles double spaces
Product: LibreOffice
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: filters and storage
Assignee: [email protected]
Reporter: [email protected]
Let's elide for now the entire argument over whether or not it is correct to
put two spaces after a period, and just accept that a large number of people
(myself included), as well as many academic studies, find that it improves
readability.
Now, that said, when you use two spaces after a period, and then you export to
EPUB, which is fundamentally containerized XHTML, those two spaces would be
collapsed to one if left unmodified. LibreOffice's EPUB export does ALMOST the
right thing here, replacing <space>space> with <space><non-breaking-space>.
The key word here is ALMOST. When a double space occurs at the end of a line,
this replacement results in an erroneous single-character indent at the
beginning of the next line,
The correct replacement would be <non-breaking-space><space>. The WORST case
here is that the erroneous space appears at the end of a line, where it is much
less visible than at the beginning. (For example, Sigil's XHTML preview mode.)
In the BEST case (for example, Amazon Kindle ebook reader), the ebook reader
collapses it entirely and flows the text as intended.
This surely cannot be a difficult change. (In fact,I'm going to look at the
code myself, and see if I can FIND the relevant code and offer a patch.)
--
You are receiving this mail because:
You are the assignee for the bug.
