ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Cecil Westerhof <cldwesterhof@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Translating PDF-files
Date: Wed, 19 Jan 2011 14:35:58 +0100	[thread overview]
Message-ID: <AANLkTik+oLMRqXgH1fw-akbGMNasGs7xnFPx23_yy-sd@mail.gmail.com> (raw)
In-Reply-To: <D5E1D04D-BD55-4809-8605-0BEBDDDB9725@hccnet.nl>


[-- Attachment #1.1: Type: text/plain, Size: 972 bytes --]

2011/1/19 R. Ermers <r.ermers@hccnet.nl>

>
> If your acquaintance actually needs an accurate translation into Russian, I
> wonder why he would choose Google Translate for that. Remember that Russian
> has 7 cases, and a complex verbal system with many different forms, all of
> which need to be deduced by Google from the much poorer English prepositions
> and the verbal foms in the text. Even though the result will no doubt show
> cyrillic words, which looks interesting, the factual result will be rubbish,
> and most likely unintelligible to any Russian.
>

I do not know if he requires Russian, he was talking about Ukrainian. But
that maybe has the same problems.

Automatic translation is always a problem. I even do not like the results
from English to Dutch. But his reasoning is: 'better a badly translated
document, as no document'. I am not sure if I agree 100%, but if that is
what he wants, who am I to -keep- telling him he is wrong?

-- 
Cecil Westerhof

[-- Attachment #1.2: Type: text/html, Size: 1255 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2011-01-19 13:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 12:58 Cecil Westerhof
2011-01-19 13:05 ` Martin Schröder
2011-01-19 13:10   ` Cecil Westerhof
2011-01-19 13:12 ` R. Ermers
2011-01-19 13:35   ` Cecil Westerhof [this message]
2011-01-19 14:30   ` Arthur Reutenauer
2011-01-19 15:03     ` R. Ermers
2011-01-19 15:18       ` Arthur Reutenauer
2011-01-19 16:06         ` R. Ermers
2011-01-19 16:18           ` Alan BRASLAU
2011-01-19 19:23             ` Alan BRASLAU
2011-01-20  9:53             ` Yury G. Kudryashov
2011-01-19 13:50 ` luigi scarso
2011-01-19 14:14   ` Cecil Westerhof
2011-01-19 14:23     ` luigi scarso
2011-01-19 14:35       ` Cecil Westerhof
2011-01-19 14:41         ` luigi scarso
2011-01-19 14:51           ` Cecil Westerhof

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=AANLkTik+oLMRqXgH1fw-akbGMNasGs7xnFPx23_yy-sd@mail.gmail.com \
    --to=cldwesterhof@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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).