Op 22-01-2026 om 20:19 schreef Egmont Koblinger:
The attached script replaces some of the empty translations to fuzzy
ones. It looks for an obsoleted longer msgid that contains the new
msgid as a substring, allowing whitespace changes;
Thanks for the attempt. But it's far from useful.
and if found then
this becomes the fuzzy translation.
Running the script here says:
Traceback (most recent call last):
File "/home/ben/...hyperlink-po-fixer.py", line 29, in <module>
entry.fuzzy = True
AttributeError: can't set attribute 'fuzzy'
Commenting out that line makes the script succeed, and it reports:
Resurrected 313 hopefully useful fuzzy translations
Looking at the --help strings for `wc`...
msgid ""
" -c, --bytes\n"
" print the byte counts\n"
msgstr " -t, --text in tekstmodus lezen (standaard)\n"
msgid ""
" -m, --chars\n"
" print the character counts\n"
msgstr " [-]echo invoertekens echoën\n"
msgid ""
" -l, --lines\n"
" print the newline counts\n"
msgstr " -l, --login de inlogprocessen tonen\n"
Those are useless, because not in any way translations of the msgid.
What a useful script should do: look for msgids that describe an option
(that is: those that start with " -" or more spaces and "--") and then
find that same option plus its description (folded into a single line)
in the obsolete msgids, and when found, extract the corresponding option
plus its description (everything upto the next option) into the new msgstr.
Not easy.
I _strongly_ urge the maintainers to _revert_ these string changes. They
are a world of hurt -- for very, very little gain, as far as I can see.
These are command-line tools, not the clickety-clickety world of the web.
You still have to manually remove the irrelevant options and manually
reformat, but that's an easy boring mechanical task.
For ten, maybe twenty strings that would be okay. But for three hundred
or more strings... that is torture.
--
Regards,
Benno
