Answers.Body: <p>That's an interesting way to make a gap between paragraphs <code>&lt;p&gt;&lt;span&gt;&amp;#160;&lt;/span&gt;&lt;/p&gt;</code>.
  Though <code>&lt;br&gt;&lt;/br&gt;</code> is still often used to break to the next line (or create an extra gap between paragraphs) its not an ideal solution, and it's recommended to not use it.
  We use the <br> for our .xhtml epub pages on rare occasion.
  But we primarily use the CSS margins and padding in a <code>&lt;p&gt;</code> tag as intended by coding correctly to create the necessary letter gap, word gap, and paragraph gap. A directly coded solution (to resolve Okular discrepancy) would be to set the paragraph padding to have its own gap before/after the paragraph. Such as:</p>
  <pre><code>p {padding: 8px 0 8px 0;}
  </code></pre>
  <p>or....</p>
  <pre><code>p {margin: .5em 0 .5em 0;}
  </code></pre>
  <p>The second is suggested by KDP:
  <a href="https://kdp.amazon.com/en_US/help/topic/GH4DRT75GWWAGBTU#formatting_paragraphs" rel="nofollow noreferrer">See KDP link</a></p>
  <p>If you seldom intend to directly adjust the CSS code.... As a viable alternative with its own built-in pre-sets is something known as '<strong>CSS framework</strong>' that you might consider. It's a big step but might be something worth looking into for your next project. These are CSS frameworks such as 'modular framework', and 'minimalist framework', and 'component-based frameworks'. The only ones suggested here are strictly the frameworks which aren't loaded via a windows Command Prompt terminal.</p>
  <p>CSS framework examples are <strong>Bootstrap</strong>, <strong>PureCSS</strong>, <strong>W3.css</strong>, <strong>Bulma</strong>, <strong>Skeleton CSS framework</strong>, etc.</p>
  <p>To answer your question, we have used <code>&lt;br&gt;&lt;/br&gt;</code> on a number of KDP epubs, Kobo epubs, also tested on Aldiko app, on Pocketbook app, ADE app, on Moon+ app, and all of them render that line-break code fine. Those are common eReaders, and during our testing (text and image heavy epubs) there has not been a problem to date using <br> on those Apps (though as mentioned above its better to use CSS paragraph adjustment instead).</p>
  <p>Here is a link with a number of alternative creative line break suggestions worth reading:</p>
  <p><a href="https://www.scaler.com/topics/css-line-break/" rel="nofollow noreferrer">Creative line-break options</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-08-29T10:55:49.040Z
Answers.Text: Thank you for the answer. Just a small note. BR is an HTML tag a little bit different from the others. It is written as a single tag. Without open and close tag.
Answers.UserDisplayName: FluidCode
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-05-14T08:19:45.753Z
Answers.Text: @FluidCode It is the same as any tag in HTML <tag></tag> is exactly the same as <tag/>
Answers.UserDisplayName: mmmmmm
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-08-18T04:38:23.490Z
Answers.LastActivityDate: 2023-08-18T04:38:23.490Z
Answers.UserDisplayName: granite
Body: <p>I opened an epub file created exporting an odf file written with a recent version of LibreOffice (7.3.6.2). All the empty lines are rendered with a space encoded as $#160; inside a <strong>span</strong> tag inside a <strong>p</strong> tag. In Calibre and Sigil they are rendered correctly, in Okular they are not rendered and the text is less readable. I am not much worried about Okular, but I wonder if it is the only reader behaving in this way. I made some research on the internet and I know that <a href="https://teleread.com/how-epubs-readers-disagree-when-non-breaking-spaces-break-standards/index.html" rel="nofollow noreferrer">in the past</a> not all the readers supported it.</p>
  <p>Strange enough, if I replace the lines with <strong>br</strong> tags it works in the readers I have available, but the linked article says that few ebook readers will support it.</p>
  <p>What is the current situation with the most common readers?</p>
  
Tags: <html>
Title: Explicit empty line in epub code what is the status of the support by current editors?
UserDisplayName: FluidCode
ThreadText: # Explicit empty line in epub code what is the status of the support by current editors?
  
  (Asked by: username_0 on 2023-02-01)
  
  I opened an epub file created exporting an odf file written with a recent version of LibreOffice (7.3.6.2). All the empty lines are rendered with a space encoded as $#160; inside a **span** tag inside a **p** tag. In Calibre and Sigil they are rendered correctly, in Okular they are not rendered and the text is less readable. I am not much worried about Okular, but I wonder if it is the only reader behaving in this way. I made some research on the internet and I know that [in the past](https://teleread.com/how-epubs-readers-disagree-when-non-breaking-spaces-break-standards/index.html) not all the readers supported it.
  
  Strange enough, if I replace the lines with **br** tags it works in the readers I have available, but the linked article says that few ebook readers will support it.
  
  What is the current situation with the most common readers?
  
  **Tags:** html
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2023-08-18. Score: 0
  
  That's an interesting way to make a gap between paragraphs  .
  Though  is still often used to break to the next line (or create an extra gap between paragraphs) its not an ideal solution, and it's recommended to not use it.
  We use the  for our .xhtml epub pages on rare occasion.
  But we primarily use the CSS margins and padding in a  tag as intended by coding correctly to create the necessary letter gap, word gap, and paragraph gap. A directly coded solution (to resolve Okular discrepancy) would be to set the paragraph padding to have its own gap before/after the paragraph. Such as:
  p {padding: 8px 0 8px 0;}
  
  or....
  p {margin: .5em 0 .5em 0;}
  
  The second is suggested by KDP:
  See KDP link
  If you seldom intend to directly adjust the CSS code.... As a viable alternative with its own built-in pre-sets is something known as 'CSS framework' that you might consider. It's a big step but might be something worth looking into for your next project. These are CSS frameworks such as 'modular framework', and 'minimalist framework', and 'component-based frameworks'. The only ones suggested here are strictly the frameworks which aren't loaded via a windows Command Prompt terminal.
  CSS framework examples are Bootstrap, PureCSS, W3.css, Bulma, Skeleton CSS framework, etc.
  To answer your question, we have used  on a number of KDP epubs, Kobo epubs, also tested on Aldiko app, on Pocketbook app, ADE app, on Moon+ app, and all of them render that line-break code fine. Those are common eReaders, and during our testing (text and image heavy epubs) there has not been a problem to date using  on those Apps (though as mentioned above its better to use CSS paragraph adjustment instead).
  Here is a link with a number of alternative creative line break suggestions worth reading:
  Creative line-break options
  
  > **Comments:**
  > **username_0**: Thank you for the answer. Just a small note. BR is an HTML tag a little bit different from the others. It is written as a single tag. Without open and close tag.  
  > **username_2**: @username_0 It is the same as any tag in HTML <tag></tag> is exactly the same as <tag/>  
  
  ---
  
  