9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: <plan9@itic.ca>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] OT -  Machine translation
Date: Tue, 14 May 2002 06:25:20 -0500	[thread overview]
Message-ID: <001e01c1fb3a$07fed260$fdffa8c0@itic.ca> (raw)
In-Reply-To: <3CE0DA59.CD735BE2@strakt.com>

Hi all,

Just to let you know about our experience of computer aided translations :

We have tried many of them... now we contract translators. The quality of
any translation fairly depends on 2 major factors : the first one is the
``style'' of the author. As soon as non regular syntax or idioms are used,
the translator process gets crazy. The second one is the lexical field. Some
translators are computing aware when others are not.

As an example, Russian requires a russian IT guy. Even a very youg one is ok
!!! French requires someone that is particulary confident with both grammar
and syntax since vocabulary is almost ``frenglish'', sometimes even english.
German has a very [excessively] structured syntax (software are almost good
for that) but you need a GermandictionnaryguythatspeekconstructedITwords :-)

Korean is the one I prefer :-) You need a korean guy, a korean dictionnary,
a US kbd, some korean pictures and some scotch tape... :-) The guy need to
type 4 keys to generate one Rune :-(  [and he only drinks tea]

In a very few words,

If you puting are that on you page translation were computated generates,
Not I am going to read her ...

----- Original Message -----
From: "Boyd Roberts" <boyd@strakt.com>
To: <9fans@cse.psu.edu>
Sent: Tuesday, May 14, 2002 4:35 AM
Subject: Re: [9fans] OT - Machine translation


Andrew Simmons wrote:
>
> I think Boyd is being a bit harsh on machine translations. I don't know
what
> Google uses, but I feel that their translations into English achieve a
> certain sublime poetry.

Strangely enough google generates the same text as bablefish:

    Pourquoi est-ce que pas le babelfish d'utilisation
    (http://babelfish.altavista.com/) une sorte de version
    d'alpha d'une traduction obtiennent commenc�e, et vous
    pourrait la signaler, et les gens pourraient-ils s'amuser
    et soumettre alors les corrections et le document pourrait-elle
    �tre am�lior�e de l� sur une base �volutionnaire?

Although it is interesting to speculate how the translation was done.

To quote from their translation FAQ:

    Unfortunately, today's most sophisticated software doesn't
    approach the fluency of a native speaker or possess the
    skill of a professional translator. Automatic translation
    is very difficult, as the meaning of words depends upon the
    context in which they are used. Because of this, accurate
    translation requires an understanding of context, as well
    as an understanding of the structure and rules of a language.
    While many engineers and linguists are working on the problem,
    it will be some time before anyone can offer a quick and seamless
    translation experience. In the interim, we hope the service
    we provide is useful for most purposes.

I couldn't agree more.

Once the context is lost the semantic content has usually been destroyed.




  reply	other threads:[~2002-05-14 11:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14  7:31 Andrew Simmons
2002-05-14  9:35 ` Boyd Roberts
2002-05-14 11:25   ` plan9 [this message]
2002-05-14 10:43     ` Boyd Roberts
2002-05-14 10:14 Andrew Simmons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001e01c1fb3a$07fed260$fdffa8c0@itic.ca' \
    --to=plan9@itic.ca \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).