Re: [Resend] Re: [tlug] Translation

[Niels Kobschätzki <n.kobschaetzki@example.com>]

On Jul 26, 2007, at 4:06 PM, Jean-Christophe Helary wrote:

> On 26 juil. 07, at 16:56, Josh Glover wrote:
>
> > On 26/07/07, Jean-Christophe Helary <fusion@example.com> wrote:
> >
> > > By the way (shameless plug) OmegaT's latest test version has a
> > > mediawiki import function to allow translators to easily get the
> > > source data, match it to existing translation memories (or
> > > glossaries) and proceed.
> > >
> > > http://sourceforge.net/projects/omegat/
> >
> > This sounds very cool, but I am too time-poor to even click the link.
> > Would you mind presenting a user story to demonstrate what problem
> > your project solves? Shaggy dogs welcome, according to Steve. ;)
>
> You can keep terminology consistent in an easier way-> OmegaT  
> matches the words to translate to a glossary you provide.
>
> OmegaT automatically translates identical sentences and proposes  
> you translations based on similarity with what you have already  
> translated (or with reference translations you use).
>
> When you work with tagged files (HTML, ODF etc) OmegaT "protects"  
> the tags to that you can't make a mess of the file when translating  
> it (unlike when you translate directly inside the code). You can  
> still make a mess though :) But it is easier to clean because  
> OmegaT will tell you exactly which tags you maimed :)

The problem is that the ppl want to translate literature here and CAT  
doesn't really work with literature. It's good for all stuff were  
general translation works but not really for literature…

Niels