932140 - [B2G][1.2][l10n][Settings] Romanian: "Fixed dialing numbers" is truncated (header and setting)

Status: RESOLVED WONTFIX

(Mozilla Localizations :: ro / Romanian, defect)

Description

[Théo Chevalier]

Attachment: Screenshot

In Romanian, there are truncations in the FDN setting.
The header displays "Numere de apelare fi…" while the setting displays "Numere de apelare …"

STR:
1. Open Settings
2. Go to "Call settings"
3. Go to "Fixed dialing numbers"


Actual Result:
The header is truncated.
The string at the left of the switch is truncated.

Expected result:
Both strings fits into the screen


Device: Keon 1.2
BuildID: 20131026225502

Comment 1

[Cristian Silaghi]

I don't know how can I shorten this. I think we need a general solution from UX team, because the font is too big and some elements from the page can be moved and/or decreased slightly. :) The main problem is that many strings are nearly fitted into the screen, but as well as in this case, the header should be "Numere de apelare fixă", so just 2 words: "...xă".

Best Regards,
Cristian Silaghi

Comment 2

[Théo Chevalier]

Attachment: Hack

Hi Cristian,

I made a little patch (it's more a hack than a real solution, thought) do you think it would be acceptable for Romanian?

The patch consists in replacing current 'classic' spaces with U+202F character (NARROW NO-BREAK SPACE), reducing the space between words to make the title fit.

For the second truncation, UX feedback is indeed needed, especially because there is already a truncation in en-US.

@fxos-ux, Is there an opened bug for the en-US truncation in FDN setting?

Comment 3

[Théo Chevalier]

Attachment: Screenshot with patch applied

Comment 4

[Raul Nicolae Malea]

After patch, header are OK but FDN setting are still truncated. However, perhaps real solution are reducing font dimension, e.g. 7px instead of 10 px.

Comment 5

[Cristian Silaghi]

Hi Théo,

Yes, with your patch now it is acceptable. :) What about the other string?

Best Regards,
Cristian Silaghi

Comment 6

[Théo Chevalier]

For the setting, I think we should wait for UX point of view, to see if they have an idea and/or to see if the en-US truncation is being tracked somewhere. If so, we would just have to wait for it to be resolved.

My personal point of view is that since the header is now fully readable for the user, the setting name being truncated becomes an issue less important: they understand that the setting is the same sentence as in the title. But again, let's UX answer.

Comment 7

[Stephany Wilkes]

Thanks, Theo. I am flagging Eric to advise on this one. Eric does have a larger solution for this sort of thing, but it may not be able to make it into the BB (for headers) immediately, so he'll be able to say if we need an ad hoc solution for this one or not. Cheers!

Comment 8

[Eric Pang [:epang] UX]

Hi Theo, I'm marking this as dependent on bug 908309.  It's a bug that I opened a while back that proposes a second line within setting list items when truncation exist. Thanks!

Comment 9

[Cristian Silaghi]

Hi Théo,

Why I get on the email "[Bugzilla] Your Outstanding Requests (1 feedback)". It's annoying.

I already asked here. Your hack is great. So I hope this change is merged.

Best Regards,
Cristian Silaghi

Comment 10

[Cristian Silaghi]

answered*, not asked.
Sorry about this

Comment 11

[Théo Chevalier]

(In reply to Cristian Silaghi from comment #9)
> Hi Théo,
> 
> Why I get on the email "[Bugzilla] Your Outstanding Requests (1 feedback)".
> It's annoying.

Hi, you have to answer the request on the patch itself an turn the "fedback?" into "feedback+" or "feedback-", until that Bugzilla will keep reminding you about it each week. You can always clear those requests on attachments by clicking on "details". Clearing this one for you right now. 

> 
> I already asked here. Your hack is great. So I hope this change is merged.

Unfortunately no, as a ro localizer you had to merge this change into the Romanian gaia l10n repository for 1.2 (the same way you localize all the other strings). Sorry if it wasn't clear enough.
The good news is that 1.3 is not affected by this bug (just checked), so this patch is now useless and we can safely close this bug. No additional action is required from you.
Sorry for the inconvenience.

> 
> Best Regards,
> Cristian Silaghi