That's an issue, regardless of the source of translation.
For my bulk translations, I have used Babbelon[0] for years. They do a great job. I wouldn't dream of replacing them entirely with ChatGPT.
What I would use ChatGPT for, is when I need to do a very minor change (like adding a simple prompt label to an app). Maybe just a few words.
Doing that through the translation service is crazy. They have a minimum price, and it can take a day or three to get the results. Since I work quickly, and most of my apps are free (for users; they usually cost me, quite a bit), changes can be a problem. Translations are a major "concrete galosh"[1].
With ChatGPT, I can ask, not only for a direct translation, but can also explain the context, so the translation is relevant to the implementation. That's a lot of work for bulk, but quite feasible for small "spot jobs."
As far as responding to reports of issues, that isn't always "black and white." For instance, I live in the US, and Spanish is basically a second US language. But it isn't just "Spanish." We have a dozen different variants, and proponents of each, can get very passionate about it.
For Spanish, I have learned to just use Castilian Spanish, most times. No one (except Spaniards) are completely happy, but it prevents too much bellyaching.
In some instances (like highly local sites), choosing a specific dialect may be advisable.
You verify by having a lot of friends, all over, who are true native speakers of languages. They usually aren't up for doing the translations, but are willing to vet the ones you do implement.
Localization is a huge topic, and maybe I'll write about it, sometime.
For my bulk translations, I have used Babbelon[0] for years. They do a great job. I wouldn't dream of replacing them entirely with ChatGPT.
What I would use ChatGPT for, is when I need to do a very minor change (like adding a simple prompt label to an app). Maybe just a few words.
Doing that through the translation service is crazy. They have a minimum price, and it can take a day or three to get the results. Since I work quickly, and most of my apps are free (for users; they usually cost me, quite a bit), changes can be a problem. Translations are a major "concrete galosh"[1].
With ChatGPT, I can ask, not only for a direct translation, but can also explain the context, so the translation is relevant to the implementation. That's a lot of work for bulk, but quite feasible for small "spot jobs."
As far as responding to reports of issues, that isn't always "black and white." For instance, I live in the US, and Spanish is basically a second US language. But it isn't just "Spanish." We have a dozen different variants, and proponents of each, can get very passionate about it.
For Spanish, I have learned to just use Castilian Spanish, most times. No one (except Spaniards) are completely happy, but it prevents too much bellyaching.
In some instances (like highly local sites), choosing a specific dialect may be advisable.
You verify by having a lot of friends, all over, who are true native speakers of languages. They usually aren't up for doing the translations, but are willing to vet the ones you do implement.
Localization is a huge topic, and maybe I'll write about it, sometime.
[0] https://www.ibabbleon.com
[1] https://littlegreenviper.com/concrete-galoshes/