g11n.rnd.huawei.comg11n.rnd.huawei.com/UIDoc/WebContent-2/Consumer/EMUI/WebC… · Web view17.09.2019 · Case Study for Huawei Multilingual Projects (Template) Project name-Lanuguage-Defect

Case Study for Huawei Multilingual Projects


(Template) Project name-Lanuguage-Defect category-other key wordsProject name includes: EMUI string/EMUI UG/Tips/MBB/FAQ/Knowledge Base Training/ Knowledge Base Maintenance/…

VOC from: GPM feedback/QC/Beta Test/LT/Frontline feedback/NPS/VIP/GTMS…

Basic InfoLanguage:

DBID: xx (if any)

TR/TO:

Feedback date: 2019-xx-xx

Issue DescriptionSource:

Original translation:

Modified:

Issue description:

Root CausePlayback of each phase (Engineering -> Translation -> Proofreading -> LT -> others if any)

1. Introduction point: Xxx (In what step or by what role the issue is introduced from the process perspective)

2. Control point: Xxx (In what step or by what role the issue should be identified from the process perspective)Analysis on other aspects (if any)

3. Resource:4. Platform: e.g terms, style guide, tools…5. Others:

2023-5-15 Huawei Proprietary and Confidential

1


Improvement Measures1. Corrective:2. Preventive:

1. EMUI string-English-Variables

VOC from: VIP

Basic InfoLanguage: English

Issue DescriptionSource: 本设备当前最多支持开通 %1$s,您已开通 %2$s,是否继续开通?

Original translation: You have added %1$s out of a maximum of %2$s. Continue?

Modified: You have added %2$s out of a maximum of %1$s. Continue?

Issue description: Variables are placed differently in English than that in Chinese. The number of currently added cards becomes the maximum number that users can add.


2


Root Cause1. Introduction point: Translation. The translator adjusted the sentence

structure, which put the currently added number in the first part, while forgot to adjust variables accordingly.

2. Control point: Review. The reviewer focused on the sentence structure, did not pay much attention to variables.

Improvement Measures1. Corrective: All strings with 2 or more than 2 variables were checked to

ensure that no similar issues exist. 2. Preventive: Clarify that reviewers must attach great importance to

variables.


3


2. EMUI string-English-Consistency

VOC from: Frontline


Issue DescriptionSource: 防误触模式Original translation: Touch-disable mode

Modified: Mistouch prevention

Issue description: "Touch-disable mode" is not clear, we decided to change it to "Mistouch prevention". Yet we did not change thoroughly. The frontline found that the name is different in two scenarios.

Root Cause1. Introduction point: String optimization. The LS got feedback on this

function, and decided to change it. The settings menu was taken as the only place that this name would appear.

2. Control point: Review. The reviewer only focused on the content of this string, while failed to consider other places that this name would be used.

Improvement Measures1. Corrective: Changed the name appeared on the lock screen. Checked all

feature names in EMUI 9.1 to ensure consistent use.


4


2. Preventive: Clarify that LSs must specify whether a change needs global change when optimizing strings. Check feature names in every version to be released.

3. EMUI string-English-LogicVOC from: VIP


Issue DescriptionSource: 全部清理Original translation: Close all

Modified: Select all

Issue description: "Close all" may also mean toggle off all switches, which is totally different from the real function. "Close all" means all apps will be closed after the screen locks, and the switches beside apps will all be toggled on. There is a dialog box followed, which would be clear to users what this switch means. Yet users may not spend too much time on reading, therefore, we changed it to "Select all" to be clearer. iOS has a similar function. Its design is different from ours


5



6


4. EMUI string-English-App name

VOC from: VIP


Issue DescriptionSource: 动态照片Original translation: Moving picture

Modified: NA

Issue description: VIP thought that the English name is a literal translation of Chinese. iOS calls this feature Live photos. Moving picture reminds English native-speakers of film. We didn't change this name.

5. EMUI string-English-TermsVOC from: VIP



7


Issue DescriptionSource: 第三方桌面Original translation: third-party home screen

Modified: third-party launcher

Issue description: "home screen" is not an accepted industry term. It should be "launcher".

Root Cause1. Introduction point: Translation. The LS did not know there was an

established term for "桌面". 2. Control point: Review. The reviewer did not know the term either.

Improvement Measures1. Corrective: Changed the string. Added "launcher" to the termlist.2. Preventive: Searched many official OS websites to accumulate such

terms.


8


6. EMUI string-English-App name

VOC from: VIP


Issue DescriptionSource: 应用分身Original translation: App twin

Modified: NA

Issue description: VIP thought "App twin" did not convey the function well. After wide and extensive discussion, we decided not to change this name.

7. EMUI string-English-Feature name

VOC from: VIP


Issue DescriptionSource: 系统升级Original translation: Updater


9


Modified: System update

Issue description: Updater is not a commonly used word, and inappropriate in this scenario. It used to be an app, but later moved to Settings.

8. EMUI string-European Portuguese-Accuracy

VOC from: GPM feedback

Basic InfoDBID: PL_367341

TR/TO: NA

DBID: PL_367350

TR/TO: NA

Feedback date: 2019-3-14

Issue DescriptionFree test file with strings sent to update had two strings with switched updated translation.


10


DBID: PL_367341

Source: Dog

Original translation: Cães

Updated translation: Gato

DBID: PL_367350

Source: Cat

Original translation: Gatos

Updated translation: Cão

No global check was made upon discovering the issue (2018-10-22). Other errors were corrected at a later point (2019-01-31).

Upon discovering the issue, the strings were corrected and pushed to the terminals assumingly via OTA update.

There is currently no available data regarding the impact.

Root CauseDuring daily work, the translator gathers strings requiring update. Upon finding an issue, all strings with the same issue are extracted from the DB and stored in Excel files (e.g.: the file "FeatureAdvisor to Feature Advisor" indicates that all the strings inside require changing "FeatureAdvisor" to "Feature Advisor"). The strings are then updated, manually, and MS Word is used for spellcheck.

After gathering several issues (any serious issue is handled in the same day it is discovered), the content of all files are merged into only one file, copy/paste the updated strings into MS Word for another round of spellcheck, and the file is sent to Dai Tuo (Michael in CC) for forwarding to the strings engineer who will update the DB.

