Best Practices for Reviewers: Offline LQE, LILT Review, and LILT Secondary Review
Selecting Error Typology
Each change made to the translation requires a Category and Severity.
This is done ONLY if the segment was modified during Review/LQE. For assigning the correct categories and severities, you can:
Review the https://support.lilt.com/kb/segment-comments#SegmentCommentsandErrorFlagging-ErrorTypology Knowledge Base page.
Check the Categories and Severities tab of the LQE sheet that you received.
Tabs of an LQE sheet
Categories and Severities are NOT needed if no change is made to the string.
Only KUDOS severity can be used to highlight a particularly good translation or one that has a high positive impact.
FAQs
What should I do if more than one error type is found in the same segment? Mark only the highest severity and report it only once. In the comment, please explain all the changes. For example, if there was a shift in meaning and also a typo, use Accuracy - Major only.
What should I do if there are repeated errors? The first time you see the error, mark it as usual by using a Category and Severity (Minor/Major/Critical). Starting the second time, use the same category but select the Repeated Error Severity. This should be done:
If the segments are identical, or
If the segments are different, but the error is the same. For example, an incorrect term used in different sentences, or incorrect punctuation for list items used in different segments.
Adding Comments
LQE reports serve as communication tools between translators, reviewers, and other stakeholders, such as decision-makers, in the process of understanding and assessing the quality of the translations. For this reason, it is important that every aspect of the original translation that needs to be reconsidered includes a comment that clearly explains what the issue is.
When writing comments in LQE reports, consider the following audiences: Client, LILT Production Team, Quality Manager, Reviewer, Translator.
Key Focus Areas
Language clarity:
Explain all errors clearly, regardless of severity.
Use language that all parties can understand, preferably English.
Support with evidence:
Provide logical and solid proof for suggestions or corrections.
Use references (links, glossaries, SGs, instructions, etc.), examples, or back translations to support your points.
Professional tone:
Maintain a polite and professional tone in all interactions.
Report any unprofessional behavior to your Point of Contact (PoC).
Objectivity:
Avoid personal bias.
Present arguments impartially, respective diverse viewpoints.
Precision and conciseness:
Keep messages concise and to the point.
Be precise in your feedback.
Back translations:
Include back translations to clarify issues.
What not to do
Emotional feedback:
Avoid emotional or angry responses.
Focus on rationale.
Avoid exclamation marks and personalization:
Use neutral language.
Refrain from rhetorical questions, rude comments, or irony.
Defend, don’t attack:
Explain why a variant is incorrect, but do so professionally.
Be subjective.
Be aggressive.
Use long sentences.
Opt for short, to-the-point sentences.
Be personal.
Bear in mind the business context.
Golden Rule: Treat others as you’d like to be treated.
Examples
Category/Severity | Do | Don’t |
Fluency - Minor | Grammatical and syntax errors. Article " an" missing and quite repetitive. Please avoid this. | This is a grammar error |
Fluency - Minor | "Lilt Page" should be written in title case, according to Glossary. | Use capitals!!! |
Fluency - Minor | Inconsistent use of "newsroom" throughout the documents. Also, missing quotation mark at the beginning of the sentence. | Inconsistency and wrong punctuation |
Accuracy - Major | "example applications" is mistranslated as "example apps" when it would mean "example use". ”Balloon" is mistranslated as "Ball” | Misinterpretation of the source |
Accuracy - Major | The original translation uses “XXX” which means “xxxxx” (backtranslation). In this context, the source text means “xxx” which should be translated as “XXXXX” | “XXXXXX” should be “XXXXX” in the target language. |
Accuracy - Major | The original translation is not appropriate for this context because it is commonly used in (a specific) field. In this context, “xxx” should be used. | “XXX” is incorrect/inaccurate Out of context |
Terminology – Major | The correct term for “xxx” is “XXXX” according to the glossary provided/according to specific industry terminology. | Here ,“XXXX” should be used. |
Terminology – Major/Minor | As per glossary, the correct terminology is “XXX” *a “more correct” term can always be suggested, but then it should take the “Neutral” severity, so it does not count as an error. | “XXX” is more correct/appropariate |
Accuracy - Major | The original translation back translates “xxxx”, which doesn’t correspond to the source text. | The translation is wrong |
Accuracy - Major | The word template is translated wrongly. “Unkaa” means 'form', the correct term is qajojiila | Wrong translation |
Accuracy - Major | “dropdown” was mistranslated as “expand” | The whole sentences is mistranslated regarding the English version |
Accuracy – Major/Minor | -The translation for the word "can" is missing. The full translation should be …. -The translation for "use" (uso) is added to the target text. It is not present in the source text. -In the source “Is this how you want it to sound?”, the translator has translated; "Would you like your voice to be like this?" While there is no "your voice" in the source. | Added words |
Accuracy – Major/Minor | "Endorsement" is omitted in the target text. | Omission/ Missing word |
Fluency - Minor | According to target language rules, there should be a space in between "XX" and "XXXX | Add a space |
Fluency - Minor | Full stop is missing between the last 2 sentences. | Incorrect punctuation |
Fluency - Minor | The sentence should start with capital letter as per standard rules | Incorrect capitals |
Terminology - Minor | -The translation for the word "Profile" is not consistent through the file. It should be translated as "កម្រងព័ត៌មាន" rather than "ទម្រង់ព័ត៌មាន" -The translator has used two words "bertek" and "Paşrakışından" for the word "Feedback", for the consistency of the translation, it is better to use the word "bertek" which is more specialized | Inconsistent translation |
Fluency – Major/Minor | All objects and phenomena are divided into masculine and feminine in the Kurmanji dialect, and the suffix "a" or "ê" is added to them at the end of the word in relation to the gender, Tim is feminine in Kurmanji, so it takes the suffix "a" instead of suffix "ê" | Wrong gender |
Style - Neutral | The reviewed target improves the fluency of the original translation by replacing "ផ្តល់ឱ្យ" (give) with "អនុញ្ញាតឱ្យ" (allow), which is more natural in the context of granting access. The reviewed target improves the original translation by removing the word "ដែល" (which) before "ប្រហែលជា" (maybe). This change makes the sentence more concise and natural-sounding, eliminating an unnecessary word that does not add to its meaning. | Style Improvement |
Style - Neutral | Sentence structure was adjusted for better readability. | The translation sound awkward |
Style - Neutral | The reviewed target translation is a more fluent and natural way to express the idea in Khmer. The word order is adjusted slightly, and the word "កាន់" (meaning "to") is added to make the sentence smoother. The reviewed translation is a good improvement over the original and should be preferred for its naturalness and clarity. | It is unnatural |