On Friday 08 of May 2020 01:43:28 Slávek Banko wrote:
> Hi,
>
> in TDE applications we have a built-in mechanism for displaying
> translators in the About dialog. It uses the POT / PO file mechanism so
> that each template contains a pair of strings Your names (NAME OF
> TRANSLATORS context) and Your emails (EMAIL OF TRANSLATORS context).
> These are extracted so that they arise from the otherwise non-existent
> _translatorinfo file.
>
> After I upgraded Weblate to 4.0.x, virtually all translations started
> reporting warnings that the intentionally non-existent _translatorinfo
> file did not exist. Please, is there any way to turn off file existence
> checking specifically for these two strings?
>
> See
> https://mirror.git.trinitydesktop.org/weblate/projects/applications/abak
>us/
>
> Especially for these two strings with a special purpose, here are other
> things that were useful to us:
>
> Is there a way to turn off the uniqueness check between components
> specifically for these two strings? Each component can be translated by
> different translators, so it is correct for these special strings to be
> different.
>
> Is it possible to automatically fill in the data of new contributors
> specifically in these two strings? Although we have information on the
> special purpose of these two strings in the manual, users often start by
> translating these strings literally.
>
> Note: As far as I know, KDE uses the same way of entering translator
> data for display in the About dialog.
>
> Note: After committing to almost all repositories, Weblate has been
> performing follow-up tasks for about 9 hours - the end is still out of
> sight. This generates a load for all 8 cores we have available. Quite a
> tragic view of the load on the system.
>
> Thank you for your advice!
>
> Cheers

Hi,

I have prepared a patch for our framework that updates POT files so that 
references to an intentionally non-existent _translatorinfo file are 
replaced with a comment that explains to the translators the special 
purpose of the two strings. This seems like a winning solution for 
everyone - Weblate will not report alerts due to a non-existent file and 
translators will have instructions right in front of their eyes.

For better perfection, I researched the possibility of setting the 
ignore-inconsistent flag using the POT template. But I don't know if I 
used it the wrong way or if it doesn't work.

See
https://mirror.git.trinitydesktop.org/gitea/TDE/abakus/commit/5f6d5ebca7648a33e33b75075241681414294ff5

Please, what is the correct way to set such flags using POT files?

Cheers
-- 
Slávek

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Weblate mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to