Translation citizenship -- tree reorg needed?

[Jens Seidel]

On Fri, Feb 06, 2009 at 10:30:12PM +0800, Dongsheng Song wrote:
> 2009/2/2 Jens Seidel <jensseidel at users.sf.net>:
> > On Sun, Feb 01, 2009 at 08:50:17AM +0800, Dongsheng Song wrote:
> >> What about xml2po ? We could do something like this:
> >
> > I asked already about PO support (via po4a which is very good!) and
> > provided also a patch (see the list archive). It was more or less ignored and
> > nobody seems interested.
> 
> I worked a mix build environment[1], translators can choose use po or xml
> freely:

Ah, code was partly stolen from Debian Lenny's Release Notes Makefile
(GPLed) :-))

> So I think our tree structure look like this:
>     ru/
>     ...
>     po/zh.po
>     po/xx.po
>     ...

Is it really necessary to separate between po and other files? Why not just
zh/zh.po or zh/svnbook.po? But I don't care much.
 
> PS: Because xml2po and po4a not compatible, thereby zh have much fuzzy
> strings.

Can you confirm that po4a is better or am I wrong?
 
PS: I do not like all ifdef-logic in the Makefile. It can probably be simplified
using a trick. po4a allows also using of a config file so that the arguments
in the Makefile can be shortened. This is just a note, for the whole discussion
it is completely unimportant and I suggest you first try to convince people
that PO format may be a good idea. I think you agree with this?

Thanks!
Jens