[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Make lang.po override translations?
From: |
Dora Scilipoti |
Subject: |
Re: Make lang.po override translations? |
Date: |
Wed, 20 Apr 2022 14:25:50 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 |
On 4/19/22 11:12, Ineiev wrote:
> On Sun, Apr 17, 2022 at 02:22:00PM +0200, Dora Scilipoti wrote:
>> Each page contains:
>>
>> * An introduction that consists of one or more paragraphs.
>> * Items: the various entries that are submitted regularly (this may be
>> what you call "articles" but I'm not sure).
>
> It also contains the copyright notices, translators' credits and
> translators' notes; the translators should be able to provide
> page-specific translations at least for these parts---but for other
> parts as well.
When I mentioned the contents of a page, I was thinking of the fields
that are unique to pages in /proprietary, basically the introduction and
the items.
And now that I know that "articles" means "pages", things are clearer to
me.
> master.$lang.po contains a very limited set of strings, and every
> string in it should be checked carefully; per-directory compendia
> contain all strings from the pages in the directory.
True. I thought it was possible to somehow "isolate" the strings that
belong only to /property and make lang.po overwrite only on those.
> I mean a means to mark the translations that would override other
> (otherwise up-to-date) translations of the same string.
Yes, I can see the issue much better now. Thank you for the explanation.
--
Dora Scilipoti
gnu.org/education
stallmansupport.org -- Disinformation succeeds because so many people
care deeply about injustice but do not take the time to check the facts.