[Po4a-devel]Merging po4a-like efforts?

[Martin Quinson]

--WhfpMioaduB5tiZL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 27, 2005 at 11:00:44PM +0200, Jordi Vilalta wrote:
> On Wed, 27 Apr 2005, Martin Quinson wrote:
> >On Sun, Apr 17, 2005 at 01:23:43PM +0200, Jordi Vilalta wrote:
> >>Maybe all this is like an utopia, but I think it's the way to go. If we
> >>decide to follow one of these roads we should tell the other projects.
> >
> >Well. I'm quite sure some of them are on this list ;) And I'm not sure we
> >should announce it too much before it gets implemented. I mean that I wo=
n't
> >have much time for this before months, and I hate announcing what I can'=
t=20
> >do ;)
>=20
> I meant to ask for help to other groups:

sure, but maybe preparing a preliminary specification could help, I think.
As you say, we need to find a way to deal with multi-translation document in
transtractor and it then can be considered as a proof of concept
implementation of the kernel. At least, I think so.

> >>- First, we (all the involved projects) should define a common interface
> >>  (extending the TransTractor one, for example) that would be able to
> >>  handle all the posible file formats (more than one translation on the
> >>  same file, etc.)
>=20
> I think we should talk to other projects to see their point of view, and=
=20
> to be able to define a generic enough solution. Else we would fall into a=
=20
> limited solution that would leave us nearly where we are now (each projec=
t=20
> dealing with their own solution).

In my mind, the main show stopper to the merge for now is that everyone uses
python beside us, which prevent us from stealing as much code as I would
like to. If we go for a C interface, we could share more easily. po4a could
become a C/perl/python stuff, if we're crazy enough to go that way.

> And maybe it would be interesting to create a new common project to=20
> concentrate all these projects' people doing the kernel, for example.

If you feel like speaking about this idea to the other groups, it'd be great
;)


Thanks for your time,
Mt.

--WhfpMioaduB5tiZL
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCcA/SIiC/MeFF8zQRAlTlAJ9vpf6t6a3BDlv14mEU33KLFQgqfwCgrrO7
l4Pt9EIExXwrvrD63thoLAc=
=BSar
-----END PGP SIGNATURE-----

--WhfpMioaduB5tiZL--