Marcin Miłkowski wrote:

> Hi All,
> 
> I think we should not overestimate Pootle. It doesn't support
> translation memories (it doesn't support fuzzy matching) because of
> performance considerations. And that makes it  something roughly equal
> to subversion/CVS, and not really a perfect translation tool. Now, I
> think we do _need_ a translation memory tool to enhance the quality and
> quality assurance of the localized versions as well.
> 
> For excellent review, read here:
> http://en.wikipedia.org/wiki/Translation_memory
> 
> And now the part you can't read in Wikipedia but most interesting to all
> of us: Open Language Tools is being developed at Sun and it has a server
> version (runs on Oracle, AFAIR). They are in the process of making a
> decision to release the code of the TM server but what we'd really need
> is a working TM server. And hopefully it could be integrated into Pootle
> for storage purposes. I can try to convince people working on OLT to do
> so.
> 

I'm against Pootle as storage and against all about OLT at this point of
time. We have translators, who used gettext based tools (also open btw) for
a years and who also participate in many other projects (KDE, Gnome, GNU
applications, various distributions like SUSE, Mandriva - and reuse also
translation compendiums across all this software).
Makes it sense to force them to use two different interfaces? Or throw a
line between Sun (only some 9 language) translators and community
translators (several dozens) and their long-time experience?
Sorry, when this message seems irritating, but I'm open to discussion. And
fix me when I'm wrong in some predjustices.
Maybe you should change experience with opensuse people, they have quite
good working translation service with merging po-repositories with updated
pot-files, updating new strings using translation memory (held in server),
subversion system with a lot of easier access for newcomers than oo.o cvs.
etc.

ain

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

Reply via email to