Open Bug 30621 Opened 25 years ago Updated 2 years ago

Address book XML table export

Categories

(MailNews Core :: Address Book, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: shwag, Unassigned)

References

Details

(Keywords: helpwanted)

Allow the address book to be exportable to a standard XML file that other
programs could parse.
Moving to helpwanted list.
Assignee: hangas → nobody
Keywords: helpwanted
Status: UNCONFIRMED → NEW
Ever confirmed: true
Moving to mozilla.org
Assignee: nobody → nobody
See also bug 52045
.
Assignee: nobody → racham
QA Contact: lchiang → nbaca
Blocks: 72400
Status: NEW → ASSIGNED
Target Milestone: --- → Future
What about exporting to a html file, similar to "print address book"?
That would be seen as a complement to this.
mass re-assign.
Assignee: racham → sspitzer
Status: ASSIGNED → NEW
Is there any difference between this rfe and bug 117231?
Is there any difference between this rfe and bug 117231?
*** Bug 117231 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Assignee: mail → nobody
Component: Address Book → MailNews: Address Book
Product: Mozilla Application Suite → Core
QA Contact: nbaca → addressbook
Target Milestone: Future → ---
As an aside, I'll note that XML and HTML, would lack the i18n problems of the current export formats:

* .csv and .tab have no way of declaring their encoding; one simply has to assume they're UTF8 (and to coerce one's tools into that assumption)

* .ldif (at least as Thunderbird implements it) encodes nonUSascii characters in some format that is not human readable, and is less than obvious how to decode.  For example, my pal Audrey's entry, "Audrey Tang (唐鳳)", ends up as:
dn:: Y249QXVkcmV5IFRhbmcgKOWUkOmzsyksbWFpbD1hdWRyZXl0QGF1ZHJleXQub3Jn
Compare this to a plain-USascii name which needs (and gets) no encoding:
dn: cn=Damian Conway,mail=damian@conway.org

XML and HTML would be quite helpful here, since both explicitly declare the document encoding; or at least could escape nonUSascii characters with the straightforward 〹 format.
Product: Core → MailNews Core

For XML, I don't think it's very supported to import/export XML. If anything, that format would be RDF (and FOAF). Exporting as JSON-LD would be more interesting (and that could in turn be converted to RDF if needed.)

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.