The issue happened during the merging of all the strings into one file, with an incorrect copy/paste between two adjacent strings, reversing the translation of the above strings:

Cats ► Dog

Dogs ►Cat


11


Because the content of the strings itself is grammatically correct, MS Word was not useful to detect this issue.

1. Introduction point: copy and merge files during free test.

2. Control point 1: compare both columns (Proofreading result and values-pt-rPT) to identify the differences and have a second check.

3. Control point 2: unless urgent, file should be reviewed by backup LS before being sent.

4. Control point 3: upon finding an issue, check if similar strings share the same problem.

Improvement MeasuresCorrective measures:

1. Correct the affected strings and send them for update.

2. Do a global check for similar issues.

Preventive measures:

1. Compare both columns (Proofreading result and values-pt-rPT) to identify the differences.

2. Unless urgent, file will be reviewed by backup LS before being sent.

3. Upon finding an issue, check if similar strings share the same problem.


12


9. EMUI string- German, Swedish-Accuracy (Portrait)

VOC from: Frontline feedback

Basic InfoDBID: PL_323967, PL_323966

TO: TO201701000287



Portrait disabled.

Portrait enabled.

Issue description:

On February 8, 2017, the European Device Product Center reported that the (Portrait Mode) translation in German and Swedish was incorrect, affecting the quality of the demo version in West Europe.

Root Cause1. Introduction point: Translation phase. Portrait in English has two

meanings. One is portrait (人像，a painting, drawing or photograph of a particular person) and the other is vertical screen (竖屏). The two meanings are both common.

2. Control point 1: Multiple-meaning words are not provided with a description during English proofreading.

3. Control point 2: In multi-lingual translation, the translator did not submit a query in case of multiple-meaning words.

4. Control point 3: This string is not submitted for LT because the module string contact person does not understand the multi-lingual test plan. The new string caused by the requirement change does not catch up with the EMUI5.1 B100 test plan.


13


Improvement Measures1. Corrective: Check all Portrait translations and correct the incorrect

translation into the string library. The involved strings are as follows, which affects 14 languages.

2. Preventive: a) If multi-meaning words exist in English proofreading, add

descriptions to help the translators understand them correctly. Owner: English proofreader

b) The multi-language test plan is added to the new string. If the new string of the module cannot catch up with the test plan, the module string contact person puts forward the test requirement. Owner: Module R&D person

10.EMUI string- 11 Langues-Accuracy (Portrait)



TR/TO: TO201901000705, TO201901000708, TO201901000707, and TR201901000305_16 for Japanese


Issue DescriptionSource: Portrait 人物Original translation: Different languages translated into different meanings.

Issue description:

The string Portrait with the meaning of images of people were mistranslated into different meaning. Errors occurred in the following 11 languages. The GPM found this issue before uploading the translation to the string library.

Language Language-code

Japanese ja

Amharic am


14


Basque eu-rES

Catalan ca

Czech cs

Gujarati gu

Hebrew iw

Hindi hi

Kannada kn

Maithili mai

Swedish sv

Root Cause1. Introduction point: The multilingual linguist translated the word

according to their own understanding. No description was given for this word in English source. A screenshot is provided with this string, but the screenshot is in Chinese with “人物 1” circled in red because the string hasn’t been loaded to the real phone when the R&D developer took this screenshot.


15


The following areas need improvement: The English version provides a description for single-words and

multi-meaning words. The screenshot is in English. In case of a single word, the multilingual linguist raise a query to

confirm the exact meaning.2. Control point 1: Proofreading 3. Control point 2: This string haven’t been sent for LT, so it cannot be

detected during LT.

Improvement MeasuresCorrective:

1. For multilingual, check and modify this strings in all languages.2. For English, global search “portrait” in all strings to add the following

description in English source: “This mode adds effects to videos of


16


people. The word Portrait in this context means images of people, and not portrait orientation.” Preventive:

1. The English version provides a description for all single-words and multi-meaning words.

2. The screenshot is in English. Multilingual linguists be cautious about single-words. Make sure the multilingual linguists should refer to the screenshot or raises queries to confirm the exact meaning in case of single-words. If multilingual linguists find any single words or multi-meaning words without a scene description, pls contact vendor PM for help and ask Huawei to add scene description.

11.EMUI string-Greek-Yes/No Error(will not be able to) and Info-Missing Error (emergency)



TR/TO: TO201607000136

DBID: PL_285243

TR/TO: TO201605000115


Issue DescriptionIssue 1: Source: PL_351481 You will not be able to place emergency calls over Wi-Fi. Enable?

Original translation: The translation result of Greek is totally opposite to that of English. //希腊语的翻译结果与英语描述完全是反的Issue 2: Source: PL_285243 Unable to make emergency calls over Wi-Fi.

Original translation: The Greek translation is unable to make calls over Wi-Fi. (The keyword "emergency" is omitted.) //希腊语翻译为无法通过 wifi 拨打电话（漏掉关键词“紧急”）Impact: EML TA releases rejected by VDF FLE, for two times; the ONLY reason for the second TA release


17


Root Cause1. Introduction point: human mistake2. Control point 1: The vendor did not arrange peer review.3. Control point 2: Unable to be tested during LT because special SIM card

in Greece is required.4. Control point 3: This string is not included in the level 0-5 string menu

testing because special SIM card in Greece is required.

Improvement MeasuresCorrective:

1. The two issues were corrected in the string library and the second TA release passed.

2. All Greek strings with the string level equal to and lower than “Translator” were submitted for a second review. Preventive:

1. Vendor arranges a second person review for all string translation.2. The string management team ensure that all newly added and but not

tested strings are submitted for a second review and marked as reviewed level in the string library.


18


12.EMUI string-Italian& Latvian-Accuracy (Greenery 绿植)



TR/TO: TO201712000678


Issue DescriptionSource: Greenery

Original translation: Verdura (Italian), Dārzeņi (Latvian) which means "Vegetable"

Modified: Change to the word corresponding to "Greenery". In languages without a direct translation for "Greenery", it could be a translation for "Plants".Issue description: This is a camera mode. Greenery, which means green plants, leaves, vegetable, etc, is translated in to Verdura (vegetable) in Italian.

