Markdown rendering should keep {}

[koppor]

JabRef has internally a field marker that marks a field as Markdown. org.jabref.model.entry.field.FieldProperty#MARKDOWN

When that field is rendered in the preview, {} should be kept.

Example content of a Comment:

# test

{ test }

```javascript
function hero() {
}
```

---

This issue is more about code reading and understanding JabRef's archictecture. The "real" fix should be a few lines of code: Checking for the field property MARKDOWN and passing the field value with plain latex (and not latex free).

[LoayGhreeb]

I would like to work on this issue

[LoayGhreeb]

Hi @koppor, I did my best for solving this issue, but I don't know how to solve it. I noticed that comment or abstract use both Markdown and HTMLChars formatters. However, the HTMLChars formatter always deletes any curly brackets in the string. I'm not sure if this is related to the issue or not.
Could you provide a hint or guide on how to proceed?

[koppor]

Related PR: #10942?

Currently, I think, following lines in the HTMLChars should be removed

            } else if (!incommand && ((c == '{') || (c == '}'))) {
                // Swallow the brace.

Adapt tests.

In .layout files, search for HTMLChars and check where to add RemoveBrackets before.

Thinking more, the LaTeX command handling in HTMLChars should be removed. In the .layout files, LaTeXToUnicode should be used. - I think, HTMLChars will be much smaller then. HTML5 default encoding is unicode, thus LaTeXToUnicode is the right formatter.

[koppor]

@LoayGhreeb Any progress here? 😅

[LoayGhreeb]

I've unassigned myself and am currently working on another issue. I'll come back to this one soon if nobody else takes it.

[jeanprbt]

You can assign me on this one if you wish !