877046 - [Buri][IOT][TRANSLATION] incorrect translation when having duplicate contact on phone and try to send SMS

Status: RESOLVED FIXED

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

Description

[sync-1]

+++ This bug was initially created as a clone of Bug #460175 +++
 
 AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.111
 Firefox os  v1.0.1
 Mozilla build ID:20130518070208
 
 DEFECT DESCRIPTION:
 
 Incorrect translation when having a duplicate contact and try to send sms to it
 
  REPRODUCING PROCEDURES:
 
  1. Turn the DuT on with a SIM card.
     2. Select English as default language.
     3. Add two contacts in DUT native addressbook with same MSISDN (same number, same identifier) called, for example: ContactX.
     4. Exchange calls and messages with this MSISDN.
     5. Check Call History and Messages Thread.
     6. Select Spanish as default language.    
     7. Check Call History and Messages Thread.
 
  EXPECTED BEHAVIOUR:
 
 I guess in English shall be “ContactX or 1 other” in both cases; in Spanish “ContactX u otro”
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:high
 
  REPRODUCING RATE: 100 %
 
  For FT PR, Please list reference mobile's behavior:
 
 ++++++++++ end of initial bug #460175 description ++++++++++
 
 
 
 CONTACT INFO (Name,Phone number):
 
  DEFECT DESCRIPTION:
 
  REPRODUCING PROCEDURES:
 
  EXPECTED BEHAVIOUR:
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[Amelie Kong]

Checked the current behavior:

It will display "ContactX or 1 other" for all languages.
No translation for this string "or 1 other"

Comment 2

[Mingming ZHAO]

Attachment: call log show

Comment 3

[Mingming ZHAO]

Attachment: SMS show

Comment 4

[Daniel Coloma:dcoloma]

This is not a blocker for TEF for 1.0.1

Comment 5

[Joe Cheng [:jcheng] (please needinfo)]

triage with tef: per comment 4, not block for v1.0.1, leo?

Comment 6

[sync-1]

Comment from Mozilla:This is not a blocker for TEF for 1.0.1

Comment 7

[bhavana bajaj [:bajaj]]

 [e-mail] :

As per your your screenshots and description they don't seem to go along with one another .The problem as we understand is there is no translation for string "or 1 other" but the screenshot's do show the translation.Can you please clarify ?

Comment 8

[sync-1]

Comment from Mozilla: [e-mail] :
 
 As per your your screenshots and description they don't seem to go along with one another .The problem as we understand is there is no translation for string "or 1 other" but the screenshot's do show the translation.Can you please clarify ?

Comment 9

[Mingming ZHAO]

Dears,

I think the call log and SMS shold keep the same label, for example in English shall be “ContactX or 1 other” in both cases; in Spanish “ContactX u otro”.

Comment 10

[Etienne Segonzac (:etienne)]

I'm not actively working on this, up for grab.

Comment 11

[Alex Keybl [:akeybl]]

Over to David to reassign. Since this is late-l10n, throwing into the QE3 milestone to ensure we resolve with time to localize.

Comment 12

[Fabien Cazenave [:kaze]]

Note: in SMS, “ContactX or 1 other” is now displayed as “ContactX (+1)”, see bug 873477.
However, this is not consistent with the Call Log, so let’s apply the same logic to the Dialer.

Comment 13

[Fabien Cazenave [:kaze]]

In the Dialer, the “ContactX or 1 other” string has been removed from the JS code by bug 865079 (but left in the locale data), and this decision has been validated by UX.

I think we should just:
 • remove the now unused strings in the dialer locales
 • uplift the patches for bugs 865079 and 873477 to v1-train

Comment 14

[Fabien Cazenave [:kaze]]

v1-train:
https://github.com/mozilla-b2g/gaia/commit/31ff278
https://github.com/mozilla-b2g/gaia/commit/46a3878
https://github.com/mozilla-b2g/gaia/commit/e6666a2

Comment 15

[Fabien Cazenave [:kaze]]

jhford: commit e6666a2 hasn’t been pushed to v1.1.0hd

Comment 16

[John Ford [:jhford] CET/CEST Berlin Time]

(In reply to Fabien Cazenave [:kaze] from comment #15)
> jhford: commit e6666a2 hasn’t been pushed to v1.1.0hd

$ git branch --contains e6666a2
  v1-train
* v1.1.0hd

Setting status flags for v1-train and v1.1.0hd