Showing posts with label editors. Show all posts
Showing posts with label editors. Show all posts

Monday, June 16, 2025

Text-book perfection – in search of a QA panacea for revising long texts

 

Long translations pose special problems for translators. The intensive process involved in translating a long legal document or multipage text leaves little time and freshness for the no-less-crucial process of QA. Simply put, by the time the hard-pressed translator gets to the editing stage, the text is already embedded in the mind as basically acceptable, limiting the translator’s ability to identify syntactic errors. This problem is not new, with translators having long used a set of tools, some old and some new, to overcome it to varying effectiveness. I will discuss some traditional QA methods, some recently developed ones and my experience with Grammarly. Whatever the individual choice of tools, professional translators and writers must employ them to properly check their work.

To illuminate the problem, the act of translating a long text, whether a legal document, a set of technical instructions or personal journal, involves multiple hours and multiple readings. Working from first draft to non-QAed finalized version may require the linguist to read through the original and source four or more times. Aside from the time invested, the creation process creates a sound and vision in the mind, which become de facto acceptable. Professionals are aware that many areas for correction and improvement lurk in the text and strive to find them in the jungle of text. However, the longer the text, the more difficult it is to locate them. The moment of truth is when the customer or translation agency editor sends back a document riddled with red marks, a truly unpleasant and often embarrassing experience. The question that most translators and editors ask is “How did I miss that?”. It often was not from lack of effort but  due to the tools they used.

The tools of translators and other linguists at minimum include
Word “spellcheck” (F7), printing and reading and use of outside editors. The Spellcheck function in Word identifies the most basic of errors with the failure to use it bordering on professional incompetence. A more comprehensive manner of editing is to print and read a text. For some reason, a text appears differently on paper than on a screen and, thus, fresher to the eyes. I personally read the text backward, i.e., from the last paragraph to the first paragraph, in order to render the document even more different and prevent me from going into “read a story” mode. Ideally, all linguists would employ outside editors, a fresh pair of eyes, to review any resulting text. In practice, the time and cost factors limit this practice from becoming standard except in literary translation. Translation agencies employ editors, especially those applying the various ISO standards. As I wrote, it is unpleasant to receive red-dotted corrections even if such a result does not affect future work. As for direct customers, the linguist is solely responsible but most technical translators do not use outside editors as a standard practice.

Two more modern and comprehensive methods are text-to-speech and AI. The text-to-speech function in Word is a simple manner of reviewing a document using a completely different method. Instead of having the eyes read a given sentence for the umpteenth time, the ears filter the sentence. Thus, poor-sounding phrases and structure immediately hit the linguistic warning bells and cause the translator or editor to reconsider the wording. It is a tool that I may try in the future. Another trendier tool is AI editing. Using one of many applications, it is possible to have AI analyze a document, identify possible errors and suggest solutions within seconds. On the surface level, it sounds quite magical, even ideal. My serious issues with this method are the lack of confidentiality, the actual process and results. First, as of today, in most cases, once a text, even without any identifying names, is posted to AI, it enters the public realm, which may be a breach of the confidentiality conditions. Some writers may be risking their copyright privilege if they use AI. Furthermore, I personally find the process of writing prompts to define and limit the range of errors as well as desired style I seek to be overcomplicated. Even when a person overcomes that difficulty, the suggested changes represent some collective image of the ideal such text, much of which is not relevant objectively and/or subjectively. In other words, the benefits, i.e., AI’s comprehensive and standardized approach, do not justify the risks, i.e., the loss of confidentiality and hassle of writing prompts. Thus, I do not use text-to-speech or AI.

However, recently faced with specific challenges, I applied Grammarly to two especially long and complicated texts and found the results positive on the balance. One text was a 20,000-word personal journal while the other was a 5000-word contract. As time and energy were short, I sought a tool that would identify phrasing errors and improve my translation in my text without risking confidentiality. I used Grammarly, an application that does involve a user fee. The process was simple, merely uploading or dragging the text into the editing box. I then selected the type of text, e.g. informal or formal. The result was a long list of possible errors and suggestions for improvement. To give a perspective, the program created 500 comments for a 5,000-word text. The vast majority, around 80%, were false positive either because of context or personal choice. For example, the program was not familiar with legal language and questioned many acceptable terms. In terms of subjective choices, I personally do not apply the Oxford comma, the comma before the word and, nor place a comma before the word but. Thus, I ignored those comments. On the positive side, it did identify many passive sentences that I could render in the active voice. This comment was of great value in the personal document but less so in the legal document even if I  try to limit use of passive structure in legal documents. Grammarly also identified sentences that could be joined or split, suggestions that I adopted several times. Overall, review of these long texts using the program involved several hours but produced better results in less time as compared to rereading.

