Automatic Translation not working

[DavithkbY]

I added a project with base language English.
Then I added Dutch (nl-BE) to this project and enabled translation memory and translation with primary provider. After this the words in nl-BE became translated automatically.

Now I have added spanish (es) as a language and this won't translate automatically. I tried removing nl-BE and tried to get the words automatically translated, this didn't work either anymore!

Any idea what I am doing wrong?

[JanCizmar]

I am not sure I got it. The automatic translation currently works only when you add new keys or initially set the source language value. If you add new language, the strings are not translated automatically (which is a part of #911). Are you referring to this or am I mistaken?

[DavithkbY]

I am not sure I got it. The automatic translation currently works only when you add new keys or initially set the source language value. If you add new language, the strings are not translated automatically (which is a part of #911). Are you referring to this or am I mistaken?

Ah it only works when adding new keys. I was exactly asking for #911 indeed.
It would also be usefull if when importing a json with keys and translations, these imported keys would be automatically translated as well.

[DavithkbY]

̶I̶s̶ ̶i̶t̶ ̶p̶o̶s̶s̶i̶b̶l̶e̶ ̶t̶o̶ ̶h̶a̶v̶e̶ ̶i̶t̶ ̶a̶u̶t̶o̶ ̶g̶e̶n̶e̶r̶a̶t̶e̶ ̶t̶r̶a̶n̶s̶l̶a̶t̶i̶o̶n̶s̶ ̶f̶o̶r̶ ̶a̶l̶l̶ ̶o̶t̶h̶e̶r̶ ̶l̶a̶n̶g̶u̶a̶g̶e̶s̶ ̶w̶h̶e̶n̶ ̶a̶d̶d̶i̶n̶g̶ ̶a̶ ̶t̶r̶a̶n̶s̶l̶a̶t̶i̶o̶n̶ ̶k̶e̶y̶ ̶w̶i̶t̶h̶ ̶e̶n̶g̶l̶i̶s̶h̶ ̶b̶a̶s̶e̶ ̶t̶r̶a̶n̶s̶l̶a̶t̶i̶o̶n̶ ̶t̶h̶r̶o̶u̶g̶h̶ ̶t̶h̶e̶ ̶r̶e̶s̶t̶ ̶P̶O̶S̶T̶ ̶a̶p̶i̶ ̶c̶a̶l̶l̶?̶(̶<̶-̶-̶-̶S̶e̶t̶s̶ ̶t̶r̶a̶n̶s̶l̶a̶t̶i̶o̶n̶s̶ ̶f̶o̶r̶ ̶e̶x̶i̶s̶t̶i̶n̶g̶ ̶o̶r̶ ̶n̶o̶t̶ ̶e̶x̶i̶s̶t̶i̶n̶g̶ ̶k̶e̶y̶)̶

Nevermind, was an error on my part it does translate when sending create api calls :)

[JanCizmar]

There is also auto-translate endpoint you can use to auto-translate keys.

[DavithkbY]

@JanCizmar For our use case, we want to use the api key with only read rights instead of using static json files with translations in our angular project for production. Is this a safety issue is we only give the api key read rights and nothing else? Because for our use case we really cannot work with static json files in our project since we have crud operations that when creating data in the database, that data needs to be translated in 15 languages. We want to use tolgee for these translations.

Ofcourse when adding the translation to tolgee we do this with a secret api key in the back end.
But we 100% need non static translations for the front end to view this translated data instantly without rebuilding the project.

Is this a safety issue?

[JanCizmar]

Its not a safety issue, but it's not recommended either. You can do it this way for now, but when CDN feature is implemented, you should go for that.

[DavithkbY]

Its not a safety issue, but it's not recommended either. You can do it this way for now, but when CDN feature is implemented, you should go for that.

Alright thank you very much! Is there a place we can donate since we're using self hosting but would still like to contribute to the project!

[ikbenignace]

This package is way underrated, has way more features than competitors and such nice incoming updates.

[JanCizmar]

Alright thank you very much! Is there a place we can donate since we're using self hosting but would still like to contribute to the project!

We are just working on features, that will be licensed under BSL also in the self-hosted version. It's enhanced permissions, CDN and Automated Backups. But before that, we will enable the donate button here. 🤑 Stay tuned.

And thanks!

[JanCizmar]

This package is way underrated, has way more features than competitors and such nice incoming updates.

@ikbenignace Thanks, you can help us by sharing it on your favorite socials :)

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.