From: Andrey Repin <anrdaemon@freemail.ru>
To: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>,
cygwin@cygwin.com
Subject: Re: FAQ and Documentation translation to other languages
Date: Sun, 22 Jul 2012 14:05:00 -0000 [thread overview]
Message-ID: <933427302.20120722180140@mtu-net.ru> (raw)
In-Reply-To: <0105D5C1E0353146B1B222348B0411A20A952A1AD7@NIHMLBX02.nih.gov>
Greetings, Buchbinder, Barry (NIH/NIAID) [E]!
> I've wondered about this. My experience with Google Translate on
> non-technical text to French (which I speak reasonably, though far from
> fluently) is that it often works very well, though occasionally it
> generates a bit of utter nonsense.
It generates utter nonsense 50% of the time, other 50% it is barely
understandable, or at least ambiguous.
This goes into both directions, English -> foreign and foreign -> English.
This was one of the reasons, why I at least cat read/write English.
> My question is whether it is good enough for something like a FAQ? Should
> this be officially recommended?
I wouldn't do so. This may cause more harm, than the potential good that you
may gain from it.
--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 22.07.2012, <17:53>
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-07-22 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 16:18 Buchbinder, Barry (NIH/NIAID) [E]
2012-07-21 17:01 ` David Sastre Medina
2012-07-21 17:38 ` SPC
2012-07-21 17:47 ` David Sastre Medina
2012-07-22 14:05 ` Andrey Repin [this message]
2012-07-22 20:58 ` SPC
2012-07-24 19:09 ` David Sastre Medina
[not found] ` <CACytpF9AYbK_cj4CR2iRwbEdfLSxrQa4wFPqxaSm+z7d0704aA@mail.gmail.com>
2012-07-24 20:35 ` Fwd: " SPC
2012-07-24 20:53 ` David Sastre Medina
2012-07-24 21:21 ` SPC
[not found] <CACytpF_e4Dyaxg6Rse7Y8nYZsMwjLvFGuQgf4dje54zL-WHehg@mail.gmail.com>
[not found] ` <CACytpF_W=rz5dF2PcZPQw-FrchcGo9=DxtCxkObJvV78uSECFw@mail.gmail.com>
2012-07-19 20:39 ` SPC
2012-07-20 8:48 ` Corinna Vinschen
[not found] ` <CACytpF8vDqQRFQsHY0b+fDX92jPs7VVBDO=MgptTYQe5JdYzOQ@mail.gmail.com>
[not found] ` <CACytpF8zAfKC+_e5mCmP_0m4Yz7nqkx1kzagX7eUVfTG7vkJaw@mail.gmail.com>
2012-07-20 21:13 ` SPC
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=933427302.20120722180140@mtu-net.ru \
--to=anrdaemon@freemail.ru \
--cc=BBuchbinder@niaid.nih.gov \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).