I can share mine here :). It was extremely simple: "Please translate the 'TODO translate:' entries into LANGUAGE, following the style of existing translations". The tool of ours that adds TODO: with `--add-missing` prepares you the file with "TODO: translate: Original phrase" - AI will just do what it's told to do. I did it with Copilot Agent - Copilot fantastically integrates with the IDE, automatically adds context as needed (adds, parses, processes additional files from your workspace if needed) and allows you to review and approve each translation or a group of them with a very intuitive UI - that shows you "before" and "after" each change - so that you can see the original and translated text.
That worked fantastically well for PL translation, and allowed us (me, Kacper, Maciek) focus on reviewing the translation and discussing some translation nitty-gritty details where we had to apply "real-human" touch. J. On Tue, Aug 5, 2025 at 8:12 AM Amogh Desai <amoghde...@apache.org> wrote: > +1 to waiting until 3.1. > > Jarek, Pierre, Elad, Shahar, and others who have used vibe-coding for this, > if you have any > prompts that could help people with only basic knowledge of the language > contribute to the > translations, it might be worth sharing those over Slack. > > Thanks & Regards, > Amogh Desai > > > On Tue, Aug 5, 2025 at 11:38 AM Jarek Potiuk <ja...@potiuk.com> wrote: > > > +1 to waiting till 3.1.0 with the decision, but also great we regularly > > check and raise it now. Hopefully that might increase interest in getting > > it "complete" :). > > Maybe we have some Dutch speaking people who could join the efforts? This > > is a fantastic - and generally very easy and quick if you use some AI > > assistance - way to contribute to Airflow. > > > > Just in case people did not notice - the Apache Software Foundation just > > published - on the official blog - an article co-authored by Shahar, > > Pierre, Brent, Elad, myself (and Gemini :) ) - about our translation > > process and role of AI in building collaboration in Open Source: > > > > > https://news.apache.org/foundation/entry/ai-and-open-source-expanding-apache-airflows-global-impact-through-collaboration > > > > > > So what we've done here with translation is pretty cool and we are > > absolutely open for people to volunteer and close the gap of > > the translation. > > > > Do we have some Dutch speaking volunteers who can help ? > > > > J. > > > > > > On Tue, Aug 5, 2025 at 7:20 AM Shahar Epstein <sha...@apache.org> wrote: > > > > > Thanks Pierre and Wei, it makes sense - let's all sync again before the > > > release of 3.1.0, I'll contact the relevant people for this case and > ask > > > them to close the gaps before that. > > > > > > > > > On Tue, Aug 5, 2025, 03:34 Pierre Jeambrun <pierrejb...@gmail.com> > > wrote: > > > > > > > I don’t think this should apply until 3.1.0 is out and > > > internationalisation > > > > is released. > > > > > > > > Basically it can be out of date as long as the translation gap is > > closed > > > > for 3.1.0. IMHO > > > > > > > > On Mon 4 Aug 2025 at 22:13, Shahar Epstein <sha...@apache.org> > wrote: > > > > > > > > > Hey everyone, > > > > > > > > > > I'd like to point out that the Dutch locale has been out of sync > for > > > > quite > > > > > a while - less than 14% coverage, which is fairly low. > > > > > There has been a PR for fixing it, yet it progresses quite slow: > > > > > https://github.com/apache/airflow/pull/51233 > > > > > > > > > > As we're getting closer to a 2nd consecutive release with low > > coverage, > > > > > according to section 6.4 in the i18n policy - it might be suggested > > for > > > > > deletion. I'd rather avoid making harsh steps, as efforts were > > invested > > > > > (which were and are highly appreciated!) - so I'd like to ask the > > > current > > > > > owners, and any other Dutch speaker within the dev list, to help > > > increase > > > > > the translation coverage (could be done in small PRs). However, I > > don't > > > > > think that we should handle the current situation for too long, as > > this > > > > is > > > > > what we deliver to the end-users. > > > > > > > > > > I'll be happy to hear the opinions of the community about what we > > > should > > > > do > > > > > in this situation and similar situations in the future - do you > think > > > > that > > > > > the current policy handles it well in its current form, should we > > make > > > it > > > > > more strict/loose? > > > > > > > > > > > > > > > Shahar > > > > > > > > > > > > > > >
