[Feat] Gracefully keep translated texts in the transaction where API limits exceeded

[ConfusedVorlon]

Steps to Reproduce:

translating a large batch of strings using Microsoft Translator request limit exceeded

Expected Behavior:

the succesfull translations should be inserted in my Strings

Current Behavior:

error shown, Remafox gives up

Environment

[ConfusedVorlon]

The batch was about 308 translations for 5 languages

[Jeehut]

@ConfusedVorlon Thank you for reporting this.

To make me fully understand the issue here, can you please explain how you did the "batch translation"? Did you use the build script? Did you start it from the Config file? If the latter, did you use "empty only" or "override all"?

Also, what you're trying to say is that if of those 308 translation keys, say 100 could be translated and the others failed, RemafoX should at least insert the 100 and can still error with "not all translations could be translated" after that, right?

[ConfusedVorlon]

I clicked "translate empty strings" in the app

yes, if 100 were translated. Then save those. That way there are fewer next attempt, and it won't hit the request limit for ever

[Jeehut]

Thank you for the clarification. Of course, it makes sense to keep what has been successfully translated!