Closed Bug 101572 Opened 24 years ago Closed 24 years ago

Unable to import non-ASCII abook cards from 4.x

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 100208

People

(Reporter: ji, Assigned: chuang)

Details

(Keywords: intl)

Attachments

(2 files)

build: win32 09/24 0.9.4 build Importiing ABOOK from Communicator 4.x fails if the address book only contains non-ASCII cards. It's a regression from NS 6.1. Steps to reproduce: 1. Export ABOOK which contains non-ASCII cards from 4.x 2. Import the address book to the current branch build. The import wizard finishes w/o any errors, but when you open the imported ABOOK, it's empty, none of the cards gets imported. I'll attach the testing address books to this report.
Added intl, regression keyword. Nominating for nsbranch. QA contact to myself.
QA Contact: nbaca → ji
There was an addition to Import UI, now we have Import from Communicator 4.x. If you chose to import from 4.x it is not working, when chosing Text ( as we did before) the Import of non-ascii works correctly
actually i don't see AB with ascii only chars imported this way neither.
i don't think we can say that this is a regression: we were importing in .ldif, .tab and .csv format before, the na2 wasn't the one for import. adding Esther and Ninoschka to the cc list.
It also doesn't work if I import from pab.na2 file in 4.x profile folder. That's right, it's not a regression, the new feature in this release is broken.
Keywords: regression
Summary: [Regression] Unable to import non-ASCII abook cards from 4.x → Unable to import non-ASCII abook cards from 4.x
Marina, import ascii cards works for me if I clean up all the imported abook before bringing up import utility.
it looks like it is working only when you have PAB and AB. If you have more than two ABs the Import for nab file won't work , but regardless of ascii or non-ascii. I was able to import both.
Reproducible on Mac 09/25 branch build, but not on linux build.
It seems a dup of bug 100208. After closing 4.x abook, I'm able to import non-ASCII cards. *** This bug has been marked as a duplicate of 100208 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Marked it as verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: