Calendar:Import Export: Difference between revisions

(→‎CSV Field Mapping: Localized, case sensitive)
Line 11: Line 11:
Currently Calendar imports only "well formed" CSV files. The first line should contain the header names. Each header name and each data field has to be enclosed in double quotes. Data fields need to be separated with commas.  
Currently Calendar imports only "well formed" CSV files. The first line should contain the header names. Each header name and each data field has to be enclosed in double quotes. Data fields need to be separated with commas.  


Effective as of version 0.8: Mandatory are the two fields "Subject" and "Start Date" in their localized naming only. Recommended date format is <code>YYYY-MM-DD</code> with a '''four''' digit year at the beginning. Time format should be <code>HH:MM:SS</code> with 24-hour values. Calendar will also understand dates and times in the locale scheme of the operating system but data format must not change within a file. The universal indicators <code>AM</code>, <code>a.m.</code>, <code>PM</code> and <code>p.m.</code> are always recognized.  
Effective as of version 0.8: Mandatory are the two fields "Subject" and "Start Date" in their localized naming only.  


The header names are localized and follow Outlook. Column order is not important. If the two mandatory headers could not be recognized all files with 22 headers are assumed to have the column order of an [https://bugzilla.mozilla.org/attachment.cgi?id=302178 English CSV file] from Outlook .
The header names are localized and follow Outlook. Column order is not important. If the two mandatory headers could not be recognized all files with 22 headers are assumed to have the column order of an [https://bugzilla.mozilla.org/attachment.cgi?id=302178 English CSV file] from Outlook .
Event and task headers and Outlook field values are case sensitive and localized. Currently only events are imported and fields in parenthesis are skipped.


Sample CSV file
Sample CSV file
  "Subject","Start Date"
  "Subject","Start Date"
  "Berlin Wall came down","1989-11-09"
  "Berlin Wall came down","1989-11-09"
==== Development goals ====
Recommended date format is <code>YYYY-MM-DD</code> with a '''four''' digit year at the beginning. Time format should be <code>HH:MM:SS</code> with 24-hour values. Calendar will also understand dates and times in the locale scheme of the operating system but data format must not change within a file. The universal indicators <code>AM</code>, <code>a.m.</code>, <code>PM</code> and <code>p.m.</code> are always recognized.


==== CSV Field Mapping ====
==== CSV Field Mapping ====
Line 89: Line 98:
| 33 ||  || Schedule+ Priority || -  
| 33 ||  || Schedule+ Priority || -  
|}
|}
Event and task headers and Outlook field values are case sensitive and localized. Currently only events are imported and fields in parenthesis are skipped.


=== Hypertext Markup Language ===
=== Hypertext Markup Language ===
Confirmed users
59

edits