This issue in Italian was found by frontline and caused a critical complaint. //Greenery 一词（含义是绿色植物, 包括树叶、灌木、乔木、青草、蔬菜等）翻译成意大利语的 Verdura（含义是蔬菜）,遭到一线严重投诉。

Root Cause1. Introduction point: Translation.

a) This is a new function in EMUI8.1. The translator is not familiar with this new function.

b) This is a camera effect mode. For different strings in this mode, the same reference screenshot is provided, which is very general and cannot clearly show the exact scenario.

c) No English description is provided.d) Considering the wording, in Italian, "Verdura" has the meaning of

"The green color, the green aspect of the vegetation；Green


19


appearance of the vegetable". The translator chooses the word of Verdura (vegetable).

The following areas need improvement:a) The screenshot should be more specific.b) The English version provides a description for single-words and

multi-meaning words.

2. Control point 1: For translations owned by internal linguists but outsourced due to translator’s leave, the internal linguist owner should review the outsourced part when he/she is back.

3. Control point 2: The internal linguist owner do the test but also failed to detect this issue because the owner is also not familiar with this new function (this new function is not trained in EMUI 8.1) and the screenshot is too general to understand.

Improvement Measures1. Corrective: Globally check and correct this error for all languages. It was

found that the string in Latvian was also mistranslated into the meaning of “vegetable”. All errors were rectified from the string library.

2. Preventive:a) The English version provides a description for all single-words and

multi-meaning words.b) Be cautious about single-words. Make sure the linguist should refer

to the screenshot or raises queries to confirm the exact meaning in case of single-words. If the screenshot is general, a query is needed for clarification of the exact meaning.

c) New features should be trained timely for internal linguist. For vendors, if the training of new features cannot be provided before version release, they could rely on English description, screenshot, and query to ensure the correct understanding.


20


13.EMUI tips-Nepali-Redundant characters

VOC from: GPM

Basic InfoTR/TO: TO201903001155


Issue DescriptionIssue description: Redundant characters appear at the beginning of a sentence.

句首出现三个冗余字符 sसासा

Root CauseThis issue is introduced due to the Studio bug in earlier versions of 2017. Redundant characters are automatically added occasionally at the beginning of a sentence. This issue has been reported to the translator and ask each translator to install the Studio patch. However, the translation personnel are not properly implemented, and the Studio is not upgraded. As a result, the issue persists.

该问题是由 Studio 版本问题引入。由于 2017 早期版本没有补丁包，会自动引入多余字符。该问题之前已经和译员反馈，但译员由于操作不当导致落实不到位，没有升级工具，导致问题依然存在。

Improvement Measures1. An email is sent to notify all translators that the patch package must be

upgraded.


21


2. For the translators who encounter this issue, we will communicate with him/her and ensure that the translators implement them.

3. In addition, to ensure that the issue does not recur, a process checking whether the tag exists is added after engineering processing. If yes, the file will be modified. Use UltraEdit to search for [^>\s]\n*<mrk mtype="seg" in the folder. It should not be found in the sdlxliff file. If it is found, locate the corresponding file and modify it.

1. 邮件再次通知所有译员必须升级补丁包。2. 针对出现该问题的译员，我们会单独沟通，并确保译员落实。译员

确认后，我们发送测试文件请译员操作处理，返回后内部进行验证。3. 另外为了确保该问题不再复现，流程上工程处理后，会在后期验证

tag 是否存在，如存在，会对文件进行修改：用 UltraEdit 在文件夹中搜索[^>\s]\n*<mrk mtype="seg"。，sdlxliff 中不应该搜索到，如发现请找到对应文件修改。

14.EMUI Tips- Italian-The XML language attribute is incorrect for some files


Basic InfoTR/TO: TR201812005082_28

DBID: NA

Issue DescriptionIn an EMUI user guide translation, Xml attribute in some files has been remained in English instead of Italian.

Root Cause1. Introduction point: When cleaning up a bilingual file to monolingual file,

the Trados should automatically modify the attribute from en-US to the target language attribute. But in this specific case the change was applied


22


only on some files but not to all of them during to the some unknown reason of the translator’s Trados.

2. Control point 1: The translator did not check the attributes of all file deliverables to ensure the attribute change has been successfully done.

3. Control point 2: The reviewer took for granted that all attributes have been already checked during the translation step and only focused on the content of this string during the review then sent the deliver right away.

Improvement Measures1. Corrective: Correct the related EN attribute of all files and re-send them

back.2. Preventive: a) Check and ensure the Trados settings are correct (as

shown in the following Figure). b) Re-checked and ensure the attribute change has been successfully applied both during the translation step internally and do final check during the Engineering process before delivery.


23


15.EMUI string- Italian- Human carelessness

VOC from: QC feedback/Frontline

Language: Italian DBID: PL_381983 Source: 4G enabled on SIM %1$d.Translation: 4G disattivato sulla SIM %1$d. -> 4G attivato sulla SIM %1$d. Root cause:High fuzzy translation was not updated during translation.Measures:1. Tool - Settings for checking unedited fuzzy matches.2. Process – Check for all the detected warnings one by one.


24


16.EMUI string- French- Human carelessness


Language: French DBID: PL_345174 Source: For additional security, PIN required every <subnode ref="en" index="1">%d</subnode> daysTranslation: Pour plus de sécurité, saisir le code est requis tous les jours <subnode ref="en" index="1">%d</subnode> jours Root cause: This issue is caused by reusing existing string (PL_345167, in same translation task)

content (copy-paste) with, as insitial objective, keeping the phrasing consistent. ● Copied string : Pour plus de sécurité, saisir le code est requis tous les jours ● QC string : Pour plus de sécurité, saisir le code est requis tous les jours <subnode ref="en" index="1">%d</subnode> jours Lack of attention lead to not noticing there was a doobloun (word repeated) No LT was arranged for this string.


25


Measures:1. Cross-review for languages have more than one linguist was added as a regular process.2. Increase LT coverage.3. Key menu testing

17.EMUI string- Hebrew - Human carelessness