It is clear that linguists, especially translators, must provide high quality products, meaning documents as clean of errors as possible, especially in the light of AI-created documents. The longer the document, the more difficulty that task is. Thus, translators and writers must use a wide variety of tools to achieve the required quality. I intend to use Grammarly on longer texts where a lack of time and freshness may harm the quality of revisions. While linguists can choose their preferred tools, it is clear that no specific method is a complete panacea.

Monday, March 27, 2023

Watch your tongue – critical safety guidelines for translators and editors

 

[leopard sleeping in a tree*]

Translators and editors are often called upon not only to correct texts but to make judgments about their writers. They even sometimes do so on their own volition. These assessments can potentially expose these linguists to a charge of defamation in certain circumstances. As I learned at an excellent webinar presented by Galit Golan , advocate, of the law firm of Firon and Associates, in Israel professional critiques enjoy significant projection from the charges of defamation but involve some care when choosing the actual words. This issue is relevant when performing professional services  and also when “entertaining” colleagues with awful examples and warning them of potential dangers from perspective customers. The key is careful consideration of any such comments.

In Israel, defamation involves several elements, primarily the sharing of information with another party that could objectively humiliate or harm the third party. Israeli law does protect certain circumstances, most notably when the receiving party has the authority or obligation to receive that information. Most interestingly, once defamation is established, the court can award up to 79,000 NIS, almost 22,000 USD, (as of this year) to the damaged party without the latter having to prove damages. Clearly, given the complexity of the matter, in the case of doubt, it is advisable to consult an attorney.

As relevant to translators and editors, the issue can arise when completing QA and translation test assessment forms. To demonstrate, in a case involving a chef sending the management a picture of a member of the kitchen staff taking a nice nap under a tree, the court found the hotel and chef guilty of defamation not because of the picture since the chef had an obligation to inform the employer. Instead, the court found cause in the sarcastic caption under the picture, which mentioned the need to purchase a mattress for the employee. Likewise, it is the clear duty and obligation of the linguists to note all linguistic errors, whether objective or style, as well as answer any specific question regarding the overall level. Thus, it would be appropriate to write “The translators lacks sufficient knowledge in the subject matter to properly translate such texts” if the facts back up this conclusion. However, it may be dangerous to write “the translator has no understanding of the source language” as the provided sample does not justify that conclusion and may harm the career of the translator. When so requested by relevant parties, only relevant criticism advisable.

Considering the same case, linguists should be careful when sharing “funny” examples of poor translations or awful writing. Many translators share photos of amusing menu items and tourist site signs. In their basic form, these posts are merely publicizing public information, objective truths. However, if the posting party adds a comment such as “I hope the restaurant pays its chefs more than it paid its translators”, defamation may become an issue as the post goes beyond the linguistic disaster in the restaurant menu to question the quality of its food. Again, think before you post.

Of critical importance to freelancers, including translators and editors, is the sharing of information on problematic customers. The legimitate purpose here is prevent others from having the same unpleasant experience. In this regard, one of the cases brought up in the webinar is illuminating. A teacher received compensation after the letter to the parents specified conviction as the reason for dismissal instead of police investigation, which was the actual case. When colleagues request feedback on a specific agency or translator, whether privately or publicly, it would be advisable to stick the facts and avoid making general conclusions. For example, it would be apparently be acceptable to state the agency only paid after four months but riskier to write” the agency is a poor payer”, as the writer cannot justify the comment without checking with most if not all the translators working with it. Without the ability to prove a statement that may harm the third party, the warning party may be exposed to a defamation complain in Israel.

Clearly, every country has its own rules for defamation. Moreover, only legal experts can properly analyze any specific set of facts. However, an ounce of prevention is worth a pound of care. Translators and editors should be very careful in how they write their critiques, however justified they may be, and avoid overreaching. As linguists have sharp pens, we need to watch our tongues.




* Picture captions help the blind fully access the Internet.

Picture credit