Oxygen XML Forum

Experimenting with Oxygen for generating HTML output of Markdown documents. One behavior that is currently a show-stopper for me is Oxygen generating a <br> tag at the end of each line when converting a Markdown document into HTML. Can this be suppressed?

This behavior is inconsistent with all the other Markdown processors I have played with, where <br> tags are only generated when using a backslash at the end of a line or 2 spaces (which to use depends on processor, where for me, I use backslash [CommonMark specification]).

Hi,
Can you tell us more about how you generate HTML from Markdown using Oxygen?
Regards,
Radu

Radu wrote: ↑Sat Feb 14, 2026 5:28 pm Can you tell us more about how you generate HTML from Markdown using Oxygen?

As of now, mainly checking if Oxygen can be used to HTML-preview Markdown files. We have Markdown files that are eventually rendered by a server, but the server does not provide a preview capabilities for verifying MD syntax and display before posting, so looking at tools to allow for HTML preview, and if Oxygen converted MD to HTML similar to other processors, we can use Oxygen to edit and preview MD files before posting markdown files/edits to server. The server in question fully supports CommonMark along with some GFM extensions.

With CommonMark, <br> is only inserted if a line ends with a backslash character, '\'.

We already use Oxygen Editor for general XML document editing, so seeing if useful for Markdown editing and preview.

Hi,

I understand now, I added an internal issue to look into this, pasting the issue ID below:
EXM-56774 Markdown preview interprets simple line break in paragraph as HTML <br>
I will update this forum thread if we manage to fix this problem in a future Oxygen version.

Regards,
Radu

Hi,
We released Oxygen 28.1 and it should have a fix for this problem you reported here.
https://www.oxygenxml.com/xml_editor/whats_new.html
Regards,
Radu

Radu wrote: ↑Wed Mar 18, 2026 7:52 pm We released Oxygen 28.1 and it should have a fix for this problem you reported here.

Great! I shall check it out. Thanks.