892735 - [B2G][l10n][Call Settings]Slovak: Call Forwarding text appears truncated

Status: RESOLVED FIXED

(Mozilla Localizations :: sk / Slovak, defect)

Description

[Sarah Parsons]

Attachment: screenshot1

Description:
Call Forwarding text appears truncated in:
-Always Forward
-Forward when busy 
-Forward when unanswered
-Forward when unreachable

Repro Steps:
1) Updated to Leo Build ID: 20130710070204
2) Go to Settings.
3) Scroll down and select Call Settings.

Actual:
Call Forwarding appears cut off.

Expected:
User should be able to see whole text.

Environmental Variables
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/aaa74e5efaf1
Gaia: 7cdcc46179d198cab11970964b181ede32a5b683
Platform Version: 18.1
RIL Version: 01.01.00.019.138 

Notes:
Repro frequency: 100%

Comment 1

[Sarah Parsons]

Attachment: screenshot2

Comment 2

[Vlado Valastiak [:wladow]]

Everything shortened except for the header on sshot2. This header is sharing "callForwarding" string with other element. We need them to use separate strings in order to be able to fix the truncation issue.

Comment 3

[Delphine Lebédel [:delphine - Use needinfo]]

Asking for devs to look into this!
Vlado: is shot2 still understandable at the time being?

Comment 4

[Evelyn Hung]

ni UX for string change.

Comment 5

[sarsenyev]

Verified on Leo V1.1 COM RIL,
No more truncation in "Call Settings" option

Environmental Variables
Build ID: 20130807071207
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/11bb1b0eefff
Gaia: 60ca81600a080dae33058b0692ecaa213556c926
Platform Version: 18.1
RIL Version: 01.01.00.019.184

Comment 6

[Vlado Valastiak [:wladow]]

This is not fixed yet, see comment 2

Comment 7

[Evelyn Hung]

redirect to UX team.

Comment 8

[Stephany Wilkes]

UX is reviewing this now, and we cannot determine why we were asked for a string change (which we think is usually recommended by localizers)? 

Please let us know what remains to be done here.

Comment 9

[Vlado Valastiak [:wladow]]

Fixed in http://hg.mozilla.org/releases/gaia-l10n/v1_3/sk/rev/b68e7703ae1f#l4.133, both issues are fixed now.