Instructions on Submitting Language Bugs

1. Where to Submit Language Bugs

Submit language bugs to the Multilingual-BugManagement sector on the ALM platform. The
language localization team will review the bugs and forward them to our multi-language vendors
for confirmation, normally 3 times a week.
Submission link: http://alm.adc.com/OPPO/Multilingual-BugManagement
Submitted bugs will be dealt with on every Monday, Wednesday, and Friday at 6 PM. It
typically takes 2 to 3 workdays to confirm the bug.
Please note that urgent confirmation services may incur an additional cost, so be sure you have
sufficient time on your project schedule.
Language bug coordinator: 王茜 (80259139)
Language bugs will no longer be received through TeamTalk. For special cases, please call the
coordinator.

2. Language Bug Types

There are two major types of language bugs, namely, linguistic issues and function/layout
issues. The definition of every bug type is listed below.

Category Bug Type Description

Linguistic Issue Improvement The original translation is fine and free from
 grammar, spelling, punctuation, and spacing errors.
It only needs to be improved in some way based on
the context.
Linguistic Issue Linguistic Un-localized The whole string or part of it is not translated.
The original translation doesn't fit in the actual
Linguistic Issue Wrong translations
context.
Grammar or spelling errors exist in the original
Linguistic Issue Grammar/Spelling
translation.
The capitalization style adopted in the original
Linguistic Issue Capitalization
translation is not in line with OPPO Style Guide.
The usage of terms or expressions are not
Linguistic Issue Inconsistency
consistent in the context.
Extra spaces or missing spaces in the original
Linguistic Issue Space error
translation.
Incorrect use of punctuation, including excessive
Linguistic Issue Punctuation
punctuation or misplaced punctuation.
The translation in Otrans is correct, while the
displayed translation on the screenshot is different
from it. The possible reason is that the translation
has not been synced to the code.
E.g.
Function/Layout issue Display error
1. The string is not translated on the screenshot
while it has translation in Otrans.
2. The translation on the screenshot is different
from Otrans in some way, such as
capitalization style.
The translation cannot fully display for limited
spaces and ends with an ellipsis. If the translation
can be shortened, select the bug type as
Function/Layout issue Missing strings
Improvement and provide a recommended
translation to Expected results. Otherwise, submit
the bug as a Missing string bug.
The translation is truncated and cannot be fully
displayed. If the original translation missed the
Function/Layout issue Truncation
line-break, submit an Improvement bug, otherwise
submit a Truncation bug.
Incorrect use of line breaks, such as one single
word is displayed in two lines. If the original
translation missed the line-break, submit the bug as
Function/Layout issue Wrong line-break
an Improvement bug; otherwise, submit it as a
Wrong line-break bug. One single word displaying
in a new line is fine if there is no line-break errors.
Function/Layout issue Wrong direction
Function/Layout issue Overlap
Function/Layout issue Misalign
Show StringID (Actually it’s
Function/Layout issue
string number)
Function/Layout issue Messy code
Function/Layout issue Font size
Function/Layout issue Function
Function/Layout issue Functional Un-localized
Function/Layout issue Other
Incorrect layout with RTL languages.
Icons or texts overlap on the screen.
The alignment of the translation is incorrect.
Some of the strings on the screen are displayed
with Number. If all strings display with Number in
the target language while the English screenshot is
normal, check whether the screenshot of the target
language was taken incorrectly.
Messy code displays on the screen while the
original translation is clean. If messy code exists in
the original translation, submit the bug as an
Improvement type and provide the recommended
translation for the string.
Part of the string has a different font size from the
rest.
Display error caused by functional issues, such as
function logic error.
String untranslated due to programming issues such
as incorrect string stitching or failing to call
variables.
For bugs not included in these types, the bug
description is required to be filled in the Remark
column.

3. Bug Fixing Process