Language: Hebrew DBID: PD_250869

Source: Screen recorder

Translation: מקליט המסך -> רשמקול המסך

The original translation equals to screen + audio recorder.

Root cause:

Translation for Recorder (audio) was wrongly selected during global changing strings containing APK names.


26


Measures:

1. Always keep quality awareness in mind for all the tasks.

2. Know background and requirements clearly.

3. Add Xbench checking + review in Beyond compare report as regular process for tasks done in Excel file.

18.EMUI string- Japanese - Reference info ignored


Language: Japanese DBID: PL_3440Source: Running time


27


Translation: ランニング時間 -> 稼働時間 Running time (sports) -> Running time (device)

Description for the string: About phone, status item title. How long the device has been running since its last reboot. Root cause:

Description of the scenario was not referenced during translation.Measures:

1. Read reference info (description, screenshot, length limit…) for each strings carefully.2. Raise queries if reference is not enough for understanding the scenario.


28


19.EMUI string- Portuguese-BR - Special rules for handling escape character


Language: Portuguese-BR DBID: PL_403569 Source: Color & eye comfortTranslation: Cor & conforto dos olhos -> Cor e conforto dos olhos“&” is not commonly used in Portuguese-BR, but was kept in the string since it was displayed as an escape character during translation.


29


Root cause: Rules of handling conflicts between language style and escape characters are not clear.Measures:

1. If you find conflicts between your language style and task requirements:2. Give a feedback to your PM about the special case.3. Add the special style to style guide.

20.EMUI string- Bulgarian - Term was not included in term list


Language: Bulgarian DBID: PL_397113 Source: NotchTranslation: Белег -> ПрорезThe original translation is not suitable for the scenario.Root cause: The term was a new feature and not included in term list during translation. Measures:If you find a new term not included in termlists,


30


1. Well understand the new feature.2. Investigate how to translate it accurately and popularly.3. Ask for FLE’s suggestion and make a final decision.4. Give the new term feedback to PM.

21.EMUI string- Bulgarian - Term update process was not followed


Language: Bulgarian DBID: PL_426891

Source: %1$s, such as account identifier.

Translation: %1$s, напр. идент. на профила-> %1$s, напр. идентификатор на акаунта


31

Instructions - EMUI Termlist Translation_V1.1_20180907.docx


Translation for “account” in term list was not followed.

Root cause: Translator thought his translation for “account” is better than what in termlist and did not follow the process for term update.

Measures:

1. Add the issue as an example and emphasize the term update process:

2. Feedback -> Confirmation -> Update termlist -> Global change for all related strings

22.EMUI string- Portuguese-BR- Unfamiliar with industry commonly-used term


Language: Portuguese-BR DBID: PL_269969

Source: %d-hour time

Translation: %d-data/hora -> Formato de %d horas

24 hours -> %d hour format

Root cause: The translator did not realize “hour time” here means hour format, while “hour time” here is commonly used in IOS.

Measures:

1. Learn and collect industry commonly used terms.


32


2. Investigation and comparison analysis of peer products.

23.EMUI String- Arabic-Typo error-Missing “and” during review

VOC from: QC


App name: CellBroadcastReceiver

String ID: enable_cmas_severe_threat_alerts_summary

TR/TO: TR201803002786_13

Feedback date: 2019-02

Issue DescriptionSource: Severe threats to life and property.

Original translation: الحياة على عالية خطورة تشكل تهديدات تلقي عند التنبيهالممتلكاتModified: الحياة على عالية خطورة تشكل تهديدات تلقي عند التنبيه

الممتلكاتوIssue description: Typo issue: The letter "and" is missing.

Root Cause1. Introduction point: During the review phase, translation was rephrased to

make it clear enough, however, the preposition letter “and” only one letter in Arabic (و) was missing from the final translation.

2. Control point 1: This error was neglected by the reviewer during the self-check because the track changes in Trados studio were not highlighted with a bright color. CAT checking tools including word spelling, unfortunately, did not help to detect such type of errors.

3. Control point 2: Review changes should get back to translator for a second confirmation. Due to tight deadline, this task was delivered by the reviewer directly without a second confirmation by the translator.

4. Control point 3: This error was neglected during the LT.


33


Improvement MeasuresCorrective: The string is updated in the string library and TM.Preventive:

1. Re-set the Track Changes colors to a more obvious color as follows. Read-back and check changes more carefully during the review stage:

Choose File > Options, and set Tracked Changes Formatting to an obvious color:

2. Get back reviewed version to the translator for a second confirmation.

3. LT stage: The linguist is required to pay more attention to the text and should use word Compare function instead, to help them highlight and review all modified parts and ensure that no spelling error introduced in such stage.

24.EMUI String- French-Misreading led to mistranslation

VOC from: Beta testing

Basic InfoLanguage: French

DBID: CS_438871

TR/TO: TR201806002746_04



34


Issue DescriptionSource: Sort card

Original translation: Carte souple (soft card)

Modified: yes

Issue description: “sort” was translated as “soft”

Root Cause1. Introduction point: misreading of source during translation2. Control point: no 2nd eye review was arranged due to linguist’s vacation.

Xbench tool cannot identify the issue. The string was not added to LT phase.

3. The above light control led to this issue detected in the beta test phone.

Improvement Measures1. Corrective: The issue was fixed in SMS. All the non-strings with lower

priorities are under reviewing.2. Preventive: 2nd eye review is now a must process for French EMUI string

translation tasks. Improved process for handling strings not added to LT: Developer shares the reason that strings cannot be added to LT scope -> GPM judges if it is reasonable and tracks the strings until they are added to LT scope.

3. For strings that cannot be reproduced in LT, a further review will be arranged from GPM.

25.EMUI String- Indonesian-Accurracy-Yes/No error: “enable” vs “disable”

VOC from: QC


App name: HWCardManager

String ID: dual_lte_enable_message

TR/TO: TO201806000367, TO201806000368



35


Issue DescriptionSource: 4G enabled on SIM %1$d.

Original translation: 4G dinonaktifkan di SIM %1$d.

Modified: 4G diaktifkan di SIM %1$d.

Issue description: Source “enabled” is mistranslated as “disabled”

