Crowdin’s default handling of these is inconsistent:
On upload, { .center } is not parsed as a string to translate, but { width=750 .center } is, and thus has to be hidden.
When translations are downloaded, ){ width=750 .center } is fine, but ){ .center } has messed up spacing: ) {.center}, and the new space between the ) and { messes up the MKDocs build.
Hi @imnasnainaec ! we checked the project once again and back with some updates
the file admin.md has the old version of parser (35) and we do not support it anymore. With the new one (36) everything should work well. To update the version, the source file should be uploaded to the project from scratch (if you have the duplicate option, then translations from the old file will migrate to the new one). Let us know if you need help with that
As for the account.md for example, the syntax !!! note “Note” is not typical for this file format so our tech team will have to investigate this (task created)
@Ira The !!! note "Note" is a bit of an odd case, since I don’t want !!! note translated, but do want Note translated. The current set-up presents the whole string, which is fine.
!!! note "Nota"
```
If the project has glosses in multiple languages, those languages must be added here for all the glosses to show up
in [Data Cleanup](goals.md). Click the magnifying glass icon to see all language codes present in the project.
```
has two sentences, which previously were presented as separate sentences to be translated. Now they are not split, so the whole paragraph has to be translated together.