Created attachment 831950 [details] Contacts/SMS app translation comparison Device language is set to Serbian-Latin. When the user creates or modifies a contact, they can determine what type of phone the contact has(Mobile, Home, Work, Fax, etc). When the user is sending a message to a contact, the phone type is displayed in a retrieved search list. The translations for phone types are different in each app. Repro Steps: 1) Updated Buri to Build ID: 20131112004004 2) Set device language to Serbian-Latin. 3) Restart device. 4) Launch Kontakti(Contacts) app. 5) Add a new contact, and tap on 'MOBILNI' to view the different label names. 6) Add a new phone number of label type to the contact and save. 7) Launch Poruke(Messages) app. 8) In the recipient, type the first letter of the contact name. 9) Compare label names in the retrieved search list to the label names in the Contacts App. Actual: Translations are inconsistent between apps. Expected: Translations are consistent across all apps. Environmental Variables Device: Buri v1.2 COM RIL Build ID: 20131112004004 Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/566e850868c7 Gaia: 35b1c6b669b7bf08126df451221113e72642abca Platform Version: 26.0 RIL Version: 01.02.00.019.106 Firmware Version: US_20131104 Notes: Repro frequency: 100% See attached screenshot. Please observe the translation maifests for each app. SMS App Tranlations: --Observe lines 98-106 http://hg.mozilla.org/releases/gaia-l10n/v1_2/sr-Latn/file/8290efc33c2c/apps/sms/sms.properties Contacts App Translations: --Observe lines 59-67 http://hg.mozilla.org/releases/gaia-l10n/v1_2/sr-Latn/file/8290efc33c2c/apps/communications/contacts/contacts.properties
Summary: [B2G][1.2][l10n][SMS][Contacts]Serbian-Latin: Inconsistent translation SMS app and Contacts app. → [B2G][1.2][l10n][SMS][Contacts]Serbian-Latin: Inconsistent translation between SMS app and Contacts app.
Translations are consistent now, check patch from bug 965262
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.