Root Cause1. Introduction point:“enabled” (should have been “diaktifkan”) was

translated as “disabled” (“dinonaktifkan”). During the translation, SDL Trados Studio provided a fuzzy match (no longer recorded when screenshot was taken) based on a similar segment before it. As seen in the screenshot below, the incorrect segment is 82. Segment 81 has a similar content and the word “disable”. The translator did not properly edit the fuzzy match in Segment 82.

2. Control point: The mistake was not detected in the QA stage because the word “enabled” and “disabled” (with -d suffix) are not in the Huawei Indonesian Terms for Terminal Products and thus is not in the Xbench checklist.

Improvement MeasuresCorrective: The string is updated in the string library and TM.Preventive:

1. Set QA Checker in Trados and go through all the unmodified fuzzy strings carefully.


36


2. In translation stage, the linguist should add the word “enabled” and “disabled” in their termbase so that these words can be identified easier. Other similar terms should also be considered to add to the termbase.

3. In QA stage, the linguist should add the word “enabled” and “disabled” in their Xbench checklist. Other similar terms should also be considered to add to the checklist.

26.EMUI String- Croatian-Accurracy- Yes/No error: “sufficient” vs “insufficient”

VOC from: QC


App name: HwSystemManager

String ID: space_clean_storage_suggestion_sufficient

TR/TO: TO201808001080


Issue DescriptionSource: Storage sufficient.

Original translation: Nedovoljan prostor za pohranu.


37


Modified: Dovoljan prostor za pohranu

Issue description: Yes/No error, “sufficient” is mistranslated as “insufficient”

Root Cause1. Introduction point: Introduced during initial translation due to a not

careful enough work. 2. Control point:

1) During Xbench check, there was no complaint triggered for this string, also for such “yes/no” mistranslation no checking rules in place. 2) Proofreading didn’t catch the mistake, since as instructed at that time proofreader would focus on spelling and grammar mistakes, and the proofreader didn’t compare the translation with English text. 3) Testing. The string was not added for testing.

Improvement Measures1. Corrective: Fixed the translation.2. Preventive:

1) Due to severity of the mistake, replace the Croatian linguist resource for EMUI string translation. 2) Share the mistranslation case to linguists to promote the quality control sense. 3) Use a special Xbench checklist which contains the opposite translation to the source to detect such error. The checklist is maintained to collect yes/no errors once they occur, and it can avoid the same mistake from happening again. It had been tested and works.

27.EMUI String- Finnish-Mistranslation due to lack of query

VOC from: frontline feedback

Basic InfoLanguage: Finnish

DBID: PL_452216

TR/TO: TO201808000648


Issue DescriptionSource: Screen time


38


Original translation: Näytön aika (time of/on the screen)

Modified: Ruutuaika (time spent looking at the screen)

Issue description: Original translation meant the how long an item showing on the screen, while the source actually meant the time spent looking at the screen.

Root CausePlayback of each phase (Engineering -> Translation -> Proofreading; The string wasn’t involved in testing)

1. Introduction point: The original translation was introduced during translation due to lack of understanding of the scenario.

2. Control point: 1) The issue cannot be detected during QA through xbench checking since it was a literal translation of the source text. 2) The issue was not detected or fixed during proofreading phase due to the proofreader was focusing on spelling and grammar mistake as per instructed for the time being. 3) The string was not added to LT phase. The English text on screenshot was ambiguous with many possible interpretation and no description was provided. In this case the linguist did not raise a query for source understanding, instead of translating it literally.

Improvement Measures1. Corrective: The string has been updated in database.2. Preventive:

1) Add the issue as a case and share to all the linguists that a query should be raised about source meaning if the linguist is not quite sure of the scenario from given screenshots and description and avoid translating with guess. 2) Add clear scene descriptions to the string if the screenshot is not quite helpful to judge the scenario.3) Compare the proofread version with the final version after the original translator checks the proofread version, to see what errors were real and fixed. Among the errors we should be able to see accuracy issues reported.4) Improved process for handling strings not added to LT: Developer shares the reason that strings cannot be added to LT scope -> GPM judges if it is reasonable and tracks the strings until they are added to LT scope.For strings that cannot be reproduced in LT, a further review will be arranged from GPM.


39


28.EMUI String- Hungarian – Accuracy (Shutter)

VOC from: Beta Test

Basic Info

Language: Hungarian

DBID: PL_441456

TR/TO: TO201806000222


Issue DescriptionSource: Shutter

Original translation: Kioldógomb

Modified: Záridő

Issue description: The back translation of original translation is shutter button. The back translation of final translation is shutter speed. Based on the scenario, it is not about a physical button, but just description for shutter. The original translation is incorrect under the scenario.


40


Root Cause

1. Introduction point: The linguist translated the word into a commonly used term for Shutter - the Shutter button. Since there is no universal „shutter” word in Hungarian and he didn’t investigate further and was not able to accurately illustrate it as Shutter Speed.

2. Control point: 1) Since the term “shutter” is often translated as Kioldógomb in

photography as well, the reviewer did not think and investigate further and translated it as “shutter button” directly.

2) In the LT stage, the same linguist was not able to recognize that shutter should refer to “shutter speed” in this case. He took it for granted as shutter button which is commonly used in life.


41


Improvement Measures

1. Corrective: 1) The translation of this string has been updated in database.2) English team will consider to update the string to a more accurate

translation of “Shutter speed” and add a detailed description of the scenario as scene description.

2. Preventive: 1) The issue is added as a case to emphasize all the linguist the

importance of investigation of unknown knowledge and area during translating EMUI interface and the importance of carefully checking scenario provided. If there is uncertainties, a query is needed.

2) Review of this string for all the languages will be arranged.

29.EMUI String- Japanese -Accurracy- Yes/No error: “moved to” vs “moved out of”


Basic InfoLanguage: Japanese

DBID:

CS_448621

CS_448599



CS_448621 - %d files were moved to Safe.

CS_448599 - %d files were moved out of Safe.


CS_448621 - %d 個のファイルが Safe ボックスから移動されました (%d files were moved out of Safe.).

CS_448599 - %d 個のファイルが Safe ボックスに移動されました (%d files were moved to Safe.)


