Closed
Bug 1014906
Opened 11 years ago
Closed 10 years ago
[B2G][1.4][l10n][Bluetooth] Galego: The string/title "Change phone name" displays with truncation on the Change phone name screen.
Categories
(Mozilla Localizations :: gl / Galician, defect)
Tracking
(b2g-v1.3 unaffected, b2g-v1.4 affected)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
b2g-v1.3 | --- | unaffected |
b2g-v1.4 | --- | affected |
People
(Reporter: mhall, Unassigned)
References
Details
(Whiteboard: LocRun1.4)
Attachments
(1 file)
(deleted),
image/png
|
Details |
Description:
In the Bluetooth app on the Change phone name screen, the string/title "Change phone name" displays with truncation in the tested language. Truncation doesn't occur in English.
Repro Steps:
1) Update a Buri to BuildID: 20140521000202
2) Tap on "Settings" from the home screen
3) Tap on "Bluetooth"
4) Tap on "Rename my device" (first tab)
5) Observe the screen/title "Change phone name" displays with truncation
Actual:
The string/title "Change phone name" displays with truncation
Expected:
The string/title "Change phone name" displays without truncation
1.4 Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140521000202
Gaia: 93623f6435849cc9f54d9996e8e64828ac9091d1
Gecko: 12fe2b67a099
Version: 30.0
Firmware Version: v1.2-device.cfg
Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/12306/
See attached: screenshot
1.3 Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140425024003
Gaia: 32a9e3db738e0b3bc44a4d4d5c16512a2617a2cf
Gecko: c96b0cf6343f
Version: 28.0
Firmware Version: v1.2-device.cfg
Galego is not an available language on the Buri 1.3 MOZ RIL
Comment 2•10 years ago
|
||
Hi.
Fixed in v1_4 and propagated to the v2_0 and v2_1 version.
http://hg.mozilla.org/releases/gaia-l10n/v1_4/gl/rev/ea2a800e25db
http://hg.mozilla.org/releases/gaia-l10n/v2_0/gl/rev/ae7d299751a6
http://hg.mozilla.org/gaia-l10n/gl/rev/cbd7a7f5d6eb
Thanks.
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•