1

Hi,

I thought that we didn't have to translate the 100% match strings as they are not included in the word count (and because obviously their translation matches the glossary).

Am I wrong?

6件のコメント

  • 1
    Avatar
    Rica Tero

    Hi @logos!

    Thanks for sharing that concern. I'm not entirely sure about it, so I created a ticket for you. Please share the details, like job ID, LP, etc., with the support team, as they might need to contact the PM. Thank you.

  • 6
    Avatar
    Paresseux

    Short answer: if it's greyed out, it can't be translated and doesn't add to the word count. If not, it's part of the translation and should be included in the word count, even if it's a translation memory match. I certainly get paid for 100% match strings (2 cents a word, but still). So consider them as editing jobs: if you think the existing translation is good, let it stand; if not, make necessary changes. After all, if the 100% match is completely off the mark, you're going to get a bad review because you've allowed a mistranslation reach the customer.

  • 1
    Avatar
    Rica Tero

    @Paresseux, that's an additional knowledge for me!
    It's greatly appreciated you shared this information. 💕

  • 3
    Avatar
    gunnarbu

    Hello Paresseux. That is also my understanding. In some special cases I have indeed corrected the 100% match, but it keeps coming back without the 'correction' in new jobs from the same client that include the same expression. Also, in such cases, i.e. where the same 100% match expression is repeated in many different jobs, and the 100% match is still erraneous, the client risks that different translators correct the same erraneous 100 % match in different ways - I wonder how the clients manage that?

  • 6
    Avatar
    mdj_cm

    On a side note, if the 100% match strings ($0.015/w MTPE) require too much work (e.g. bad literal translations requiring completely new translations), leading to underpaid jobs in your country, then please proceed as follows:

    cancel / unreasonable request / "bad MTPE, underpaid job"

     

  • 3
    Avatar
    Chris

    As some have alluded to, there are three different cases, here:  Glossary, Translation Memory (TM) and Machine Translation (MT/MTPE). The latter two lead to a lower payment, in my opinion too low. Like mentioned, the translator takes full responsibility for the quality of the translation and the starting point is often bad, especially with shorter strings.

    To the best of my recollection, Glossary terms (as in the integrated glossary) aren't prefilled, so the OP is likely talking about TM or MT. I haven't worked on a Glossary job in a while, though, so I might be wrong.

    In my experience, translations for matching jobs in the same collection will be prefilled automatically, but changes to the TM are only reflected once the collection is submitted (after which both versions appear as suggestions). If there is a wrong glossary term, I'd leave a comment pointing that out and ideally get confirmation from the customer.

    The TM can be quite good at times and horrible at others. In the more positive cases, it seems to be customer and project specific, in others, only customer specific or even completely unrelated/general. Not sure if those are customer submitted or if Gengo offers to use or start out with a general TM (or maybe it's assigned by project managers).
    Either way, shorter strings can be a problem in all those cases.

サインインしてコメントを残してください。