42


Issue description:

In Japanese original translation, the translation of two strings is reversed.

Wrong translation in the deliverables:

Root Cause1. Introduction point: High fuzzy match in Trados studio causes this reverse

error.2. Control point: No proofreading, no LT (this is a dialog prompt which is

displayed too fast for screenshot, so it is not included in the LT based on screenshot)


43


Improvement MeasuresCorrective: The strings were updated in the string library and TM.Preventive:All translators are required to set the check reminder for the fuzzy strings that are not edited in the Trados tool and confirm them one by one.Below is an option in Studio QA checker that can identify fuzzy strings not updated and generate warnings for you to recheck during QA.Path: Project Settings -> Verification -> InconsistenciesSelect Check for unedited fuzzy matches checkbox -> All segments

Please do select this option in your Trados and go through the related warnings one by one carefully during QA.

30.EMUI String- 25 languages -Accurracy-Train and Cycle mistranslation


Basic Info

Language: all involved 25 languages

DBID:

CS_489615 Train


44


CS_366798 Cycle


Issue Description

Two words in the same page of the Health app were mistranslated in 20+ languages and were also missed during LT, which caused a crash in version release and caused distrust from our customers.

Case 1: Source: Train 训练Original translation: A wrong word which means Train 火车, a means of transportation

Modified: Changed to the word with the meaning of training, a physical exercise

Issue description: Train actually means training, a physical exercise but is mistranslated as “a means of transportation”

Case 2: Source: Cycle 骑行Original translation: A wrong word which means series of events or processes that is repeated again and again (周期)

Modified: Change to the word with the meaning of riding a bicycle

Issue description: Cycle actually means riding a bicycle but is mistranslated as “series of events or processes that is repeated again and again”

The screenshot for translation is:


45


The screenshot for testing (LT) is:

For the consideration of avoiding truncation, the four menus were finally unified into four verbs in English source instead of verb+ing.


46


Root Cause

Case 1: Source: Train 训练1. Introduction point: Translation phase. Train in English has two

meanings. One is a means of transportation and the other is training, a physical exercise. The two meanings are both common. The translator chose the wrong meaning without fully understanding the string scenario and function.

2. Control point 1: In multi-lingual translation, the translator did not completely understand the function and scenario correspond to this string. Actually, in the screenshot, the Exercise menu at the bottom of this screenshot can help to understand, but the translator did not see it. The string ID “IDS_track_sport_type_train” in the reference table can also help for scenario clarification, but all these information were ignored by the translators.

3. Control point 2: Multiple-meaning words were not provided with a description during English proofreading.

4. Control point 3: This string was submitted for LT and the screenshot is very clear for a correct understanding, however, testers of 25 languages fail to find this error during the testing.

Case 1: Source: Cycle 骑行2023-5-15 Huawei Proprietary and

Confidential47


1. Introduction point: Translation phase. Cycle in English has more than one meaning. When cycle is a noun, it means “series of events or processes that is repeated again and again” or “Bicycle”, or other meanings. When cycle is a verb, it has a meaning of “riding a bicycle”. The translator chose the wrong meaning without fully understanding the string scenario and function.

2. Control point 1: In multi-lingual translation, there was no screenshot is provided. The translator did not submit a query in case of multiple-meaning words.

3. Control point 2: Multiple-meaning words were not provided with a description during English proofreading.

4. Control point 3: This string was not submitted for LT.

Improvement Measures1. Corrective: Check all Train and Cycle translations and correct the

translation into the string library.2. Preventive:

a) If multi-meaning words exist in English proofreading, add descriptions to help the translators understand them correctly. Owner: English proofreader

b) For all translators: Make sure you translate all strings after you fully understanding the function and scenario. Accuracy should always be placed in the first place. Any carelessness or negligence will lead to potential errors.

c) For all testers: LT should also be done based on a comprehensive understanding of the function and scenario.

31.EMUI String- Hungarian - Accuracy error: “volume”


Basic InfoLanguage: Hungarian

DBID: PL_479307


Issue DescriptionSource: Volume

Original translation: Hangerő


48


Issue description: “Volume” was translated into “Hangerő”, which refers to the sound volume, but under the scenario, It should be “bulk” under HiMeasure module.

Root Cause1. Introduction point: Translation stage.

In translation stage, neither EN screenshot nor description of the string was provided, so the translator just made his best guess and followed the TM/glossary. As the translation team now recalls, this string was shown as a confirmed full match and they just assumed that it is such a common word and it should be of no risk to leave as it is.


49


Below is the screenshot provided during translation:

2. Control point: The error was not detected during QA and proofreading stages

with the same reason.LT was done by the same linguist who provide the translation. The translation error should have been identified during LT since the meaning is pretty obvious on the screenshots. However, the tester didn’t check the screenshot carefully and missed detecting the error. The tester also encountered bad performance of LT.


50


Improvement MeasuresCorrective: the translation error was fixed during QC string check. Preventive:

Clear description of the scenario was added as reference info to the review task of strings containing polysemous words for all the languages to double check.

Confirmed 100% matches might be misleading to the translators. Engineers will populate TM matches without confirming 100% matches. The confirmation part will be done by linguists that will have to check the matches.

Add the issue as a case and share with all the linguists working on translation and on testing to remind them of the importance of checking the screenshots, understanding the meaning of it and raising queries, especially when it comes to terms with multiple meanings.

Improve xDevice performance.


51


32.EMUI String- Hungarian - Accuracy error: “in”



DBID: PL_479290


Issue DescriptionSource: in

Original translation: itt:

Issue description: “in” was translated into “itt:”, which means “inside” and it is completely wrong under the context. It refers to “inch” here.

Root Cause1. Introduction point: Translation stage.

In translation stage, neither EN screenshot nor description of the string was provided, so the translator just made his best guess and followed the TM/glossary. As the translation team now recalls, this string was shown as a confirmed full match and they just assumed that it is such a common word and it should be of no risk to leave as it is.

Below is the screenshot provided during translation:

2. Control point:


52


The error was not detected during QA and proofreading stages with the same reason.LT was done by the same linguist who provide the translation. The translation error should have been identified during LT since the meaning is pretty obvious on the screenshots. However, the tester didn’t check the screenshot carefully and missed detecting the error. The tester also encountered bad performance of LT.

