Steps to reproduce: - give a non-ascii name to AB; Import a file with non-ascii name through the Import utility(File|Import); //note: there is no data imported , all cards are blank
I don't have this problem when I import an address book with Ja filename. All the cards in it (including non-ASCII cards) are displayed okay after importing.
Marina, please specify the actual name of the addressbook you tested, thanks.
i need to investigate this one , because it looks like it's not an i18n problem but maybe an important of the renamed file.
i was trying to re-import by renaming a mab file (because i don't see any way to Export file from Nscp6) and this doesn't work. How are we saving an AB file in nscp6?
Reassign to chuang.
You can't rename a .mab file into a .ldif file and try to import it. The data format is totally different. You can rename a .ldif into a different name (a.ldif to b.ldif) and import the ldif file.
One more thing, we don't have Export in 6.0 yet. We can't save the address book into .ldif or .tab file.
yes, .ldif is fine, it was mab that after renaming has a blank data, so it is as designed??
changed a component
.mab file is our database file for address book as .na2, .nab file in 4.x. Normal user should not rename or do something about it. This is not a bug or design issue, it's the same as we don't rename .na2 file and try to import it in 4.x. Lack of Export is a missing feature, you can file a bug for it.
so i invalid this one and open another one for feature request?
Either way is fine with me, change the summary or create a new bug. QA can decide which way is better.
changed the summary per our discussion to reflect the actual problem with saving AB file
*** This bug has been marked as a duplicate of 52045 ***
Verified as a duplicate of Bug 52045.