aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/calcurse.1.txt8
-rw-r--r--doc/manual.txt28
-rw-r--r--doc/repeat.txt173
3 files changed, 162 insertions, 47 deletions
diff --git a/doc/calcurse.1.txt b/doc/calcurse.1.txt
index d8275d6..4605219 100644
--- a/doc/calcurse.1.txt
+++ b/doc/calcurse.1.txt
@@ -57,7 +57,7 @@ The first form shows how to invoke calcurse interactively; the remainder is
command line forms.
The second form shows queries (as opposed to interactive use). For
-convenience, common queries have abbriviated forms shown in the third line.
+convenience, common queries have abbreviated forms shown in the third line.
All queries may be combined with filter options as well as format options.
The fourth form shows operations on the calcurse data files, one for
@@ -91,7 +91,7 @@ and issue reminders; it stops automatically when the interactive mode is
reentered.
This man page mainly describes the command-line mode. The following two
-subsections contain some general desriptions of command line options and usage.
+subsections contain some general descriptions of command line options and usage.
Input and Output Date Format
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -190,7 +190,7 @@ displays those for yesterday and today. The first form is equivalent to *-Q
<<_format_options,Format Options>>.
*--export-uid*::
- When exporting items, add the hash of each item to the exported object as an
+ When exporting items, add the hash of each item to the exported object as a
UID property.
*--from* 'date'::
@@ -206,7 +206,7 @@ displays those for yesterday and today. The first form is equivalent to *-Q
*-g*, *--gc*::
Run the garbage collector for note files. The garbage collector removes
files from the +notes+ directory (see <<_files,FILES>>) that are no longer
- linked to an item. Ususally done automatically by setting the configuration
+ linked to an item. Usually done automatically by setting the configuration
option +general.autogc+ in the 'General Options' submenu in interactive mode.
*-G*, *--grep*::
diff --git a/doc/manual.txt b/doc/manual.txt
index cb59e8d..7eaa211 100644
--- a/doc/manual.txt
+++ b/doc/manual.txt
@@ -117,7 +117,7 @@ gettext library
`gettext` utilities. This means `calcurse` can produce multi-lingual messages
if compiled with native language support (i.e. *NLS*).
-However, *NLS* is optionnal and if you do not want to have support for
+However, *NLS* is optional and if you do not want to have support for
multi-lingual messages, you can disable this feature. This is done by giving
the `--disable-nls` option to `configure` (see section
<<install_process,Install process>>). To check if the `gettext` utilities are
@@ -143,7 +143,7 @@ Install process
First you need to gunzip and untar the source archive:
----
-$ tar zxvf calcurse-4.5.1.tar.gz
+$ tar zxvf calcurse-4.7.0.tar.gz
----
Once you meet the requirements and have extracted the archive, the install
@@ -303,7 +303,7 @@ can be specified using the `-c` flag.
information on format strings.
`--export-uid`::
- When exporting items, add the hash of each item to the exported object as an
+ When exporting items, add the hash of each item to the exported object as a
UID property.
`-F`, `--filter`::
@@ -596,7 +596,7 @@ Environment variable for i18n
<<install_requirements_gettext,gettext library>>). Thus, if you wish to have
messages displayed into your native language, first make sure it is available
by looking at the `po/LINGUAS` file. This file indicates the set of available
-languages by showing the two-letters corresponding code (for exemple, *fr*
+languages by showing the two-letters corresponding code (for example, *fr*
stands for french). If you do not find your language, it would be greatly
appreciated if you could help translating `calcurse` (see the <<contribute,How
to contribute?>> section).
@@ -607,7 +607,7 @@ If your language is available, run `calcurse` with the following command:
$ LC_ALL=fr_FR calcurse
----
-... where *fr_FR* is the locale name in this exemple, but should be replaced by
+... where *fr_FR* is the locale name in this example, but should be replaced by
the locale corresponding to the desired language.
You should also specify the charset to be used, because in some cases the
@@ -933,7 +933,7 @@ Here are the properties that are not implemented:
* negative time durations are not taken into account (item is skipped)
-* some recurence frequences are not recognize: "SECONDLY" / "MINUTELY" /
+* some recurrence frequencies are not recognize: "SECONDLY" / "MINUTELY" /
"HOURLY"
* some recurrence keywords are not recognized (all those starting with `BY`):
@@ -1096,7 +1096,7 @@ applied. It is possible to keep the terminal's default colors by selecting the
corresponding choice in the list.
The chosen color theme will then be applied to the panel borders, to the
-titles, to the keystrokes, and to general informations displayed inside status
+titles, to the keystrokes, and to general information displayed inside status
bar. A black and white theme is also available, in order to support non-color
terminals.
@@ -1241,7 +1241,7 @@ native language, it would be appreciated if you could help translating it.
To do so, just copy one of the existing manual file to `manual_XX.html`, where
*XX* identifies your language. Then translate this newly created file and send
-it to the author (see <<bugs,Reporting bugs and feeback>>), so that it can be
+it to the author (see <<bugs,Reporting bugs and feedback>>), so that it can be
included in the next `calcurse` release.
calcurse i18n
@@ -1251,10 +1251,10 @@ As already mentioned, `gettext` utilities are used by `calcurse` to produce
multi-lingual messages. We are currently using
http://www.transifex.net/[Transifex] to manage those translations.
-This section provides informations about how to translate those messages into
+This section provides information about how to translate those messages into
your native language. However, this howto is deliberately incomplete, focusing
on working with `gettext` for `calcurse` specifically. For more comprehensive
-informations or to grasp the Big Picture of Native Language Support, you should
+information or to grasp the Big Picture of Native Language Support, you should
refer to the `GNU gettext` manual at:
http://www.gnu.org/software/gettext/manual/
@@ -1379,19 +1379,19 @@ msgid ""
You should also fill in the Last-Translator field, so that potential
contributors can contact you if they want to join you in the translation team,
or have remarks/typo fixes to give about the translations. You can either just
-give your name/nick, or add an email address, for exemple:
+give your name/nick, or add an email address, for example:
+
----
"Last-Translator: Frederic Culot <frederic@culot.org>\n"
----
*Comments*::
- Adding comments (lines begining with the `#` character) can be a good way to
+ Adding comments (lines beginning with the `#` character) can be a good way to
point out problems or translation difficulties to proofreaders or other
members of your team.
*Strings size*::
- `calcurse` is a curses/console program, thus it can be heavily dependant on
+ `calcurse` is a curses/console program, thus it can be heavily dependent on
the terminal size (number of columns). You should think about this when
translating. Often, a string must fit into a single line (standard length is
80 characters). Don't translate blindly, try to look where your string will
@@ -1519,7 +1519,7 @@ Thanks
Its time now to thank other people without whom this program would not exist!
So here is a list of contributing persons I would like to thank:
-* Alex for its patches, help and advices with `C` programming
+* Alex for its patches, help and advice with `C` programming
* Gwen for testing and general discussions about how to improve `calcurse`
diff --git a/doc/repeat.txt b/doc/repeat.txt
index 16a71da..584a442 100644
--- a/doc/repeat.txt
+++ b/doc/repeat.txt
@@ -4,32 +4,147 @@ Repeat
Repeat an event or an appointment.
You must first select the item to be repeated by moving inside the appointment
-panel. Then running the repeat command will lead you to a set of three
-questions, with which you will be able to specify the repetition
-characteristics:
-
- o type: you can choose between a daily, weekly, monthly or
- yearly repetition by pressing 'D', 'W', 'M' or 'Y'
- respectively.
-
- o frequency: this indicates how often the item shall be repeated.
- For example, if you want to remember an anniversary,
- choose a 'yearly' repetition with a frequency of '1',
- which means it must be repeated every year. Another
- example: if you go to the restaurant every two days,
- choose a 'daily' repetition with a frequency of '2'.
-
- o ending date: this specifies when to stop repeating the selected
- event or appointment. To indicate an endless
- repetition, enter '0' and the item will be repeated
- forever.
-
-Notes
------
-
-* Repeated items are marked with an '*' inside the appointment panel, to be
- easily recognizable from non-repeated ones.
-
-* The 'Repeat' and 'Delete' command can be mixed to create complicated
- configurations, as it is possible to delete only one occurrence of a repeated
- item.
+panel. Then invoke the repeat command, and you will be asked you to select a
+simple or advanced repetition. A simple repetition will lead you to a set of
+three questions with which you specify the basic repetition characteristics:
+
+ o type: choose between a daily, weekly, monthly or yearly base period
+
+ o frequency: choose the interval between base periods. '1' means every day
+ (week, month or year), '2' means every other day (week, ...).
+ For example, if you want to remember an anniversary, choose a
+ yearly type with a frequency of 1, which means it will be
+ repeated every year. Another example: if you go to a restaurant
+ every second day, choose a daily type with a frequency of 2.
+
+ o until date: specifies a day after which the repetitions do not occur. To
+ indicate an endless repetition, enter 0 (zero) or RETURN, and
+ the item will be repeated forever. To obtain a specific
+ number of repetitions (a repeat count) enter '#' followed by
+ a number (e.g. #10); it will be turned into the appropriate
+ until date.
+
+For an advanced repetition you may, in addition to the basic characteristics,
+specify three lists of either days of the week, months of the year or days of
+the month. The three lists modify the simple repetition in some way by either
+limiting or expanding the basic pattern.
+
+ o Weekdays: abbreviated names of days of the week (as they appear above
+ the calendar). For monthly or yearly repetitions the name may
+ have a numerical prefix (1, 2, ... or -1, -2, ...) to specify
+ a particular weekday of the month or year, counted from either
+ the start or the end of the month or year.
+
+ o Months: the numerical name of a month (1, 2,..., 12).
+
+ o Monthdays: the numerical name of a day of the month (1, 2,..., 31) or the
+ opposites (-1, -2,..., -31) which count from the end of the
+ month.
+
+For each list you may enter one or several values separated by spaces. The
+prompt for the list gives a hint as to the format. If you enter '?' only, you
+get very terse, context dependent information as to the effect on the
+repetition. Note that both format and effect depend on the basic type. The
+combined effect on the basic type of the listed days and months is derived
+from the iCalendar specification (RFC5545).
+
+Briefly, a weekday or monthday limits the repetitions of type daily, but
+expands those of type weekly, monthly and yearly. For example, with 'Weekdays'
+set to 'Sat Sun' a daily type (with frequency one) is only repeated on
+Saturdays and Sundays (two instead of seven repetitions per week), while a
+weekly type is also repeated on the extra day (two instead of one repetition
+per week).
+
+Similarly, a month limits the repetitions of type daily, weekly and monthly,
+but expands those of type yearly. For example, with 'Months' set to '3 10', a
+weekly type is only repeated in March and October, while a yearly type is also
+repeated in the extra month (two instead of one yearly repetition).
+
+Mnemonic. If the list type (day or month) is shorter than the basic type (day,
+week, month, year), it expands the repetitions of the basic type, if not, it
+limits them.
+
+There are a some important exceptions, though, for 'Weekdays':
+
+ o For a monthly type, the expanded repetitions are special: a weekday with a
+ prefix expands to that particular weekday of the month ('3Mon' = third
+ Monday), while a weekday without prefix expands to all weekdays of the
+ month ('Wed' = all Wednesdays). Furthermore, repetitions are limited if
+ 'Monthdays' is also set (for example, if 'Weekdays' is set to 'Fri' with
+ 'Monthdays' set to '13', the monthly repetition occurs only on Friday 13th).
+
+ o For a yearly type, the expanded repetitions are special and depend also on
+ the setting of 'Months'. A weekday with a prefix expands to that particular
+ weekday of the year ('-1Sun' = last Sunday of the year), or, if 'Months' is
+ also set, to that weekday of the listed months. A weekday without prefix
+ expands to all weekdays ('Thu' = all Thursdays in either the year or listed
+ months). Furthermore, repetitions are limited if 'Monthdays' is also set
+ as for monthly type.
+
+When you are finished setting up the repeating item, you may test it
+interactively with the 'next' command, a subcommand of the generic command
+(default ': n'). Invoked with a repeating item selected in the appointments
+panel, it will go to the next repetition. By doing this repeatedly, you may
+step through the repetitions one by one.
+
+If you edit an item that is already repeating, you will be led through all six
+characteristics and can modify any of them.
+
+Here are some typical examples. It is assumed that you have invoked the repeat
+command on what will become the first repetition and have selected an advanced
+repetition, that your date input format is dd/mm/yyyy, and that your language
+is English.
+
+ o an event that occurs every Tuesday and Thursday forever
+ type: weekly
+ frequency: 1
+ until: 0
+ weekdays: Tue Thu
+ months: (empty)
+ monthdays: (not possible)
+
+ o an event that occurs on workdays except in July forever (holidays are not
+ taken into account)
+ type: daily
+ frequency: 1
+ until: 0
+ weekdays: Mon Tue Wed Thu Fri
+ months: 1 2 3 4 5 6 8 9 10 11 12
+ monthdays: (empty)
+
+ o an appointment that occurs on the first and last Monday of the month forever
+ type: monthly
+ frequency: 1
+ until: 0
+ weekdays: 1Mon -1Mon
+ months: (empty)
+ monthdays: (empty)
+
+ o an appointment that occurs on all Wednesdays in June and July until the
+ end of June 2022
+ type: monthly
+ frequency: 1
+ until: 30/6/2022
+ weekdays: Wed
+ months: 6 7
+ monthdays: (empty)
+
+ o an event that occurs when Daylight Saving Time begins in the EU (last
+ Sunday in March)
+ type: yearly
+ frequency: 1
+ until: 0
+ weekdays: -1Sun
+ months: 3
+ monthdays: (empty)
+
+ o an event that occurs on the penultimate day of February forever
+ type: monthly
+ frequency: 1
+ until: 0
+ weekdays: (empty)
+ months: 2
+ monthdays: -2
+
+For an example that is not possible to specify consider an event that occurs
+on the last workday of each month.