Hello

On Fri, Nov 11, 2005 at 12:18:42PM +0100, Valéry Perrin wrote:
> Hello,
> 
> > I do not fully understand this. Why is removing it a bad idea as
> > it is regenerated anyway?
> 
> There is at least three reasons :
> 
> 1) All translators do not know how to create a pot file (for some
> packets it's very difficult). If source package include pot file, this
> is easier for them.
In this case it is trivial. Just type make.

> 2) The translators teams use robots which automatically scan source
> packages, search pot files and put these files "for translation" at
> translators. If there is no pot file, the robot believes that the
> package is not ready for the l10n and the packet has much less luck to
> be translated in another language.

Isn't it better to search for .po files ?
Or even search for packages that depend on po4a ?
I think this search tools is broken.

> 3) The pot is always recreated at each build time by the maintener and
> that allows all translators to work on the same pot (include in source
> package) and not each one on a different pot according to the options
> which they will have taken for pot file creating.

I do not really understand this. The pot file will be recreated so patching
that file do not help in this case.

> Consequently, it is not essential to leave the pot but is much better to
> do it.
> 
> I hope that my explanations were lucid.

It certainly did but I still do not really understand this fully.

Regards,

// Ola

> Regards
> 
> Valéry Perrin
> 



-- 
 --------------------- Ola Lundqvist ---------------------------
/  [EMAIL PROTECTED]                     Annebergsslingan 37      \
|  [EMAIL PROTECTED]                 654 65 KARLSTAD          |
|  +46 (0)54-10 14 30                  +46 (0)70-332 1551       |
|  http://www.opal.dhs.org             UIN/icq: 4912500         |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---------------------------------------------------------------


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to