[BUG]Unwanted code present when exporting to ePub in 6.0.2.1 - Writer

Hi! Great work getting this implemented.

I’m having the following issue hen exporting to ePub:

I have a 100+ page document that looks fine on LO but when I export it to ePub there are random sections of text (full paragraphs and pages) that have weird decorations that I didn’t even know existed in LO.

I’ve download Sigil to find out the issue and I can see code like:

  1. < p style="margin: 0px 0px 0px 0px; text-align: justify; ">< span style="background-color: transparent; font-effect: outline; font-family: ‘Linux Libertine Display G5’; font-size: 10.0000pt; font-style: normal; font-weight: normal; text-decoration: overline; text-shadow: 1px 1px 1px #666666; ">
  2. < /span>< span style="background-color: transparent; font-effect: outline; font-family: ‘Linux Libertine Display G5’; font-size: 10.0000pt; font-style: normal; font-weight: normal; text-decoration: overline; text-shadow: 1px 1px 1px #666666; ">
    and others similar to those.

Other instances of this show when “Line through” code is present, so I think It might be a leftover from a time when I did that to something and maybe deleted the line through text but I can’t confirm that that’s the only source of the problem.

In Sigil I’ve found over 2000 (Not a typo, i do mean over two thousand) instances of those annoying decorations in the whole document through the “Find” feature.

Can anyone tell me how to get rid of those lines of code within LO in order to be able to make changes there and Export to ePub without having use Sigil to fix the ePub version every time I make a tiny correction to the source?

None of this issues are shown in LO so I can’t figure out how to delete the code in it.
Images:

THANK YOU in ADVANCE! and keep up the good work :slight_smile:

(Edit: activated screenshot -AK)

Sorry, but bug reports are not within the scope of this site. To report a bug, visit the Bugzilla “guided” template for LibreOffice. Thanks! Still, someone here might have some wisdom on this issue … if it’s not a bug but a “feature”… :confused:

Thanks David, I’ve posted it there as well.