Linguistic Issues:
1、 Confirm the translation: The Localization Team Assistant WANG Xi (80259139) will export
improved translations and forward them to our multi-language vendors for confirmation,
normally 3 times a week, on every Monday, Wednesday, and Friday at 6 PM. For special
cases, the confirmation frequency can be increased based on the demand. The whole process
typically takes 2 to 3 workdays and its progress can be monitored through the bug status and
the date remarked in the testing arrangement explanation.

Status Stage Testing arrangement explanation

Displayed as “新建”
New /
on the page
Solving Fixing translation Forwarded to TR on 0000-00-00
Solved by TR/Reject Solved by TR/Reject Replied by TR on 0000-00-00
RD to merge the new translation to
RD Handling RD Handling
the code
To Be Verified To Be Verified To be verified by the tester
 “Reopened/已关闭”
Reopened/Closed
on the page

2、 Code update and testing: After TR confirms the updated translation, the Localization Team
Assistant will change the bug status to "Solved by TR" or "Reject" according to the
translator's advice. If the translation issue is solved, the assistant will assign the bug to the
corresponding developer. The developer should change the status to RD Handling once
received the bug and update it to "To Be Verified" after the code is submitted. The subsequent
testing can be divided into the following two situations:
 For minor OS version updates test or sporadic bugs, the corresponding tester or PM needs
to notify the developer to update the code and provide a new APK for the tester for
verification.
 For the main OS version upgrade test or the test for a brand new language or market,
language test PM will arrange test vendors to carry out verification.
3、 Verification: The tester to verify whether the translation displayed on the screen is the same as
the expected result on ALM and there are no layout issues. If so, change the bug status to
"Closed". Otherwise, check the update history of the string on Otrans and follow the
instructions below:
 If the string was firstly updated as the expected result but was later changed to a more
recent one, the bug verification should be regarded as passed.
 If the expected result has not been uploaded to Otrans while the bug status is not "Reject",
change the bug status to "Reopen" and write a note in Mark that the translation is not
updated, then pass on the case to 王茜 (Jenny).
 If the translation on Otrans has been updated as the expected result, change the bug status
to "Reopen" and write a note in Mark that the translation has not been merged to the code.
Then notify the corresponding developer to update the code and provide a new APK for
verification.

Server address to view updated translations: \\172.17.121.34\测试领域资料\ROM 中心资料

存储文件夹\14-其他\多语言\翻译公司返回词条处理结果

Function/Layout Issue
Note: If there are obvious issues such as Overlap, Truncation, and Misalign on the screenshot,
the tester should contact the developer timely to fix it before it becomes a language bug.

The developer shall solve this kind of bugs together with the UI designer. Refer to the slides
Function/Layout issues and how to deal with them for example and solutions.
If the issue is caused by the overlong translation, the developer needs to assign the bug to the
corresponding translator. The translator shall confirm whether the translation can be shortened.
See the instruction picture below:
If the translation cannot be further shortened, the bug should be changed to "Reopened". The
developer and UI designer should jointly evaluate the case and give a feasible solution.

4. Additional Information
The developer needs to fill in the string number for the bug if it's not provided. (Not required
for strings with no numbers.) Follow the instructions below:
Note: Testers shall provide the screenshot of the defective string with its string numbers.
1、 String number: The same String ID may correspond to more than one string so it's not an
effective way to locate the defective string. String number, however, is a unique number
generated randomly for each single string.
String ID and Number are as shown below:

2、 How to find out the string number: The developer can get the string ID from the code, and
then confirm the string number according to the module name and source text. Otrans query
link: https://otrans-new.oppoer.me/#/wentry/query; Apply for Otrans permission:
http://upm.myoas.com/siag/index#/console/system/limit
3、 Fill in the string number: The developer needs to fill in the string number in the "Number"
field in the bug page as well as its English translation and defective target language translation
in the "English" and "Target Language" fields. See the picture below:
 Query a string
  Complete the string info and save the bug page

Appendix:
 Function/Layout issues and how to deal with them