I see. Another question to answer would be whether it would be
desirable and helpful to integrate the whole Pootle product to
Native-Lang projects.

Pootle offers online management and translation tools for
localizations (though no Glossary management yet), but automatic
translation using Translation Memory is not supported yet.

The way I see it is that we should contact Pootle developers and ask
them if they would be willing to integrate the online glossary
management/ collaoration tool, as well as Translation Memory-aided
translation. Open source translation memory algorithm is included in
Vaclav Slavik's wonderful too PoEdit, as well as in KDE's Kbabel.

If Pootle developers agree to have theese functions included in their
product, that I think it would be wise to have the product made
avaiable to all the NL projects. Otherwise, it may be wiser to
integrate only glossary management tool, since localizing OOo should
not be done without Translation Memory-assisted translation.

--
Aiet

On Apr 6, 2005 1:49 PM, Charles-H.Schulz <[EMAIL PROTECTED]> wrote:
> Hello,
> 
> I think that many people and projects here would be interested in having
> this tool.
> We can always find a server for this in one of the NL projects if
> SourceCast can't.
> 
> Best,
> 
> Charles.
> 
> On Tue, 2005-04-05 at 00:09 -0700, Louis Suarez-Potts wrote:
> > Hi,
> >
> >
> > >
> > >Louis,
> > >
> > >since you mentioned that a tool like this might need to be linked from
> > >another server, is there a preferance wether such tool should use
> > >specific database or server-side scripting language? Currently, it
> > >uses php for server-side scripting and XML as a database (being the
> > >requirements of the servers it is hosted), but I could modify it to
> > >migrate to MySQL, python, etc.
> >
> > From my end, no.  At least, I don't have a preference at the moment. It
> > actually depends on what server would be available, who would maintain
> > it, their preferences, etc., etc.
> >
> > >
> > >Best regards,
> > >Aiet
> >
> > Best
> > Louis
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to