Hi, I might be misunderstanding the situation again, so take this comment with a grain of salt.
I'd highly appreciate if AI-generated translations would all be marked as fuzzy, requiriing manual verification and manual removal of the fuzzy flag, no matter how boring that is. Maybe it's just me, but I wouldn't trust the AI-generated script to get all the new approx. 14 * 560 translation correct; or to be smart enough to know which ones it's super-duper confident in and mark those as non-fuzzy. In this regard, I can't see how updating the formatting of msgid would improve the game. They will be properly formatted after a msgmerge, presumably maintaining the fuzzy matches generated by AI. e. On Sun, Jan 25, 2026 at 11:18 AM <[email protected]> wrote: > > > Op 24-01-2026 om 23:39 schreef Pádraig Brady: > > I asked claude sonnet 4.5 to code a script to split > > the combined options in the existing po files > > to separate translations per option. > > It basically one shotted it in about 10 seconds. > > Nice! > > > At that stage there are only whitespace differences > > and msgmerge is able to fuzzy match those fine. > > Hmm. It results in around 560 fuzzy matches, of which the vast > majority would be exact matches if the msgid had been formatted > the same way as in current coreutils.pot: the option description > on a separate line preceded by nine spaces. It would be nice if > Claude could print out both msgid and msgstr in that format. It > will save fourteen translators a lot of busywork. > > > So I presume we could just update all latest po files with this script, > > then upload all these "split" po files without involving translators? > > When a script with the above improvement becomes available, I will > run it at the TP and create a new series of PO files (9.9.258) that > will supersede the current 9.9-pre1, to avoid overwriting the actual > work of the translators. > > > -- > Regards, > > Benno >
