0% found this document useful (0 votes)
30 views18 pages

German LQA and Translation Review Guide

The document outlines tasks related to localization quality assurance (LQA), translation review, and file processing for various languages. It includes instructions for creating bug reports, marking translation issues, and identifying bottlenecks in the localization process. Additionally, it emphasizes the need for context and clarity in translation to ensure accuracy across different languages.

Uploaded by

Andrija Petrovic
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
30 views18 pages

German LQA and Translation Review Guide

The document outlines tasks related to localization quality assurance (LQA), translation review, and file processing for various languages. It includes instructions for creating bug reports, marking translation issues, and identifying bottlenecks in the localization process. Additionally, it emphasizes the need for context and clarity in translation to ensure accuracy across different languages.

Uploaded by

Andrija Petrovic
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd

German LQA.

Examine two screenshots of a tool’s UI in English (EN-US source text)


and German (DE localized version). Create a bug report for the development team
describing the issues and possible solutions. You may find a bug report template on the
respective sheet.
1) Present a text that needs fixing in the Issue text/screenshot field.
2) Elaborate on the bug in the Issue description field.
3) Leave any additional comments for the development team in the Comments section.

Translation Review. Study EN-US source texts and translations into FR, PL, and ZH-
[Link] the review marking any possible issues you encounter. Pay attention to
the comments left by other [Link] the Reviewed Translation field to indicate any
changes. Use the Comments section to describe the issue as well as to leave an
information request for a vendor or developer.

File Processing. Study EN-US source texts that need to be translated to ES, FR, IT,
DE, PT-BR, JA. Process the file before assigning translation tasks. Identify possible
bottlenecks in the localization process and communicate them to the development team
in the Comments section.
EN Screenshot
DE Screenshot
Issue Text/Screenshot Issue Description
Overlapping text with Image: In the targ

The source is not translated, as well as


Comments
Is there a possibility to change the translation, or to edit the font in order to fit?

Is there a possibility for development team to change the date?


Source
FR
Here are the pages taking the biggest hits:
{page1} ⬇️11K
{page2} ⬇️8K
Take a closer look at these pages with significant
traffic decline and explore areas for potential
improvement.

A way to send keywords to Keyword Manager from


Keyword Gap: a red rechtangle is highlighting the
selected keywords and a red rectangle is pointing to
the <b>Add to keyword list</b> button.

Current {metric}

PL
{"one":"%1 star","many":"%1 stars"}

Please enter a valid 11-digit CPF number, like this:


000.111.222-33.

Georgia

ZH-HANS
Add more keywords for your topic from <0>Keyword
Magic Tool</0>
Last {NUM, plural, one {# year} other {# years}}
Translation Reviewed Translation

Voici les pages qui ont accusé les plus fortes pertes :
{page1} ⬇️11.000
{page2} ⬇️8.000 Voici les pages qui ont accusé les plus fortes
Examinez de plus près les pages accusant une baisse pertes :
significative de trafic et découvrez comment les améliorer. {page1} ⬇️11.000
{page2} ⬇️8.000
Examinez de plus près les pages accusant
une baisse significative de trafic et découvrez
comment les améliorer.
Un moyen de transférer des mots clés vers Keyword
Manager depuis Possibilités de mots clés : un rectangle
rouge encadre les mots clés sélectionnés, et une flèche
rouge pointe vers le bouton <b>« Ajouter à la liste de mots
clés <b>».

Un moyen de transférer des mots clés vers Keywo


{metric} actuel

Actuel {metric}

{"one":"%1 gwiazdka","many":"%1 gwiazdki"}

Wprowadź prawidłowy 10-znakowy numer identyfikacji


podatkowej (NIP) na przykład: 123-456-78-19

Wprowadź prawidłowy 11-znakowy numer identyfikacji podatkowej


Gruzja

< 0>Keyword Magic Tool<0>からあなたのトピックのキーワードをもっと追加


します

<0>Keyword Magic Tool</0>からあなたのトピックのキーワードをもっと追加します


过去 {NUM, plural, one {# year} other {# 年}}

过去 {NUM, plural, one {# year} other {# 年}}


Comments

In the last sentence, there was a double space


between words Examinez and de. There is a
slight inconsistency in the formatting of
numerical values. The source text uses "11K"
and "8K" to represent thousands, while the
translation spells out the numbers in full.

There is a minor spelling error in the


translation. "Rechtangle" should be
"rectangle." Additionally, there is a missing
space before "<b>« Ajouter à la liste de mots
clés <b>»." The use of punctuation marks
around the button text ("<b>« »</b>") could be
improved for consistency and clarity. There is
also different tag in source </b> and target <b>

It may suppose to be opposite, like in the


source.

In target language there are different numbers


as well as the translation, and the form of the
11-digit CPF number, it is translated as 10-digit
CPF number. Punctuation mark missing at the
end of the sentence. Also there is double
space after the punctuation before the digits.

Spacing error < 0>, and different tag </0>


# year is not translated.
Source Key

Export top keywords data to "export.aria_label"

Only {device} date is available. "[Link]"

Trending Pages for: "widget.trending_pages.[Link]

Add competitors "compare.add_competitors"

Hide {number} less "[Link].hide_qty"

Select multiple "geo_selector.switcher"

Used: {0} Used: {0}

The {{type}} “{{title}}” has been added to your


favourites. added_to_favorites

{{action}} your agency page agency_form.heading

Last {NUM, plural, one {# day} other {# days}} "[Link]"


Candidate's Comments

What variable follows after "to"? Need to use descriptive keys to clarify the purpose of each text segment/ needs context

What variable follows after "for"? May need adaptation to suit cultural preferences or linguistic nuances in the target languages

Different languages have different ways of saying "less" depending on the previously stated amount. Also, what object does the
What is the context for "used"? This could
make it harder for translators to understand
its purpose
Select or content.
multiple what exactly? Some languages are very gendered and translators need to know what the main noun of this sen

Depending on the type, it's corresponding particle can change. Additional context or clarification needed on the nature of being

The placeholder "{{action}}" lacks specific context, making it challenging for translators to determine the appropriate action to be

Is "last" a verb? Why is "other" in this sentence? Here is also visible pluralization rule. It should be noted for translators to ensur
gment/ needs context

nces in the target languages

nt. Also, what object does the number refer to? Is it a person, a living being or inanimate object? Is it amount of something, if yes, what?

hat the main noun of this sentence is. Context needed to ensure accurate translations.

eeded on the nature of being added to favorites, including the possible values for "{{type}}" and "{{title}}".

e the appropriate action to be performed.

noted for translators to ensure correct plural forms in the target languages.
something, if yes, what?

You might also like