889490 - [B2G][l10n][SIM Security] Nederlands: Header text is truncated in the Enter SIM PIN menu

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::Settings, defect)

Description

[sarsenyev]

Attachment: screenshot attachment

Description:
The Header text, "Voer simpincod..." is truncated 

Repro Steps:
1) Updated to Buri/Inari/Leo/Unagi Build ID: 20130621070212
2) In "Settings" change a language to "Nederlands"
3) Open the "Settings" from the home menu
4) Open the "Sim Security (Simbeveiliging)
5) Switch "Simpincode" to on position

Actual:
The "Header Title" is truncated

Expected:
The whole title fits on the screen

Environmental Variables
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/a34f6d62cb05
Gaia: cca61224e6df8e9f7e450d77cb6a8cf91029be64
Platform Version: 18.1

Notes:
Repro frequency: 100%
See the screeshot

Comment 1

[Sarah Parsons]

adding localizers to see if they can find a work around for this

Comment 2

[Tim Maks van den Broek [:mad_maks]]

I don't think we can translate this string different. a general UX solution is needed as l10n needs often more space as en_US!

Comment 3

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

Tim: have you read the UX l10n guidelines and tried to apply them? You can find them here: https://docs.google.com/document/d/16P56U6bSM1KVunkCG3WLmtH1cmhQf7YxT4mTPyWAnUw/edit

If following those guidelines you still can't find any solution, please let me know and we'll flag UX team. thanks

Comment 4

[Tim Maks van den Broek [:mad_maks]]

we can use the Verb omission here. 

Ton can you change 'voer simpincode in' to just simpincode ?

Comment 5

[Ton [:Tonnes]]

I don’t think omitting the verb is a good idea for several reasons. In this case, the (grey) top line or Header title ought to represent the action and thus have an infinitive form (infinitief /hele werkwoord) for nl, as in dialog headers, not imperative (gebiedende wijs). Hence we should have used “Simpincode invoeren” instead, but that’s even a bit longer. Apart from the fact omission is not a real option (rather a workaround - sorry), using “Simpincode” only would result in a screen showing the same words twice, which looks bad.

In general, I think strings like these should use some auto font size feature - either that, or developers define a maxchar value (or add +30% width by default).

It would make me happy if “Pincode invoeren” fits though, but am afraid not. Tim, could you check that locally? The Windows emulator is broken for a long time now (and can’t handle sim cards or reach their settings anyway ;-) ). Note this string likely resides in settings.properties - I’d consider the other one for startup OK as it is.

Comment 6

[Tim Maks van den Broek [:mad_maks]]

i disagree, i think omitting the verb is not a problem here. for a user it is clear what the meaning of the dialog is. But it is your call :-)

That said; in the latest version on the keon is this not a problem anymore, the header is not truncated. So marking this Resolved

Comment 7

[Ton [:Tonnes]]

(In reply to Tim Maks van den Broek [:mad_maks] from comment #6)
> i disagree, i think omitting the verb is not a problem here. for a user it
> is clear what the meaning of the dialog is. But it is your call :-)

Again, it would result in a screen with 2 similar strings, which is bad.

> That said; in the latest version on the keon is this not a problem anymore,
> the header is not truncated. So marking this Resolved

Nothing has changed on this - the bug is about the occurrence in Settings (grey bar), not the one at startup (orange bar), which does fit. Checking the latest build, the problem still occurs in Settings on a Keon.

Please let me know if you can emulate “Voer pincode in” or not, though it’ll likely fit, considering the string lengths for fr and de. If not, I’ll change both occurrences in a next edit and see what comes out. I can live with the imperative in these cases.

Comment 8

[Ton [:Tonnes]]

Changed both startup and settings occurrences to ‘Voer pincode in’ in today’s build, and both appearances display well now on a Keon. Not sure about this bug’s status.