931158 - [B2G][1.2][l10n][Gallery] Nederlands: The string Set as wallpaper is truncated

Status: RESOLVED WONTFIX

(Mozilla Localizations :: nl / Dutch, defect)

Description

[KTucker [:KTucker][Inactive 3/4/2016]]

Attachment: 2013-10-25-12-09-51.png

Description:
"Set as wallpaper" is truncated in the button when a picture is selected to add as a wallpaper.

Repro Steps:
1)  Updated Buri to Build ID: 20131025004000
2)  Tap on "Gallery".
3)  Tap on a picture.
4)  Tap on the "Share" icon.
5)  Tap on "Wallpaper".

Actual:
The string "Set as wallpaper" 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

Comment 1

[Ton [:Tonnes]]

Can’t find a way of shortening this. As this is a developer's issue (…assuming 'set as' is only 6 characters wide for any language…), it needs a UX solution, e.g. by moving the button divider to the left (dynamically), or just creating two buttons on top of instead of next to each other, like elsewhere.

Comment 2

[Tim Maks van den Broek [:mad_maks]]

just a thought. as you are allready in the background setting is it not clear enough to use only 'instellen' and then we open a bug to change it in en-us also.

Comment 3

[Tim Maks van den Broek [:mad_maks]]

Fixed, verified on a flame, software 2.2 build 20140927040203

Comment 4

[Ton [:Tonnes]]

Please don't close Gaia bugs when
- the software version you are using is different from the version the bug was reported for
- your device is different than the one the bug was reported for, as well as the behaviour may or may not occur on various devices
- a string was changed, but the original problem persists (hence it is a UX issue, even when the bug wasn't set as such (yet))

I'd also appreciate it if you talk Gaia string issues over on irc if possible.

In this case, there is no fix involved and the problem is still valid on 1.2 and probably on any device.

Comment 5

[Francesco Lodolo [:flod]]

(In reply to Ton from comment #4)
> - the software version you are using is different from the version the bug
> was reported for
> - your device is different than the one the bug was reported for, as well as
> the behaviour may or may not occur on various devices

I haven't tested it with Dutch, but this should be fixed on 2.1 and 2.2 (see bug 841366).

If we don't close bugs because they're still valid on old versions (e.g. 1.2), we're never going to close them and the number of open bugs won't reflect the actual status of the localization.

Comment 6

[Ton [:Tonnes]]

(In reply to Francesco Lodolo [:flod] from comment #5)

> If we don't close bugs because they're still valid on old versions (e.g.
> 1.2), we're never going to close them and the number of open bugs won't
> reflect the actual status of the localization.

I know, and it would make it easier to close bugs allright. Yet I’d expect to see changed afected version info for the bug though, or comments like "closing (wfm) as this version is obsolete" in order to keep clear what versions were / are still affected.

Comment 7

[Tim Maks van den Broek [:mad_maks]]

(In reply to Francesco Lodolo [:flod] from comment #5)

> If we don't close bugs because they're still valid on old versions (e.g.
> 1.2), we're never going to close them and the number of open bugs won't
> reflect the actual status of the localization.

Agree.

I wonder, on which version is there still active ux development ( I tought the ux changes are closed in 1.2 and 1.3)? Because having ux bugs in the dutch component on versions who are not developed anymore is usesless.

Comment 8

[Tim Maks van den Broek [:mad_maks]]

open or close?

Comment 9

[Ton [:Tonnes]]

(In reply to Tim Maks van den Broek [:mad_maks] from comment #7)
> 
> I wonder, on which version is there still active ux development ( I tought
> the ux changes are closed in 1.2 and 1.3)? Because having ux bugs in the
> dutch component on versions who are not developed anymore is usesless.

Same question here. As this affects v1.2-2.0 and was solved in 2.1+, we could fix it for 2.0, but does it make sense to do so for 1.4 and below?

Comment 10

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

Just my 2 cents: there are quite a few examples recently where partners are still shipping on 1.3 or 1.4, for example. So I would say it makes sense to correct major issues in past versions

Comment 11

[Ton [:Tonnes]]

Thanks. Any idea if they'd be implemented for end user builds though, i.o.w. do all of them get updates, does it depend on manufacturers/partners etc.?

Comment 12

[BMO Automation]

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