-
I am (finally) transferring our in-house translations management system to Weblate. We use I decided to transform our custom format to Format.JS, as it was fairly easy. The problem: We have dots in key names. This seems to be a problem (or I did something wrong). What went in:
What came out (in Gitlab Merge request, right after the import finished):
Moreover, it seems like most of the translations got lost. My guess would be that only the translations with keys without dots made it - but I didn't check. Is this expected behavior, or is this a bug? Using hosted version of weblate. The folder on the branch that Weblate is set to: https://gitlab.com/greensteps/ark/-/tree/1867-weblate-integration/frontend/src/lang/locales?ref_type=heads The merge request: https://gitlab.com/greensteps/ark/-/merge_requests/1286 |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Update: After resetting the weblate repository (Danger zone -> Reset all changes in the Weblate repository). the keys are showing correctly in the web interface and the already translated content is there too. After commiting and pushing, the resulting file is stil nested according to dots in the key, thou. |
Beta Was this translation helpful? Give feedback.
-
This should be addressed by translate/translate#5462 (the fix is not yet released). |
Beta Was this translation helpful? Give feedback.
This should be addressed by translate/translate#5462 (the fix is not yet released).