Bug 1379576 - [ALL LANG] Unlocalized strings in gnome-contacts GUI.
Summary: [ALL LANG] Unlocalized strings in gnome-contacts GUI.
Keywords:
Status: CLOSED DUPLICATE of bug 1370033
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-contacts
Version: 7.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Alexander Larsson
QA Contact: Engineering Localization bugs mailing list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-27 07:35 UTC by Lijun Li
Modified: 2016-09-28 09:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-28 09:04:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
[ALL LANG] Unlocalized strings in gnome-contacts GUI. (16.67 KB, image/png)
2016-09-27 07:36 UTC, Lijun Li 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Lijun Li 2016-09-27 07:35:44 UTC 
Description of problem:
[ALL LANG] Unlocalized strings in gnome-contacts GUI.

Version-Release number of selected component (if applicable):
gnome-contacts-3.14.2-4.el7.x86_64.rpm   

How reproducible:
100%

Steps to Reproduce:
1. run gnome-contacts in target locales.


Actual results:
[ALL LANG] Unlocalized strings in gnome-contacts GUI.

Expected results:
All strings should be localized.

Additional info:
Please see the attached screen-shot.
Comment 1 Lijun Li 2016-09-27 07:36:32 UTC 
Created attachment 1205080 [details]
[ALL LANG] Unlocalized strings in gnome-contacts GUI.
Comment 2 sandeep shedmake 2016-09-28 09:04:09 UTC 
Form Comment 1,

The said string is already localized for all the required languages. Please, see bug #1370033 comment #6.

Also, gnome-contacts-3.14.2-4.el7 is 100% localized for all the required languages. Please, see bug #1370033 comment #4.


Thereby, marking this bug as duplicate of bug #1370033.

*** This bug has been marked as a duplicate of bug 1370033 ***
Note You need to log in before you can comment on or make changes to this bug.