I’m having an issue where indented Markdown text is being reformatted as text fenced in with backticks now, which does not work for our site generator.
Source file:
Exported translation:
(note the indents now being interpreted as a code block and the paragraph fenced with backticks at Line 14 in the export above)
I think this is new Crowdin behavior because it is only happening with recently modified files. This is a problem for us because this isn’t a code block, it’s meant to be an admonition (https://squidfunk.github.io/mkdocs-material/reference/admonitions/#usage - I can’t add more links as a new forum user) (a markdown extension added by mkdocs-material), so this new format doesn’t get rendered properly.
Hope you’re doing just great and sorry for the late reply, it seems we’ve missed the notification about your response
I know about the recent MD version change (well, new versions are added from time to time, we can’t keep an outdated parser) but it may affect only converted MD files (like the ones that are extracted from site builders or so).
We might be able to assist you, but I’ll need some extra info on the matter. I contacted you via email, please check your mailbox.
@Dima I would like to add to this case. I’ve been investigating where these backticks come from in deliveries from our LSP (also just like in this instance, they appear in hint blocks), because they don’t appear when we carry out our internal translations and this only happens when the LSP imports XLIFFs they exported from Trados back into the .md file in the project.
Hi @mneustadt
We’ve double-checked on our side, on export you get identical files to your sources. If any symbols are added when importing translations, we can’t change or erase them from the file
The backticks also aren’t visible when I open the same file in the editor.
This leads me to believe that these backticks are added somewhere in a parsing/conversion step upon either importing the XLIFF into the MD file or upon exporting the translation.