Improvement MeasuresCorrective: the translation error was fixed during QC string check. Preventive:

Clear description of the scenario was added as reference info to the review task of strings containing polysemous words for all the languages to double check.

Confirmed 100% matches might be misleading to the translators. Engineers will populate TM matches without confirming 100% matches. The confirmation part will be done by linguists that will have to check the matches.

Add the issue as a case and share with all the linguists working on translation and on testing to remind them of the importance of checking the screenshots, understanding the meaning of it and raising queries, especially when it comes to terms with multiple meanings.


53


Improve xDevice performance.

33.EMUI String- Japanese –termlist not followed



DBID: PL_367533


Issue DescriptionSource: Voice control

Original translation: 音声操作Updated translation: 音声制御Issue description: the updated translation is a more accurate translation for the term “Voice control” and it is also the existing translation in termlist.

Root Cause1. Introduction point: translator did not load termbase based on published

termlist on language assets platform correctly.2. Control point:

The translator did not load xBench checklist based on published termlist on language assets platform correctly, so the issue was not detected during QA phase. The issue was not detected by human check and tool check during LT.

Improvement MeasuresCorrective: the translation error was fixed during QC string check. Preventive: Add the issue as a case and share with all the linguists to emphasize the importance of compliance of the process (loading terms from language assets platform to termbase and xBench checklist).


54


34.EMUI String- Italian–Accuracy


Basic InfoLanguage: Italian

DBID: CS_334674


Issue DescriptionSource: I have read and understand the %1$sdisclaimer%2$s

Original translation: Ho letto e compreso l\'%1$sesclusione di responsabilità%2$s

Updated translation: Ho letto e compreso l\'%1$esclusione dalla garanzia%2$s

Issue description: This is a case of “Over interpretation”. The old translation does not really fit this specific context of “warranty denial” but simply referred to a "responsibility exemption”

Root Cause1. Introduction point: The target language has different ways to translate

this legal term so this can be considered a tricky translation, and unfortunately, during the translation the context has been over interpreted.

2. Control point: The problem cannot really be detected by tools, so the only way to prevent the issue is a second eye review, both during the translation and LT, but unfortunately missed for this string.

Improvement MeasuresCorrective: the translation error was fixed during the LT but the frontline spotted it before. Preventive:Especially for legal terms, the translator must be sure about the context, and ask a query if there is any uncertainty due to lack of context. For next cases involving the same term, an accurate analysis of the disclaimer content should be provided in order to find the most specific and accurate translation in the target. String by string review during LT is also needed.


55


35.EMUI String- Japanese - Accuracy error: “interval”

VOC from: review feedback


DBID: CS_510467


Issue DescriptionSource: Low-intensity intervals

Original translation: 低強度期間Updated translation: 低強度間隔Issue description: “interval” was mistranslated into “期間” (period), which is not specific enough in the context. It should be translated into “間隔” (a break period).

Root Cause1. Introduction point: Translator didn’t understand source context clearly,

was unfamiliar with sports/fitness field, and lack of some basic knowledge, so he/she mistranslated the word “interval”.

2. Control point: The error was not detected during QA stage. The translator didn’t raise query about unclear source, while he/she just translated the text

based on subjective judgement.

Improvement MeasuresCorrective: the translation error was fixed during the review. Preventive:

1. Add this issue as a case and share it with all linguists to study. 2. Remind linguists of the importance of checking the screenshots, understanding the meaning of it and raising queries, especially when it comes to terms with ambiguous meanings.


56


36.EMUI String- Japanese - Accuracy error: “in”



DBID: PL_507188


Issue DescriptionSource: Try again in %2$d minutes.

Original translation: %2$d 分以内に再試行してください。Updated translation: %2$d 分後に再試行してください。Issue description: The meaning for “in” was incorrectly conveyed into “within”.

Root Cause1. Introduction point: The translator didn’t understand source clearly and

mistranslated it into “以内” which means “within”. Some linguists couldn’t distinguish such kind of source.

2. Control point: The issue was not detected by human check and tool check during translation and review stages.

.

Improvement MeasuresCorrective: the translation error was fixed during the review. Preventive: Add the issue as a case and share to all the linguists about this commonly used expression.


57


37.EMUI String- Japanese - Accuracy error: “time”



DBID: CS_521436


Issue DescriptionSource: Time of application: %s

Original translation: 申請の回数： %s

Updated translation: 申込時刻： %s

Issue description: Translator didn’t focus on the example with this variable but understood it as the “number of times/frequency” directly, instead of the “point of time”.

Root Cause1. Introduction point: Translator didn’t refer to scenario and misunderstood

the meaning of “time”.2. Control point: The error was not detected during QA and proofreading

stages.

Improvement MeasuresCorrective: the translation error was fixed during the review. Preventive:

1. Add this issue as a case and share to all the linguists, query should be raised about source meaning if the linguist is not quite sure of the scenario from given screenshots and description and avoid translating with guess.


58


38.EMUI String- Japanese - Accuracy error: “Face recognition”

VOC from: QC feedback


DBID: PL_497065


Issue DescriptionSource: Face not recognized. Touch twice to try again.

Original translation: 顔認証に失敗しました。再試行するには、カギマークを 2 回タップしてください。Updated translation: 顔認証に失敗しました。再試行するには、2 回タップしてください。

Issue description: Unnecessary カギマークを (key mark) was wrongly added, which makes the translation not correspondence with source. In the context, it means “touch the face mark twice to try again”. It wrongly narrowed down the actual operation from “tap anywhere of the whole screen” to “tap the key mark”.

Root CauseIntroduction point: During LT, the linguist thought face can only be recognized by tapping the key mark on the screen after checking the screenshot provided during LT without raising a query.

Checking point: No second eye review was arranged for the updated translation made during LT.

Improvement MeasuresCorrective: the translation error was fixed and rolled back to the original translation totally corresponding to source provided during translation phase.Preventive: Add the issue as a case and share to all the linguists to emphasize the importance of raising queries when you have doubt but not translating strings by subjective perception.


59


