Closed Bug 931646 Opened 11 years ago Closed 10 years ago

[B2G][1.2][l10n][Settings]German: Add more keyboards appear truncated under keyboard settings.

Categories

(Mozilla Localizations :: de / German, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ahubenya, Unassigned)

References

Details

(Keywords: l12y, Whiteboard: LocRun1.2)

Attachments

(1 file)

Attached image Screenshot
Description:
The word “number” is not translated in the Build-in Keyboard option in the Settings – Keyboard.

Repro Steps:
1) Updated Buri to BuildID: 20131025004000
2) Set device language to German/Deutsch
3) Select ‘Settings’ application 
4) Select ‘Keyboards’
5) Select ‘Selected keyboards’
6) Select ‘Add more keyboards’

Actual:
"Add more keyboards" header appears truncated.

Expected:
"Add more keyboards" header is not truncated.
 

Environmental Variables
Device: Buri v 1.2 COM RIL
Build ID: 20131025004000
Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/5eabd267ef04
Gaia: 606517ceafe0950c2b89822d5f13353743334f2c
Platform Version: 26.0a2
RIL Version: 01.02.00.019.082 

Notes:
See attached: screenshot
Asking for some UX help as this string not understandable anymore.
THanks!
Flags: needinfo?(firefoxos-ux-bugzilla)
Delphine, are you asking for a string change or for UX/visual adjustment?
Flags: needinfo?(lebedel.delphine)
Flagging Sebastian to see if he can maybe just put "More Keyboards" instead of "Add more keyboards", and see what his general input is about this
Flags: needinfo?(lebedel.delphine) → needinfo?(archaeopteryx)
The string "Add more keyboards" is shared between the button and the pane/view it launches where it is used as header. Because it's not truncated on the button, it's okay to be truncated in the opening view as long as this is the only way to launch that dialog.

An alternative would be to change it to "Aktivierte Tastaturen" ("Activated keyboards"), but dropping the verb is likely against UX guidelines because it doesn't assure that people will understand that the button is a button.

The general solution would be to wrap long texts in headers and in normal text to two lines if necessary (similar to bug 892700).

Wontfixing it, feel free to reopen if you have other opinions/more information.
Flags: needinfo?(archaeopteryx)
I think the future solution for those strings might be to switch to L20n and put in some kind of context variable that allows us to switch to different strings for headers and buttons.
Flags: needinfo?(firefoxos-ux-bugzilla)
The currently used strings "Aktivierte Tastaturen" und "Tastaturen auswählen" aren't cropped.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: