On 25/01/2026 10:18, [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.
Right, the new wrapped msgid will happen automatically
with the next msgmerge but will be tagged as fuzzy.
We could easily enough wrap the msgid to avoid that.
I was wondering about whether translators would prefer
having these auto adjusted translations marked as fuzzy or not.
I'll defer to your preference on this so.
As for wrapping the msgstr, I was a bit more wary as languages
have different wrapping attributes. For example we don't wrap
some utils like ptx where the descriptions currently fit.
Also some languages like "zh" are naturally more concise and
thus would prefer not to wrap.
So 2 questions.
1. Do we really want to wrap the msgstrs too?
2. If we don't, do we still want to wrap the msgid to avoid the fuzzy tag?
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.
Sounds good.
thanks,
Padraig.
