Re: New proofing / consistency feature

Thanks for the feedback Karl,

We can certainly make this optional with a setting in the config.

Would you mind explaining how to use Pology? I never got it working in a way I could really understand, and its output in the editor tab wasn't very helpful for me to learn.

And I'm a little cautious about depending on Pology for a check like this --- unless we set Pology as a required package (and get maintainers to provide it for their distro), or bundle it with Lokalize somehow, we're depending on proofing from a tool that might not exist on the user's system, and might require building just to set up. This is not user-friendly...

Thanks,
Finley

Feb 13, 2026, 19:47 by [email protected]:

> [email protected] skreiv 12.02.2026 14:55:
>
>>
>> Hi translators,
>>
>> Varun, a Season of KDE mentee, is working in this merge request here, adding more functionality to Lokalize's editor tab https://invent.kde.org/sdk/lokalize/-/merge_requests/286
>>
>> What are you thoughts about this new feature being implemented? Is the KMessageWidget warning too distracting?
>>
>
> I would find it annoying. I have seen the feature in other (online) PO editors, and have *never* found it useful. There are tons of false positives (partly because my translations are usually much more consistent than the original English strings). Also note that a good implementation must take into language-specific rules. See the Translate Toolkit rules for some inspiration: https://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/pofilter_tests.html
>
> I’m not *against* this feature, but it must be possible to easily disable it.
>
> And I actually think the suggested KMessageWidget UI is OK. The (supposed) error is easy to notice, which is important.
>
> But I would prefer that work would be done to use this UI for the Pology-based checks that *already exist* in Lokalize. In the current UI, it’s easy to miss the errors. An advantage of the Pology-based checks is that each translation team can easily add their own language-specific (and even file-specific and project-specific) rules, and the checks can be much more sophisticated.
>
> Regarding the trailing space feature: I like this very much and would *not* want to see it moved to a KMessageWidget.
>
>
> --
> Karl Ove Hufthammer
>