No AutoTranslation on migrating from gettext to json web-extension

[bussnet]

Hi.

After >1day of trying, I hope for help where my problems are :(

We want migrate from gettext to json, so I created a new git repository, convert the .pot files to json and add this repo as new project to weblate.

My plan was to use the auto translate feature to let weblate do the lang file creation and the translation.

But everything I tried, there is nothing found after a automatic translation.

I assert/tried:

• the string 100% exists as translation in the old project and in the weblate memory (export and checked it).
• both projects share translation memory
• add the EN string as value to the "template" json file
• both, via extension and via manual
• both, from other components (all and specific) and via MT with Weblate&WeblateMemory
• moved the component to the old project and try auto translation there

I have no idea what to check else.

Maybe the root of the problem is the switch from the "two" to "single" language thing, because this json format is designed for translation via ID, not from source language like gettext.

We just use the original english text as "id", so don't know what the automatic translator will use to translate - my guess is, the value of the EN file with the same ID?

BTW, also add the extension which should autofill write protected strings (so in this case the EN file?) with the "id", but this do nothing. Wether I allow edit these file or not.

Thanks for taking your time to help me!

best, Thorsten

[nijel]

How do you trigger automatic translation? The 100% match won't work when context in PO files doesn't match keys in JSON, you need to lower the threshold to 95% for that.