Hacker News Reader

Comment by hussong | Hacker News Reader

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).

View on HN

(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 :)

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]

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

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

I can translate most text faster than I can fix a machine translated text.

It is better to offer translators easy access to electronic dictionaries from within the translation window.

We're considering options, but actually optimizing the interface for translators seems to be less controversial (some translators HATE machine pre-translation) and potentially better for performance and quality. But not ruling it out.

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

Reply on news.ycombinator.com