39.EMUI String- Arabic - Redundant word

VOC from: QC feedback

Basic InfoLanguage: Arabic

DBID:

PL_423639



In order to provide this service, we need to collect and use the following information:


التالية المعلومات جمع إلى نحتاج فإننا يقوم الخدمة، هذه توفير أجل من:واستخدامها

Recommended translation from Frontline:

واستخدامها التالية المعلومات جمع إلى نحتاج فإننا الخد هذه توفير أجل :من

Final translation

التالية المعلومات واستخدام جمع إلى نحتاج الخدمة، هذه :لتوفيرIssue description:

A redundant word should be deleted from frontline’s feedback, while a spelling error was introduced in the recommended translation.

Root Cause1. Introduction point: The translation recommended by frontline has a

spelling error, but we accepted the recommended translation and ignored the spelling error introduced by the frontline.

2. Control point: We didn’t double check the recommended translation to detect the issue, and left the “final translation” column blank as the QC template was updated at that time, and we weren’t familiar with this new template.


60


Improvement MeasuresCorrective: the translation error was fixed during QC string check. Preventive:1. Add the issue as a case and share with all the linguists to emphasize the importance of double checking recommended translation.2. Do the QC string check as per the latest requirements, add detailed comments and provide the final translation without errors. Compare differences among original translation, recommended translation and final translation, to avoid any issues introduced in the final translation.

40.Watch string – Polish – Weather forecast string; incorrect word/spelling issue

VOC from: FLE

Basic InfoLanguage: Polish

DBID/Text ID: IDS_Weather_Text_Shower



Showers


Przelotne odpady deszczu

Recommended translation from Frontline:

Przelotne opady deszczu

Issue description:

Second word in the original translation has an additional “d” letter which changes meaning from ‘fall’ (of rain) to ‘waste’. Categorized as spelling mistake.

Root Cause1. Introduction point: Translation project for HWWatch strings was handed

in September 2018. The file contained strings for weather forecast. There were multiple phrases for ‘rain fall’ in English (e.g. heavy, light). There was also word ‘showers’ which in Polish translates as ‘temporary rain


61


fall’. When typing translation for ‘fall’ I unintentionally added letter d which changed meaning of the phrase from ‘temporary rain fall’ to ‘temporary rain waste’: opady -- odpady

2. Control point: No spelling checker or QA tool can detect this mistake. Both words (opady and odpady) are real words, thus won’t be reported by spellchecker or grammar checker. Because during proofreading and QA I focused more on first word in the phrase, which specify type of rain fall, I overlooked typo in the second word, that is ‘odpady’. Compare:Light rain > Lekkie opady deszczu; heavy rain > intensywne opady deszczuShower >przelotne opady deszczuThe mistake was not spotted during the most recent first LT task for Watch, for two reasons: 1) same as in case of proofreading translation for the first time; 2) the string on the screenshot was not fully visible.

Improvement MeasuresCorrective: Translation was updated in LT retest Preventive:3. Since no tool can detect this kind of issues by default, I am now collecting all words (with similar spelling but different meaning), phrases and collocations that my lead to similar problem. In my personal xBench check list I include less used forms, this way xBench will notify me whenever a suspicious translation appears


62


4. For LT tasks, it is advised that attention is paid to every single word of a string, which is particularly important for wearables where the space is limited and translation has to be the most direct and informative.5. Every LT task should be followed by QA section for both passes strings as well as failed to avoid any possible mistakes that were either overlooked in strings that were passed or introduced in recommended translations. This section should include spell checking, xBench verification (for variables, terms, and other check lists) as well as personal check list, and analysis of Beyond compare report.

41.EMUI String – Polish – inaccurate translation, contact

VOC from: Beta user

Basic InfoLanguage: Polish

DBID/Text ID: PL_458904


Issue DescriptionSource: Delete multiple entries


63


Original translation: Delete multiple contacts

Recommended translation from Frontline: Delete multiple entries

Issue description:

The translator misinterpreted general term ‘entry’ as ‘contact’ (where entry stands for ‘an entry in call log’). While translating strings related to Dialer and Contacts, linguist assumed entries referred to contacts. During LT linguist got confused by “Blocked” item next to the “Delete entries”, as he thought block and delete may only refer to contact rather than entries. And so after checking translation on the screen matched the string table he passed the string.

Root Cause1. For project C18160808056_TO201808000638&639_B647_6L, which

was handed off on 8/21/2018, string Delete multiple entries was translated as Delete multiple contacts. The mistake was not rectified in LT task. During LT linguist got confused by “Blocked” item next to the “Delete entries”, as he thought block and delete may only refer to contact rather than entries. And so after checking translation on the screen matched the string table he passed the stringThe mistake was not spotted during the most recent first LT task for Watch, for two reasons: 1) same as in case of proofreading translation for the first time; 2) the string on the screenshot was not fully visible.

2. Later on, the string was changed by English team to Delete entries and Polish translation was then updated to correct translation. However, in the older versions of EMUI the wrong translation was kept and was reported by a Beta User. This was not detected by linguist during KMT because the test phone was running a newer version. However, a beta user was using obsolete version with the incorrect translation.

Figure 1 Screenshot of string history

Improvement MeasuresCorrective: Translation was corrected in QC task.Preventive:

1. To assure accuracy, strings containing words like items, entries, etc. that may have different meaning depending on context should be double checked on the screenshot and scene description and confirmed in context and even rise a query to the client.


64


2. When dealing with a string in testing it should be checked for linguistic accuracy as well as functional accuracy. In this particular case, should the linguist tap the string to see the action, it would become clearer that an entry from call log is deleted not a contact in Contacts app.

3. The issue would be avoided if strings updated in English and then Target languages were updated also in previous versions. Otherwise different users have different versions of the same string DBID.

4. In case of English string update, screenshots should be provided not only in English but also in target language to check accuracy of original translation and make decision if string has to be updated based on the context.\


65

Documents

g11n.rnd.huawei.comg11n.rnd.huawei.com/UIDoc/WebContent-2/Consumer/EMUI/WebC… · Web view17.09.2019 · Case Study for Huawei Multilingual Projects (Template) Project name-Lanuguage-Defect