You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using inline formatting that is not surrounded by spaces, e.g. H<strong>e</strong>llo, in a translation, surrounding spaces will be added automatically when the content is converted back to markdown.
Translation editor:
Rendered Page:
The text was updated successfully, but these errors were encountered:
) is exactly identical to the html entered to the translation editor.
I think (but haven't verified this yet) that html2text parses the whole HTML input into some AST-like structure that does not preserve formatting and uses some generic formatting rules when rewriting it as markdown, thus adding the spaces.
@dropforge I think it would be feasible, and given how much problems the HTML representation already caused I think it would be a good way forward. Back when we implemented the prototype/MVP it worked good enough, so we decided to go with it as it was quicker. If you are willing to do a deepdive on that I'd highly appreciate it!
When using inline formatting that is not surrounded by spaces, e.g.
H<strong>e</strong>llo
, in a translation, surrounding spaces will be added automatically when the content is converted back to markdown.Translation editor:
Rendered Page:
The text was updated successfully, but these errors were encountered: