Description: The string "Data usage limit" is truncated in Cost Control. Repro Steps: 1) Updated Buri to Build ID: 20131025004000 2) Pull down the notification bar. 3) Tap "Next" on the welcome screen. 4) Tap "Next" on "Data Report". 5) Tap on the toggle "Data use alert". 6) Tap on "Let's go". Actual: The string "Data usage limit" is truncated. Expected: The string is not truncated. Environmental Variables Device: Buri v 1.2.0 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: Repro frequency: 100% See attached: screenshot

Can anyone from l10n community to attend this bug? Thank you.

I'm not sure if it's a good use of the l10n community to figure out what happened back in October last year. I'd much rather spend our time on current problems. In this particular case, without looking into the details, I'd not be surprised if this was a "button and title are the same string" problem, which we've fixed for 1.3 or .4 by separating the strings used for each. Thus, if this bug reproduces on master, we should have another look.

(In reply to Axel Hecht [:Pike] from comment #2) > In this particular case, without looking into the details, I'd not be > surprised if this was a "button and title are the same string" problem, > which we've fixed for 1.3 or .4 by separating the strings used for each. It looks like there is no ‘shared string’ issue here, but it is a classic matter of reserving too little space (16 characters?) for a word that’s likely to use more space for other locales than English. Hence, it relies on using smaller fonts (bug 908300) and/or shortening the English string and/or not using a string this large between the X and Done button. It might be possible to shorten this for 1.2 by using ‘data limit’ in Dutch only (instead of data usage limit), though I’m not fond of it.

I think I'd prefer a more context-sensitive title compared to a smaller font size. Damn Dutch for being so German about making every other thing just a single word ;-) Moving this bug over to the Dutch localization component, as it's apparently a current issue. Going forward, we discussed with UX to focus on strings that can grow by 50-100% compared to en-US, so the en-US string might either be shorter to begin with, or include a suggestion for a shorter phrase.

(In reply to Axel Hecht [:Pike] from comment #4) > I think I'd prefer a more context-sensitive title compared to a smaller font > size. Of course, but a string this big would simply need more room for most locales - mxr shows most have dropped either Usage or Limit here because it simply does not fit. And it’s not the fact Dutch or German doesn’t use spaces in nouns, it’s just the length, and developers not taking this into account, as I wrote elsewhere. Basically to break this habit, developers should use their own language (once) and substitute English strings when they’re done in order not to introduce this problem for localizers. > Going forward, we discussed with UX to focus on strings that can grow by > 50-100% compared to en-US, so the en-US string might either be shorter to > begin with, or include a suggestion for a shorter phrase. This is clearly one of them, and 1.3 * [English length] is a good rule of thumb allright. As for the suggestion: I’d be happy to see ‘Data limit’ here in English, as a) it’s the (provider’s) data limit that counts, b) we don’t set a real limit for usage and c) it matches best with the rest of the screen info.

Stil a issue on a flame, software 2.2 build 20140927040203 but now it is the togglebutton witch truncate the text

We've stopped shipping Firefox OS for phones. Thus resolving this as WONTFIX.