116975 - solve the OE vs NS style export of .tab and .csv

Status: RESOLVED DUPLICATE of bug 180057

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

Description

[(not reading, please use [e-mail] instead)]

solve the OE vs NS style export of .tab and .csv

see nsAddressBook.cpp

when Outlook Express exports to .csv, the first line of the file is the column
descriptions.  I think we should do that too.  

otherwise, this data is just data, who knows what is what.

but we may have to fix the import code to automatically (or manually, with a
checkbox) skip the first card before we can do that.  
 
the problem is Netscape 4.x didn't this, so if we always skip the first card

we'll lose data when importing from 4.x.  for now, we do it how 4.x does it and
how the current import code expect it.
 
note, these are more fields that 4.x expects, so Mozilla -> 4.x will not work
right.  and if we add an extra row of column names, mozilla -> 6.x won't work
right either, but who really cares.

the critical case to get right is mozilla to mozilla, when people want to
transfer files between machines or between profiles.

Comment 1

[scottputterman]

What you're suggesting would make it so we'd never have to have that panel where
users match columns to data in the import wizard when transfering from one
version of our product to another.  Currently, if we import and export in the
same order, the user will see that panel but in theory should be able to skip
it.  Do we import and export columns in the same order?

Comment 2

[Mark Banner (:standard8)]

The import skip option has now been implemented via bug 180057, and the export
case will be fixed there as well. Therefore duping to that bug.

*** This bug has been marked as a duplicate of 180057 ***