Hello Alexey,

> >I think this proves my point that the translation should be done by a
> native English speaker.
>
> If you know someone, please give me his contacts.

I already recommended proz.com. This is probably the best site in the world
for finding qualified translators and information on their experience,
credentials, peer reviews etc.

If you select Russian -> English without specifying the native language of
the translator, you get loads of interesting results, including some
native Russian or bilingual translators who live in England or America or
had their education there.

If you specify that the native language must be English, you still get
313 (members) or 2169 (non-members) results. You can even go further and
stipulate that they must be living in Russia. This narrows it down to
13 members and 256 non-members.

Now I'm not saying that these are all good candidates for the job at hand.
But the top of the list usually consists of people with long experience,
verified credentials, etc.

You can also give Concorde Translations a try.
(https://www.concorde.nl/en/translations/contact-info).

I did a lot of translation and correction work for them a number of
years ago, and they were very professional. They work with target
language natives and/or in-country translators exclusively; see
https://www.concorde.nl/en/about-our-translators

However, for a project this size a test translation is always necessary,
and should ultimately be judged by native English speakers. Errors due
to non-familiarity with technical lingo are acceptable, errors betraying
an inadequate command of the target language are not.

Which brings me to the 'parentheses' issue. Believe me, I did read your
message carefully. But someone who translates into English should know
what 'parentheses' are, just as he should know what a 'comma' is, or a
'semicolon'. This has nothing to do with SQL or programmers' jargon,
but with the English language itself. These are parentheses:

 ( )

Words, like BEGIN or END, or word pairs, are not parentheses.
Also, there is no English term "operator parentheses" (and if there was,
it would mean something like "parentheses around an operator").
There is a "parentheses operator" in some languages, but that's an
entirely different beast.

It's perfectly OK for you and me to make this kind of mistakes. But for
a professional translator doing a $7000 job, it is not.


Cheers,
Paul Vinkenoog

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Firebird-docs mailing list
Firebird-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-docs

Reply via email to