471 karma · joined March 30, 2010
That's absolutely right, you don't. But email deliverability turned from a massive mystery and headache for us, into a sure-fire deal, the day after we implemented SendGrid. We develop translation/localization related apps, not email apps. So for us that's cool :)
Makes me sound like a hard-ass manager... :(
Basically the bundle works with your yaml file and allows you to order translation, either by machine, or using myGengo's human translation service.
The guy who created the bundle has pretty much thought of everything. We're pretty excited by it as it's a great use of our API.
[disclosure — I'm one of the founders of myGengo]
The context problem is a continual issue with translation - but most of the time our customers handle it by adding comments to jobs.
We do allow you to attach comments to the job call - so you can add context there and also links to related material if required. We're considering adding an option to attach files too.
You can also group jobs together if you want them to be handled by a single translator - this obviously takes longer but makes sense for all-in-one projects.
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 :)
Actually this is kind of cool though :)
I think if you keep it simple and convenient, it's nice.