7

On the 21th I received a review where I got two omission errors on these texts:

<スマートフォンアプリ(iOSとAndroid)>

<PCのウェブブラウザ>

According to the review (screenshot [omitted]), these are seen 'translated' as '{1}' and '{2}', respectively.

While in fact, in the actual submitted translation, I DID properly translate those parts, as you can see [omitted].

So for some reasons, when this job got presented to the LS for review, the <スマートフォンアプリ(iOSとAndroid)> and <PCのウェブブラウザ> were replaced by {1} and {2} respectively. I contacted support, and they suggested me to send a re-review request instead, citing that I could reach the Translator Operations team directly by using it.

So I wrote a re-review request explaining the matter in English (usually I wrote these in my first language since the person you're interacting with is the LS and not Gengo team) and presenting the proofs, in hope that aside from LS, the Gengo team could also read and understand that there's something wrong in the material presented that it has missing content compared to the original translation.

Today (27/11), I received the re-review result. The score? EXACT same one as I get in the first place. As if they did not read, or simply chose to brush aside my explanation and just treated it as your usual re-review request.

This is concerning as this is a serious issue on their end and despite me trying to give explanation and proofs, the team failed to acknowledge the issue let alone look into it.

5件のコメント

  • 1
    Avatar
    Rica Tero

    Hi @Ryan. 

    I apologize for the late response to this matter. I checked with the team, and your issue is now resolved. I deleted the screenshots shared here as they violated the forum guidelines. Please be careful next time, as it might lead to grave consequences.

    We will improve and continuously share the re-review process with our community, so everyone will be informed of the whole process. We are always grateful for your support, patience, and understanding on this matter.

  • 1
    Avatar
    Rica Tero

    No worries, @Ryan. I understand your frustration with the matter and the need for evidence to support it.


    I just don't want you to encounter another issue due to a violation of guidelines or agreement when you are already facing another one. If you are unfamiliar with what to do about a certain situation, don't hesitate to contact the support team or me. You can also consult our translator support resources.😊

  • 0
    Avatar
    Ustimenko Ilya

    The problem here is wrong type of angle brackets. Enclosed content was treated as html tags and is missing from delivered translation.

  • 0
    Avatar
    Ryan

    @UI - That's what I suspected as well. Still, considering that many of us are not that well-versed in html, I think that they could've put out some kind of warning of potential transformation to html tag before I submitted the translation. Nevertheless, I got a second re-review where they finally revised my score.

     

    @Rica - Understood, Rica. I normally refrain from sharing identifiable information of a job, it's just in this specific case, I don't think I can really convey my case without presenting the actual proof i.e. screenshot.

  • 0
    Avatar
    Ryan

    Duly noted, and I appreciate your concern for me @Rica.

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