Human translation blackbox now has API

by cmod • 16 years ago

36 19 16 years ago

That's pretty awesome for developers. The rates are really low for the translators, but I guess that is the sweet spot for simple content.

Betsy_B2• 16 years ago

I beg to differ. As a translator, I can say the rates are fair, considering the simple content, the well designed job management system, and the reliable, fast paycheck.

rgrieselhuber• 16 years ago

This is one of my favorite startups and they're right here in Tokyo.

fookyong• 16 years ago

indeed. good to see great work coming out of Tokyo - it's a surprisingly small community here...

robert_mygengo5• 16 years ago

Small but we work damn hard :) And fewer distractions unless you count gyoza.

IanLewis• 16 years ago

Even smaller if you don't count Japanese startups.

angrydicemoose• 16 years ago

Great stuff, great for developers.

hussong• 16 years ago

Smart move. On the wordpress side of things, integration of multi-language plugins with translation services has become standard: WPML ties into icanlocalize and qTranslate uses web-translations.com.

Sending translation jobs directly from the CRM (and getting it back in there with all formatting preserved) can save a lot of time and money for long-tail multilingual sites.

The pricing of mygengo looks very competitive, icanlocalize comes in at $0.07/word (value) and web-translations around $.025 (professional).

robert_mygengo5• 16 years ago

(Disclosure: I'm CEO of myGengo)

I'd say the distinction we have over other services is that we offer a completely transparent solution - all our translators are tested and rated to ensure they meet a consistent quality standard, so you don't have to pick and choose them as you do with others.

So you can literally treat us like a machine, which hasn't been true when I've tested those other services (I got bombarded with emails from translators asking me to pick them for my jobs, which really annoyed me).

We think that's pretty compelling for developers, and makes us a much more scalable solution :)

Loic• 16 years ago

Very short question here as it may be of interest for other HN readers. How would you send a .pot file to be translated through your API? Removing everything but the text and send a kind of one page work? Are you splitting the work in the background in smaller chunks if long?

Edit: They have the solution for .po files: http://mygengo.com/string/about

c1sc0• 16 years ago

Have you considered using machine translation to speed up the process? Tokenize > Machine Translation > Human Correction

danohuiginn• 16 years ago

There's a very similar service called Babylon, http://translator.babylon.com/. I'd be interested to hear your take on the differences between the two projects. At first glance, I see 2: (a) they don't yet have an API, and (b) they require qualifications and experience for their translators, whereas you choose them based on a test.

Anything else I'm missing?

[I do occasional translations for Babylon, and have been pretty impressed by the company and the people behind it. But I'll probably sign up for myGengo too, and at least see how it compares]

jeffjim• 16 years ago

Smart move indeed. As far as reaching client, there might be a problem. We have been using http://www.tomedes.com and might consider another solution

amr• 16 years ago

What other languages are you planning to offer? (Dropdown on translation form says more languages are coming soon)

robert_mygengo5• 16 years ago

Our focus is on Asian<>European language pairs. The next to appear will be Korean<>English, Korean<>Japanese, Chinese<>Japanese. But other European languages like Portuguese are coming soon too. A full roadmap is in the works.

Human translation blackbox now has API

Related Stories