On Saturday 16 of May 2020 19:51:51 Michal Čihař via Weblate wrote:
> Hi
>
> Slávek Banko píše v So 09. 05. 2020 v 02:05 +0200:
> > 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/5f6d5ebc
> >a7648a33e33b75075241681414294ff5
> >
> >
> > Please, what is the correct way to set such flags using POT files?
>
> I think this is supposed to work, but the flag is supposed to be in the
> PO files, the POT file is only used when creating new translations. The
> tricky thing is that msgmerge used to remove flags it doesn't know...
Hi,
I think that special flags for source strings should be set according to
the POT file. I will give reasons why I consider this way to be correct:
1. For standard flags set in POT files, these are decisive for setting
flags in PO files during msgmerge.
2. When I manually set the ignore-inconsistent flag on the source string in
Weblate, this is decisive for all languages. So the behavior is completely
consistent with 1.
3. The source strings and their flags are read from the POT files, so there
makes sense for the special flags for the source strings in the Weblate to
be set in accordance with the POT files.
4. If special flags are not loaded for source strings from POT files, then
the flags displayed in the Weblate are inconsistent with the state of the
flags to be actually used.
5. It is definitely easier to make an adjustment in generating POT files
than to make an adjustment in all existing PO files.
6. I will give the best reason last: Setting special flags by existing PO
files simply does not work at all!
On one component, I tried to add flags to existing PO files:
https://mirror.git.trinitydesktop.org/cgit/abakus/commit/?id=c9cfcec56a
Subsequently, Weblate automatically updated the PO files according to the
POT and the added ignore-inconsistent flags were immediately removed:
https://mirror.git.trinitydesktop.org/cgit/abakus/commit/?id=6fcf93d2ee
So the method for specifying special flags using PO files that you mention
is not applicable - it doesn't work. Therefore, I believe that specifying
special flags on source strings according to the POT files is the only
really useful way.
Cheers
--
Slávek
signature.asc
Description: This is a digitally signed message part.
___
Weblate mailing list -- weblate@lists.cihar.com
To unsubscribe send an email to weblate-le...@lists.cihar.com
