I'm sure all of us J>E translators have noticed the (kind of ridiculous, in my opinion) influx of little teeny tiny jobs from (what I perceive) one single customer -- the ones that all start with <p>.


What do you do about those?  It's been my experience that there's in no way enough information to appropriately translate them, but there's also no way I would be willing to go through and flag every single one of them!  One of them started with, "ない” as a single sentence! Do you just do the best you can and hope, or just ignore them?


Also, there was a $0.05 job (from, again, what I perceive to be the same guy/girl) that was 100% English! That one I flagged.


But seriously, is there no way to group these little bits and pieces in to one (or 10, perhaps) coherent groups?


  • 0

    I'm double-posting and if that's against the rules I apologize, but I read in another thread that it would be nice if Gengo advised customers of etiquette regarding jobs.


    I'd like to propose that rather than "etiquette," per se, before being allowed to order translations they should be greeted with a message that plays up to their sensibilities, I.E. the fact that they want translations quickly, and tell them that if, for example, they want a $50 translation done, but want it done in less than two days, they should break it not sentence by sentence or word by word(ugh!) but into $10-$15 fragments, and provide appropriate and necessary notes regarding background info, necessary vocabulary, and style.


    My reasoning is, in addition to the work being MUCH easier for us translators, it also increases of being completed quickly by 10-fold, as I'm pretty sure most translators jump at the $5 and up translations (assuming they have enough information).  It still won't necessarily be a 100% cohesive translation in the end, but it works to benefit the needs of both translators and customers.

  • 0
    Brent Curtis

    Hello Ashuri!

    Yeah we completely agree! There are real solutions for this type of issue in the pipeline, as we wish the jobs would be grouped too. What often happens is a new API customer has some trouble interfacing with Gengo, and accidentally sends all their jobs as single jobs.

    We absolutely don't expect you to have to flag all of them. But if you could, say, flag one, then maybe send a quick email off to support with a couple example jobs, we can contact the customer and sort it out. Depending on the situation we may even sit them down with our API team to help with the coding.

    This is just a short term fix. For the long term, we want to do things like intelligent grouping or similar solutions.

    For the retail customers using our order form, I like that feedback and we can pass it along to product :) Thanks!

  • 0

    Hi Brent, 

    Just wanted to drop a line to say that this topic had already been raised a number of times and in different flavors in the past on here, from as early as April 2013 (maybe even before).

    E.g. https://support.gengo.com/entries/23510196-How-to-deal-with-extremely-short-source-texts-  https://support.gengo.com/entries/22082510-Teach-clients-not-to-submit-multiple-few-word-translations  https://support.gengo.com/entries/22239670-Fragmented-Jobs  https://support.gengo.com/entries/22715299-Multiple-1-5-word-jobs-why-   https://support.gengo.com/entries/24101854-One-word-jobs-thanks-but-no-thanks  https://support.gengo.com/entries/22441915-Loose-word-groups-of-jobs   etc.

    Also, if the main issue here is that a "new API customer has some trouble interfacing with Gengo, and accidentally sends all their jobs as single jobs", why not just make the grouping the 'default' option for posting this kind of jobs, as already suggested in one of the above threads? That way there just wouldn't be any more 'accidents' of this kind and the customer would have to manually choose to split their source in smaller batches if that actually is what they want (even though that would harm consistency). 

    In the end, I may be wrong, but I kind of doubt that customers who don't even take the time to answer comments and provide context (which would be in their own interest in the first place) would spend a lot of time reading instructions or chatting away with support...

Please sign in to leave a comment.