Bug 529476 - import/export addressbook problem
Summary: import/export addressbook problem
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-17 11:26 UTC by Sergei LITVINENKO
Modified: 2018-04-11 10:26 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-10-17 12:07:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 522865 0 None None None Never

Description Sergei LITVINENKO 2009-10-17 11:26:14 UTC
Description of problem:
In locale ru_RU.UTF-8:
CSV file of address book from thunderbird can not be used for import into gmail.
CSV file of address book from gmail can not be used for import into thunderbird.

Version-Release number of selected component (if applicable):
thunderbird-3.0-2.7.b4.fc11.i586

How reproducible:
100%

Steps to Reproduce:
1. set locale ru_RU.UTF-8
2. run thunderbird
3. export address book from thunderbird and import it into gmail.
4. export address book from gmail and import it into thunderbird.
  
Actual results:
imported records have all important fields blank

Expected results:
All well known fields are filled.

Additional info:

for export/import thunderbird use localized names of fields (as is), but not well known standard.

Part of header of google CSV
---
[sergeil@homedesk download]$ head contacts.csv
First Name,Middle Name,Last Name,...
---

Part of header of thunderbird CSV
---
Имя,Фамилия,Отображаемое имя,Псевдоним,Адрес электронной ...
---

PS: KAddressBook can import CSV file from gmail correct.

Comment 1 Matěj Cepl 2009-10-17 12:07:39 UTC
We filed this bug in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=522865) and believe that it is more appropriate to let it be resolved upstream.

We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.

Thank you for the bug report.


Note You need to log in before you can comment on or make changes to this bug.