Calendar:Import Export: Difference between revisions
(→Comma Separated Value: Field Mapping) |
m (add sort key 'Import Export') |
||
| (4 intermediate revisions by one other user not shown) | |||
| Line 9: | Line 9: | ||
CSV import and export are optimized for collaboration with Outlook which can't handle the iCalendar format in the necessary extent. CSV offers an easy way to exchange data with spreadsheets or word processors too. | CSV import and export are optimized for collaboration with Outlook which can't handle the iCalendar format in the necessary extent. CSV offers an easy way to exchange data with spreadsheets or word processors too. | ||
Currently Calendar imports only "well formed" CSV files. The first line should contain the header names. Each header | Currently Calendar imports only "well formed" CSV files. The first line should contain the header names. Each header field and each data field has to be enclosed in double quotes. Fields need to be separated with commas. | ||
Mandatory are the two fields "Subject" and "Start Date" in their localized naming only (since 0.8). | |||
The header names are localized and follow Outlook. Column order is not important. If the two mandatory headers | The header names are localized and follow Outlook. Column order is not important. If the two mandatory headers were not recognized a fall back attempt is made for a file with 22 headers. It is assumed to have the column order of an [https://bugzilla.mozilla.org/attachment.cgi?id=302178 English CSV file] regardless of its headers. | ||
Sample CSV file | Event and task headers and Outlook boolean field values are case sensitive and localized. Currently only events are imported and fields in parenthesis are skipped. | ||
Sample CSV file: | |||
"Subject","Start Date" | "Subject","Start Date" | ||
"Berlin Wall came down","1989-11-09" | "Berlin Wall came down","1989-11-09" | ||
"Genscher at embassy in Prague","1989-09-30" | |||
Future development goals are in the [[Calendar:Feature_Implementations:ImportExport:CSV|Feature Implementations]] | |||
=== Hypertext Markup Language === | === Hypertext Markup Language === | ||
| Line 97: | Line 29: | ||
[[category:calendar]] | [[category:calendar|Import Export]] | ||
Latest revision as of 13:18, 24 August 2008
Calendar can import data in iCalendar (iCal) and Comma Separated Value (CSV) formats. Export is possible in these formats and is additionally in Hypertext Markup Language (HTML).
iCalendar
Recommended for data exchange. The format is standardized in RFC 2445 and widely used.
Comma Separated Value
CSV import and export are optimized for collaboration with Outlook which can't handle the iCalendar format in the necessary extent. CSV offers an easy way to exchange data with spreadsheets or word processors too.
Currently Calendar imports only "well formed" CSV files. The first line should contain the header names. Each header field and each data field has to be enclosed in double quotes. Fields need to be separated with commas.
Mandatory are the two fields "Subject" and "Start Date" in their localized naming only (since 0.8).
The header names are localized and follow Outlook. Column order is not important. If the two mandatory headers were not recognized a fall back attempt is made for a file with 22 headers. It is assumed to have the column order of an English CSV file regardless of its headers.
Event and task headers and Outlook boolean field values are case sensitive and localized. Currently only events are imported and fields in parenthesis are skipped.
Sample CSV file:
"Subject","Start Date" "Berlin Wall came down","1989-11-09" "Genscher at embassy in Prague","1989-09-30"
Future development goals are in the Feature Implementations
Hypertext Markup Language
HTML export gives an event list with the todo items on top of that list.