summaryrefslogtreecommitdiff
path: root/doc/import.txt
diff options
context:
space:
mode:
authorLukas Fleischer <calcurse@cryptocrack.de>2013-07-22 16:29:02 +0200
committerLukas Fleischer <calcurse@cryptocrack.de>2013-07-22 16:29:02 +0200
commit5aa2f0de3caa29c5e9dcef1351dc8b307aea5d1d (patch)
treec92caff0ef406d534e78f807a3fdeb1b3da24b89 /doc/import.txt
parent3f621c69fc42d0404017c1db53cd27d09c02da22 (diff)
downloadcalcurse-5aa2f0de3caa29c5e9dcef1351dc8b307aea5d1d.zip
doc/: Formatting fixes
* Use an AsciiDoc-compatible layout. * Use a maximum line width of 79 characters everywhere. Signed-off-by: Lukas Fleischer <calcurse@cryptocrack.de>
Diffstat (limited to 'doc/import.txt')
-rw-r--r--doc/import.txt27
1 files changed, 14 insertions, 13 deletions
diff --git a/doc/import.txt b/doc/import.txt
index 65d963e..9f64348 100644
--- a/doc/import.txt
+++ b/doc/import.txt
@@ -2,18 +2,19 @@ Import
======
Import data from an icalendar file.
-You will be asked to enter the file name from which to load ical
-items. At the end of the import process, and if the general option
-'system_dialogs' is set to 'yes', a report indicating how many items
-were imported is shown.
+
+You will be asked to enter the file name from which to load ical items. At the
+end of the import process, and if the general option 'system_dialogs' is set to
+'yes', a report indicating how many items were imported is shown.
+
This report contains the total number of lines read, the number of
-appointments, events and todo items which were successfully imported,
-together with the number of items for which problems occured and that
-were skipped, if any.
+appointments, events and todo items which were successfully imported, together
+with the number of items for which problems occured and that were skipped, if
+any.
+
+If one or more items could not be imported, one has the possibility to read the
+import process report in order to identify which problems occured.
-If one or more items could not be imported, one has the possibility to
-read the import process report in order to identify which problems
-occured.
-In this report is shown one item per line, with the line in the input
-stream at which this item begins, together with the description of why
-the item could not be imported.
+In this report is shown one item per line, with the line in the input stream at
+which this item begins, together with the description of why the item could not
+be imported.