Calendar:Import Export: Difference between revisions

no edit summary
(New page: <small><< Back to Calendar Home Page</small> Calendar can import data in iCalendar (iCal) and Comma Separated Value (CSV) formats. Exporting is additionally possi...)
 
No edit summary
Line 1: Line 1:
<small>[[Calendar:Home_Page |<< Back to  Calendar Home Page]]</small>
<small>[[Calendar:Home_Page |<< Back to  Calendar Home Page]]</small>


Calendar can import data in iCalendar (iCal) and Comma Separated Value (CSV) formats. Exporting is additionally possible in Hypertext Markup Language (HTML).  
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 ===
=== iCalendar ===
Line 11: Line 11:
Currently Calendar needs "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 needs "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" 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.
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.
The universal indicators AM, a.m., PM and p.m are always recognized.
 
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 .


Sample CSV file
Sample CSV file
<code>
"Subject","Start Date"
"Subject","Start Date"
"Berlin Wall came down","1989-11-09"
"Berlin Wall came down","1989-11-09"
 
</code>
 




=== Hypertext Markup Language ===
=== Hypertext Markup Language ===
HTML export gives an event list with the todo items on top of that list.
HTML export gives an event list with the todo items on top of that list.






[[category:calendar]]
[[category:calendar]]
Confirmed users
59

edits