Re: [native-lang] Integrating OOo Online Glossary Management to xy.openoffice.org

Hi Aiet

The Pootle developers are listening :-)

I am very keen to see integration between Pootle and glossary management 
and Translation Memory.
These are the issues as far as I see it...

- Pootle still has some important initial goals to finish off, such as 
managing permissions, goals etc. Permissions is almost done now, and I 
am working on goals. I want to make sure I get these things finished off 
first.
- I don't know much about the architecture of your glossary tool. It 
would be nice to find a way to integrate them that is simple. Could you 
describe the architecture (language, database etc), requirements, and 
basic 'how-it-works'?
- Translation Memory is also important. It's not neccessarily easy to 
just pull the translation memory out of other programs. I have my own 
ideas about how to do this. If a third-party tool is integrated the 
architecture discussion would need to happen as for the Glossary tool.
- I would say Pootle is not quite ready for general release yet, and is 
still in active development. However, it is approaching release time. It 
would be great if we could have a nice server to run a central Pootle 
server off (currently running on a fairly small system that has been 
offered in the mean time). And obviously the wider range of 
functionality available together with it the better. I do not expect 
that it would be easy to integrate with SourceCast... but would be 
gladly proved wrong :-)
- Pootle can support multiple projects and languages. Currently it is 
assumed these are all hosted off one site, however we could work at 
linking it into the existing openoffice site structure in due course.

David

Aiet Kolkhi wrote:

>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]
>
>  
>