po4a-dev
[Top][All Lists]
Advanced

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

Re: [Po4a-dev]. Introducing po-pod


From: Martin Quinson
Subject: Re: [Po4a-dev]. Introducing po-pod
Date: Mon, 18 Nov 2002 12:00:59 +0100
User-agent: Mutt/1.4i

On Mon, Nov 18, 2002 at 10:26:01AM +0100, Denis Barbier wrote:
> On Mon, Nov 18, 2002 at 09:04:52AM +0100, Martin Quinson wrote:
> [...]
> >   * pod-translate:
> 
> Just for the record, my feeling is that this name makes full sense
> when documents contain only a single language, but it is not
> adequate when multiple languages are encountered, as with po-debconf
> by instance.
> IMO we should not try to have a unique interface, but 2.

Mmm. I dunno. You may be right, but I really would like to unify the
interface. Dunno if it's possible.
 
> [...]
> > - I could also work on po-debiandoc to move it to the new interface
> >   (gettextize, updatepo and translate) and use the new Po.pm. Denis, what do
> >   you think?
> 
> Yes, po-debiandoc should use it.

That is to say ? Do you allow me to hack on your code ?

> > - Last possibility, I could package it as perl module, but I dunno how to do
> >   that, and I would prefer to do something else.
> 
> I do not understand this sentence, what is "it"? po-pod? Po4a?

Mainly, Po.pm.

> PS: is it be possible to rename Po4a into po4a in CVS?  It is error prone.

Sure, but it would need to be a real package.
I thought to name it po4a, or po-all if we want to follow the same naming
convention accross modules. But this one is perticular: it's kind of root in
dependency tree (once Po.pm is there). Or we could call this
liblocale-po4a-perl, if we want to follow the Perl policy ;)

I did do the changes to the maintainer field you said.

Mt.

-- 
Un clavier azerty en vaut deux.




reply via email to

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