[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 'make publish' does not copy compendia

From: Ineiev
Subject: Re: 'make publish' does not copy compendia
Date: Fri, 04 Jan 2013 10:14:18 +0000

On 01/04/2013 09:41 AM, D. Barbier wrote:

I guess that having compendia under
in our team's repository makes sense; at the moment, these files are
located at the root directory, but this is not very logical.
Maybe it would be easier to move compendia under
server/gnun/compendia/po/ in www.

I don't think moving to .../po/ would matter; most probably, compendia
should be processed differently anyway.

compendium.XX.po can be handled like any other PO file
(sync/publish/report), since there is a POT file.

I'm not sure. compendium.$lang.po were intended to be automatically
maintained files; GNUN collects the translations for the most `popular'
strings and reuses them with `fuzzy' mark when they are absent in
master.$lang.po and the article.$lang.po. IIRC I put them to CVS
for two reasons: first, they may be used as a stub for master.$lang.po;
second, the translators may want them in order to do very fine tuning.

So, the translators generally shouldn't care of untranslated messages
in their compendium.$lang.po; it means that there are `popular' messages
that appear in no $lang translations yet. when a translator adds
a translation with a new (for that team) `popular' message, it
will be automatically added to compendium.$lang.po.

About master.XX.po, publish and report can be applied too.  Sync is a
little bit trickier, I believe that the right behaviour is to copy www
file if cmp-POs gives differences.

I see.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]