Hello,
I wanted to share this to see if I'm the only one that has experienced these very frustrating issues or if this could be a wider problem with regards of how jobs are reviewed.
First up there's the issue of subjective matters, and I can take direct examples of my own experiences so we're not even talking about imaginative scenarios. I've gotten marked multiple times as errors cases where I've translated words correctly but that the LS's consider that the English word is commonly used and should be left as is. Now, while I agree that a segment of the population, mainly the well-off and the ones that already speak English would have no issue with words in English being thrown in, I'm thinking here of people who speak no English at all. One example is the word: "vintage" and in this case it was used to describe clothing. I translated it as "con acabado antiguo" which in English would be something like "with an antique look". So, my translation isn't incorrect in the sense that I am not choosing the wrong words to convey what the original text says, but the LS's consider that it is an error because they consider that the word in English is widely used and should not be translated. All of this are subjective matters and what interests me is the question if my translation should be marked as an error? I would totally be okay with a suggestion (which is not marked as an error, mainly as a note for future jobs), but why is it an error? And who decides when the English word is sufficiently used to leave it as is? Yeah, I'd understand it and my English-fluent friends would as well, but I'm sure my immediate family who doesn't speak any English at all would struggle with those. Again, this is only an example but the list of words where this very same issue could happen is an extensive one. But the fundamental question is: in these cases; should they be marked as errors or simply as suggestions? I think it's also worth noting that our job is to translate and the goal is to translate one text and make it fully intelligible in the target language. When you consider this, I'd argue that my take on it, to translate them instead of leaving the source text as it is, is the better option of the two.
Another issue that I've seen happen is when it comes to large volume and multiple jobs from the same customer. I know we're not supposed to talk about who the customers are - according to the Translation Agreement -, as far as I understood, and I want to respect that, so let's just say that in this case I'm talking about a large e-commerce platform that sells all kinds of products. Pretty much anything you can imagine, you'd find it in such platform. Now, the issue here is mainly about brand names. And I want to point out that in the customer's instructions, there is no glossary of brand names nor any links to product's pages in order to see if the text is referring to the actual description of the product or if it's part of the name of the brand, and to see where in the text does the brand name begin and where it ends. I can also use a real-life example of one that occurred to me. So apparently there is a clothing brand whose name is: "Screaming Eagle", and in my case the text was describing a jacket from this brand. Now, I don't know if screaming eagle is the name of the brand or if the actual jacket has a screaming eagle and the product description is describing that. I should note that all of these jobs are TM jobs, so very poorly paid and again, no info or reference as to what are brand names or even links to the products so that translators can check them. It is also worth mentioning the immense volume of jobs coming in sometimes and the ranges of products that are covered, in essence: anything you could find at a large e-commerce store. So, I'm talking about products and categories that vary from auto parts - and those being both electrical and mechanical parts -, clothing, musical instruments, camera gear, baby products, food products, toys, furniture, home appliances, electronics of all kinds (computers, phones, tablets, etc.), audio equipment, beauty products, personal hygiene, cleaning products etc. And that is only to name a few or the ones that come to mind right now. Am I supposed to be familiar with all the brands that exist in all of the above mentioned (and beyond) categories of products? And with no index or listings of brand names or any links to the products themselves? And on top of that, with the incredible volume of these type of jobs and the very low compensation? And yet, they were marked as critical errors, and thus, severely impacting my final score of the review.
At this point I'm simply tired and don't even want to submit re-review processes because they never seem to understand what my actual point is, and in many cases, they only double down or simply ignore some instances and they don't even comment on why they don't think it was wrong, so in some cases I don't even get any answers from the LS's. And sometimes people simply don't want to admit they were wrong and instead double down on their stance.
I thank you for taking the time to read all of this, and I wonder if there's others that have faced similar frustrating situations like the ones mentioned above?
87 comments
I'm going to try to be brief... I'd say that yes, the reviews can be frustrating sometimes, although in my experience the reviewers are right in most cases.
Re: vintage, I'd personally agree that one is debatable although it would have to be considered in context. In my understanding, "vintage" does not always refer to new products with an oldfashioned look, but mainly to things that are genuinely old...
Re: brand and product names, I hate that one as well. I don't get to see the example you mention in my language pair, but there are others. I think that basically everything that's capitalized, such as, Screaming Eagle, is suspicious of being a name, so you basicaly have no other choice but to Google it if you want to check. I have encountered one case though, where the customer wanted to have all the product names translated - converting the whole thing into a "transcreation" (as opposed to translation) job. Whenever I find that kind of requests I'd rather not accept them, especially not at Standard rate.
Same here. It is frustrating. It simply puts us at the mercy of senior translators who sometimes downgrade our scores for no legit reason.
Hi Fernando,
It sounds like a frustrating situation. You're not alone. Over the years that I've followed these message boards, I think I've read more frustration and angst regarding translation reviews than for any other general workflow topic here.
For the issue of brand names:
I translate into English from a language where the source material is always inconsistent with capitalization (brand names are often written in lower case while common nouns are frequently and inexplicably written with initial capital letters). Obviously, this makes it difficult at times to determine what is and isn't a brand name.
However, the main TM client for whom I see jobs of this nature supplies accompanying photographs of the items in question, and invariably one of the photos shows the brand logo or label, solving the confusion. Otherwise, a quick Google search usually provides the answer I need.
Yes, it's a bit annoying, and yes, those TM jobs don't pay very richly, but it is what it is. When I accept one of the jobs, I realize it will often require a good deal of research to make sense of sloppy, error-ridden source text. I try to make it fun and take pride in correcting source misspellings of brand names, designer names, etc.
As for "vintage," I wonder if a standard Spanish-only dictionary published in your country/region (ie Europe or Latin America) lists the word? If it does, I would consider it fair game to leave in a Spanish translation. If it doesn't, then wouldn't a good bilingual dictionary give you the standard, "official" translation? It seems to me that if you follow standard practice as found in an authoritative dictionary for your region or country, then you're basically covered from a LS review perspective. (With the caveat that some clients offer glossaries for certain words/terms that would take precedence over a general dictionary. The client that I alluded to earlier, for example, provides a glossary that includes "vintage.")
Hang in there!
Hi Fernando,
I think Kevan above has offered great advice regarding those TM jobs -- research :) Of course, you're not expected to be familiar with all brand names (could someone, ever, really?) but when in doubt or unsure, a quick Google search of the product should be enough to shed some light and point you in the right direction.
As for "vintage", in the fashion industry in Spain, this is a term which is used as is (untranslated) to describe a certain style, which doesn't always entirely match the connotations that the word "antiguo" has when you translate it. Please note that it's always important to stay aware of the context, the type of text, and the type of target audience for that text, meaning that in the context of a product description or even a fashion magazine, you can assume that the intention is to use language consistent with industry standard.
Regardless, while I do understand your frustration and that there may have been other instances that you don't mention above, as always, the best way to address these issues and to have the team look at them is to fill out a review for a re-request. These requests not only provide feedback to the LS and to the Quality team at large, but also serve as a reference for us to know when something may not be working as intended.
Hope this helps!
Lara
Hello,
I have also often felt frustrated by the absence of any communication channel with the LS.
I would suggest that the link towards the rereview process be present on all our reviews, instead of having to search for it deep down in the support guidelines:
https://support.gengo.com/hc/en-us/articles/360043592993-What-is-a-re-review-request-and-how-do-I-submit-one- (try finding the "here" which is barely visible in a slighter greener font in the middle of the page).
Or at least, there should be some form of messaging service to ask for clarification on the error. I usually don't go to the trouble of asking for a rereview (It annoys me to have to explain that a translation of "twenty" to "vingt" in French is clearly not a misspelling error for example. Even if the style guide says we should use numbers, I can give you hundreds of examples where Victor Hugo writes "vingt", and the customer clearly chose to use letters in the source text...).
If one could leave a quick comment or question to the LS, I think we would all feel less frustrated by the LS's "ivory tower", and we would learn a thing or too in the process instead of being put off (and frustrated) by all the warnings on the "rereview request" page.
Lara, you now that what you state is not exactly true:
Recently, on 17/05/2020 (with no notification, no collection no., nothing) I had a 1 tenth deduction + the arrow downwards. I notified this irregularity to support and to you Lara and the answer nobody knew the answer, but the deduction was not rectified. When insisting in getting a reasonable answer both to support and to Lara, the answer was absolute silence on both parts. Is this the respect that translators deserve?
And on 14/6/2020, the same happened again: the same deduction but no notification (this time with collection number). This is totally unethical, unprofessional an unacceptable fron any point of view, but nobody does anything. We translators are totally scorned, with no real vias to defend ourselves (at least my case)
The new modality in gengo is that when you insist in getting a reasonable answer to your question, they simply don’t answer (at least that was my experience regarding support and Lara).
Same problem here. I recently submitted a re-review request about a word that the senior translator judged - subjectively - was wrong in context, which I 100% disagree. He is the only senior translator in my language, so that is it, there is nothing we can do.
@Ballmar — About your score deduction, I have seen your exchanges with Support in which not only the way the score is calculated has been repeatedly explained to you, but also they have provided the charts on a spreadsheet to show how each of your scores affected the overall final calculation. You may agree or disagree with the formula, of course, but on our end we have done as much as we can to try to explain it to you.
Also, for the record: last time you wrote to me, you were already in touch with Antonio and he was already familiar with your case. I immediately responded to inform you of this and that he was working on a reply. While it’s true that it took him a while to respond to you, he eventually did, and I expressly wrote to you to inform you about this as well. If you didn’t receive our emails, as you claim, I’m more than happy to resend them anytime :) Just let me know!
@Bruno — please email me at lara.fernandez@gengo.com so I can bring this up with the team. While this is not standard procedure, and while I can’t promise changes, we understand LSs are human and can make mistakes, and I would rather double check just in case, especially if there’s only one LS in your language pair.
Hello, Lara, lately the support team and you seem to understand what suits you best but not what you are exactly asked:
This time I wasn’t referring to the different unfair deductions from different collections with which I didn’t agree at all because they were absolutely unfair, but to the one with no previous notification, or collection number or any other reference.
Regarding that issue, as you referred to it publicly, I remind you the content of my question and Antonio’s answer to it:
* My FR-EN scorecard, with no review or notification in the middle, the 17/05 late in the night, suddenly changed from 8.9 with a green arrow upwards to 8.8 with a red arrow downwards.
“You received a review for Job 68147342 on May 16, with a score of 10/10. The word count of this job is 36, and it was replacing another 10/10 with a word count of 85, so maybe this is the reason the score dropped a decimal point (since the average, on which the score is based, is weighted based on word count and recency). I know it’s difficult to understand, even for us, so I hope it kind of makes sense.”
In my opinion, the answer is absolutely offensive and insulting, since cannot be a deduction with no justification (no collection number, no notification, nothing), and also adding that it was maybe due to a 10/10 score on previous review. If you think this make sense, I must have lost my rationality.
And it is absolutely true that you did not answer to my message questionning the insulting answer from Antonio, for which silence I ironically thanked you. Do you remember?
Hi Ballmar — my apologies. I actually just checked in my email and saw that you did email me after Antonio’s reply, but it somehow didn’t show in my Primary folder. For this one email, I do apologize that I missed it. Over the years, we’ve repeatedly exchanged lengthy emails and never once I have failed to reply to you (or to any other translator) on purpose.
Regardless, there was no need for me to reply further because Antonio’s explanation is correct: you did receive a review on May 16th. Perhaps, just like I missed your last email, you missed the email notification about it. Or perhaps there was a malfunction on that day with the notification system. Luckily, all of our translators have access to their GoCheck history from their dashboard so it’s easy for you to verify this information. I have just hijacked your account and checked the GoCheck history for your FR>EN-GB and the review of May 16th is there. Please click View History next to FR>EN-GB on your Scorecard to view all your past GoChecks :)
At any rate, as you know, I’m always open to discussion — but this doesn’t mean that I can change the system.
Lara, the review you mention (see below) is previous to the one I'm referring to for the last two months
I have repeated for two months that what I'm referring to is to have been deducted a tenth and a red arrow downwards from a non existing collection, with no review notification and with no reference whatsoever. Do I explain myself?
I hate reiteration for it speaks badly of both emisor and receiver but I had to do it again and again. Therefore, my conclusion is that, either I have a communication problem that prevent my message to get through or the people whom I try to communicate it are not interested in understanding it.
Can you understand that a non existing collection can not be shown on my GoCheck history and that, therefore, nothing can be deducted from it? Do you consider it acceptable and fair?
Hi Ballmar,
What seems to be implied is that at least the score change on the 17th of May was simply a delayed effect of the review on the 16th.
Have you considered this / can you exclude this? (Not trying to be insulting, btw., and I don't think it was anyone's intention to insult you.)
Hello, Chris,
I know what I'm talking about. If I say that I feel insulted is what I exactly mean. No need for outer interpretations. Thanks.
Hello all,
I think that very many of the issues you have with LS, or the customer for that matter, regarding e.g. brand names or using commonly used English terms like 'vintage' in the target text could have been easily avoided/solved by posting comments like the following in the customer comments field: Example 1) "I am aware that 'vintage' is commonly used and understood in Spanish, however in this particular context I have used a Spanish term, as that flows better here. (Please advise if you nevertheless prefer that I use 'vintage' as is.)" Example 2) I have assumed that 'Screaming Eagle' is a brand name and left it untranslated. Please advise if that is not correct, or if you neverthelss want me to translate it."
Gunnar
@Ballmar — I understand you perfectly and like always, try to explain things as clearly as I can. Like I’ve mentioned before to you personally via email, however, respect is a two-way street and I’d appreciate it if you kept a civil tone.
The review affecting your score is the one from May 16th which you’ve pasted, not some “non-existing collection”, despite the slight time delay (we can’t really know at what time exactly you saw or noticed the change) but looking at your score changes, it does match your scores and the deduction that you keep mentioning. I infer your issue is rather that you can’t accept that this review had an effect of decreasing your score, being a 10/10, and you expected it to increase — this would be a better, more objective way to frame your question. In reality, like Antonio has explained to you, like it’s written in our Support articles, and like I have explained to others here in the forums, this is not always necessarily the case because the average part of your score is weighted. This means that while your newest score is a 10/10 and in as simple average calculation it would indeed increase your score, in the weighted calculation it reshuffles the weight of each score taken into account. As Antonio mentioned, this job is shorter than the 10/10 it pushed out the list, and therefore it has a lighter weight on the overall result. As the weight was reshuffle other slightly lower scores for longer jobs also became heavier and therefore the final score is slightly lower than the previous. Additionally as always, the standard deviation is deducted. How this one specific score results in this calculation has, once again, been shown to you, and while I understand that you may not agree with this type of formula, there’s no ongoing “irregularity.”
If you wish to further discuss this topic, please feel free to email me directly.
I would also additionally like to remind you of our Guidelines for participation, as your tone, not only to me but also to fellow translators trying to help you understand what I’m explaining, is growing increasingly aggressive:
Guidelines for Participation
DO help others—if you can! :)
DO respect your fellow translators and Language Specialists / Reviewers
DON’T report urgent technical issues; these go here
DON’T make comments that are hurtful, mean or likely to make anyone uncomfortable
@gunnarbu — Great advice :)
I want to thank everyone for their replies and contributions to the discussion. That's the main reason why I thought it was important to start this topic and I can already see that there's many like me that feel that this process has a long way to go when it comes to perfecting it.
Rup75 - You mention that you'd rather not take those types of jobs, especially at a Standard rate, but this one's are not even standard rate, as I mentioned in my post, due to them being TM, they're almost half of what a standard rate job is.
Emre Yapar - I do think it is frustrating when they don't offer a genuine chance for dialogue, and like I mentioned in the post, some people only double down on their original stance when questioned by others.
KevanSF - Thank you for your lengthy reply and your insights. I think you understand what I mean when I say that it seems unreasonable to work that way when the client doesn't provide any photos or links so that translators can see what the product or brand is. I've relied on Google searches to look them up, but given the wide range of products, sometimes you don't really find an easier. While a lot of them are big brand names that I don't even have to look up, a lot of them are not or they seem to be more like Made In China products that will not have a website or easily accessible information. It's funny that you mention the dictionary example, because I have used that as a guidance and I have been penalized in other reviews for doing that. In an example that I remember, I used a word provided by the dictionary in order to avoid a colloquial term that you couldn't even find in a dictionary, and I got it marked wrong because the LS determined that the word isn't commonly used in my country. Again, this is why I allude to "subjective matters" in reviews. How am I supposed to know what one LS considers fair game and thus will not be marked as an error, and what another doesn't and thus, will be marked as an error.
Lara Fernandez - I guess the first part I already answered above, in my reply to Kevan, that a Google search (which is a practice that I regularly use due to the lack of info provided for these jobs) doesn't always help. The example that you provide doesn't apply because I was translating for Mexican Spanish and not from Spain.You say: "Please note that it's always important to stay aware of the context, the type of text, and the type of target audience for that text" and you are precisely saying that I'm right. Because precisely because of those reasons, I based my decision in translating it instead of leaving the English word. In my country, 42% of the population live in either poverty or extreme poverty, the vast majority of these don't speak English, many of them hardly have basic formal education and some don't even have that. I'm thinking of those people who will not understand words that are in English. Even if the small minority of the top classes do and use them around frequently. I know neither you nor the LS have any bad intentions nor do it on purpose, but I think it's a bit insulting to not think of the people who will not understand that. Again, our job is to make a text fully intelligible to everyone, and I always try to keep in mind that the person reading the translation might perhaps not know a word in English, so it's my job that they'll still be able to fully understand the translated text, if not, I think you're failing at what you do. And again, as I mentioned in the original post, and as others have replied, sometimes you submit a re-review only to have parts of it completely ignored, no explanation and no modifications, in essence the message they send (whether they intend to or not) is: It's an error because I say so. I don't think this speaks very well, or it doesn't seem like there's an enthusiasm for listening and learning about what could be improved as you mentioned in your reply.
AlexF - Yes, I have also been intimidated and put off due to all the warnings of submitting a re-review request. In fact, in the link you provided, it warns that it should be done sparingly.
gunnarbu - Thanks for your reply and tips Gunnar. However in this case that process doesn't apply because the ones marking an error are the LS's and not the customer itself. It could very well be that the customer is perfectly happy of my decisions but it doesn't matter because the LS is the one determining that it is wrong. In fact, given the nature of these jobs, you wouldn't even be able to get a reply from the customer, but even if you could and acted upon their requests, it doesn't matter if the LS in the end thinks that it is wrong from his perspective. In at least two occasions, I've gotten bad reviews for following customer's orders. I don't know if this is because LS's don't have access to the job comments and instructions or simply because they don't read them, and thus, don't take it into account when reviewing the final translation.
Thanks again to everyone for their contributions, I think we all can learn everyday and this is why we do this.
@Fernando - I fully understand you frustration, and what you mean about the context of the demographic in Mexico (and it is commendable that you always try to put yourself in the shoes of the reader like that, I think this is an amazing skill and trait to have!) What I wanted to point out in my comment (more or less successfully) is the fact that sometimes the "target audience" is a demographic familiar with a certain industry and it may call for the usage of language specific to said industry (and I understand how this, in certain situations, may seem "exclusive".) Also, please note I'm just trying to bring up that perspective as something to also think about and consider :)
At any rate, while I also understand that it might be "tiring" to fill out a re-review request, please just allow me to reiterate that this is actually important, not only because the review might change, but because it serves as feedback, both for the LSs and for us, and it also leaves a track history that we can always go back and refer to (track history of your requests, track history of patterns with an LS that we may come to see later, and so on and so forth).
Thank you so much for your elaborate comment and for opening up the discussion :)
Oh, also (sorry for the broken comments) @gunnarbu's tips are actually useful because, even though the comment section is for the customers, LSs are supposed to take said comments into account when reviewing a job, so that would give them insight into your thought process and choices when considering whether to mark something as an error or not :) And if you've ever gotten a review that is contradictory to the customer's specific requests, you're more than entitled to have the job re-reviewed, as our LSs are supposed to prioritize customer's instructions (it just may happen that they failed or forgot to read the instructions, as they're human after all, but if you were indeed following said instructions, you should request a re-review). Please keep this in mind in the future!
Thanks for your insights Lara. I still think Gunnar's tips are not applicable as these types of jobs are the ones that get approved automatically without a pending approval of the customer. I guess you'd know more about this than I do, but I guess it'd be very hard to get a response from the customer (which i highly doubt that there'll be one given that these jobs are high volume and I doubt there's someone at the other end replying to doubts from translators) but in any case, we all know that there is a time constraint for each job that is implemented by the platform, so let us assume that you can ask the customer when in doubt, and you ask them, but as is almost always the case, even if they reply, they take a lot longer than what the time constraint allows before the job expires, so in any case, I'd have to submit the job as to not lose it, and this in turn, automatically approves the job without the possibility of getting a reply from the customer and of further changes in the future. As to the second point, I find it enlightening and confusing because as I mentioned, I've gotten bad reviews twice, that could've easily been avoided by reading the comments. In the first instance, I submitted a re-review and even though it was corrected in my favour (I could tell because my score went up considerably even though no new reviews had taken place) I never recieved a formal reply that the review had been corrected in my favour due to the fact that I was following customer's instructions. Why they didn't do this in the first place, even if you mention that they do indeed have access to this information, I have no idea. Do they also get scores? Do they also get penalized as we do when we commit an error? Yes, I understand they're also human and can commit errors (as we do) but then it'd only be fair that they also get some sort of penalization when they commit an error (as we do). I'm not asking or have any interest in vengeance - nor that is why I ask this -, I'm asking for reasons of fairness and equality.
Which takes me to the second instance where this happened. I submitted a job re-review noting the controversy that I was being unfairly reviewed because of following the customer's desires. In this case, I again never received any answer whatsoever nor did I notice any fluctuation in my score. Again, from our side this doesn't come across as being open for dialogue. And in fact, it only disappoints to see this type of behaviour or answer (or should I say a complete lack of it) when one does try to be open for dialogue. This is extremely damaging, because it not only doesn't give us the chance to be redeemed when we were right in the first place, but in the cases when we were in fact wrong, it doesn't provide you with an answer so that it can become an occasion to learn from.
Hello Lara,
If Gengo is truly serious in saying in your own words :
"this is actually important, not only because the review might change, but because it serves as feedback, both for the LSs and for us, and it also leaves a track history that we can always go back and refer to (track history of your requests, track history of patterns with an LS that we may come to see later, and so on and so forth)."
Then I would really like to repeat my above suggestion: the link towards the rereview form should be displayed on all the Gocheck reviews, instead of having to search for it deep down in the support guidelines, and having to reread all the dire warnings about submitting a rereview request.
I think that would definitely help alleviate some of the frustrations vented here.
Thank you !
@Fernando - my point about the comment (and also @gunnarbu's point) is not that you'd get a response from the client, but rather that you'd leave the comment with the idea in mind that the LS will be able to see it in the event that your job gets picked up for review. In this sense, you'd be leaving the comment more for the LS, just in case, than for the customer :)
As to you not receiving a formal reply when your score was corrected after a re-review, that is odd! You should have indeed received a second re-review and, if for whatever reason you didn't receive it in your email, the new review should at least be found now in your GoCheck history (I recommend you review this in order to see the new review and comments/explanation.) Email is definitely not the most reliable medium, and this is why we improved the UI so all GoCheck reviews are accessible on the translator's dashboard (this used to not be the case in the past). If you ever see a change in your score and no email accordingly, I would recommend you check your GoCheck history for a new review :)
As for LSs, they're checked and monitored by our Quality Team, who is also working on improving their performance review system as we speak.
@AlexF - I understand your point of adding the link to the GoCheck notification email. This is something that I myself have suggested to the team in the past. However, it is important to us that all translators are properly informed of what submitting a re-review entails and what are grounds for a re-review. Unfortunately, and please bear with me for being so blunt, without this information visible and emphasized, we risk the system being flooded with requests that wouldn't be entirely valid, leaving us to spend valuable time and resources sorting through them to find the ones that we can actually take action on. I understand this is likely not the case for you guys posting on here, but it's also a fact. Perhaps a better compromise would be to implement the link to the Support article on re-review requests in the GoCheck emails, and make the link to the request more visible within the article? :)
When I submit a re-review I always get a new email with a revised score (or an unchanged score ...) with a verbal feedback.
Lara, I see what you mean now, and I thank you for clarifying what you meant. Though that doesn't resolve the issue mentioned above that comments sometimes go completely ignored in instances where they were crucial for LS's to take into account in their final reviews, as has happened to me in more than one occasion. My point being that: what good is it to have an instruction written down, or to have a law that in theory sounds great but in practice isn't going to be implemented? Even worse than that; I could very well do that in order to have as a "backup" if I indeed get something marked as an error that I had previously asked as a question, and when I try to exercise my opportunity for a replica, I don't get an answer at all?
Which leads me to the second part of your answer, it might sound weird to you but I never got an answer to that first re-review that got corrected in my favour. And with regards to the other, I have checked my GoCheck history and verified that it never got re-reviewed. It still is the same original review with the same marked errors. So, not only did I never got a reply either informing me that they had resolved either in or against my case, they simply never went into it. Again, you can tell me that the rules say one thing, but what I'm telling you is that in practice it is very different. I hope I'm being clear enough about this so that you don't reply again saying: this is what it says on paper, because that's not the argument here, the argument is how things go in practice.
Hi Fernando,
If the LSs fails to take a customer's account (or your comments in that regard) into account when conducting a review, that is grounds for a re-review request as indicated in this Support article.
We have consistently reminded LSs to take such customer instructions and comments into account when reviewing and, while it should not happen, they sometimes fail to see these comments. As such, it's important to us to continue to remind them to do that, and if you submit a re-review about this very issues, that would highlight to us when these instances occur so that we can take action. Now, I understand that you mentioned that submitting a re-review is tiring, but that's the way to make your voice heard.
If you submit a re-review requesting for comments to be taken into account, and the re-review is not performed, or the comments are ignored, for whatever reason, I would then recommend that you email me directly (at lara.fernandez@gengo.com) so I can take a deeper look into what may be happening.
In the same way, whenever a job is reviewed, you should receive the second re-review (and if for whatever reason it doesn't make it to your email, it should be in your GoCheck history), if you can't find it, you can always write to support@gengo.com for assistance. As for the second re-review, the one you mention didn't get re-reviewed and you didn't get a reply, I would be more than happy to look into it. Feel free to email me the job number and re-review request so I can take a look at it. Please also note that in this article it is explained that if the translator's explanations are insufficient or if any issue is encountered, a request for re-review will not be processed. I would like to take a closer look at the request you mention to check whether this was the case.
Last but not least, I also wanted to share this article on our LS team and how Gengo manages it, as it may provide better insights on the importance of your feedback by means of submitting a re-review request (see How does Gengo know if an LS is performing unfair reviews? section.)
Have a great weekend, everybody!
Hi Lara (and all),
Wow!!! After all these years and 1,317,425 words... this is a first!
I have just received a review pointing out 16(!?) "errors".
I can easily substantiate my choices with official sources, links, etc.
The problem is... I only have 6 fields to do this.
Would you be so kind as to tell me what to do?
Best regards,
I feel you guys.
Clients style guide : "Overall tone: Informal".
Does this mean that you should turn your translation into a literary or academic text? Nope. Nevertheless, as soon as you start using an informal, relaxed, conversational tone... you better watch out for the trigger happy reviewer hidden behind the barrel. If you use an informal tone, of course, the reviewer will always be able to find a better version.
BTW - Dear Lara,
How can I defend against an accusation based on a simple "because I say so"? In practical terms, the translator is always considered guilty until he/she can prove otherwise. It does not make any sense.
Substantiating every decision should be mandatory for proofreaders. This is the only way you can be sure that the reviewer did a proper research and knows what he/she is talking about. Additionally, the substantiation of the decision allows you to accept it immediately or challenge it based on real facts. It would save a lot of time for everyone. Is it my job to ask for a re-review just to explain the difference between "app views" and "app impressions", when the reviewer could have researched this before considering it an error?
And why are suggestions still being treated as errors?
Best,
Nelson Brás
Update: 20 "errors" (1671 words) - 5.81 / 10. WOW!!!
And there goes my score... from 9.8 to 8.4.
Be honest - if you were in my shoes, wouldn't you be thinking "there's something wrong with this reviewer"?
Now I see why the previous translator declined this job. My instinct was telling me to do the same, but the need to provide for my family was stronger... and we are all living difficult times due to COVID19 after all.
Yep. This is the kind of text where a happy-trigger reviewer can find a lot of opportunities to express his/her creativity (let's call it this way).
This is not my best translation, I know (the client asked for an informal tone and my style is a litlle more technical/legal/formal) but, after working as a full-time translator for several governments, major brands and international organizations... I finally found a reviewer who considers my work below average! I don't even know how to react.
My question is still the same: only 1 out of these 20 "errors" pointed out by the reviewer can really be considered an error. No problem - I can easily substantiate my choices with official sources, links, etc. - Wait a minute... I can't! I only have 6 fields for 19 errors!
???
Hi Nelson - I’m out of office as it’s the weekend. Please go ahead and send me your appeal to my email (lara.fernandez@gengo.com) and I’ll check what can be done regarding a re-review for you on Monday. Thanks!