Re: [RFC] Introducing AI Agents to Git Localization
- From
Jiang Xin <worldhello.net@gmail.com>
- Date
- Feb 5, 2026, 01:04 UTC
- Message-ID
- <CANYiYbEpfC1TO13U1DF+3ZmBYw=HkgFtZvpWdiZ5PaJLw6t-Yw@mail.gmail.com>
- In-Reply-To
- <534b9313b19a73bcee6e0ac1d7299e19@softwolves.pp.se>
On Wed, Feb 4, 2026 at 8:28 PM Peter Krefting <peter@softwolves.pp.se> wrote:
Show 12 quoted lines
> > 2026-02-04 10:31 skrev Jiang Xin: > > > Please try using AI coding tools to update translations in po/XX.po or > > review historical translations, following the prompts below: > > No. > > Please disable this altogether for the Swedish localization. > "Translation" using stochastic parrots is not mature and just creates > gibberish that takes more time to clean up than to do the translation > from scratch manually.
Thank you for your feedback — I completely understand your concerns.
To clarify, the intention is not to enforce automated translations via a central bot. Instead, each l10n team should retain full control over whether or not to use AI assistance in their workflow. The recent commits in the git-po next branch only add optional guidance in po/README.md to help AI agents (if a team chooses to use them) perform specific tasks more effectively—such as recognizing glossary terms from the .po header, locating untranslated or fuzzy strings, and splitting large files for easier handling.
We fully acknowledge that AI translation quality varies significantly across languages, and for some—like Swedish—it may not yet be reliable enough for direct use. The goal is to provide tools that teams can optionally leverage, not to replace human judgment or community oversight.