Hi,
thank you very much for the very quick explanation!
That is very good to know—we definitely thought the error was due to our
erroneous commit.
We should be able to workaround this by getting rid of the dots in the keys.
To help with fixing this issue eventually, we have contributed a
Hi
There is really no difference in this, if you choose "JSON nested
structure file", the key is parsed and JSON structure generated based
on that. If you use "JSON file" no parsing happens and the keys can be
formatted anyhow.
In YAML it is less likely to hit the error as that uses -> to separate
Hi
This is known issue with the JSON format, see
https://github.com/WeblateOrg/weblate/issues/2149#issuecomment-409260230
I've now added explanation to the documentation:
https://github.com/WeblateOrg/weblate/commit/f26401ad589d9140ef88a8e65821b8b3ca461145
id="-x-evo-selection-start-marker">
Hi,
first of all thank you for Weblate and the Open Source hosting service—without
it, we would not be able to offer our website in this many languages!
We are unfortunately having one problem which needs regular manual fixing by
the maintainers: A while ago, when moving our translations from
