On Sat, Jan 24, 2026 at 4:08 PM Benno Schulenberg <[email protected]> wrote:
> The reduction in work is not significant -- what your script does is > what most translation tools can do too via their translation memory. Thanks for the explanation! It makes sense. I have to admit, I'm not familiar with translation tools. I am reasonably familiar with gettext's msg* tools. I know that they can perform fuzzy matching in order to come up with translation drafts (marked as fuzzy), and also carry some history in obsolete (commented out) translations. This time many of the old translations weren't available in the updated .po files in either of these forms. What I didn't know was that translation tools also duplicate these two functionalities: carry their own (larger) history that's not carried in .po files, and perform their own fuzzy matching on these strings. This, I assume, depends on other factors too, like translators actually using such advanced tools, not having reinstalled their system and thus accidentally wiped off the history, one guy not stepping in to continue someone else's work -- or else feed the tool with older translations first. But I guess these can easily be taken care of. Looks like my script also sort of duplicated (in a primitive way) these features that these tools have. > No, no, I was not expecting anything from you at all. You're reading > too much into it. I was just reasoning from the position of a dozen > different translators: you cannot expect them all to have a recent > distro or replace a file with one that's not provided by the distro. This is absolutely not how your words sounded to me. I clearly didn't expect every translator to be able to run my script, that's why I clearly offered to send the results. When I asked you to "can you please try replacing...", I didn't mean that that's what every translator will have to do. It was a debugging step to understand the problem and to allow you to run the script and check its output. Had that worked out and had you found the tool useful, we could have e.g. bundled that file, or found some other solution. e.
