aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--ChangeLog10
-rw-r--r--Makefile.am13
-rw-r--r--configure.ac31
-rw-r--r--doc/Makefile.am18
-rw-r--r--doc/manual.css355
-rw-r--r--doc/manual.txt1112
-rw-r--r--doc/manual_de.html1327
-rw-r--r--doc/manual_en.html1331
-rw-r--r--doc/manual_es.html1347
-rw-r--r--doc/manual_fr.html1505
-rw-r--r--doc/manual_it.html1587
-rw-r--r--doc/manual_nl.html1350
12 files changed, 1172 insertions, 8814 deletions
diff --git a/ChangeLog b/ChangeLog
index ccadb78..2c52d77 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,13 @@
+2011-02-12 Lukas Fleischer <calcurse@cryptocrack.de>
+
+ * doc/manual_en.txt: Convert English manual into AsciiDoc format.
+
+ * doc/*: Remove old documentation (switching to AsciiDoc).
+
+ * Makefile.am
+ * configure.ac
+ * doc/Makefile.am: Integrate AsciiDoc into the build process.
+
2011-01-14 Lukas Fleischer <calcurse@cryptocrack.de>
* src/help.c: Avoid a segfault when resizing the help window
diff --git a/Makefile.am b/Makefile.am
index eca73b2..dfd1bc5 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -1,21 +1,14 @@
-# $calcurse: Makefile.am,v 1.7 2010/03/22 12:40:16 culot Exp $
+# $calcurse: Makefile.am,v 1.8 2011/02/24 11:36:50 fleischer Exp $
AUTOMAKE_OPTIONS= foreign
ACLOCAL_AMFLAGS = -I m4
-SUBDIRS = po src
+SUBDIRS = doc po src
man_MANS= src/calcurse.1
EXTRA_DIST = \
$(man_MANS) \
INSTALL \
- ABOUT-NLS \
- doc/manual.css \
- doc/manual_en.html \
- doc/manual_fr.html \
- doc/manual_de.html \
- doc/manual_es.html \
- doc/manual_nl.html \
- doc/manual_it.html
+ ABOUT-NLS
diff --git a/configure.ac b/configure.ac
index 9be24fc..246f3d6 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1,4 +1,4 @@
-# $calcurse: configure.ac,v 1.36 2010/05/26 17:59:57 culot Exp $
+# $calcurse: configure.ac,v 1.37 2011/02/24 11:36:50 fleischer Exp $
#-------------------------------------------------------------------------------
# Init
@@ -68,6 +68,33 @@ AC_CHECK_HEADERS([math.h], [
AC_MSG_ERROR(The math library is required in order to build calcurse!))
], AC_MSG_ERROR(The math header is required in order to build calcurse!))
#-------------------------------------------------------------------------------
+# Check whether to build documentation
+#-------------------------------------------------------------------------------
+AC_ARG_WITH(asciidoc,
+ AS_HELP_STRING([--with-asciidoc],
+ [Use asciidoc to regenerate documentation.]),
+ [use_asciidoc=$withval],
+ [use_asciidoc="auto"])
+if test x"$use_asciidoc" = x"auto"; then
+ AC_PATH_PROG([ASCIIDOC], [asciidoc])
+ if test -z "$ASCIIDOC"; then
+ have_asciidoc=no
+ AC_MSG_WARN([AsciiDoc not found - documentation will be skipped!])
+ else
+ have_asciidoc=yes
+ fi
+elif test x"$use_asciidoc" = x"yes"; then
+ AC_PATH_PROG([ASCIIDOC], [asciidoc])
+ if test -z "$ASCIIDOC"; then
+ AC_MSG_ERROR([AsciiDoc not found and "--with-asciidoc" specified!])
+ fi
+ have_asciidoc=yes
+elif test x"$use_asciidoc" = x"no"; then
+ AC_MSG_WARN(["--without-asciidoc" specified - documentation will be skipped!])
+ have_asciidoc=no
+fi
+AM_CONDITIONAL(HAVE_ASCIIDOC, test $have_asciidoc = yes)
+#-------------------------------------------------------------------------------
# Compilation options
#-------------------------------------------------------------------------------
CFLAGS="$CFLAGS -Wall"
@@ -90,7 +117,7 @@ AM_CONDITIONAL(CALCURSE_MEMORY_DEBUG, test x$memdebug = xyes)
#-------------------------------------------------------------------------------
# Create Makefiles
#-------------------------------------------------------------------------------
-AC_OUTPUT(Makefile src/Makefile po/Makefile.in po/Makefile)
+AC_OUTPUT(Makefile doc/Makefile src/Makefile po/Makefile.in po/Makefile)
#-------------------------------------------------------------------------------
# Summary
#-------------------------------------------------------------------------------
diff --git a/doc/Makefile.am b/doc/Makefile.am
new file mode 100644
index 0000000..32e99e2
--- /dev/null
+++ b/doc/Makefile.am
@@ -0,0 +1,18 @@
+# $calcurse: Makefile.am,v 1.1 2011/02/24 11:36:50 fleischer Exp $
+
+AUTOMAKE_OPTIONS = foreign
+
+ASCIIDOC_ARGS = \
+ -n \
+ -a toc \
+ -a icons
+
+doc_DATA = \
+ manual.html
+
+docdir = $(datadir)/doc/$(PACKAGE)
+
+.txt.html:
+if HAVE_ASCIIDOC
+ $(AM_V_GEN) $(ASCIIDOC) $(ASCIIDOC_ARGS) $<
+endif
diff --git a/doc/manual.css b/doc/manual.css
deleted file mode 100644
index d84028b..0000000
--- a/doc/manual.css
+++ /dev/null
@@ -1,355 +0,0 @@
-/* $calcurse: manual.css,v 1.5 2009/07/05 20:32:47 culot Exp $ */
-
-/*
- * Calcurse - text-based organizer
- *
- * Copyright (c) 2008 Frederic Culot <frederic@culot.org>
- * All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * - Redistributions of source code must retain the above
- * copyright notice, this list of conditions and the
- * following disclaimer.
- *
- * - Redistributions in binary form must reproduce the above
- * copyright notice, this list of conditions and the
- * following disclaimer in the documentation and/or other
- * materials provided with the distribution.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- */
-
-body {
- margin: 0;
- padding: 0;
- padding-top: 10px;
- text-align: center;
-}
-
-
-@media screen {
- #mainContent{
- width: 70%;
- overflow: auto;
- }
- body {
- overflow: auto;
- background-color: #d3d3d3;
- }
- pre {
- margin-left: 2.5cm;
- margin-right: 2cm;
- }
-}
-
-@media print {
- #mainContent{
- width: 90%;
- overflow: visible;
- }
- body {
- overflow: visible;
- background-color: #ffffff;
- }
- pre {
- margin-left: -1cm;
- margin-right: 2cm;
- }
-}
-
-#mainContent{
- margin-right: auto;
- margin-left: auto;
- padding-left: 10px;
- padding-right: 10px;
- margin-bottom: 1em;
- border: 1px solid gray;
- text-align: left;
- font-family: arial, helvetica, verdana, sans-serif;
- font: 10px/12px cursive;
- background-color: white;
-}
-
-#title {
- text-align: center !important;
- font: 24px/20px cursive !important;
-}
-
-div#mainContent h1 {
- text-align: left;
- padding: 0.5em;
- padding-top: 1em;
- font: 20px/16px cursive;
-}
-
-div#mainContent h2 {
- margin-left: 1.5cm;
- padding-top: 0.5em;
-}
-
-div#mainContent h2, h3 {
- margin-bottom: 0;
- padding-bottom: 0.3em;
-}
-
-div#mainContent h2 {
- font: 14px/14px cursive;
-}
-
-div#mainContent h3 {
- font: 12px/12px cursive;
-}
-
-p, blockquote {
- text-align: justify;
- text-indent: 1cm;
- margin-top: 0;
-}
-
-h3, p, div.bib, ul, ol, dl, blockquote {
- margin-left: 2.5cm;
- margin-right: 2cm;
-}
-
-ul, ol, dl {
- margin-top: 0;
- margin-bottom: 1em;
-}
-
-dl.compact dt {
- float: left;
-}
-
-dl.compact dd {
- margin-bottom: 0.5em;
-}
-
-dd {
- margin-bottom: 1em;
-}
-
-ul.sub, ol.sub, dl.sub {
- margin-left: 0;
- list-style: circle;
-}
-
-li {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-pre {
- display: block;
- border-left: 1px solid gray;
- padding-left: 2em;
- margin-right: 2cm;
-}
-
-code {
- font-family: monospace;
- font-weight: bold;
-}
-
-table {
- border-style: solid;
- border-collapse: collapse;
- border-width: 1px;
-}
-
-div.tab {
- padding: 1.5em;
- margin-left: 4.5cm;
- margin-right: 2cm;
-}
-
-img {
- border-style: none;
-}
-
-div.img {
- text-align: center;
-}
-
-tr, td, thead, tbody {
- margin: 0;
-}
-
-thead {
- background-color: gray;
- color: black;
- text-align: center;
-}
-
-td {
- border-style: solid;
- border-width: 1px;
-}
-
-span.main {
- border-style: none;
- border-bottom-style: dashed;
- border-bottom-width: 1.5px;
- padding: 0.2em;
-}
-
-#toc {
- margin-top: 1.5cm;
- margin-bottom: 1cm;
- padding-top: 0;
- padding-bottom: 0.2cm;
- border-width: 0;
- border-left-width: 1cm;
- border-left-color: gray;
- border-style: solid;
-}
-
-#toc h1 {
- font: 12px/12px cursive;
-}
-
-#toc a {
- text-decoration: none;
- color: black;
-}
-
-a {
- color: black;
-}
-
-#toc li {
- list-style-type: none;
- margin-top: 0;
- margin-bottom: 0;
-}
-
-#toc ul ul li {
- margin-top: 0;
- margin-bottom: 0;
-}
-
-#toc ul ul ul li {
- margin-left: -0.5cm;
-}
-
-#toc ul {
- margin-top: 0;
- margin-bottom: 0;
- margin-left: 0;
- padding-left: 1cm;
-}
-
-.todo {
- color: green;
-}
-
-div.warn {
- margin-top: 1cm;
- margin-bottom: 1cm;
- border-style: solid;
- border-width: thin;
- padding: 0.5em;
- text-align: justify;
-}
-
-div.warn h1 {
- display: inline;
- padding: 0.5em;
- margin: 0;
- font: 8px/10px cursive;
-}
-
-div.res {
- text-align: center;
-}
-
-span.res {
- border-width: thin;
- border-style: solid;
-}
-
-div.footer {
- margin: 20px;
- margin-left: 4%;
- margin-top: 2cm;
- border-width: 0;
- border-style: solid;
- border-top-width: medium;
- font-style: italic;
- text-align: right;
-}
-
-p.abstract {
- margin-left: 3cm;
- margin-right: 3cm;
-}
-
-.rq {
- text-indent: 0;
- font-style: italic;
- border-style: solid;
- border-width: medium;
- border-left-width: 0;
- border-top-width: 0;
- border-color: gray;
- padding: 0.4em;
-}
-
-dl .rq, ol .rq, ul .rq {
- margin-left: 0;
- margin-right: 0;
- border: 0;
-}
-
-p.time {
- text-indent: 0;
- font-style: italic;
- border-style: solid;
- border-width: medium;
- border-left-width: 0;
- border-top-width: 0;
- border-color: gray;
- padding: 0.4em;
- text-align: right;
-}
-
-p.qu {
- font-style: italic;
- text-align: left;
- font: 8px/10px cursive;
- border-width: 0;
- border-left-width: thin;
- border-left-color: gray;
- border-style: double;
- color: gray;
-}
-
-.valorise {
- text-decoration: underline;
-}
-
-.big {
- font-weight: bolder;
- font: 12px/12px cursive;
-}
-
-.emp {
- font-style: italic;
-}
-
-.tablesubtitle {
- font-style: italic;
- text-align: center;
-}
diff --git a/doc/manual.txt b/doc/manual.txt
new file mode 100644
index 0000000..563f9e2
--- /dev/null
+++ b/doc/manual.txt
@@ -0,0 +1,1112 @@
+////
+/*
+ * $calcurse: manual.txt,v 1.1 2011/02/24 11:36:50 fleischer Exp $
+ *
+ * Copyright (c) 2004-2010 Frederic Culot <frederic@culot.org>
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ *
+ * - Redistributions of source code must retain the above
+ * copyright notice, this list of conditions and the
+ * following disclaimer.
+ *
+ * - Redistributions in binary form must reproduce the above
+ * copyright notice, this list of conditions and the
+ * following disclaimer in the documentation and/or other
+ * materials provided with the distribution.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+ * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+ * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+ * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+ * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+ * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+ * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+ * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ */
+////
+
+CALCURSE - text-based organizer
+===============================
+
+Abstract
+--------
+
+This manual describes `calcurse` functionnalities, and how to use them. The
+installation from source is first described, together with the available
+command line arguments. The user interface is then presented, with all of the
+customizable options that change `calcurse` behavior. Last, bug reporting
+procedure is explained, as well as the way one can contribute to `calcurse`
+development.
+
+Introduction
+------------
+
+`calcurse` is a text-based calendar and scheduling application. It helps
+keeping track of events, appointments and everyday tasks. A configurable
+notification system reminds user of upcoming deadlines, and the curses based
+interface can be customized to suit user needs. All of the commands are
+documented within an online help system.
+
+Overview
+--------
+
+Creation history
+~~~~~~~~~~~~~~~~
+
+I started thinking about this project when I was finishing my Ph.D. in
+Astrophysics... It started to be a little hard to organize myself, and I really
+needed a good tool to help me in that difficult task ;)
+
+I like programs which use Text User Interfaces, because they are simple, fast,
+portable and efficient, so I thought about working on coding a simple calendar
+using such an interface. Moreover, I wanted to go on learning the `C`
+language, which I only used for a while during my undergraduate studies. So I
+thought that would be the good project to start in order to get organized and
+to learn about a few `C` things !
+
+Unfortunately, I finished my Ph.D. before finishing `calcurse`, but anyway, I
+still wanted to work on it, hoping it would be helpful to other people. So
+here it is...
+
+But why _calcurse_ anyway ? Well, it is simply the concatenation of _CALendar_
+and _nCURSEs_, the name of the library used to build the user interface.
+
+Important features
+~~~~~~~~~~~~~~~~~~
+
+`Calcurse` is multi-platform and intended to be lightweight, fast and reliable.
+It is to be used inside a console or terminal, locally or on a distant machine
+within an ssh (or similar) connection.
+
+`Calcurse` can be run in two different modes : interactive or non-interactive
+mode. The first mode allows oneself to view its own personal organizer almost
+everywhere, thanks to the text-based interface. The second mode permits to
+easily build reminders just by adding `calcurse` with appropriate command line
+arguments inside a cron tab or within a shell init script.
+
+Moreover, `calcurse` was created with the end-user in mind, and tends to be as
+friendly as possible. This means a complete on-line help system, together with
+having all of the possible actions displayed at any time inside a status bar.
+The user interface is configurable, and one can choose between several color
+and layout combinations. Key bindings are also configurable, to fit everyone's
+needs. Last, a configurable notification system reminds user of upcoming
+appointments. The reminders are sent even if the user's interface is not
+running, as calcurse is able to run in background.
+
+Installation
+------------
+
+Requirements
+~~~~~~~~~~~~
+
+ncurses library
+^^^^^^^^^^^^^^^
+
+`Calcurse` requires only a `C` compiler, such as `cc` or `gcc`, and the
+`ncurses` library. It would be very surprising not to have a valid `ncurses`
+library already installed on your computer, but if not, you can find it at the
+following url: http://ftp.gnu.org/pub/gnu/ncurses/
+
+NOTE: It is also possible to link `calcurse` against the `ncursesw` library
+ (ncurses with support for unicode). However, UTF-8 is not yet supported
+ by `calcurse`.
+
+[[installation_requirements_gettext]]
+gettext library
+^^^^^^^^^^^^^^^
+
+`calcurse` supports internationalization (*i18n* hereafter) through the
+`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
+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
+installed on your system, you can search for the `libintl.h` header file for
+instance:
+
+----
+$ locate libintl.h
+----
+
+If this header file is not found, then you can obtain the `gettext` sources at
+the following url : http://ftp.gnu.org/pub/gnu/gettext/
+
+NOTE: Even if `libintl.h` is found on your system, it can be wise to specify
+ its location during the <<install_process,install process>>, by using the
+ `--with-libintl-prefix` option with `configure`. Indeed, the `configure`
+ could fail to locate this library if installed in an uncommon place.
+
+[[install_process]]
+Install process
+~~~~~~~~~~~~~~~
+
+First you need to gunzip and untar the source archive:
+
+----
+$ tar zxvf calcurse-2.8.tar.gz
+----
+
+Once you meet the requirements and have extracted the archive, the install
+process is quite simple, and follows the standard three steps process:
+
+----
+$ ./configure
+$ make
+$ make install # (may require root privilege)
+----
+
+Use `./configure --help` to obtain a list of possible options.
+
+calcurse basics
+---------------
+
+Invocation
+~~~~~~~~~~
+
+[[invocation_commandline]]
+Command line arguments
+^^^^^^^^^^^^^^^^^^^^^^
+
+`calcurse` takes the following options from the command line (both short and
+long options are supported):
+
+`-a, --appointment`::
+ Print the appointments and events for the current day and exit. The calendar
+ from which to read the appointments can be specified using the `-c` flag.
+
+`-c <file>, --calendar <file>`::
+ Specify the calendar file to use. The default calendar is
+ `~/.calcurse/apts` (see section <<basics_files,calcurse files>>).
+
+`-d <date|num>, --day <date|num>`::
+ Print the appointments for the given date or for the given number of
+ upcoming days, depending on the argument format. Two possible formats are
+ supported:
++
+--
+ * a date (possible formats described below).
+ * a number `n`.
+--
++
+In the first case, the appointment list for the specified date will be
+returned, while in the second case the appointment list for the `n` upcoming
+days will be returned. As an example, typing `calcurse -d 3` will display
+your appointments for today, tomorrow, and the day after tomorrow. Possible
+formats for specifying the date are defined inside the general configuration
+menu (see <<options_general,General options>>), using the
+`input_datefmt` variable.
++
+Note: as for the `-a` flag, the calendar from which to read the appointments
+can be specified using the `-c` flag.
+
+`-D <dir>, --directory <dir>`::
+ Specify the data directory to use. This option is incompatible with -c.
+ If not specified, the default directory is `~/.calcurse/`.
+
+`-h, --help`::
+ Print a short help text describing the supported command-line options,
+ and exit.
+
+`-i <file>, --import <file>`::
+ Import the icalendar data contained in `file`.
+
+`-n, --next`::
+ Print the next appointment within upcoming 24 hours and exit. The indicated
+ time is the number of hours and minutes left before this appointment.
++
+Note: the calendar from which to read the appointments can be specified using
+the `-c` flag.
+
+`-N, --note`::
+ When used with the `-a` or `-t` flag, also print note content if one is
+ associated with the displayed item.
+
+`-r[num], --range[=num]`::
+ Print events and appointments for the num number of days and exit. If no num
+ is given, a range of 1 day is considered.
+
+`-s[date], --startday[=date]`::
+ Print events and appointments from date and exit. If no date is given, the
+ current day is considered.
+
+`-S<regex>, --search=<regex>`::
+ When used with the `-a`, `-d`, `-r`, `-s`, or `-t` flag, print only the items
+ having a description that matches the given regular expression.
+
+`--status`::
+ Display the status of running instances of calcurse. If calcurse is
+ running, this will tell if the interactive mode was launched or if
+ calcurse is running in background. The process pid will also be indicated.
+
+`-t[num], --todo[=num]`::
+ Print the `todo` list and exit. If the optional number `num` is given, then
+ only todos having a priority equal to `num` will be returned. The priority
+ number must be between 1 (highest) and 9 (lowest). It is also possible to
+ specify `0` for the priority, in which case only completed tasks will be
+ shown.
+
+`-v, --version`::
+ Display `calcurse` version and exit.
+
+`-x[format], --export[=format]`::
+ Export user data to specified format. Events, appointments and todos are
+ converted and echoed to stdout. Two possible formats are available: ical and
+ pcal (see section <<links_others,Links>> below). If the optional
+ argument `format` is not given, ical format is selected by default.
++
+Note: redirect standard output to export data to a file, by issuing a command
+such as:
++
+----
+$ calcurse --export > my_data.dat
+----
+
+Environment variable for i18n
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+`calcurse` can be compiled with native language support (see
+<<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*
+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).
+
+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
+the locale corresponding to the desired language.
+
+You should also specify the charset to be used, because in some cases the
+accents and such are not displayed correctly. This charset is indicated at the
+beginning of the po file corresponding to the desired language. For instance,
+you can see in the fr.po file that it uses the iso-8859-1 charset, so you could
+run `calcurse` using the following command:
+
+----
+$ LC_ALL=fr_FR.ISO8859-1 calcurse
+----
+
+Other environment variables
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The following environment variables affect the way `calcurse` operates:
+
+`VISUAL`::
+ Specifies the external editor to use for writing notes.
+
+`EDITOR`::
+ If the `VISUAL` environment variable is not set, then `EDITOR` will be used
+ as the default external editor. If none of those variables are set, then
+ `/usr/bin/vi` is used instead.
+
+`PAGER`::
+ Specifies the default viewer to be used for reading notes. If this variable
+ is not set, then `/usr/bin/less` is used.
+
+User interface
+~~~~~~~~~~~~~~
+
+Non-interactive mode
+^^^^^^^^^^^^^^^^^^^^
+
+When called with at least one of the following arguments: `-a`, `-d`, `-h`,
+`-n`, `-t`, `-v`, `-x`, `calcurse` is started in non-interactive mode. This
+means the desired information will be displayed, and after that, `calcurse`
+simply quits and you are driven back to the shell prompt.
+
+That way, one can add a line such as `calcurse --todo --appointment` in its
+init config file to display at logon the list of tasks and appointments
+scheduled for the current day.
+
+[[basics_interface_interactive]]
+Interactive mode
+^^^^^^^^^^^^^^^^
+
+NOTE: Key bindings that are indicated in this manual correspond to the default
+ ones, defined when `calcurse` is launched for the first time. If those
+ key bindings do not suit user's needs, it is possible to change them
+ within the keys configuration menu (see <<options_keys,key bindings>>).
+
+When called without any argument or only with the `-c` option, `calcurse` is
+started in interactive mode. In this mode, you are shown an interface
+containing three different panels which you can browse using the `TAB` key,
+plus a notification bar and a status bar (see figure below).
+
+----
+ appointment panel---. .---calendar panel
+ | |
+ v v
+ +------------------------------------++----------------------------+
+ | Appointments || Calendar |
+ |------------------------------------||----------------------------|
+ | (|) April 6, 2006 || April 2006 |
+ | ||Mon Tue Wed Thu Fri Sat Sun |
+ | || 1 2 |
+ | || 3 4 5 6 7 8 9 |
+ | || 10 11 12 13 14 15 16 |
+ | || 17 18 19 20 21 22 23 |
+ | || 24 25 26 27 28 29 30 |
+ | || |
+ | |+----------------------------+
+ | |+----------------------------+
+ | || ToDo | todo
+ | ||----------------------------| panel
+ | || | |
+ | || | |
+ | || |<--.
+ | || |
+ +------------------------------------++----------------------------+
+ |---[ Mon 2006-11-22 | 10:11:43 ]---(apts)----> 01:20 :: lunch <---|<--.
+ +------------------------------------------------------------------+ notify-bar
+ | ? Help R Redraw H/L -/+1 Day G GoTo C Config |
+ | Q Quit S Save J/K -/+1 Week Tab Chg View |<-.
+ +------------------------------------------------------------------+ |
+ |
+ status bar
+----
+
+The first panel represents a calendar which allows to highlight a particular
+day, the second one contains the list of the events and appointments on that
+day, and the last one contains a list of tasks to do but which are not assigned
+to any specific day.
+
+Depending on the selected view, the calendar could either display a monthly
+(default as shown in previous figure) or weekly view. The weekly view would
+look like the following:
+
+----
++------------------------------------+
+| Calendar |
+|----------------------------(# 13)--|
+| Mon Tue Wed Thu Fri Sat Sun |
+| 29 30 31 01 02 03 04 |
+| <----+-- slice 1: 00:00 to 04:00 AM
+| -- -- -- -- -- -- |
+| <----+-- slice 2: 04:00 to 08:00 AM
+| -- -- -- -- -- -- |
+| <----+-- slice 3: 08:00 to 12:00 AM
+| - -- -- -- -- -- -- - <-+-- midday
+| <----+-- slice 4: 12:00 to 04:00 PM
+| -- -- -- -- -- -- |
+| <----+-- slice 5: 04:00 to 08:00 PM
+| -- -- -- -- -- -- |
+| <----+-- slice 6: 08:00 to 12:00 PM
++------------------------------------+
+----
+
+The current week number is displayed on the top-right side of the panel (*# 13*
+meaning it is the 13th week of the year in the above example). The seven days
+of the current week are displayed in column. Each day is divided into slices of
+4 hours each (6 slices in total, see figure above). A slice will appear in a
+different color if an appointment falls into the corresponding time-slot.
+
+In the appointment panel, one can notice the *`(|)`* sign just in front of the
+date. This indicates the current phase of the moon. Depending on which is the
+current phase, the following signs can be seen:
+
+` |) `::
+ first quarter
+
+` (|) `::
+ full moon
+
+` (| `::
+ last quarter
+
+` | `::
+ new moon
+
+no sign::
+ Phase of the moon does not correspond to any of the above ones.
+
+At the very bottom of the screen there is a status bar, which indicates the
+possible actions and the corresponding keystrokes.
+
+Just above this status bar is the notify-bar, which indicates from left to
+right : the current date, the current time, the calendar file currently in use
+(apts on the above example, which is the default calendar file, see the
+following section), and the next appointment within the upcoming 24 hours. Here
+it says that it will be lunch time in one hour and twenty minutes.
+
+NOTE: Some actions, such as editing or adding an item, require to type in some
+ text. This is done with the help of the built-in input line editor.
+
+Within this editor, if a line is longer than the screen width, a `>`, `*`, or
+`<` character is displayed in the last column indicating that there are more
+character after, before and after, or before the current position,
+respectively. The line is scrolled horizontally as necessary.
+
+Moreover, some editing commands are bound to particular control characters.
+Hereafter are indicated the available editing commands (`^` stands for the
+control key):
+
+`^a`::
+ moves the cursor to the beginning of the input line
+
+`^b`::
+ moves the cursor backward
+
+`^d`::
+ deletes one character forward
+
+`^e`::
+ moves the cursor to the end of the input line
+
+`^f`::
+ moves the cursor forward
+
+`^h`::
+ deletes one character backward
+
+`^k`::
+ deletes the input from the cursor to the end of the line
+
+`ESCAPE`::
+ cancels the editing
+
+[[basics_daemon]]
+Background mode
+~~~~~~~~~~~~~~~
+
+When the daemon mode is enabled in the notification configuration menu (see
+<<options_notify,Notify-bar settings>>), `calcurse` will stay in background
+when the user interface is not running. In background mode, `calcurse` checks
+for upcoming appointments and runs the user-defined notification command when
+ necessary. When the user interface is started again, the daemon automatically
+ stops.
+
+`calcurse` background activity can be logged (set the `notify-daemon_log`
+variable in the notification configuration <<options_notify,menu>>),
+and in that case, information about the daemon start and stop time, reminders'
+command launch time, signals received... will be written in the `daemon.log`
+file (see section <<basics_files,files>>).
+
+Using the `--status` command line option (see section
+<<basics_invocation_commandline,Command line arguments>>), one can know if
+`calcurse` is currently running in background or not. If the daemon is
+running, a message like the following one will be displayed (the pid of the
+daemon process will be shown):
+
+----
+calcurse is running in background (pid 14536)
+----
+
+NOTE: To stop the daemon, just send the `TERM` signal to it, using a command
+ such as: `kill daemon_pid`, where *daemon_pid* is the process id of the
+ daemon (14536 in the above example).
+
+[[basics_files]]
+calcurse files
+~~~~~~~~~~~~~~
+
+The following structure is created in your `$HOME` directory (or in the
+directory you specified with the -D option) the first time `calcurse` is run
+:
+
+----
+$HOME/.calcurse/
+ |___notes/
+ |___conf
+ |___keys
+ |___apts
+ |___todo
+----
+`notes/`::
+ this subdirectory contains descriptions of the notes which are attached to
+ appointments, events or todos. One text file is created per note, whose name
+ is built using mkstemp(3) and should be unique, but with no relation with the
+ corresponding item's description.
+`conf`::
+ this file contains the user configuration
+`keys`::
+ this file contains the user-defined key bindings
+`apts`::
+ this file contains all of the events and user's appointments
+`todo`::
+ this file contains the todo list
+
+NOTE: If the logging of calcurse daemon activity was set in the notification
+ configuration menu, the extra file `daemon.log` will appear in calcurse
+ data directory. This file contains logs about calcurse activity when
+ running in background.
+
+Import/Export capabilities
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The import and export capabilities offered by `calcurse` are described below.
+
+Import
+^^^^^^
+
+Data in icalendar format as described in the rfc2445 specification (see
+<<links_others,links>> section below) can be imported into calcurse. Calcurse
+ical parser is based on version 2.0 of this specification, but for now on, only
+a subset of it is supported.
+
+The following icalendar properties are handled by calcurse:
+
+* `VTODO` items: "PRIORITY", "VALARM", "SUMMARY", "DESCRIPTION"
+
+* `VEVENT` items: "DTSTART", "DTEND", "DURATION", "RRULE", "EXDATE", "VALARM",
+ "SUMMARY", "DESCRIPTION"
+
+The icalendar `DESCRIPTION` property will be converted into calcurse format by
+adding a note to the item. If a "VALARM" property is found, the item will be
+flagged as important and the user will get a notification (this is only
+applicable to appointments).
+
+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" /
+ "HOURLY"
+
+* some recurrence keywords are not recognized (all those starting with `BY`):
+ "BYSECOND" / "BYMINUTE" / "BYHOUR" / "BYDAY" / "BYMONTHDAY" / "BYYEARDAY" /
+ "BYWEEKNO" / "BYMONTH" / "BYSETPOS" plus "WKST"
+
+* the recurrence exception keyword "EXRULE" is not recognized
+
+* timezones are not taken into account
+
+Export
+^^^^^^
+
+Two possible export formats are available: `ical` and `pcal` (see section
+<<links_others,Links>> below to find out about those formats).
+
+Online help
+~~~~~~~~~~~
+
+At any time, the built-in help system can be invoked by pressing the `?`
+key. Once viewing the help screens, informations on a specific command can be
+accessed by pressing the keystroke corresponding to that command.
+
+Options
+-------
+
+All of the `calcurse` parameters are configurable from the Configuration menu
+available when pressing `C`. You are then driven to a submenu with five
+possible choices : pressing `C` again will lead you to the Color scheme
+configuration, pressing `L` allows you to choose the layout of the main
+`calcurse` screen (in other words, where to put the three different panels on
+screen), pressing `G` permits you to choose between different general options,
+pressing `K` opens the key bindings configuration menu, and last you can modify
+the notify-bar settings by pressing `N`.
+
+[[options_general]]
+General options
+~~~~~~~~~~~~~~~
+
+These options control `calcurse` general behavior, as described below:
+
+`auto_save` (default: *yes*)::
+ This option allows to automatically save the user's data (if set to *yes*)
+ when quitting. <p class="rq"><span class="valorise">warning:</span> No data
+ will be automatically saved if `auto_save` is set to *no*. This means the
+ user must press `S` (for saving) in order to retrieve its modifications.
+
+`periodic_save` (default: *0*)::
+ If different from `0`, user's data will be automatically saved every
+ *periodic_save* minutes. When an automatic save is performed, two asterisks
+ (i.e. `**`) will appear on the top right-hand side of the screen).
+
+`confirm_quit` (default: *yes*)::
+ If set to *yes*, confirmation is required before quitting, otherwise pressing
+ `Q` will cause `calcurse` to quit without prompting for user confirmation.
+
+`confirm_delete` (default: *yes*)::
+ If this option is set to *yes*, pressing `D` for deleting an item (either a
+ *todo*, *appointment*, or *event*), will lead to a prompt asking for user
+ confirmation before removing the selected item from the list. Otherwise, no
+ confirmation will be needed before deleting the item.
+
+`skip_system_dialogs` (default: *no*)::
+ Setting this option to *yes* will result in skipping the system dialogs
+ related to the saving and loading of data. This can be useful to speed up
+ the input/output processes.
+
+`skip_progress_bar` (default: *no*)::
+ If set to *yes*, this will cause the disappearing of the progress bar which
+ is usually shown when saving data to file. If set to *no*, this bar will be
+ displayed, together with the name of the file being saved (see section
+ <<basics_files,calcurse files>>).
+
+`calendar_default_view` (default: *0*)::
+ If set to `0`, the monthly calendar view will be displayed by default
+ otherwise it is the weekly view that will be displayed.
+
+`week_begins_on_monday` (default: *yes*)::
+ One can choose between Monday and Sunday as the first day of the week. If the
+ option `week_begins_on_monday` is set to *yes*, Monday will be first in the
+ calendar view. Else if the option is set to *no*, then Sunday will be the
+ first day of the week.
+
+`output_datefmt` (default: *%D*)::
+ This option indicates the format to be used when displaying dates in
+ non-interactive mode. Using the default values, dates are displayed the
+ following way: *mm/dd/aa*. You can see all of the possible formats by typing
+ `man 3 strftime` inside a terminal.
+
+`input_datefmt` (default: *1*)::
+ This option indicates the format that will be used to enter dates in
+ *calcurse*. Four choices are available:
++
+1. mm/dd/yyyy
+2. dd/mm/yyyy
+3. yyyy/mm/dd
+4. yyyy-mm-dd
+
+[[options_keys]]
+Key bindings
+~~~~~~~~~~~~
+
+One can define it's own keybindings within the `Keys` configuration menu. The
+default keys look like the one used by the `vim` editor, especially the
+displacement keys. Anyway, within this configuration menu, users can redefine
+all of the keys available from within calcurse's user interface.
+
+To define new keybindings, first highlight the action to which it will apply.
+Then, delete the actual key binding if necessary, and add a new one. You will
+then be asked to press the key corresponding to the new binding. It is possible
+to define more than one key binding for a single action.
+
+An automatic check is performed to see if the new key binding is not already
+set for another action. In that case, you will be asked to choose a different
+one. Another check is done when exiting from this menu, to make sure all
+possible actions have a key associated with it.
+
+The following keys can be used to define bindings:
+
+* lower-case, upper-case letters and numbers, such as `a`, `Z`, `0`
+
+* CONTROL-key followed by one of the above letters
+
+* escape, horizontal tab, and space keys
+
+* arrow keys (up, down, left, and right)
+
+* `HOME` and `END` keys
+
+While inside the key configuration menu, an online help is available for each
+one of the available actions. This help briefly describes what the highlighted
+action is used for.
+
+Color themes
+~~~~~~~~~~~~
+
+`calcurse` color theme can be customized to suit user's needs. To change the
+default theme, the configuration page displays possible choices for foreground
+and background colors. Using arrows or calcurse displacement keys to move, and
+`X` or space to select a color, user can preview the theme which will be
+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
+bar. A black and white theme is also available, in order to support non-color
+terminals.
+
+NOTE: Depending on your terminal type and on the value of the `$TERM`
+ environnement variable, color could or could not be supported. An error
+ message will appear if you try to change colors whereas your terminal
+ does not support this feature. If you do know your terminal supports
+ colors but could not get `calcurse` to display them, try to set your
+ `$TERM` variable to another value (such as *xterm-xfree86* for instance).
+
+Layout configuration
+~~~~~~~~~~~~~~~~~~~~
+
+The layout corresponds to the position of the panels inside `calcurse` screen.
+The default layout makes the calendar panel to be displayed on the top-right
+corner of the terminal, the todo panel on the bottom-right corner, while the
+appointment panel is displayed on the left hand-side of the screen (see the
+figure in section <<basics_interface_interactive,Interactive mode>> for an
+exemple of the default layout). By choosing another layout in the
+configuration screen, user can customize `calcurse` appearence to best suit his
+needs by placing the different panels where needed.
+
+The following option is used to modify the layout configuration:
+
+`layout` (default: *0*)::
+ Eight different layouts are to be chosen from (see layout configuration
+ screen for the description of the available layouts).
+
+Sidebar configuration
+~~~~~~~~~~~~~~~~~~~~~
+
+The sidebar is the part of the screen which contains two panels: the calendar
+and, depending on the chosen layout, either the todo list or the appointment
+list.
+
+The following option is used to change the width of the sidebar:
+
+`side-bar_width` (default: *0*)::
+ Width (in percentage, 0 being the minimum width) of the side bar.
+
+[[options_notify]]
+Notify-bar settings
+~~~~~~~~~~~~~~~~~~~
+
+The following options are used to modify the notify-bar behavior:
+
+`notify-bar_show` (default: *yes*)::
+ This option indicates if you want the notify-bar to be displayed or not.
+
+`notify-bar_date` (default: *%a %F*)::
+ With this option, you can specify the format to be used to display the
+ current date inside the notification bar. You can see all of the possible
+ formats by typing `man 3 strftime` inside a terminal.
+
+`notify-bar_time` (default: *%T*)::
+ With this option, you can specify the format to be used to display the
+ current time inside the notification bar. You can see all of the possible
+ formats by typing `man 3 strftime` inside a terminal.
+
+`notify-bar_warning` (default: *300*)::
+ When there is an appointment which is flagged as `important` within the next
+ `notify-bar_warning` seconds, the display of that appointment inside the
+ notify-bar starts to blink. Moreover, the command defined by the
+ `notify-bar_command` option will be launched. That way, the user is warned
+ and knows there will be soon an upcoming appointment.
+
+`notify-bar_command` (default: *printf '\a'*)::
+ This option indicates which command is to be launched when there is an
+ upcoming appointment flagged as `important`. This command will be passed to
+ the user's shell which will interpret it. To know what shell must be used,
+ the content of the `$SHELL` environment variable is used. If this variable is
+ not set, `/bin/sh` is used instead.
++
+====
+Say the `mail` command is available on the user's system, one can use the
+following command to get notified by mail of an upcoming appointment (the
+appointment description will also be mentioned in the mail body):
+
+----
+$ calcurse --next | mail -s "[calcurse] upcoming appointment!" user@host.com
+----
+====
+
+`notify-daemon_enable` (default: *no*)::
+ If set to yes, daemon mode will be enabled, meaning `calcurse` will run into
+ background when the user's interface is exited. This will allow the
+ notifications to be launched even when the interface is not running. More
+ details can be found in section <<basics_daemon,Background mode>>.
+
+`notify-daemon_log` (default: *no*)::
+ If set to yes, `calcurse` daemon activity will be logged (see section
+ <<basics_files,files>>).
+
+Known bugs
+----------
+
+Incorrect highlighting of items appear when using calcurse black and white
+theme together with a `$TERM` variable set to *xterm-color*. To fix this bug,
+and as advised by Thomas E. Dickey (`xterm` maintainer), *xterm-xfree86* should
+be used instead of *xterm-color* to set the `$TERM` variable:
+
+____
+"The xterm-color value for $TERM is a bad choice for XFree86 xterm because it
+is commonly used for a terminfo entry which happens to not support bce. Use the
+xterm-xfree86 entry which is distributed with XFree86 xterm (or the similar one
+distributed with ncurses)."
+____
+
+[[bugs]]
+Reporting bugs and feedback
+---------------------------
+
+Please send bug reports and feedback to: `calcurse .at. culot .dot. org` or to
+the author: `frederic .at. culot .dot. org`.
+
+[[contribute]]
+How to contribute?
+------------------
+
+If you would like to contribute to the project, you can first send your
+feedback on what you like or dislike, and if there are features you miss in
+`calcurse`. For now on, possible contributions concern the translation of
+`calcurse` messages and documentation.
+
+NOTE: any help in getting `calcurse` internationalized would be very welcomed,
+ but before contributing, send a mail to `calcurse-i18n .at. culot .dot.
+ org` to know if someone already started the translation process into your
+ language.
+
+Translating documentation
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The *doc/* directory of the source package already contains translated version
+of `calcurse` manual. However, if the manual is not yet available into your
+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
+included in the next `calcurse` release.
+
+calcurse i18n
+~~~~~~~~~~~~~
+
+As already mentioned, `gettext` utilities are used by `calcurse` to produce
+multi-lingual messages. This section provides informations 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 refer to the `GNU gettext` manual at:
+http://www.gnu.org/software/gettext/manual/
+
+Basically, three different people get involved in the translation chain:
+coders, language coordinator, and translators. After a quick overview of how
+things work, the translator tasks will be described hereafter.
+
+Overview
+^^^^^^^^
+
+To be able to display texts in the native language of the user, two steps are
+required: *internationalization* (i18n) and *localization* (l10n).
+
+i18n is about making `calcurse` support multiple languages. It is performed by
+coders, who will mark translatable texts and provide a way to display them
+translated at runtime.
+
+l10n is about making the i18n'ed `calcurse` adapt to the specific language of
+the user, ie translating the strings previously marked by the developers, and
+setting the environment correctly for `calcurse` to use the result of this
+translation.
+
+So, translatable strings are first marked by the coders within the `C` source
+files, then gathered in a template file (*calcurse.pot* - the *pot* extension
+meaning *portable object template*). The content of this template file is then
+merged with the translation files for each language (*fr.po* for french, for
+instance - with *po* standing for *portable object*, ie meant to be read and
+edited by humans). A given translation team will take this file, translate its
+strings, and send it back to the developers. At compilation time, a binary
+version of this file (for efficiency reasons) will be produced (*fr.mo* - *mo*
+stands for *machine object*, ie meant to be read by programs), and then
+installed. Then `calcurse` will use this file at runtime, translating the
+strings according to the locale settings of the user.
+
+
+Translator tasks
+^^^^^^^^^^^^^^^^
+
+Suppose someone wants to initiate the translation of a new language. Here are
+the steps to follow:
+
+* First, find out what the locale name is. For instance, for french, it is
+ `fr_FR`, or simply `fr`. This is the value the user will have to put in his
+ `LC_ALL` environment variable for software to be translated (see
+ <<basics_invocation_variable,Environment variable for i18n>>).
+
+* Then, go into the *po/* directory, and create a new po-file
+ from the template file using the following command: `msginit -i calcurse.pot
+ -o fr.po -l fr --no-translator` If you do not have `msginit` installed on
+ your system, simply copy the *calcurse.pot* file to *fr.po* and edit the
+ header by hand.
+
+Now, having this *fr.po* file, the translator is ready to begin.
+
+po-files
+^^^^^^^^
+
+The format of the po-files is quite simple. Indeed, po-files are made of four
+things:
+
+1. *location lines:* tells you where the strings can be seen (name of file and
+ line number), in case you need to see a bit of context.
+
+2. *msgid lines:* the strings to translate.
+
+3. *msgstr lines:* the translated strings.
+
+4. *lines prefixed with `#`:* comments (some with a special meaning, as we will
+ see below).
+
+Basically, all you have to do is fill the *msgstr* lines with the translation
+of the above *msgid* line.
+
+A few notes:
+
+*Fuzzy strings*::
+ You will meet strings marked with a `"#, fuzzy"` comment. `calcurse` won't
+ use the translations of such strings until you do something about them. A
+ string being fuzzy means either that the string has already been translated
+ but has since been changed in the sources of the program, or that this is a
+ new string for which `gettext` made a 'wild guess' for the translation, based
+ on other strings in the file. It means you have to review the translation.
+ Sometimes, the original string has changed just because a typo has been
+ fixed. In this case, you won't have to change anything. But sometimes, the
+ translation will no longer be accurate and needs to be changed. Once you are
+ done and happy with the translation, just remove the `"#, fuzzy"` line, and
+ the translation will be used again in `calcurse`.
+
+*c-format strings and special sequences*::
+ Some strings have the following comment: `"#, c-format"`. This tells that
+ parts of the string to translate have a special meaning for the program, and
+ that you should leave them alone. For instance, %-sequences, like `"%s"`.
+ These means that `calcurse` will replace them with another string. So it is
+ important it remains. There are also \-sequences, like `\n` or `\t`. Leave
+ them, too. The former represents an end of line, the latter a tabulation.
+
+*Translations can be wrapped*::
+ If lines are too long, you can just break them like this:
++
+----
+msgid ""
+"some very long line"
+"another line"
+----
+
+*po-file header*::
+ At the very beginning of the po-file, the first string form a header, where
+ various kind of information has to be filled in. Most important one is the
+ charset. It should resemble
++
+----
+"Content-Type: text/plain; charset=utf-8\n"
+----
++
+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:
++
+----
+"Last-Translator: Frederic Culot <frederic@culot.org>\n"
+----
+
+*Comments*::
+ Adding comments (lines begining 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
+ 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
+ be displayed to adapt your translation.
+
+*A few useful tools*::
+ The po-file format is very simple, and the file can be edited with a standard
+ text editor. But if you prefer, there are few specialized tools you may find
+ convenient for translating:
++
+* `poEdit` (http://www.poedit.org/)
+* `KBabel` (http://i18n.kde.org/tools/kbabel/)
+* `GTranslator` (http://gtranslator.sourceforge.net/)
+* `Emacs` po mode
+* `Vim` po mode
+
+*And finally*::
+ I hope you'll have fun contributing to a more internationalized world. :) If
+ you have any more questions, don't hesitate to contact me at *frederic .at.
+ culot .dot. org*.
+
+Links
+-----
+
+This section contains links and references that may be of interest to you.
+
+calcurse homepage
+~~~~~~~~~~~~~~~~~
+
+The `calcurse` homepage can be found at http://culot.org/calcurse
+
+calcurse announce list
+~~~~~~~~~~~~~~~~~~~~~~
+
+If you are interested in the project and want to be warned when a new release
+comes out, you can subscribe to the `calcurse` announce list. In doing so, you
+will receive an email as soon as a new feature appears in `calcurse`.
+
+To subscribe to this list, send a message to *calcurse-announce .at. culot
+.dot. org* with "subscribe" in the subject field.
+
+calcurse RSS feed
+~~~~~~~~~~~~~~~~~
+
+Another possibility to get warned when new releases come out is to follow the
+RSS feed at: http://culot.org/calcurse/news_rss.xml
+
+This RSS feed is updated each time a new version of calcurse is available,
+describing newly added features.
+
+[[links_others]]
+Other links
+~~~~~~~~~~~
+
+You may want to look at the ical format specification (rfc2445) at:
+http://tools.ietf.org/html/rfc2445
+
+The pcal project page can be found at: http://pcal.sourceforge.net/
+
+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
+
+* Gwen for testing and general discussions about how to improve `calcurse`
+
+* Herbert for packaging `calcurse` for FreeBSD
+
+* Zul for packaging `calcurse` for NetBSD
+
+* Wain, Steffen and Ronald for packaging `calcurse` for Archlinux
+
+* Kevin, Ryan, and fEnIo for packaging `calcurse` for Debian and Ubuntu
+
+* Pascal for packaging `calcurse` for Slackware
+
+* Alexandre and Markus for packaging `calcurse` for Mac OsX and Darwin
+
+* Igor for packaging `calcurse` for ALT Linux
+
+* Joel for its calendar script which inspired `calcurse` calendar view
+
+* Michael Schulz and Chris M. for the german translation of `calcurse` and its
+ manual
+
+* Jose Lopez for the spanish translation of `calcurse` and its manual
+
+* Neil Williams for the english translation
+
+* Leandro Noferini for the italian translation
+
+* Tony for its patch which helped improving the recur_item_inday() function,
+ and for implementing the date format configuration options
+
+* Jeremy Roon for the dutch translation
+
+* Erik Saule for its patch implementing the `-N`, `-s`, `-S`, `-r` and `-D`
+ flags
+
+* people who write softwares I like and which inspired me, especially :
+
+ - `vim` for the displacement keys
+ - `orpheus` and `abook` for documentation
+ - `pine` and `aptitude` for the text user interface
+ - `tmux` for coding style
+
+And last, many many thanks to all of the `calcurse` users who sent me their
+feedback.
diff --git a/doc/manual_de.html b/doc/manual_de.html
deleted file mode 100644
index 2957acf..0000000
--- a/doc/manual_de.html
+++ /dev/null
@@ -1,1327 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<!--
-/*
- * $calcurse: manual_de.html,v 1.28 2010/03/29 18:18:01 culot Exp $
- *
- * Copyright (c) 2004-2010 Frederic Culot <frederic@culot.org>
- * All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * - Redistributions of source code must retain the above
- * copyright notice, this list of conditions and the
- * following disclaimer.
- *
- * - Redistributions in binary form must reproduce the above
- * copyright notice, this list of conditions and the
- * following disclaimer in the documentation and/or other
- * materials provided with the distribution.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- */
--->
-
-<html>
-<head>
-<title>CALCURSE documentation</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css" media="all">
- @import url(manual.css);
-</style>
-</head>
-<body>
-
-<div id="mainContent">
-
-<h1 id="title">
-<span class="main">CALCURSE - textbasierter Terminkalender</span></h1>
-
-<div class="warn">
-<div class="todo">
-<h1>Abstract</h1> This manual describes <code>calcurse</code> functionnalities,
-and how to use them. The installation from source is first described, together
-with the available command line arguments. The user interface
-is then presented, with all of the customizable options that change
-<code>calcurse</code> behavior. Last, bug reporting procedure is explained, as
-well as the way one can contribute to <code>calcurse</code> development.
-</div>
-</div>
-
-<div id="toc">
-<h1>Inhaltsverzeichnis</h1>
-<ul>
- <li><a href="#intro">1. Einleitung</a></li>
- <li><a href="#overview">2. &Uuml;berblick</a>
- <ul>
- <li><a href="#overview_history">2.1 Anlass</a></li>
- <li><a href="#overview_features">2.2 Wichtige Eigenschaften</a></li>
- </ul></li>
- <li><a href="#install">3. Installation</a>
- <ul>
- <li><a href="#install_requirements">3.1 Voraussetzungen</a>
- <ul>
- <li><a href="#install_requirements_ncurses">3.1.1 <code>ncurses</code> Bibliothek</a></li>
- <li><a href="#install_requirements_gettext">3.1.2 <code>gettext</code> Bibliothek</a></li>
- </ul></li>
- <li><a href="#install_process">3.2 Installationsprozess</a></li>
- </ul></li>
- <li><a href="#basics">4. <code>calcurse</code> Grundlagen</a>
- <ul>
- <li><a href="#basics_invocation">4.1 Programmaufruf</a>
- <ul>
- <li><a href="#basics_invocation_commandline">4.1.1 Programmargumente</a></li>
- <li><a href="#basics_invocation_variable">4.1.2 Umgebungsvariable f&uuml;r i18n</a></li>
- <li><a href="#basics_invocation_environment"><span class="todo">4.1.3 Other environment
- variables</span></a></li>
- </ul></li>
- <li><a href="#basics_interface">4.2 Benutzer-Interface</a>
- <ul>
- <li><a href="#basics_interface_noninteractive">4.2.1 Nicht-interaktiver Modus</a></li>
- <li><a href="#basics_interface_interactive">4.2.2 Interaktiver Modus</a></li>
- </ul></li>
- <li><a href="#basics_daemon"><span class="todo">4.3 Background mode</span></a></li>
- <li><a href="#basics_files">4.4 <code>calcurse</code> Dateien</a></li>
- <li><a href="#basics_import_export"><span class="todo">4.5 Import/Export capabilities</span></a>
- <ul>
- <li><a href="#basics_import"><span class="todo">4.5.1 Import</span></a></li>
- <li><a href="#basics_export"><span class="todo">4.5.2 Export</span></a></li>
- </ul></li>
- <li><a href="#basics_help">4.6 Onlinehilfe</a></li>
- </ul></li>
- <li><a href="#options">5. Optionen</a>
- <ul>
- <li><a href="#options_general">5.1 Allgemeine Optionen</a></li>
- <li><a href="#options_keys"><span class="todo">5.2 Key bindings</span></a>
- <li><a href="#options_colors">5.3 Einstellen der Terminalfarben</a></li>
- <li><a href="#options_layout">5.4 Einstellen des Layouts</a></li>
- <li><a href="#options_sidebar"><span class="todo">5.5 Sidebar configuration</span></a></li>
- <li><a href="#options_notify">5.6 Einstellen der Benachrichtigungszeile</a></li>
- </ul></li>
- <li><a href="#known_bugs">6. Bekannte Fehler</a></li>
- <li><a href="#bugs">7. Mitteilung von Fehlern und Anregungen</a></li>
- <li><a href="#contribute">8. Wie kann ich einen Beitrag leisten?</a>
- <ul>
- <li><a href="#contribute_documentation">8.1 &Uuml;bersetzung der Dokumentation</a></li>
- <li><a href="#contribute_i18n">8.2 <code>calcurse</code> i18n</a>
- <ul>
- <li><a href="#contribute_i18n_overview">8.2.1 &Uuml;berblick</a></li>
- <li><a href="#contribute_i18n_translator">8.2.2 Aufgaben des &Uuml;bersetzers</a></li>
- <li><a href="#contribute_i18n_po-files">8.2.3 po-Dateien</a></li>
- </ul></li>
- </ul></li>
- <li><a href="#links">9. Links</a>
- <ul>
- <li><a href="#links_homepage">9.1 <code>calcurse</code> Internetseite</a></li>
- <li><a href="#links_list">9.2 <code>calcurse</code> Ank&uuml;ndigungsliste</a></li>
- <li><a href="#links_rss">9.3 <code>calcurse</code> RSS</a></li>
- <li><a href="#links_others"><div class="todo">9.4 Other links</div></a></li>
- </ul></li>
- <li><a href="#thanks">10. Danksagungen</a></li>
-</ul>
-</div>
-
-
-<h1>1. Einleitung<a name="intro"></a></h1>
-<p>
-<code>calcurse</code> ist ein
-textbasierender Kalender, der Ihnen bei der Organisation von
-Ereignissen, Terminen und t&auml;glichen Aufgaben hilft. Ein
-konfigurierbares Notitzsystem erinnert Benutzer an bevorstehende
-Termine. Die curses basierende Benutzeroberflache kann auf eigene die
-Bed&uuml;rfnisse angepa&szlig;t werden. Alle Programmbefehle sind in
-einem online Hilfesystem dokumentiert.
-</p>
-
-<h1>2. &Uuml;berblick<a name="overview"></a></h1>
-<h2>2.1 Anlass<a name="overview_history"></a></h2>
-<p>
-Nachdem ich mein Diplom in Astrophysik absolviert hatte, kam mir die
-Idee dieses Programm zu schreiben. Alles begann etwas unorganisiert zu
-werden. Ein Programm, dass mir bei meiner Terminplanung etwas hilft,
-war wirklich vonn&ouml;ten. ;)
-</p>
-<p>
-Ich mag Programme mit Textinterfaces, weil sie einfach, schnell,
-portabel und effizient sind. Also dachte ich dar&uuml;ber nach ein
-Programm mit textorientiertem Benutzer-Interface zu entwickeln.
-Dar&uuml;ber hinaus wollte ich meine Kenntnisse in der Programmiersprache
-<code>C</code> erweitern. Im Grundstudium kam ich mit <code>C</code>
-erstmals in Kontakt. Ich denke es ist eine gute Idee ein solches
-Projekt zu beginnen und dabei meine Kenntnisse in <code>C</code> zu
-erweitern!
-</p>
-<p>
-Mein Diplom habe ich nun absolviert, <code>calcurse</code>
-ist aber noch immer nicht fertig. Nach wie vor entwickle ich dieses
-Programm weiter, in der Hoffnung, dass es f&uuml;r andere von Nutzen sein
-wird. Also hier ist es...
-</p>
-<p>
-Doch warum nenne ich es 'calcurse'? Nun, es ist einfach
-zusammengesetzt aus den W&ouml;rtern 'CALendar' und 'nCurses', dem Namen
-der Bibliothek die f&uuml;r das Benutzer-Interface verwendet wird.
-</p>
-
-<h2>2.2 Wichtige Eigenschaften<a name="overview_features"></a></h2>
-<p>
-<code>Calcurse</code> ist portabel und setzt sich zum Ziel klein,
-schnell und sicher zu sein. Es ist auf einer Konsole oder einem
-Terminal zu verwenden, entweder lokal oder auf einem entfernten System
-mithilfe einer ssh-Verbindung (oder &Auml;hnlichem).
-</p>
-<p>
-<code>Calcurse</code> kann in zwei unterschiedlichen Modi gestartet
-werden: Im interaktiven und im nicht-interaktiven Modus. Der erste Modus
-erzeugt Dank des textbasierten Interfaces die Ansicht eines eigenen
-pers&ouml;nlichen Terminkalenders. Mit dem zweiten Modus ist es m&ouml;glich
-sich ein Erinnerungstool (Reminder) zu erstellen, wenn
-<code>calcurse</code> mit den entsprechenden Argumenten in 'cron tab'
-oder einem 'init script' eingebunden wird.
-</p>
-<p>
-Dar&uuml;ber hinaus ist <code>calcurse</code> f&uuml;r Benutzer erstellt worden,
-mit der Absicht so benutzerfreundlich wie m&ouml;glich zu sein. Das
-bedeutet, dass eine komplette Onlinehilfe im Programm zu Verf&uuml;gung
-steht, sowie alle m&ouml;gliche Aktionen jederzeit in einer Statuszeile
-ersichtlich sind. Das Benutzer-Interface ist ebenfalls
-einstellbar. Ebenso kann man verschiedene Textfarben und Layouts
-w&auml;hlen.
-<span class="todo">Key bindings are also configurable, to fit everyone's needs.</span>
-Ein konfigurierbares Notizsystem erinnert den Benutzer
-an bevorstehende Termine.
-<span class="todo">The reminders are sent even if the user's interface
-is not running, as calcurse is able to run in background.</span>
-</p>
-
-<h1>3. Installation<a name="install"></a></h1>
-<h2>3.1 Voraussetzungen<a name="install_requirements"></a></h2>
-<h3>3.1.1 <code>ncurses</code> Bibliothek<a name="install_requirements_ncurses"></a></h3>
-<p>
-<code>Calcurse</code> ben&ouml;tigt einen C-Compiler wie etwa
-<code>cc</code> oder <code>gcc</code>. Ferner wird die
-ncurses-Bibliothek ben&ouml;tigt, die jedoch auf den meisten Unix-Systemen
-verf&uuml;gbar sein sollte. Falls nicht, k&ouml;nnen Sie sie von folgender URL herunter
-laden:</p>
-<pre>http://ftp.gnu.org/pub/gnu/ncurses/</pre>
-
-<div class="todo">
-<p>
- <p class="rq"><span class="valorize">Note:</span>
- It is also possible to link <code>calcurse</code> against the
- <code>ncursesw</code> library (ncurses with support for unicode).
- However, UTF-8 is not yet supported by <code>calcurse</code>.</p>
-</div>
-
-<h3>3.1.2 <code>gettext</code> Bibliothek<a name="install_requirements_gettext"></a></h3>
-<p>
- <code>calcurse</code> unterst&uuml;tzt die Internationalisierung
- (k&uuml;nftig <span class="emp">i18n</span>) durch <code>gettext</code>.
- Das bedeutet, dass <code>calcurse</code> mehrsprachige Mitteilungen
- erzeugen kann, wenn es mit der entsprechenden Sprachunterst&uuml;tzung
- kompiliert wurde (z.B. <span class="emp">NLS</span>).
-</p>
-<p>
- Dennoch, <span class="emp">NLS</span> ist optional und wenn keine mehrsprachigen Mitteilungen
- gew&uuml;nscht sind, kann diese Eigenschaft abgestellt werden.
- Rufen Sie hierzu einfach das <code>configure</code> Skript mit der Option
- <code>--disable-nls</code> auf (siehe Abschnitt <ahref="#install_process">
- Installationsprozess</a>).
- Um zu &uuml;berpr&uuml;fen, ob <code>gettext</code> auf dem System installiert ist,
- kann man nach der <code>libintl.h</code> Datei suchen:</p>
- <pre>locate libintl.h</pre>
-<p>
- Wurde diese Datei nicht gefunden, kann <code>gettext</code> von folgender URL
- herunter geladen werden:</p>
- <pre>http://ftp.gnu.org/pub/gnu/gettext/</pre>
-<p>
- <p class="rq"><span class="valorize">Beachte:</span>
- Auch wenn <code>libintl.h</code> auf dem System
- gefunden wurde, kann es erforderlich sein den Pfad dieser Datei w&auml;hrend des
- <ahref="#install_process"> Installationsprozesses</a> anzugeben. Die entsprechende
- Option f&uuml;r das <code>configure</code> Skript lautet dann
- <code>--with-libintl-prefix</code>.
- Das <code>configure</code> Skript wird nat&uuml;rlich vorzeitig abbrechen, wenn die
- dazugeh&ouml;rige Bibliothek nicht gefunden wurde.</p>
-
-
-<h2>3.2 Installationsprozess<a name="install_process"></a></h2>
-<p>
-Als erstes m&uuml;ssen die Dateien entpackt werden:</p>
-<pre>tar zxvf calcurse-2.8.tar.gz</pre>
-<p>
-Ist diese Voraussetzung erf&uuml;llt und das Archiv entpackt,
-sind nur noch die drei &uuml;blichen Schritte erforderlich:</p>
- <ol>
- <li><code>./configure</code></li>
- <li><code>make</code></li>
- <li><code>make install</code> (mit Root-Rechten)</li>
- </ol>
-<p>
-Rufen Sie <code>./configure --help</code> auf, um die
-verf&uuml;gbaren Optionen aufgelistet zu bekommen.
-</p>
-
-<h1>4. <code>calcurse</code> Grundlagen<a name="basics"></a></h1>
-<h2>4.1 Programmaufruf<a name="basics_invocation"></a></h2>
-<h3>4.1.1 Programmargumente<a name="basics_invocation_commandline"></a></h3>
-<p>
-<code>Calcurse</code> kann mit den folgenden Optionen aufgerufen werden.
-Es werden sowohl kurze als auch lange Optionsangaben unterst&uuml;tzt.</p>
-
-<p>
-<dl>
- <dt><code>-a, --appointment</code></dt>
- <dd>Gibt die Termine des heutigen Tags aus.
- <p class="rq"><span class="valorise">Beachte:</span>
- Die Kalender-Datei, aus der die Termine gelesen
- werden sollen, kann mit mit Hilfe der '-c' Option angegeben werden.</p>
- </dd>
- <dt><code>-c &lt;file&gt;, --calendar &lt;file&gt;</code></dt>
- <dd>Gibt die zu lesende Kalender-Datei an.
- Der Standardkalender ist <code>~/.calcurse/apts</code> (beachte auch
- Abschnitt: <a href="#basics_files"><code>calcurse</code> Dateien</a>).
- </dd>
- <dt><code>-d &lt;date|num&gt;, --day &lt;date|num&gt;</code></dt>
- <dd>Gibt die Termine eines angegebenen Datums oder alle Termine der
- anzugebenden nachfolgenden Tage aus. Somit sind zwei Formate m&ouml;glich:
- <ul>
- <li>Datum: <span class="todo">(possible formats described below).</span></li>
- <li>Anzahl der Tage: 'n'.</li>
- </ul>
- Im ersten Fall wird eine Liste mit allen Terminen des angegebenen
- Datums ausgegeben. Der zweite Fall listet alle folgenden Termine auf,
- die in den n&auml;chsten 'n' Tagen zu erledigen sind.
- Beispiel: Die Eingabe <code>calcurse -d 3</code> gibt alle Termine des
- heutigen und der beiden folgenden Tage aus.
- <div class="todo">
- Possible formats for specifying the date are defined inside the
- general configuration menu (see
- <a href="#options_general">General options</a>), using the
- <code>input_datefmt</code> variable.
- <p class="rq"><span class="valorise">Note:</span> as for the '-a'
- flag, the calendar from which to read the appointments
- can be specified using the '-c' flag.</p>
- </div>
- </dd>
- <dt><code>-D &lt;dir&gt;, --directory &lt;dir&gt;</code></dt>
- <dd>
- <div class="todo">
- Specify the data directory to use. This option is
- incompatible with -c. If not specified, the
- default directory is <code>'~/.calcurse/'</code>.
- </div>
- </dd>
- <dt><code>-h, --help</code></dt>
- <dd>Gibt eine Hilfe zu den unterst&uuml;tzten Optionen aus.
- </dd>
- <dt><code>-i &lt;file&gt;, --import &lt;file&gt;</code></dt>
- <dd>
- <div class="todo">
- Import the icalendar data contained in <code>file</code>.
- </div>
- </dd>
- <dt><code>-n, --next</code></dt>
- <dd>Gibt den Termin aus, der innerhalb der kommenden 24 Stunden als
- n&auml;chstes stattfindet.
- Die dargestellte Zeitangabe weist darauf hin, in wie viel Stunden
- und Minuten der Termin beginnen wird.
- <p class="rq"><span class="valorise">Beachte:</span>
- Die Kalender-Datei, aus der die Termine gelesen
- werden sollen, kann mit mit Hilfe der '-c' Option angegeben werden.</p>
- </dd>
- <dt><code>-N, --note</code></dt>
- <dd>
- <div class="todo">
- When used with the '-a' or '-t' flag, also print note content
- if one is associated with the displayed item.
- </div>
- </dd>
- <dt><code>-r[num], --range[=num]</code></dt>
- <dd>
- <div class="todo">
- Print events and appointments for the num number of
- days and exit. If no num is given, a range of 1 day
- is considered.
- </div>
- </dd>
- <dt><code>-s[date], --startday[=date]</code></dt>
- <dd>
- <div class="todo">
- Print events and appointments from date and exit.
- If no date is given, the current day is considered.
- </div>
- </dd>
- <dt><code>-S&lt;regex&gt;, --search=&lt;regex&gt;</code></dt>
- <dd>
- <div class="todo">
- When used with the '-a', '-d', '-r', '-s', or '-t' flag,
- print only the items having a description that matches the given
- regular expression.
- </div>
- </dd>
- <dt><code>--status</code></dt>
- <dd>
- <div class="todo">
- Display the status of running instances of calcurse. If
- calcurse is running, this will tell if the interactive
- mode was launched or if calcurse is running in background.
- The process pid will also be indicated.
- </div>
- </dd>
- <dt><code>-t[num], --todo[=num]</code></dt>
- <dd>Gibt die 'todo' Liste aus.
- Wird die optionale Angabe <code>num</code> &uuml;bergeben, werden nur diejenigen
- Aufgaben angezeigt, denen die Priori&auml;t <code>num</code> zugewiesen wurde.<br>
- <div class="todo">
- The priority number must be between 1 (highest) and 9 (lowest). It is also possible
- to specify '0' for the priority, in which case only completed tasks will be shown.</p>
- </div>
- </dd>
- <dt><code>-v, --version</code></dt>
- <dd>Gibt die aktuelle Version von Calcurse aus.
- </dd>
- <dt><code>-x[format], --export[=format]</code></dt>
- <dd><div class="todo">
- Export user data to specified format. Events, appointments and
- todos are converted and echoed to stdout.
- Two possible formats are available: ical and pcal
- (see section <a href="#links_others">Links</a> below).
- If the optional argument <code>format</code> is not given,
- ical format is selected by default.
- </div>
- <p class="rq"><span class="valorise">Beachte:</span>
- leiten Sie die Ausgabe in eine Datei, etwa wie im folgenden Beispiel:
- <code>$ calcurse --export > my_data.dat</code></p>
- </dd>
-</dl>
-
-<h3>4.1.2 Umgebungsvariable f&uuml;r i18n<a name="basics_invocation_variable"></a></h3>
-<p>
- <code>calcurse</code> kann mit Unterst&uuml;tzung f&uuml;r verschiedene Sprachen
- kompiliert werden (siehe <a
- href="#install_requirements_gettext"><code>gettext</code>
- Bibliothek</a>). Um Meldungen in anderen Sprachen zu erhalten,
- sollte zun&auml;chst gepr&uuml;ft werden, ob die <code>po/LINGUAS</code> Datei verf&uuml;gbar ist.
- Diese Datei zeigt alle verf&uuml;gbaren Sprachen durch
- zweibuchstabige K&uuml;rzel an (beispielsweise steht <span class="emp">fr</span>
- f&uuml;r Franz&ouml;sisch). Ist Ihre Muttersprache nicht aufgef&uuml;hrt, w&auml;re es
- nat&uuml;rlich gro&szlig;artig, wenn Sie sich an der &Uuml;bersetzung von <code>calcurse</code>
- in andere Sprachen beteiligen k&ouml;nnten (siehe Abschnitt <a href="#contribute">Wie kann
- ich einen Beitrag leisten?</a>).</p>
-<p>
- Wird Ihre Sprache bereits unterst&uuml;tzt, k&ouml;nnen Sie
- <code>calcurse</code> mit dem folgenden Aufruf starten:</p>
- <pre>LC_ALL=fr_FR calcurse</pre>
-<p>
- wobei <span class="emp">fr_FR</span> der Name der gew&uuml;nschten Spracheausgabe ist und durch
- das K&uuml;rzel Ihrer Sprache ersetzt werden kann.</p>
-<p>
- Zus&auml;tzlich sollten Sie den verwendeten Zeichensatz angeben, da in einigen F&auml;llen
- Sonderzeichen wie etwa Akzente und Umlaute nicht korrekt dargestellt werden.
- Auf den der entsprechende Sprache gew&uuml;nschten Zeichensatz wird am Anfang der po-Datei
- hingewiesen. Der Datei fr.po k&ouml;nnen Sie beispielsweise entnehmen, dass der Zeichensatz
- iso-8859-1 verwendet wird. Sie k&ouml;nnten <code>calcurse</code> folgenderma&szlig;en
- aufrufen:</p>
- <pre>LC_ALL=fr_FR.ISO8859-1 calcurse</pre>
-
-<div class="todo">
-<h3>4.1.3 Other environment variables<a name="basics_invocation_environment"></a></h3>
-<p>
- The following environment variables affect the way <code>calcurse</code>
- operates:</p>
- <dl>
- <dt><code>VISUAL</code></dt>
- <dd>Specifies the external editor to use for writing notes.
- </dd>
- <dt><code>EDITOR</code></dt>
- <dd>If the <code>VISUAL</code> environment variable
- is not set, then <code>EDITOR</code> will be used as
- the default external editor. If none of those variables are set,
- then <code>/usr/bin/vi</code> is used instead.
- </dd>
- <dt><code>PAGER</code></dt>
- <dd>Specifies the default viewer to be used for reading notes.
- If this variable is not set, then <code>/usr/bin/less</code> is used.
- </dd>
- </dl>
-</div>
-
-<h2>4.2 Benutzer-Interface<a name="basics_interface"></a></h2>
-<h3>4.2.1 Nicht interaktiver Modus<a name="basics_interface_noninteractive"></a></h3>
-<p>
-Wird <code>calcurse</code> mit den Optionen:
-<code>-a</code>, <code>-d</code>, <code>-h</code>,
-<code>-n</code>, <code>-t</code>, <code>-v</code>, <code>-x</code>
-gestartet, wird das Programm im nicht-interaktiven Modus
-ausgef&uuml;hrt. Das bedeutet, dass die gew&uuml;nschten Informationen
-ausgegeben werden und das Programm anschlie&szlig;end sofort wieder beendet
-wird.</p>
-<p>
-Durch das Einbinden von <code>calcurse --todo --appointment</code> in eine init config
-Datei ist es beispielsweise m&ouml;glich, sich seine zu erledigenden Aufgaben
-und alle Termine des heutigen Tages beim Logon anzeigen zu lassen.</p>
-
-
-<h3>4.2.2 Interaktiver Modus<a name="basics_interface_interactive"></a></h3>
-<div class="todo">
- <p class="rq"><span class="valorise">Note:</span>
- Key bindings that are indicated in this manual correspond to
- the default ones, defined when <code>calcurse</code> is launched
- for the first time. If those key bindings do not suit user's needs,
- it is possible to change them within the keys configuration menu
- (see <a href="#options_keys">key bindings</a>).</p>
-</div>
-<p>
-Wird keine, oder nur Option -c angegeben, startet
-<code>calcurse</code> im interaktiven Modus. In diesem Modus erh&auml;lt
-man ein Interface mit drei unterschiedlichen Panels, einer
-Benachrichtigungszeile, sowie einer Status-Zeile (siehe unten).
-Die einzelnen Panels lassen sich durch die 'TAB'-Taste ansteuern.</p>
-<pre>
-
- Termin-Panel---. .---Kalender-Panel
- | |
- v v
- +------------------------------------++----------------------------+
- | Termine || Kalender |
- |------------------------------------||----------------------------|
- | (|) 6. April 2006 || April 2006 |
- | || Mo Di Mi Do Fr Sa So |
- | || 1 2 |
- | || 3 4 5 6 7 8 9 |
- | || 10 11 12 13 14 15 16 |
- | || 17 18 19 20 21 22 23 |
- | || 24 25 26 27 28 29 30 |
- | || |
- | |+----------------------------+
- | |+----------------------------+
- | || Aufgaben | todo-
- | ||----------------------------| Panel
- | || | |
- | || | |
- | || |&lt;--.
- | || |
- +------------------------------------++----------------------------+
- |---[ So 2006-10-22 | 10:11:43 ]---(apts)----&gt; 01:20 :: lunch &lt;---|&lt;--.
- +------------------------------------------------------------------+ Benachrichtigungszeile
- | ? Hilfe S Speichern H/L -/+1 Tag Tab &auml;ndere Ansicht |
- | Q Beenden G Gehe zu J/K -/+1 Woche C Einstellung |&lt;-.
- +------------------------------------------------------------------+ |
- |
- Statuszeile
-
-</pre>
-<p>
-Das Kalender-Panel hebt den gew&uuml;nschten Tag farblich hervor, w&auml;hrend
-das Termin-Panel die Liste mit Terminen des angesteuerten Tags
-anzeigt. Das todo-Panel dagegen zeigt eine Liste mit den zu
-erledigenden Aufgaben, die keinem bestimmten Tage zugeordnet sind.</p>
-
-<div class="todo">
-<p>
- Depending on the selected view, the calendar could either display
- a monthly (default as shown in previous figure) or weekly view.
- The weekly view would look like the following:</p>
- <pre>
-
-+------------------------------------+
-| Calendar |
-|----------------------------(# 13)--|
-| Mon Tue Wed Thu Fri Sat Sun |
-| 29 30 31 01 02 03 04 |
-| <----+-- slice 1: 00:00 to 04:00 AM
-| -- -- -- -- -- -- |
-| <----+-- slice 2: 04:00 to 08:00 AM
-| -- -- -- -- -- -- |
-| <----+-- slice 3: 08:00 to 12:00 AM
-| - -- -- -- -- -- -- - <-+-- midday
-| <----+-- slice 4: 12:00 to 04:00 PM
-| -- -- -- -- -- -- |
-| <----+-- slice 5: 04:00 to 08:00 PM
-| -- -- -- -- -- -- |
-| <----+-- slice 6: 08:00 to 12:00 PM
-+------------------------------------+
-
- </pre>
-<p>
- The current week number is displayed on the top-right side of the panel
- (<span class="emp"># 13</span> meaning it is the 13th week of the year
- in the above example). The seven days of the current week are displayed
- in column. Each day is divided into slices of 4 hours each (6 slices in
- total, see figure above). A slice will appear in a different color if
- an appointment falls into the corresponding time-slot.
-</p>
-</div>
-
-<p>
- Im Termin-Panel kann man <span class="emp">'(|)'</span> Symbol vor das
-Datum setzen. Dies zeigt die aktuelle Mondfase. Je nach Mondfase
-k&ouml;nnen die folgenden Symbole erscheinen:
- <dl class="compact">
- <dt>'<code> |) </code>':</dt>
- <dd>Halbmond, erste H&auml;lfte</dd>
- <dt>'<code> (|) </code>':</dt>
- <dd>Vollmond</dd>
- <dt>'<code> (| </code>':</dt>
- <dd>Halbmond, letzte H&auml;lfte</dd>
- <dt>'<code> | </code>':</dt>
- <dd>Neumond</dd>
- <dt>Kein Symbol:</dt>
- <dd>die Mondfase ist keinem der oberen zuzuordnen</dd>
- </dl>
-</p>
-<p>
-Die letzten beiden Zeilen des Interfaces zeigen die Status-Zeile, die
-&uuml;ber die m&ouml;glichen Befehle und ihre entsprechenden Tasten
-informiert.</p>
-<p>
-Direkt &uuml;ber der Statuszeile befindet sich die Benachrichtigungszeile, die
-von links nach rechts gesehen die folgenden Elemente anzeigt: Das aktuelle Datum,
-die aktuelle Uhrzeit, die momentan verwendete Kalenderdatei (im obigen Beispiel
-die standardm&auml;&szlig;ig verwendete Kalenderdatei apts [Vergleiche hierzu
-den folgenden Abschnitt]) und der n&auml;chste Termin, der in den kommenden 24
-Stunden ansteht. Im Beispiel ist dies der Termin lunch, der in 1 Stunde und
-zwanzig Minuten beginnt.</p>
-<p class="rq"><span class="valorise">Beachte:</span>
-Einige Handlungen, wie beispielsweise das Ver&auml;ndern oder
-Hinzuf&uuml;gen eines Termins, ben&ouml;tigen Texteingaben, die
-mithilfe des eingebauten Eingabeeditors eingegeben werden.</p>
-<p>
-Geht eine Zeile &uuml;ber die Bildschirmzeile hinaus, wird dies innerhalb
-des Editors durch die Zeichen '&gt;', '*', und '&lt;' dargestellt.
-Dadurch wird in der letzten Spalten darauf hingewiesen, dass sich
-vor, vor und hinter, beziehungsweise nur hinter der momentanten
-Position weiterer Text befindet. Gegebenenfalls wird Zeile
-horizontal gescrollt.</p>
-<p>
-Dar&uuml;berhinaus sind einigen Editierfunktionen spezielle Tastenk&uuml;rzel
-zugewiesen, die in der folgenden &Uuml;bersicht zusammengefasst sind.
-Hierbei steht '^' f&uuml;r die Taste 'Strg' beziehungsweise 'Ctrl':
-<dl class="compact">
- <dt><code>^a</code>:</dt>
- <dd>Positioniert den Cursor an den Anfang der Eingabezeile</dd>
- <dt><code>^b</code>:</dt>
- <dd>Bewegt den Cursor r&uuml;ckw&auml;rts</dd>
- <dt><code>^d</code>:</dt>
- <dd>L&ouml;scht das folgende Zeichen</dd>
- <dt><code>^e</code>:</dt>
- <dd>Positioniert den Cursor an das Ende der Eingabezeile</dd>
- <dt><code>^h</code>:</dt>
- <dd>L&ouml;scht das vorhergehende Zeichen</dd>
- <dt><code>^k</code>:</dt>
- <dd>L&ouml;scht die Eingabe von der aktuellen Cursorposition bis
- an das Zeileende</dd>
- <dt><code>ESCAPE</code>:</dt>
- <dd>Bricht die Bearbeitung ab</dd>
-</dl>
-</p>
-
-<div class="todo">
-<h2>4.3 Background mode<a name="basics_daemon"></a></h2>
-
-<p>When the daemon mode is enabled in the notification configuration menu
-(see <a href="#options_notify">Notify-bar settings</a>), <code>calcurse</code> will stay
-in background when the user interface is not running. In background mode,
-<code>calcurse</code> checks for upcoming appointments and runs the user-defined
-notification command when necessary. When the user interface is started again,
-the daemon automatically stops.</p>
-
-<p><code>calcurse</code> background activity can be logged (set the
-<code>notify-daemon_log</code> variable in the notification configuration
-<a href="#options_notify">menu</a>), and in that case, information about the daemon
-start and stop time, reminders' command launch time, signals received... will be written
-in the <code>daemon.log</code> file (see section <a href="#basics_files">files</a>).</p>
-
-<p>
-Using the <code>--status</code> command line option (see section
-<a href="#basics_invocation_commandline">Command line arguments</a>),
-one can know if <code>calcurse</code> is currently running in background or not.
-If the daemon is running, a message like the following one will be displayed (the pid of
-the daemon process will be shown):
-<pre>calcurse is running in background (pid 14536)</pre>
-
-<p class="rq"><span class="valorise">Note:</span>
-To stop the daemon, just send the <code>TERM</code> signal to it, using a command such as:
-<code>'kill daemon_pid'</code>, where <span class="emp">daemon_pid</span> is the process id
-of the daemon (14536 in the above example).
-</p>
-</div>
-
-<h2>4.4 <code>calcurse</code> Dateien<a name="basics_files"></a></h2>
-<p>
-Die folgende Verzeichnisstruktur wird im $HOME-Verzeichnis angelegt,
-<div class="todo">(or in the directory you specified with the -D option)</div>
-wenn <code>calcurse</code> das erste Mal gestartet wird:</p>
-<pre>
-$HOME/.calcurse/
- |___notes/
- |___conf
- |___keys
- |___apts
- |___todo
-</pre>
-<dl class="compact">
- <dt><code>notes/</code>:</dt>
- <dd><span class="todo">this subdirectory contains descriptions of the notes
- which are attached to appointments, events or todos. One text file is
- created per note, whose name is built using mkstemp(3) and should be
- unique, but with no relation with the corresponding item's description.</span></dd>
- <dt><code>conf</code>:</dt>
- <dd>Datei enth&auml;lt die Informationen zur Benutzerkonfiguration.</dd>
- <dt><code>keys</code>:</dt>
- <dd><span class="todo">this file contains the user-defined key bindings</span></dd>
- <dt><code>apts</code>:</dt>
- <dd>Datei enth&auml;lt alle Termine.</dd>
- <dt><code>todo</code>:</dt>
- <dd>Datei enth&auml;lt die todo-Liste.</dd>
-</dl>
-
-<div class="todo">
- <p class="rq"><span class="valorise">Note:</span>
- If the logging of calcurse daemon activity was set in the notification
- configuration menu, the extra file <code>daemon.log</code> will appear
- in calcurse data directory. This file contains logs about calcurse activity
- when running in background.
- </p>
-</div>
-
-
-<div class="todo">
-<h2>4.5 Import/Export capabilities<a name="basics_import_export"></a></h2>
-<p>
- The import and export capabilities offered by <code>calcurse</code>
- are described below.
-</p>
-
-<h3>4.5.1 Import<a name="basics_import"></a></h3>
-<p>
- Data in icalendar format as described in the rfc2445 specification
- (see <a href="#links_others">links</a> section below) can be imported
- into calcurse. Calcurse ical parser is based on version 2.0 of this
- specification, but for now on, only a subset of it is supported.
-</p>
-<p>
- The following icalendar properties are handled by calcurse:
- <ul>
- <li><code>VTODO</code> items:<br>
- "PRIORITY", "VALARM", "SUMMARY", "DESCRIPTION"</li>
- <li><code>VEVENT</code> items:<br>
- "DTSTART", "DTEND", "DURATION", "RRULE", "EXDATE", "VALARM", "SUMMARY",
- "DESCRIPTION"</li>
- </ul>
-</p>
-<p>
- The icalendar "DESCRIPTION" property will be converted into calcurse format
- by adding a note to the item. If a "VALARM" property is found, the item
- will be flagged as important and the user will get a notification (this is
- only applicable to appointments).
-</p>
-<p>
- Here are the properties that are not implemented:
- <ul>
- <li>negative time durations are not taken into account (item is skipped)</li>
- <li>some recurence frequences are not recognize:<br>
- "SECONDLY" / "MINUTELY" / "HOURLY"</li>
- <li>some recurrence keywords are not recognized
- (all those starting with 'BY'):<br>
- "BYSECOND" / "BYMINUTE" / "BYHOUR" / "BYDAY" / "BYMONTHDAY"<br>
- "BYYEARDAY" / "BYWEEKNO" / "BYMONTH" / "BYSETPOS"<br>
- plus "WKST"</li>
- <li>the recurrence exception keyword "EXRULE" is not recognized</li>
- <li>timezones are not taken into account</li>
- </ul>
-</p>
-
-<h3>4.5.2 Export<a name="basics_export"></a></h3>
-<p>
- Two possible export formats are available: <code>ical</code> and
- <code>pcal</code> (see section <a href="#links_others">Links</a> below
- to find out about those formats).
-</p>
-</div>
-
-<h2>4.6 Online Hilfe<a name="basics_help"></a></h2>
-<p>
-Das integrierte Hilfe-System kann jederzeit mit '?' aufgerufen
-werden. Informationen &uuml;ber bestimmte Befehle k&ouml;nnen mit der
-entsprechenden Taste des Befehls aufgerufen werden.
-</p>
-
-<h1>5. Optionen<a name="options"></a></h1>
-<p>
-S&auml;mtliche in <code>calcurse</code> ver&auml;nderbaren Parameter lassen sich
-Konfigurationsmen&uuml; einstellen. Dr&uuml;cken Sie hierzu die Taste 'C'.
-Daraufhin erscheint ein Untermen&uuml; mit vier weiteren Wahlm&ouml;glichkeiten:
-Das erneute Bet&auml;tigen von 'C' f&uuml;hrt Sie zu den Farbeinstellungen und
-&uuml;ber 'L' gelangen Sie in ein Untermen&uuml;, in dem Sie die Anordnung der
-drei Panel &auml;ndern k&ouml;nnen. Dr&uuml;cken Sie 'G' um ins Auswahlmen&uuml;
-der allgemeinen Optionen zu gelangen.
-<span class="todo">pressing 'K' opens the key bindings configuration
-menu.</span>
-Zu guter Letzt k&ouml;nnen Sie die
-Einstellungen der Benachrichtigungszeile &auml;ndern, indem Sie die Taste 'N'
-bet&auml;tigen.</p>
-
-<h2>5.1 Allgemeine Optionen<a name="options_general"></a></h2>
-<p>
-Die im Folgenden beschriebenen Optionen steuern <code>calcurse</code>s
-allgemeines Verhalten.</p>
-<dl>
- <dt><code>automatisches_Speichern</code>
- (Voreinstellung: <span class="emp">ja</span>)</dt>
- <dd>Ist diese Option aktiviert, werden die Benutzerdaten automatisch beim
- Verlassen gespeichert.
- <p class="rq"><span class="valorise">warnung:</span>
- Beim Verlassen werden keine Daten gespeichert,
- wenn <code>automatisches_Speichern</code> auf <span class="emp">nein</span> gesetzt wurde. Um Ihre
- Eingaben dennoch zu speichern, m&uuml;ssen Sie als Nutzer die Taste 'S'
- bet&auml;tigen.</p>
- </dd>
-
- <dt><code><span class="todo">periodic_save</code>
- (default: <span class="emp">0</span>)</span></dt>
- <dd><span class="todo">If different from '0', user's data will be automatically
- saved every <span class="emp">periodic_save</span> minutes.
- When an automatic save is performed, two asterisks
- (i.e. '<code>**</code>') will appear on the top right-hand side
- of the screen).</span>
- </dd>
-
- <dt><code>Beenden_best&auml;tigen</code>
- (Voreinstellung: <span class="emp">ja</span>)</dt>
- <dd>Wenn <span class="emp">ja</span> eingestellt worden ist, wird nachgefragt, ob das
- Programm wirklich beenden werden soll. Wurde <span class="emp">nein</span> gew&auml;hlt,
- wird das Programm durch die Eingabe von 'Q' ohne Nachfrage sofort beendet.</dd>
- <dt><code>L&ouml;schen_best&auml;tigen</code>
- (Voreinstellung: <span class="emp">ja</span>)</dt>
- <dd>Wurde <span class="emp">ja</span> eingestellt, fragt das Programm nach, ob ein
- Eintrag wirklich gel&ouml;scht werden soll (entweder ein todo-Eintrag oder
- ein Termin). Wurde <span class="emp">nein</span> gew&auml;hlt, wird beim Dr&uuml;cken von 'D'
- ohne Nachfrage gel&ouml;scht.</dd>
- <dt><code>Systemdialoge_&uuml;berspringen</code>
- (Voreinstellung: <span class="emp">nein</span>)</dt>
- <dd>Durch Setzen auf <span class="emp">ja</span> werden die Dialoge beim Speichern und
- Laden umgangen. N&uuml;tzlich, wenn es mal schnell gehen muss.</dd>
- <dt><code>Fortschrittsanzeige_&uuml;berspringen</code>
- (Voreinstellung: <span class="emp">nein</span>)</dt>
- <dd>Wird diese Option aktiviert, wird die beim Speichern von Daten normalerweise
- erscheinende Fortschrittsanzeige nicht mehr angezeigt.
- Ist diese Option auf <span class="emp">nein</span> gesetzt, werden ein
- Zustandsbalken und der Name der zu speichernden Datei (siehe
- Abschnitt <a href="#basics_files">Calcurse Dateien</a>) angezeigt.</dd>
-
- <dt><code><span class="todo">calendar_default_view</span></code>
- (default: <span class="emp">0</span>)</dt>
- <dd><span class="todo">If set to <span class="emp">0</span>, the monthly calendar view will be
- displayed by default otherwise it is the weekly view that will be displayed.</span>
- </dd>
-
- <dt><code>Wochenbeginn_am_Montag</code>
- (Voreinstellung: <span class="emp">ja</span>)</dt>
- <dd>Es ist m&ouml;glich zwischen Montag und Sonntag als ersten Tag der Woche
- zu w&auml;hlen. Wird die Option auf <span class="emp">ja</span> gesetzt, wird Montag
- als erster Tag der Woche festgelegt. Ist <span class="emp">nein</span> gew&auml;hlt,
- beginnt die Woche sonntags.</dd>
-
- <dt><code><span class="todo">output_datefmt</code>
- (default: <span class="emp">%D</span>)</span></dt>
- <dd><span class="todo">This option indicates the format to be used when displaying dates
- in non-interactive mode. Using the default values, dates are displayed the
- following way: <span class="emp">mm/dd/aa</span>.
- You can see all of the possible formats by typing <code>man 3 strftime</code>
- inside a terminal.</span></dd>
-
- <dt><code><span class="todo">input_datefmt</code>
- (default: <span class="emp">1</span>)</span></dt>
- <dd><span class="todo">This option indicates the format that will be used to enter dates in
- <span class="emp">calcurse</span>. Four choices are available:</span>
- <ol>
- <li>mm/dd/yyyy</li>
- <li>dd/mm/yyyy</li>
- <li>yyyy/mm/dd</li>
- <li>yyyy-mm-dd</li>
- </ol>
- </dd>
-</dl>
-
-<div class="todo">
-<h2>5.2 Key bindings<a name="options_keys"></a></h2>
-<p>
- One can define it's own keybindings within the 'Keys' configuration
- menu. The default keys look like the one used by the <code>vim</code>
- editor, especially the displacement keys. Anyway, within this
- configuration menu, users can redefine all of the keys available from
- within calcurse's user interface.</p>
-<p>
- To define new keybindings, first highlight the action to which it will
- apply. Then, delete the actual key binding if necessary, and add a new
- one. You will then be asked to press the key corresponding to the new
- binding. It is possible to define more than one key binding for a single
- action.</p>
-<p>
- An automatic check is performed to see if the new key binding
- is not already set for another action. In that case, you will be asked
- to choose a different one. Another check is done when exiting from this
- menu, to make sure all possible actions have a key associated with it.</p>
-<p>
- The following keys can be used to define bindings:
- <ul>
- <li>lower-case, upper-case letters and numbers, such as 'a', 'Z', '0'</li>
- <li>CONTROL-key followed by one of the above letters</li>
- <li>escape, horizontal tab, and space keys</li>
- <li>arrow keys (up, down, left, and right)</li>
- <li>'HOME' and 'END' keys</li>
- </ul> </p>
-<p>
- While inside the key configuration menu, an online help is available for
- each one of the available actions. This help briefly describes what the
- highlighted action is used for.</p>
-</div>
-
-<h2>5.3 Textfarben einstellen<a name="options_colors"></a></h2>
-<p>
-<code>calcurse</code> Textfarben k&ouml;nnen nach eigenen
-Vorlieben eingestellt werden. Um die Standartfarben zu wechseln,
-zeigt die Konfigurationsseite m&ouml;gliche Farbwerte f&uuml;r
-Vordergrund und Hintergrund. Benutze die Pfeiltasten zum bewegen und
-'X' bzw. die Leertaste um eine Farbe zu w&auml;hlen. Benutzer k&ouml;nnen
-das gew&auml;hlte Farbschema vorher betrachten. Die Liste enth&auml;lt
-auch den Eintrag f&uuml;r die Standartfarben des Terminals.</p>
-<div class="todo">
-<p>
- 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 bar. A black and white theme is also
- available, in order to support non-color terminals.</p>
-</div>
-<p class="rq"><span class="valorise">Beachte:</span>
- Der Farbunterst&uuml;tzung ist vom verwendeten Terminal und des der
- Umgebungsvariablen <code>$TERM</code> zugewiesenen Werts abh&auml;ngig.
- Es erscheint eine Fehlermeldung, wenn versucht wird die Farbeinstellung
- zu &auml;ndern, obwohl das Terminal keine Farben unterst&uuml;tzt.
- Wenn sie sicher sind, dass ihr Terminal Farben darstellen kann,
- in <code>calcurse</code> aber keine Farben erscheinen, versuchen Sie
- die <code>$TERM</code> Variable auf einen anderen Wert zu setzen
- (etwa <span class="emp">xterm-xfree86</span>).
-</p>
-
-<h2>5.4 Layout einstellen<a name="options_layout"></a></h2>
-<p>
-Das Layout bezieht sich auf die Positionen der einzelnen Panel. Das
-Standard-Layout zeigt das Kalender-Panel in der oberen linken Ecke des
-Terminals, das todo-Panel befindet sich in der unteren rechten Ecke
-und das Termin-Panel auf der linken Seite des Terminals (vgl. die
-im Abschnitt <a href="#basics_interface_interactive">Interaktiver Modus</a>
-dargestellte Zeichnung des Standard-Layouts).
-Durch Auswahl eines anderen Layouts kann der Benutzer das
-Erscheinungsbild von <code>calcurse</code> seinen eigenen W&uuml;nschen
-entsprechend anpassen.</p>
-
-<div class="todo">
-<p>
- The following option is used to modify the layout configuration:</p>
- <dl>
- <dt><code>layout</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>Eight different layouts are to be chosen from (see layout
- configuration screen for the description of the available layouts).</dd>
- </dl>
-</div>
-
-<div class="todo">
-<h2>5.5 Sidebar configuration<a name="options_sidebar"></a></h2>
-<p>
- The sidebar is the part of the screen which contains two panels:
- the calendar and, depending on the chosen layout, either the todo
- list or the appointment list.</p>
-<p>
- The following option is used to change the width of the sidebar:</p>
- <dl>
- <dt><code>side-bar_width</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>Width (in percentage, 0 being the minimum width) of the side bar.</dd>
- </dl>
-</div>
-
-<h2>5.6 Benachrichtigungszeile einstellen<a name="options_notify"></a></h2>
-<p>
- Folgende Optionen &auml;ndern das Verhalten der Benachrichtigungszeile:</p>
- <dl>
- <dt><code>Benachrichtigungszeile_anzeigen</code> (Voreinstellung: <span class="emp">ja</span>)</dt>
- <dd>Mit dieser Option legen Sie fest, ob die Benachrichtigungszeile anzeigt werden soll. </dd>
- <dt><code>Benachrichtigungszeile_Datum</code> (Voreinstellung: <span class="emp">%a %F</span>)</dt>
- <dd>Hiermit kann das Format festgelegt werden, wie das aktuelle Datum innerhalb
- der Benachrichtigungszeile angezeigt werden soll.
- Die m&ouml;glichen Formatdefinitionen k&ouml;nnen Sie sich durch die Eingabe
- von <code>man 3 strftime</code> auf der Kommandozeile anzeigen lassen.</dd>
- <dt><code>Benachrichtigungszeile_Uhrzeit</code> (Voreinstellung: <span class="emp">%T</span>)</dt>
- <dd>Hiermit kann das Format festgelegt werden, wie die aktuelle Uhrzeit
- innerhalb der Benachrichtigungszeile angezeigt werden soll.
- Die m&ouml;glichen Formatdefinitionen k&ouml;nnen Sie sich durch die
- Eingabe von <code>man 3 strftime</code> auf der Kommandozeile anzeigen
- lassen.</dd>
- <dt><code>Benachrichtigungszeile_Alarm</code> (Voreinstellung: <span class="emp">300</span>)</dt>
- <dd>Beginnt ein Termin innerhalb der n&auml;chsten, in 'Benachrichtigungszeile_Alarm'
- festgelegten Sekunden, wird der Termin innerhalb der Benachrichtigungszeile
- blinkend dargestellt. Auf diese Weise wird der Nutzer auf einen baldigen Termin
- hingewiesen.
- Au&szlig;erdem wird der Befehl, der durch
- <code>Benachrichtigungszeile_Befehl</code> definiert ist, ausgef&uuml;hrt.</dd>
- <dt><code>Benachrichtigungszeile_Befehl</code> (Voreinstellungt: <span class="emp">printf '\a'</span>)</dt>
- <dd>Diese Option zeigt an, welcher Befehl ausgef&uuml;hrt wird,
- wenn ein bevorstehender Termin durch 'wichtig' gekennzeichnet ist.
- Dieser Befehl wird auf dem Terminal des Benutzers ausgef&uuml;hrt.
- Die <code>$SHELL</code> Umgebungsvariable wird bei der Wahl des
- richtigen Terminals ber&uuml;cksichtigt. Ist diese Variable nicht
- gesetzt, wird stattdessen <code>/bin/sh</code> zur Ausf&uuml;hrung
- gew&auml;hlt.
- <p class="rq"><span class="valorise">Beispiel:</span>
- Der <code>mail</code> Befehl ist auf dem System
- des Benutzer verf&uuml;gbar. Man kann den folgenden Befehl benutzen,
- um an bevorstehende Termine erinnert zu werden (die Beschreibung
- des Termins wird ebenso ber&uuml;cksichtigt im Mailkopf):</p>
- <code>
-calcurse --next | mail -s "[calcurse] upcoming appointment!" user@host.com
- </code>
- </dd>
-
- <dt><code><span class="todo">notify-daemon_enable</code>
- (default: <span class="emp">no</span>)</span></dt>
- <dd><span class="todo">If set to yes, daemon mode will be enabled, meaning <code>calcurse</code>
- will run into background when the user's interface is exited. This will allow the
- notifications to be launched even when the interface is not running. More details
- can be found in section <a href="#basics_daemon">'Background mode'</a>.</span>
- </dd>
- <dt><code><span class="todo">notify-daemon_log</code>
- (default: <span class="emp">no</span>)</span></dt>
- <dd><span class="todo">If set to yes, <code>calcurse</code> daemon activity will be logged (see section
- <a href="#basics_files">files</a></span>).
- </dd>
-</dl>
-
-<h1>6. Bekannte Fehler<a name="known_bugs"></a></h1>
-<p>
- Es kommt vor, dass W&ouml;rter bei Verwendung der schwarz/wei&szlig;en
- Farbkombination falsch hervorgehoben werden, wenn die
- <code>$TERM</code> Variable auf <span class="emp">xterm-color</span> gesetzt ist.
- Um diesen Fehler zu vermeiden, sollte nach Aussage von
- Thomas E. Dickey (zust&auml;ndig f&uuml;r <code>xterm</code>),
- <span class="emp">xterm-xfree86</span> an Stelle f&uuml;r <span class="emp">xterm-color</span> als
- <code>$TERM</code> Variable gesetzt werden:</p>
- <blockquote class="rq">
- "The xterm-color value for $TERM is a bad choice for XFree86 xterm
- because it is commonly used for a terminfo entry which happens to
- not support bce. Use the xterm-xfree86 entry which is distributed
- with XFree86 xterm (or the similar one distributed with ncurses)."
- </blockquote>
-
-<h1>7. Mitteilung von Fehlern und Anregungen<a name="bugs"></a></h1>
-<p>
-Bitte mailen Sie Fehler oder auch Anregungen an:</p>
-<pre>calcurse @ culot . org</pre>
-<p>
-Oder an den Autor:</p>
-<pre>frederic @ culot . org</pre>
-
-<h1>8. Wie kann ich einen Beitrag leisten?<a name="contribute"></a></h1>
-<p>
-Wenn Sie gerne dieses Projekt unterst&uuml;tzen m&ouml;chten, k&ouml;nnen Sie mir
-zuerst eine kurze R&uuml;ckmeldung geben. Was finden Sie an diesem Programm gut
-oder was k&ouml;nnte besser sein? Gibt es vielleicht Programmeigenschaften, die
-Sie vermissen? Teilen Sie sie mir mit!</p>
-<p>
-Von nun an ist es auch m&ouml;glich, sich an der &Uuml;bersetzung der Programmmitteilungen
-und der Dokumentation von <code>calcurse</code> zu beteiligen. </p>
- <p class="rq"><span class="valorise">Beachte:</span>
- Jegliche Unterst&uuml;tzung <code>calcurse</code>
- in andere Sprachen zu &uuml;bersetzen ist sehr willkommen. Bevor Sie beginnen, sollten
- Sie jedoch eine E-Mail an <code>calcurse-i18n @ culot . org</code> senden: So erfahren Sie,
- ob jemand die &Uuml;bersetzung in Ihrer Sprache schon begonnen hat.</p>
-
-<h2>8.1 &Uuml;bersetzung der Dokumentation<a name="contribute_documentation"></a></h2>
-<p>
- Das <span class="emp">doc/</span> Verzeichnis des Quellcodearchivs enth&auml;lt bereits
- &uuml;bersetzte Versionen des <code>calcurse</code> Handbuchs.
- Ist eine &Uuml;bersetzung in Ihrer Sprache noch nicht vorhanden,
- w&auml;re es gro&szlig;artig, wenn Sie eine solche erstellen k&ouml;nnten.</p>
-<p>
- Kopieren Sie dazu eine der vorhandenen Version mit dem Dateinamen
- <code>manual_XX.html</code>, wobei <span class="emp">XX</span>
- das entsprechende K&uuml;rzel Ihrer Sprache ist. &Uuml;bersetzen Sie diese
- Datei anschlie&szlig;end und senden Sie sie dann an den Autor
- (siehe <a href="#bugs">Mitteilung von Fehlern und Anregungen</a>), damit Ihre
- &Uuml;bersetzung der n&auml;chsten <code>calcurse</code> Version
- hinzugef&uuml;gt werden kann.</p>
-
-<h2>8.2 <code>calcurse</code> i18n<a name="contribute_i18n"></a></h2>
-<p>
- Wie bereits erw&auml;hnt, verwendet <code>calcurse</code> die <code>gettext</code>
- Utilities um mehrsprachige Programmmitteilungen zu erzeugen.
- Dieser Abschnitt informiert Sie dar&uuml;ber, wie Programmmitteilungen in Ihre
- Muttersprache &uuml;bersetzt werden. Dieses Howto zur &Uuml;bersetzung von
- <code>calcurse</code> mittels <code>gettext</code> ist nat&uuml;rlich nur als Einstieg
- gedacht und mit Absicht recht knapp gehalten. Um umfassendere Informationen
- zu erhalten und sich die gro&szlig;e weite Welt der Internationalisierung von Software zu
- erschlie&szlig;en, sollten Sie die Seite der <code>GNU
- gettext</code>-Anleitung besuchen:</p>
- <pre>http://www.gnu.org/software/gettext/manual/</pre>
-<p>
- An der &Uuml;bersetzung sind im Grunde drei verschiedene Entwickler beteiligt:
- Programmierer, Sprachkoordinator und &Uuml;bersetzer.
- Nach einem kurzen &Uuml;berblick, wie so etwas funktioniert, werden anschlie&szlig;end die
- Aufgaben des &Uuml;bersetzers beschrieben.</p>
-
-
-<h3>8.2.1 &Uuml;berblick<a name="contribute_i18n_overview"></a></h3>
-<p>
-Um Text in der Muttersprache des Benutzers erscheinen zu lassen, sind zwei Schritte n&ouml;tig:
-<span class="emp">Internationalisierung</span>
-(i18n) und <span class="emp">Lokalisierung</span> (l10n).</p>
-<p>
- Bei der i18n geht es darum, <code>calcurse</code> auf die Unterst&uuml;tzung mehrerer
- Sprachen vorzubereiten. Dies ist die Aufgabe des Programmierers, der die zu
- &uuml;bersetzenden Texte markiert und andererseits sicherstellen muss, dass zur Laufzeit
- des Programms der &uuml;bersetzt Text erscheint.</p>
-<p>
- Bei der l10n geht es darum, dem bereits internationalisierten - also i18n markierten -
- <code>calcurse</code> die entsprechende &Uuml;bersetzung des Benutzers zur Verf&uuml;gung
- zu stellen.
- Gem&auml;&szlig; den Umgebungsvariablen ersetzt <code>calcurse</code> die zuvor vom
- Programmierer markierten Texte durch die entsprechenden &Uuml;bersetzungen.</p>
-<p>
- Die zu &uuml;bersetzenden Texte werden also zun&auml;chst vom Programmierer im
- <code>C</code>-Quellcode markiert und in einem Template (<span class="emp">calcurse.pot</span> -
- die Dateierweiterung <span class="emp">pot</span> steht f&uuml;r <span class="emp">portable object template</span>)
- gesammelt. Anschlie&szlig;end wird der Inhalt dieses Templates mit den Dateien, die
- die &Uuml;bersetzungen enthalten zusammengef&uuml;hrt (<span class="emp">fr.po</span> enth&auml;lt
- beispielsweise die Franz&ouml;sische &Uuml;bersetzung (<span class="emp">po</span> steht hierbei
- f&uuml;r <span class="emp">portable object</span>, also ein von Menschen les- und ver&auml;nderbares
- Dateiformat),
- Der &Uuml;bersetzer kann diese Datei &ouml;ffnen, die enthaltenen Texte &uuml;bersetzen
- und sie dann an den Programmierer zur&uuml;ck senden.
- Wird das Programm compiliert, erzeugt der Compiler (aus Gr&uuml;nden der Effizienz)
- eine bin&auml;re Version dieser Datei, die sp&auml;ter installiert wird (<span class="emp">fr.mo</span>
- - <span class="emp">mo</span> steht f&uuml;r <span class="emp">machine object</span>; dieses Format kann nur von
- Programmen gelesen werden). <code>calcurse</code> nutzt diese Datei zur Laufzeit,
- um die Texte in Abh&auml;ngigkeit der lokalen Einstellungen des Benutzers zu
- &uuml;bersetzen.</p>
-
-
-<h3>8.2.2 Aufgaben des &Uuml;bersetzers<a name="contribute_i18n_translator"></a></h3>
-<p>
- Wenn Sie mit der &Uuml;bersetzung in eine neue Sprache beginnen m&ouml;chten,
- finden Sie hierzu die n&ouml;tigen Schritte:</p>
- <ul>
- <li>Finden Sie zun&auml;chst das K&uuml;rzel Ihrer Sprache heraus.
- Beispielsweise ist das K&uuml;rzel f&uuml;r Franz&ouml;sisch 'fr_FR', oder
- einfach nur 'fr'. Diesen Wert muss der Benutzer der Umgebungsvariablen
- <code>LC_ALL</code> zuweisen, um die Software &uuml;bersetzt starten zu k&ouml;nnen
- (siehe <a href="#basics_invocation_variable">Umgebungsvariable f&uuml;r i18n</a>).</li>
- <li>Wechseln Sie dann ins <span class="emp">po/</span> Verzeichnis und erzeugen Sie aus dem Template
- mit dem folgendem Aufruf eine neue po-Datei:
- <code>'msginit -i calcurse.pot -o fr.po -l fr --no-translator'</code>
- Sollte <code>msginit</code> nicht auf Ihrem System installiert sein, kopieren Sie einfach
- die Datei <span class="emp">calcurse.pot</span> nach <span class="emp">fr.po</span> und &auml;nderen Sie den Inhalt am
- Anfang der Datei von Hand.</li>
- </ul>
-<p>
- Wurde die Datei <span class="emp">fr.po</span> erstellt, kann mit der eigentlichen &Uuml;bersetzung
- begonnen werden.</p>
-
-
-<h3>8.2.3 po-Dateien<a name="contribute_i18n_po-files"></a></h3>
-<p>
- Das Format der po-Dateien ist relativ einfach. po-Dateien gliedern sich in lediglich
- vier Bestandteile:</p>
- <ol>
- <li><span class="emp">location Zeilen:</span> geben an, wo sich der Text befindet (Name der Datei und Zeilennummer).</li>
- <li><span class="emp">msgid Zeilen:</span> der urspr&uuml;ngliche, also zu &uuml;bersetzende Text.</li>
- <li><span class="emp">msgstr Zeilen:</span> der &uuml;bersetzte Text.</li>
- <li><span class="emp">Zeilen, die mit '#' beginnen:</span> Kommentare (einige mit spezieller Bedeutung,
- wie wir weiter unten noch sehen werden).</li>
- </ol>
-<p>
- &Uuml;bersetzen Sie die <span class="emp">msgid</span> Zeilen und tragen Sie den &uuml;bersetzten Text in die
- sich direkt darunterbefindlichen, mit <span class="emp">msgstr</span> gekennzeichneten Zeilen ein.</p>
-<p>
- <span class="valorise">Einige Anmerkungen:</span>
- <dl>
- <dt><span class="emp">Fuzzy Texte</span></dt>
- <dd>Einige Texte sind mit <code>"#, fuzzy"</code> kommentiert. <code>calcurse</code> nutzt
- derart markierte Texte nicht. Ein als fuzzy markierter Text deutet entweder darauf hin, dass
- der Text schon &uuml;bersetzt wurde, aber die Stelle im Programmcode ver&auml;ndert wurde, oder
- aber es handelt sich um einen neuen Text, f&uuml;r welchen <code>gettext</code> eine sog. 'wild
- guess' vornimmt, also selbst eine &Uuml;bersetzung versucht.
- Das bedeutet, die &Uuml;bersetzung sollte noch einmal &uuml;berarbeitet werden.
- Manchmal wurde der Originaltext ver&auml;ndert, weil ein Rechtschreibfehler korrigiert wurde.
- In einem solchen Fall muss nichts ge&auml;ndert werden.
- Mitunter ist die &Uuml;bersetzung aber nicht mehr passend oder schlichtweg falsch und muss
- abge&auml;ndert werden.
- Entfernen Sie die <code>"#, fuzzy"</code>-Zeilen, wenn Sie mit Ihrer &Uuml;bersetzung fertig
- sind, damit <code>calcurse</code> die &uuml;bersetzten Zeilen wieder verwendet und anzeigt.</dd>
- <dt><span class="emp">c-Format Texte und besondere Sequenzen</span></dt>
- <dd>Einige Texte haben folgende Kommentare: <code>"#, c-format"</code>.
- Dieser Kommentar weist darauf hin, dass Teile dieses Textes eine besondere Bedeutung
- haben und dieser Text nicht ver&auml;ndert werden sollte.
- Beispielsweise bedeuten die %-Sequenzen, wie <code>"%s"</code>, dass <code>calcurse</code>
- dort Text einf&uuml;gen wird. Es ist also wichtig, diese nicht zu ver&auml;ndern.
- Ebenso kommen \-Sequenzen , wie etwa <code>\n</code> oder <code>\t</code> vor. Bitte
- nehmen Sie auch hier keine Ver&auml;nderungen vor. Erstere stellt das Zeilenende dar,
- letztere einen Tabulator.</dd>
- <dt><span class="emp">&Uuml;bersetzungen k&ouml;nnen in Bl&ouml;cke geschrieben werden</span></dt>
- <dd>Sollten Zeilen zu lang werden, k&ouml;nnen sie auf mehrere verteilt werden:
- <pre>
-msgid ""
-"some very long line"
-"another line"
- </pre>
- <dt><span class="emp">po-Header</span></dt>
- <dd>Ganz zu Anfang einer po-Datei befindet sich der Header, der einige Informationen enth&auml;lt.
- Die wichtigste Information ist der Zeichensatz. Er sollte diesem &auml;hnlich sein
- <pre>
-"Content-Type: text/plain; charset=utf-8\n"
- </pre>
- Auch das &Uuml;bersetzer-Feld sollte ausgef&uuml;llt sein, damit potentielle Mitstreiter,
- die sich an der &Uuml;bersetzung beteiligen wollen, mit Ihnen Kontakt aufnehmen k&ouml;nnen.
- Ebenso k&ouml;nnen von anderen entdeckte Fehler an den &Uuml;bersetzer gemeldet werden. Geben
- Sie Ihren Namen an, oder tragen Sie Ihre E-Mail-Adresse ein. Zum Beispiel folgenderma&szlig;en:
- <pre>
-"Last-Translator: Frederic Culot &lt;frederic@culot.org&gt;\n"
- </pre></dd>
- <dt><span class="emp">Kommentare</span></dt>
- <dd>Das Hinzuf&uuml;gen von Kommentaren (Zeilen beginnen mit dem '#' Zeichen) ist eine gute
- M&ouml;glichkeit, um Probleme und &Uuml;bersetzungsschwierigkeiten anderen besser
- mitteilen zu k&ouml;nnen.</dd>
- <dt><span class="emp">L&auml;ngen der Texte</span></dt>
- <dd><code>calcurse</code> ist ein curses/Konsolen Programm und ist somit stark von der
- Gr&ouml;&szlig;e des Terminals (Anzahl der Spalten) abh&auml;ngig. Dies sollte bei
- der &Uuml;bersetzung ber&uuml;cksichtigt werden. H&auml;ufig m&uuml;ssen Texte in
- eine einzige Zeile passen (Standardl&auml;nge ist 80 Zeichen).
- &Uuml;bersetzen Sie nicht blindlings darauf los! Versuchen Sie herauszufinden, wo der
- Text angezeigt wird, um die &Uuml;bersetzung entsprechend anzupassen.</dd>
- <dt><span class="emp">Ein paar n&uuml;tzliche Programme</span></dt>
- <dd>Das po-Dateiformat ist sehr einfach und kann mit jedem Standard-Editor bearbeitet werden.
- Es gibt aber auch einige spezielle Tools die das Erstellen und &Auml;nder der po-Dateien
- vereinfachen:
- <ul>
- <li><code>poEdit</code> (<a
- href="http://www.poedit.org/" target="_blank">
- http://www.poedit.org/</a>)</li>
- <li><code>KBabel</code> (<a
- href="http://i18n.kde.org/tools/kbabel/" target="_blank">
- http://i18n.kde.org/tools/kbabel/</a>)</li>
- <li><code>GTranslator</code> (<a
- href="http://gtranslator.sourceforge.net/" target="_blank">
- http://gtranslator.sourceforge.net/</a>)</li>
- <li><code>Emacs</code> po mode</li>
- <li><code>Vim</code> po mode</li>
- </ul>
- </dd>
- <dt><span class="emp">Zu Schluss noch</span></dt>
- <dd>Ich hoffe es wird Ihnen Freude bereiten, wenn Sie sich an diesem Projekt und
- seiner Internationalisierung beteiligen :). Bitte scheuen Sie sich nicht, mir
- eine E-Mail, <span class="emp">frederic @ culot . org</span>, zu schreiben, sollten noch Fragen offen sein.</dd>
- </dl>
-
-
-<h1>9. Links<a name="links"></a></h1>
-<p>
-Dieser Abschnitt enth&auml;lt Links und Angaben, die Sie interessieren
-k&ouml;nnten.</p>
-
-<h2>9.1 <code>calcurse</code> Internetseite<a name="links_homepage"></a></h2>
-<p>
-Die Internetseite des Projekts <code>calcurse</code> lautet:</p>
-<pre>http://culot.org/calcurse</pre>
-
-<h2>9.2 <code>calcurse</code> Ank&uuml;ndigungsliste<a name="links_list"></a></h2>
-<p>
-Wenn Sie an <code>calcurse</code> Interesse gefunden haben und Sie gerne
-&uuml;ber Neuerscheinungen informiert werden m&ouml;chten, k&ouml;nnen Sie sich
-gerne in <code>calcurse</code>s Ank&uuml;ndigungsliste eintragen.</p>
-<p>
-Sobald eine neue Version ver&ouml;ffentlicht wird, werden Sie per E-Mail &uuml;ber
-die neusten Eigenschaften von <code>calcurse</code> informiert<br>
-Um sich in die Liste einzutragen, schicken Sie einfach eine E-Mail mit dem Betreff
-"subscribe" an <span class="emp">calcurse-announce @ culot . org</span>.</p>
-
-<h2>9.3 <code>calcurse</code> RSS feed<a name="links_rss"></a></h2>
-<p>
- Um &uuml;ber neue Programmversionen informiert zu werden, k&ouml;nnen Sie
- auch einfach den folgenden RSS-Feed aufrufen:</p>
- <pre>http://culot.org/calcurse/news_rss.xml</pre>
-<p>
- Sobald eine neue <code>calcurse</code>-Version verf&uuml;gbar ist wird
- der RSS-Feed aktualisiert und enth&auml;lt eine Beschreibung der neu
- hinzugekommenen Programmfunktionen.</p>
-
-<h2><div class="todo">9.4 Other links</div><a name="links_others"></a></h2>
-<div class="todo">
-<p>
- You may want to look at the ical format specification (rfc2445) at:
- <pre>http://tools.ietf.org/html/rfc2445</pre>
-<p>
- The pcal project page can be found at:
- <pre>http://pcal.sourceforge.net/</pre>
-</div>
-
-<h1>10. Danksagungen<a name="thanks"></a></h1>
-<p>
-Folgenden Leuten m&ouml;chte ich gerne f&uuml;r Ihre Unterst&uuml;tzung danken, ohne
-die dieses Projekt nicht m&ouml;glich gewesen w&auml;re. Hier ist die Liste
-derjenigen, denen ich Danke sagen m&ouml;chte:
-<ul>
-<li>Alex f&uuml;r die Patches, Hilfen und Erl&auml;uterungen zur <code>C</code> Programmierung.</li>
-<li>Gwen f&uuml;rs Testen und die Anregungen, wie <code>calcurse</code> verbessert werden kann.</li>
-<li>Herbert f&uuml;r das Binary-Packet auf FreeBSD</li>
-<li>Zul f&uuml;r das Binary-Packet auf NetBSD</li>
-<li>Wain, Steffen und Ronald f&uuml;r das Binary-Packet auf Archlinux</li>
-<li>Kevin, Ryan, und fEnIo f&uuml;r das Binary-Packet auf Debian und Ubuntu.</li>
-<li>Pascal f&uuml;r das Binary-Packet auf Slackware</li>
-<li>Alexandre f&uuml;r das Binary-Packet auf Mac OsX und Darwin.</li>
-<li>Igor f&uuml;r das Binary-Packet auf ALT Linux</li>
-<li>Joel f&uuml;r sein Kalender-Skript, das mich zum Calcurse-Layout inspiriert hat.</li>
-<li>Michael Schulz und Chris M. f&uuml;r die &Uuml;bersetzung der Dokumentation ins Deutsche.</li>
-<li>Jose Lopez f&uuml;r die &Uuml;bersetzung der Dokumentation ins Spanische.</li>
-<li>Neil Williams f&uuml;r die &Uuml;bersetzung ins Englische.</li>
-<li>Leandro Noferini f&uuml;r die &Uuml;bersetzung ins Italienisches.</li>
-<li>Tony f&uuml;r seine Patches, welche die Funktion
-recur_item_inday() verbessern half
-<span class="todo">, and for implementing the date format configuration options</span></li>
-<li>Jeremy Roon f&uuml;r die &Uuml;bersetzung ins Dutch.</li>
-<li><div class="todo">Erik Saule for its patch implementing the '-N', '-s', '-S', '-r' and '-D' flags</div></li>
-<li>Leute die Programme geschrieben haben, die ich mag und mich inspiriert haben, insbesondere:
- <ul>
- <li><code>vim</code> f&uuml;r die Befehlssteuerung</li>
- <li><code>orpheus</code> und <code>abook</code> f&uuml;r die Dokumentation</li>
- <li><code>pine</code> und <code>aptitude</code> f&uuml;r das Text-Benutzer-Interface</li>
- <li><span class="todo"><code>tmux</code> for coding style</span></li>
- </ul></li>
-</ul>
-</p>
-<p>
-Und zuletzt, vielen vielen Dank an alle <code>calcurse</code>
-Benutzer, die mir Ihr Feedback mitgeteilt haben.</p>
-
-<div class="footer">
- Copyright &copy; 2004-2010 Frédéric Culot<br>
- German translation by Michael Schulz
- <code>&lt;bloodshower .at. web .dot. de&gt;</code>, and Chris.<br>
- Calcurse version 2.8 - Last change: March 29, 2010<br>
-</div>
-</div>
-
-</body>
-</html>
diff --git a/doc/manual_en.html b/doc/manual_en.html
deleted file mode 100644
index 89ba526..0000000
--- a/doc/manual_en.html
+++ /dev/null
@@ -1,1331 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<!--
-/*
- * $calcurse: manual_en.html,v 1.29 2010/03/29 18:18:02 culot Exp $
- *
- * Copyright (c) 2004-2010 Frederic Culot <frederic@culot.org>
- * All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * - Redistributions of source code must retain the above
- * copyright notice, this list of conditions and the
- * following disclaimer.
- *
- * - Redistributions in binary form must reproduce the above
- * copyright notice, this list of conditions and the
- * following disclaimer in the documentation and/or other
- * materials provided with the distribution.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- */
--->
-
-<html>
-<head>
-<title>CALCURSE documentation</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css" media="all">
- @import url(manual.css);
-</style>
-</head>
-<body>
-
-<div id="mainContent">
-
-<h1 id="title">
-<span class="main">CALCURSE - text-based organizer</span></h1>
-
-<div class="warn">
-<h1>Abstract</h1> This manual describes <code>calcurse</code> functionnalities,
-and how to use them. The installation from source is first described, together
-with the available command line arguments. The user interface
-is then presented, with all of the customizable options that change
-<code>calcurse</code> behavior. Last, bug reporting procedure is explained, as
-well as the way one can contribute to <code>calcurse</code> development.
-</div>
-
-<div id="toc">
-<h1>Table of Contents</h1>
-<ul>
- <li><a href="#intro">1. Introduction</a></li>
- <li><a href="#overview">2. Overview</a>
- <ul>
- <li><a href="#overview_history">2.1 Creation history</a></li>
- <li><a href="#overview_features">2.2 Important features</a></li>
- </ul></li>
- <li><a href="#install">3. Installation</a>
- <ul>
- <li><a href="#install_requirements">3.1 Requirements</a>
- <ul>
- <li><a href="#install_requirements_ncurses">3.1.1 <code>ncurses</code> library</a></li>
- <li><a href="#install_requirements_gettext">3.1.2 <code>gettext</code> library</a></li>
- </ul></li>
- <li><a href="#install_process">3.2 Install process</a></li>
- </ul></li>
- <li><a href="#basics">4. <code>calcurse</code> basics</a>
- <ul>
- <li><a href="#basics_invocation">4.1 Invocation</a>
- <ul>
- <li><a href="#basics_invocation_commandline">4.1.1 Command line arguments</a></li>
- <li><a href="#basics_invocation_variable">4.1.2 Environment variable for i18n</a></li>
- <li><a href="#basics_invocation_environment">4.1.3 Other environment variables</a></li>
- </ul></li>
- <li><a href="#basics_interface">4.2 User interface</a>
- <ul>
- <li><a href="#basics_interface_noninteractive">4.2.1 Non-interactive mode</a></li>
- <li><a href="#basics_interface_interactive">4.2.2 Interactive mode</a></li>
- </ul></li>
- <li><a href="#basics_daemon">4.3 Background mode</a></li>
- <li><a href="#basics_files">4.4 <code>calcurse</code> files</a></li>
- <li><a href="#basics_import_export">4.5 Import/Export capabilities</a>
- <ul>
- <li><a href="#basics_import">4.5.1 Import</a></li>
- <li><a href="#basics_export">4.5.2 Export</a></li>
- </ul></li>
- <li><a href="#basics_help">4.6 Online help</a></li>
- </ul></li>
- <li><a href="#options">5. Options</a>
- <ul>
- <li><a href="#options_general">5.1 General options</a></li>
- <li><a href="#options_keys">5.2 Key bindings</a></li>
- <li><a href="#options_colors">5.3 Color themes</a></li>
- <li><a href="#options_layout">5.4 Layout configuration</a></li>
- <li><a href="#options_sidebar">5.5 Sidebar configuration</a></li>
- <li><a href="#options_notify">5.6 Notify-bar settings</a></li>
- </ul></li>
- <li><a href="#known_bugs">6. Known bugs</a></li>
- <li><a href="#bugs">7. Reporting bugs and feedback</a></li>
- <li><a href="#contribute">8. How to contribute?</a>
- <ul>
- <li><a href="#contribute_documentation">8.1 Translating documentation</a></li>
- <li><a href="#contribute_i18n">8.2 <code>calcurse</code> i18n</a>
- <ul>
- <li><a href="#contribute_i18n_overview">8.2.1 Overview</a></li>
- <li><a href="#contribute_i18n_translator">8.2.2 Translator tasks</a></li>
- <li><a href="#contribute_i18n_po-files">8.2.3 po-files</a></li>
- </ul></li>
- </ul></li>
- <li><a href="#links">9. Links</a>
- <ul>
- <li><a href="#links_homepage">9.1 <code>calcurse</code> homepage</a></li>
- <li><a href="#links_list">9.2 <code>calcurse</code> announce list</a></li>
- <li><a href="#links_rss">9.3 <code>calcurse</code> RSS feed</a></li>
- <li><a href="#links_others">9.4 Other links</a></li>
- </ul></li>
- <li><a href="#thanks">10. Thanks</a></li>
-</ul>
-</div>
-
-<h1>1. Introduction<a name="intro"></a></h1>
-<p>
-<code>calcurse</code> is a text-based calendar and scheduling application. It helps
-keeping track of events, appointments and everyday tasks.
-A configurable notification system reminds user of upcoming deadlines,
-and the curses based interface can be customized to suit user needs.
-All of the commands are documented within an online help system.
-</p>
-
-<h1>2. Overview<a name="overview"></a></h1>
-<h2>2.1 Creation history<a name="overview_history"></a></h2>
-<p>
- I started thinking about this project when I was finishing
- my Ph.D. in Astrophysics... It started to be a little hard
- to organize myself, and I really needed a good tool to help
- me in that difficult task ;)
-</p>
-<p>
- I like programs which use Text User Interfaces, because they
- are simple, fast, portable and efficient, so I thought about
- working on coding a simple calendar using such an interface.
- Moreover, I wanted to go on learning the <code>C</code>
- language, which I only used for a while during my undergraduate
- studies. So I thought that would be the good project to start
- in order to get organized and to learn about a few
- <code>C</code> things !
-</p>
-<p>
- Unfortunately, I finished my Ph.D. before finishing
- <code>calcurse</code>,
- but anyway, I still wanted to work on it, hoping it would
- be helpful to other people. So here it is...
-</p>
-<p>
- But why 'calcurse' anyway ? Well, it is simply the
- concatenation of 'CALendar' and 'nCURSEs', the name of the
- library used to build the user interface.
-</p>
-
-<h2>2.2 Important features<a name="overview_features"></a></h2>
-<p>
- <code>Calcurse</code> is multi-platform and intended to be
- lightweight, fast and reliable. It is to be used inside a
- console or terminal, locally or on a distant machine within
- an ssh (or similar) connection.
-</p>
-<p>
- <code>Calcurse</code> can be run in two different modes :
- interactive or non-interactive mode. The first mode allows
- oneself to view its own personal organizer almost everywhere,
- thanks to the text-based interface.
- The second mode permits to easily build reminders just by adding
- <code>calcurse</code> with appropriate command line arguments
- inside a cron tab or within a shell init script.
-</p>
-<p>
- Moreover, <code>calcurse</code> was created with the end-user
- in mind, and tends to be as friendly as possible. This means
- a complete on-line help system, together with having all of
- the possible actions displayed at any time inside a status bar.
- The user interface is configurable, and one can choose
- between several color and layout combinations.
- Key bindings are also configurable, to fit everyone's needs.
- Last, a configurable notification system reminds user of upcoming
- appointments. The reminders are sent even if the user's interface
- is not running, as calcurse is able to run in background.
-</p>
-
-<h1>3. Installation<a name="install"></a></h1>
-<h2>3.1 Requirements<a name="install_requirements"></a></h2>
-<h3>3.1.1 <code>ncurses</code> library<a name="install_requirements_ncurses"></a></h3>
-<p>
- <code>Calcurse</code> requires only a <code>C</code> compiler, such as
- <code>cc</code> or <code>gcc</code>, and the <code>ncurses</code>
- library.
- It would be very surprising not to have a valid <code>ncurses</code>
- library already installed on your computer, but if not, you can
- find it at the following url :</p>
- <pre>http://ftp.gnu.org/pub/gnu/ncurses/</pre>
-<p>
- <p class="rq"><span class="valorize">Note:</span>
- It is also possible to link <code>calcurse</code> against the
- <code>ncursesw</code> library (ncurses with support for unicode).
- However, UTF-8 is not yet supported by <code>calcurse</code>.</p>
-
-<h3>3.1.2 <code>gettext</code> library<a name="install_requirements_gettext"></a></h3>
-<p>
- <code>calcurse</code> supports internationalization
- (<span class="emp">i18n</span> hereafter) through the <code>gettext</code>
- utilities. This means <code>calcurse</code> can produce
- multi-lingual messages if compiled with native language
- support (i.e. <span class="emp">NLS</span>).
-</p>
-<p>
- However,
- <span class="emp">NLS</span> is
- optionnal and if you do not want to have support for
- multi-lingual messages, you can disable this feature. This is
- done by giving the <code>--disable-nls</code> option to
- <code>configure</code> (see section <a
- href="#install_process">Install process</a>).
- To check if the <code>gettext</code> utilities are
- installed on your system, you can search for the
- <code>libintl.h</code> header file for instance:</p>
- <pre>locate libintl.h</pre>
-<p>
- If this header file is not found, then you can obtain the
- <code>gettext</code> sources at the following url :</p>
- <pre>http://ftp.gnu.org/pub/gnu/gettext/</pre>
-<p>
- <p class="rq"><span class="valorize">Note:</span>
- Even if <code>libintl.h</code> is found on your
- system, it can be wise to specify its location during the <a
- href="#install_process">install process</a>, by using the
- <code>--with-libintl-prefix</code> option with
- <code>configure</code>. Indeed, the <code>configure</code>
- could fail to locate this library if installed in an uncommon
- place.</p>
-
-
-<h2>3.2 Install process<a name="install_process"></a></h2>
-<p>
- First you need to gunzip and untar the source archive:</p>
- <pre>tar zxvf calcurse-2.8.tar.gz</pre>
-<p>
- Once you meet the requirements and have extracted the archive,
- the install process is quite simple, and follows the standard
- three steps process:
- <ol>
- <li><code>./configure</code></li>
- <li><code>make</code></li>
- <li><code>make install</code> (may require root privilege)</li>
- </ol>
-</p>
-<p>
- Use <code>./configure --help</code> to obtain a list of
- possible options.
-</p>
-
-<h1>4. <code>calcurse</code> basics<a name="basics"></a></h1>
-<h2>4.1 Invocation<a name="basics_invocation"></a></h2>
-<h3>4.1.1 Command line arguments<a name="basics_invocation_commandline"></a></h3>
-<p>
- <code>calcurse</code> takes the following options from the
- command line (both short and long options are supported):</p>
- <p>
-
- <dl>
- <dt><code>-a, --appointment</code></dt>
- <dd>
- Print the appointments and events for the current day and exit.
- <p class="rq"><span class="valorise">Note:</span> the calendar from
- which to read the appointments can be specified using the '-c'
- flag.</p>
- </dd>
- <dt><code>-c &lt;file&gt;, --calendar &lt;file&gt;</code></dt>
- <dd>
- Specify the calendar file to use.
- The default calendar is <code>~/.calcurse/apts</code>
- (see section <a href="#basics_files"><code>calcurse</code>
- files</a>).
- </dd>
- <dt><code>-d &lt;date|num&gt;, --day &lt;date|num&gt;</code></dt>
- <dd>
- Print the appointments for the given date or for the
- given number of upcoming days, depending on the argument
- format. Two possible formats are supported:
- <ul>
- <li>a date (possible formats described below).</li>
- <li>a number 'n'.</li>
- </ul>
- In the first case, the appointment list for the
- specified date will be returned, while in the second
- case the appointment list for the 'n' upcoming days
- will be returned.
- As an example, typing <code>calcurse -d 3</code>
- will display your appointments for today, tomorrow,
- and the day after tomorrow.
- Possible formats for specifying the date are defined inside the
- general configuration menu (see
- <a href="#options_general">General options</a>), using the
- <code>input_datefmt</code> variable.
-
- <p class="rq"><span class="valorise">Note:</span> as for the '-a'
- flag, the calendar from which to read the appointments
- can be specified using the '-c' flag.</p>
- </dd>
- <dt><code>-D &lt;dir&gt;, --directory &lt;dir&gt;</code></dt>
- <dd>
- Specify the data directory to use. This option is
- incompatible with -c. If not specified, the
- default directory is <code>'~/.calcurse/'</code>.
- </dd>
- <dt><code>-h, --help</code></dt>
- <dd>
- Print a short help text describing the supported
- command-line options, and exit.</dd>
- <dt><code>-i &lt;file&gt;, --import &lt;file&gt;</code></dt>
- <dd>
- Import the icalendar data contained in <code>file</code>.
- </dd>
- <dt><code>-n, --next</code></dt>
- <dd>
- Print the next appointment within upcoming 24 hours and exit.
- The indicated time is the number of hours and minutes left
- before this appointment.
- <p class="rq"><span class="valorise">Note:</span> the calendar
- from which to read the appointments can be specified using the
- '-c' flag.</p>
- </dd>
- <dt><code>-N, --note</code></dt>
- <dd>
- When used with the '-a' or '-t' flag, also print note content
- if one is associated with the displayed item.
- </dd>
- <dt><code>-r[num], --range[=num]</code></dt>
- <dd>
- Print events and appointments for the num number of
- days and exit. If no num is given, a range of 1 day
- is considered.
- </dd>
- <dt><code>-s[date], --startday[=date]</code></dt>
- <dd>
- Print events and appointments from date and exit.
- If no date is given, the current day is considered.
- </dd>
- <dt><code>-S&lt;regex&gt;, --search=&lt;regex&gt;</code></dt>
- <dd>
- When used with the '-a', '-d', '-r', '-s', or '-t' flag,
- print only the items having a description that matches the given
- regular expression.
- </dd>
- <dt><code>--status</code></dt>
- <dd>
- Display the status of running instances of calcurse. If
- calcurse is running, this will tell if the interactive
- mode was launched or if calcurse is running in background.
- The process pid will also be indicated.
- </dd>
- <dt><code>-t[num], --todo[=num]</code></dt>
- <dd>
- Print the 'todo' list and exit. If the optional number
- <code>num</code> is given, then only todos having a priority
- equal to <code>num</code> will be returned. The priority number
- must be between 1 (highest) and 9 (lowest). It is also possible
- to specify '0' for the priority, in which case only completed
- tasks will be shown.</p>
- </dd>
- <dt><code>-v, --version</code></dt>
- <dd>
- Display <code>calcurse</code> version and exit.
- </dd>
- <dt><code>-x[format], --export[=format]</code></dt>
- <dd>
- Export user data to specified format. Events, appointments and
- todos are converted and echoed to stdout.
- Two possible formats are available: ical and pcal
- (see section <a href="#links_others">Links</a> below).
- If the optional argument <code>format</code> is not given,
- ical format is selected by default.
- <p class="rq"><span class="valorise">Note:</span>
- redirect standard output to export data to a file,
- by issuing a command such as:
- <code>$ calcurse --export &gt; my_data.dat</code></p>
- </dd>
- </dl>
-
-<h3>4.1.2 Environment variable for i18n<a name="basics_invocation_variable"></a></h3>
-<p>
- <code>calcurse</code> can be compiled with native language
- support (see <a
- href="#install_requirements_gettext"><code>gettext</code>
- library</a>). Thus, if you wish to have messages displayed
- into your native language, first make sure it is available by
- looking at the <code>po/LINGUAS</code> file.
- This file indicates the set of available languages by showing
- the two-letters corresponding code (for exemple,
- <span class="emp">fr</span>
- stands for french). If you do not find your language, it
- would be greatly appreciated if you could help translating
- <code>calcurse</code> (see the <a href="#contribute">How to
- contribute?</a> section).</p>
-<p>
- If your language is available, run
- <code>calcurse</code> with the following command:</p>
- <pre>LC_ALL=fr_FR calcurse</pre>
-<p>
- where <span class="emp">fr_FR</span> is the locale name in this exemple, but
- should be replaced by the locale corresponding to the desired
- language.</p>
-<p>
- You should also specify the charset to be used, because in some
- cases the accents and such are not displayed correctly.
- This charset is indicated at the beginning of the po file
- corresponding to the desired language. For instance, you can see
- in the fr.po file that it uses the iso-8859-1 charset, so you
- could run <code>calcurse</code> using the following command:</p>
- <pre>LC_ALL=fr_FR.ISO8859-1 calcurse</pre>
-
-<h3>4.1.3 Other environment variables<a name="basics_invocation_environment"></a></h3>
-<p>
- The following environment variables affect the way <code>calcurse</code>
- operates:</p>
- <dl>
- <dt><code>VISUAL</code></dt>
- <dd>Specifies the external editor to use for writing notes.
- </dd>
- <dt><code>EDITOR</code></dt>
- <dd>If the <code>VISUAL</code> environment variable
- is not set, then <code>EDITOR</code> will be used as
- the default external editor. If none of those variables are set,
- then <code>/usr/bin/vi</code> is used instead.
- </dd>
- <dt><code>PAGER</code></dt>
- <dd>Specifies the default viewer to be used for reading notes.
- If this variable is not set, then <code>/usr/bin/less</code> is used.
- </dd>
- </dl>
-
-<h2>4.2 User interface<a name="basics_interface"></a></h2>
-<h3>4.2.1 Non-interactive mode<a name="basics_interface_noninteractive"></a></h3>
-<p>
- When called with at least one of the following arguments:
- <code>-a</code>, <code>-d</code>, <code>-h</code>,
- <code>-n</code>, <code>-t</code>, <code>-v</code>,
- <code>-x</code>,
- <code>calcurse</code> is started in non-interactive mode.
- This means the desired information will be displayed, and
- after that, <code>calcurse</code> simply quits and you are
- driven back to the shell prompt.</p>
-<p>
- That way, one can add a line such as
- <code>'calcurse --todo --appointment'</code>
- in its init config file to display at logon the list of tasks
- and appointments scheduled for the current day. </p>
-
-
-<h3>4.2.2 Interactive mode<a name="basics_interface_interactive"></a></h3>
-<p>
- <p class="rq"><span class="valorise">Note:</span>
- Key bindings that are indicated in this manual correspond to
- the default ones, defined when <code>calcurse</code> is launched
- for the first time. If those key bindings do not suit user's needs,
- it is possible to change them within the keys configuration menu
- (see <a href="#options_keys">key bindings</a>).</p>
-
- <p>When called without any argument or only with the
- <code>-c</code> option, <code>calcurse</code> is started in
- interactive mode. In this mode, you are shown an interface
- containing three different panels which you can browse using
- the 'TAB' key, plus a notification bar and a status bar
- (see figure below).</p>
- <pre>
-
- appointment panel---. .---calendar panel
- | |
- v v
- +------------------------------------++----------------------------+
- | Appointments || Calendar |
- |------------------------------------||----------------------------|
- | (|) April 6, 2006 || April 2006 |
- | ||Mon Tue Wed Thu Fri Sat Sun |
- | || 1 2 |
- | || 3 4 5 6 7 8 9 |
- | || 10 11 12 13 14 15 16 |
- | || 17 18 19 20 21 22 23 |
- | || 24 25 26 27 28 29 30 |
- | || |
- | |+----------------------------+
- | |+----------------------------+
- | || ToDo | todo
- | ||----------------------------| panel
- | || | |
- | || | |
- | || |&lt;--.
- | || |
- +------------------------------------++----------------------------+
- |---[ Mon 2006-11-22 | 10:11:43 ]---(apts)----&gt; 01:20 :: lunch &lt;---|&lt;--.
- +------------------------------------------------------------------+ notify-bar
- | ? Help R Redraw H/L -/+1 Day G GoTo C Config |
- | Q Quit S Save J/K -/+1 Week Tab Chg View |&lt;-.
- +------------------------------------------------------------------+ |
- |
- status bar
-
- </pre>
-<p>
- The first panel represents a calendar which allows to highlight
- a particular day, the second one contains the list of the events
- and appointments on that day, and the last one contains a list
- of tasks to do but which are not assigned to any specific day.</p>
-<p>
- Depending on the selected view, the calendar could either display
- a monthly (default as shown in previous figure) or weekly view.
- The weekly view would look like the following:</p>
- <pre>
-
-+------------------------------------+
-| Calendar |
-|----------------------------(# 13)--|
-| Mon Tue Wed Thu Fri Sat Sun |
-| 29 30 31 01 02 03 04 |
-| <----+-- slice 1: 00:00 to 04:00 AM
-| -- -- -- -- -- -- |
-| <----+-- slice 2: 04:00 to 08:00 AM
-| -- -- -- -- -- -- |
-| <----+-- slice 3: 08:00 to 12:00 AM
-| - -- -- -- -- -- -- - <-+-- midday
-| <----+-- slice 4: 12:00 to 04:00 PM
-| -- -- -- -- -- -- |
-| <----+-- slice 5: 04:00 to 08:00 PM
-| -- -- -- -- -- -- |
-| <----+-- slice 6: 08:00 to 12:00 PM
-+------------------------------------+
-
- </pre>
-<p>
- The current week number is displayed on the top-right side of the panel
- (<span class="emp"># 13</span> meaning it is the 13th week of the year
- in the above example). The seven days of the current week are displayed
- in column. Each day is divided into slices of 4 hours each (6 slices in
- total, see figure above). A slice will appear in a different color if
- an appointment falls into the corresponding time-slot.
-</p>
-
-<p>
- In the appointment panel, one can notice the <span
- class="emp">'(|)'</span> sign just in front of the date.
- This indicates the current phase of the moon.
- Depending on which is the current phase, the following signs can be
- seen:
- <dl class="compact">
- <dt>'<code> |) </code>':</dt>
- <dd>first quarter</dd>
- <dt>'<code> (|) </code>':</dt>
- <dd>full moon</dd>
- <dt>'<code> (| </code>':</dt>
- <dd>last quarter</dd>
- <dt>'<code> | </code>':</dt>
- <dd>new moon</dd>
- <dt>no sign:</dt>
- <dd>phase of the moon does not correspond to any of
- the above ones</dd>
- </dl>
- </p>
- <p>
- At the very bottom of the screen there is a status bar, which
- indicates the possible actions and the corresponding keystrokes.</p>
- <p>
- Just above this status bar is the notify-bar, which indicates
- from left to right : the current date, the current time, the
- calendar file currently in use (apts on the above example, which
- is the default calendar file, see the following section), and
- the next appointment within the upcoming 24 hours. Here it says
- that it will be lunch time in one hour and twenty minutes.</p>
- <p class="rq"><span class="valorise">Note:</span>
- Some actions, such as editing or adding an item,
- require to type in some text. This is done with the help of
- the built-in input line editor.</p>
- <p>
- Within this editor, if a line is longer than the screen width,
- a '&gt;', '*', or '&lt;' character is displayed in the last
- column indicating that there are more character after, before and
- after, or before the current position, respectively. The line is
- scrolled horizontally as necessary.</p>
- <p>
- Moreover, some editing commands are bound to particular control
- characters. Hereafter are indicated the available editing commands
- ('^' stands for the control key):
- <dl class="compact">
- <dt><code>^a</code>:</dt>
- <dd>moves the cursor to the beginning of the input line</dd>
- <dt><code>^b</code>:</dt>
- <dd>moves the cursor backward</dd>
- <dt><code>^d</code>:</dt>
- <dd>deletes one character forward</dd>
- <dt><code>^e</code>:</dt>
- <dd>moves the cursor to the end of the input line</dd>
- <dt><code>^f</code>:</dt>
- <dd>moves the cursor forward</dd>
- <dt><code>^h</code>:</dt>
- <dd>deletes one character backward</dd>
- <dt><code>^k</code>:</dt>
- <dd>deletes the input from the cursor to the end of the line</dd>
- <dt><code>ESCAPE</code>:</dt>
- <dd>cancels the editing</dd>
- </dl>
-</p>
-
-<h2>4.3 Background mode<a name="basics_daemon"></a></h2>
-
-<p>When the daemon mode is enabled in the notification configuration menu
-(see <a href="#options_notify">Notify-bar settings</a>), <code>calcurse</code> will stay
-in background when the user interface is not running. In background mode,
-<code>calcurse</code> checks for upcoming appointments and runs the user-defined
-notification command when necessary. When the user interface is started again,
-the daemon automatically stops.</p>
-
-<p><code>calcurse</code> background activity can be logged (set the
-<code>notify-daemon_log</code> variable in the notification configuration
-<a href="#options_notify">menu</a>), and in that case, information about the daemon
-start and stop time, reminders' command launch time, signals received... will be written
-in the <code>daemon.log</code> file (see section <a href="#basics_files">files</a>).</p>
-
-<p>
-Using the <code>--status</code> command line option (see section
-<a href="#basics_invocation_commandline">Command line arguments</a>),
-one can know if <code>calcurse</code> is currently running in background or not.
-If the daemon is running, a message like the following one will be displayed (the pid of
-the daemon process will be shown):
-<pre>calcurse is running in background (pid 14536)</pre>
-
-<p class="rq"><span class="valorise">Note:</span>
-To stop the daemon, just send the <code>TERM</code> signal to it, using a command such as:
-<code>'kill daemon_pid'</code>, where <span class="emp">daemon_pid</span> is the process id
-of the daemon (14536 in the above example).
-</p>
-
-
-<h2>4.4 <code>calcurse</code> files<a name="basics_files"></a></h2>
-<p>
- The following structure is created in your <code>$HOME</code>
- directory (or in the directory you specified with the -D option)
- the first time <code>calcurse</code> is run :</p>
- <pre>
-$HOME/.calcurse/
- |___notes/
- |___conf
- |___keys
- |___apts
- |___todo
- </pre>
- <dl class="compact">
- <dt><code>notes/</code>:</dt>
- <dd>this subdirectory contains descriptions of the notes
- which are attached to appointments, events or todos. One text file is
- created per note, whose name is built using mkstemp(3) and should be
- unique, but with no relation with the corresponding item's description.</dd>
- <dt><code>conf</code>:</dt>
- <dd>this file contains the user configuration</dd>
- <dt><code>keys</code>:</dt>
- <dd>this file contains the user-defined key bindings</dd>
- <dt><code>apts</code>:</dt>
- <dd>this file contains all of the events and user's appointments</dd>
- <dt><code>todo</code>:</dt>
- <dd>this file contains the todo list</dd>
- </dl>
-
- <p class="rq"><span class="valorise">Note:</span>
- If the logging of calcurse daemon activity was set in the notification
- configuration menu, the extra file <code>daemon.log</code> will appear
- in calcurse data directory. This file contains logs about calcurse activity
- when running in background.
- </p>
-
-<h2>4.5 Import/Export capabilities<a name="basics_import_export"></a></h2>
-<p>
- The import and export capabilities offered by <code>calcurse</code>
- are described below.
-</p>
-
-<h3>4.5.1 Import<a name="basics_import"></a></h3>
-<p>
- Data in icalendar format as described in the rfc2445 specification
- (see <a href="#links_others">links</a> section below) can be imported
- into calcurse. Calcurse ical parser is based on version 2.0 of this
- specification, but for now on, only a subset of it is supported.
-</p>
-<p>
- The following icalendar properties are handled by calcurse:
- <ul>
- <li><code>VTODO</code> items:<br>
- "PRIORITY", "VALARM", "SUMMARY", "DESCRIPTION"</li>
- <li><code>VEVENT</code> items:<br>
- "DTSTART", "DTEND", "DURATION", "RRULE", "EXDATE", "VALARM", "SUMMARY",
- "DESCRIPTION"</li>
- </ul>
-</p>
-<p>
- The icalendar "DESCRIPTION" property will be converted into calcurse format
- by adding a note to the item. If a "VALARM" property is found, the item
- will be flagged as important and the user will get a notification (this is
- only applicable to appointments).
-</p>
-<p>
- Here are the properties that are not implemented:
- <ul>
- <li>negative time durations are not taken into account (item is skipped)</li>
- <li>some recurence frequences are not recognize:<br>
- "SECONDLY" / "MINUTELY" / "HOURLY"</li>
- <li>some recurrence keywords are not recognized
- (all those starting with 'BY'):<br>
- "BYSECOND" / "BYMINUTE" / "BYHOUR" / "BYDAY" / "BYMONTHDAY"<br>
- "BYYEARDAY" / "BYWEEKNO" / "BYMONTH" / "BYSETPOS"<br>
- plus "WKST"</li>
- <li>the recurrence exception keyword "EXRULE" is not recognized</li>
- <li>timezones are not taken into account</li>
- </ul>
-</p>
-
-<h3>4.5.2 Export<a name="basics_export"></a></h3>
-<p>
- Two possible export formats are available: <code>ical</code> and
- <code>pcal</code> (see section <a href="#links_others">Links</a> below
- to find out about those formats).
-</p>
-
-<h2>4.6 Online help<a name="basics_help"></a></h2>
-<p>
- At any time, the built-in help system can be invoked by
- pressing the '?' key. Once viewing the help screens,
- informations on a specific command can be accessed by pressing
- the keystroke corresponding to that command.
- </p>
-
-<h1>5. Options<a name="options"></a></h1>
-<p>
- All of the <code>calcurse</code> parameters are configurable from the
- Configuration menu available when pressing 'C'. You are then
- driven to a submenu with five possible choices : pressing 'C'
- again will lead you to the Color scheme configuration,
- pressing 'L' allows you to choose the layout of the main
- <code>calcurse</code> screen (in other words, where to put the three
- different panels on screen), pressing 'G' permits you to choose between
- different general options, pressing 'K' opens the key bindings configuration
- menu, and last you can modify the notify-bar settings by pressing 'N'.</p>
-
-<h2>5.1 General options<a name="options_general"></a></h2>
-<p>
- These options control <code>calcurse</code> general behavior,
- as described below:</p>
- <dl>
- <dt><code>auto_save</code>
- (default: <span class="emp">yes</span>)</dt>
- <dd>This option allows to automatically save the user's data
- (if set to <span class="emp">yes</span>) when quitting.
- <p class="rq"><span class="valorise">warning:</span>
- No data will be automatically saved if
- <code>auto_save</code> is set to <span class="emp">no</span>.
- This means the user must press 'S' (for saving) in order to
- retrieve its modifications.</p>
- </dd>
- <dt><code>periodic_save</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>If different from '0', user's data will be automatically
- saved every <span class="emp">periodic_save</span> minutes.
- When an automatic save is performed, two asterisks
- (i.e. '<code>**</code>') will appear on the top right-hand side
- of the screen).</p>
- </dd>
- <dt><code>confirm_quit</code>
- (default: <span class="emp">yes</span>)</dt>
- <dd>If set to <span class="emp">yes</span>, confirmation is required before
- quitting, otherwise pressing 'Q' will cause <code>calcurse</code>
- to quit without prompting for user confirmation.
- </dd>
- <dt><code>confirm_delete</code> (default: <span class="emp">yes</span>)</dt>
- <dd>If this option is set to <span class="emp">yes</span>, pressing 'D' for
- deleting an item (either a <span class="emp">todo</span>,
- <span class="emp">appointment</span>,
- or <span class="emp">event</span>), will lead to a prompt asking for user
- confirmation before removing the selected item from the list.
- Otherwise, no confirmation will be needed before deleting the item.
- </dd>
- <dt><code>skip_system_dialogs</code>
- (default: <span class="emp">no</span>)</dt>
- <dd>Setting this option to <span class="emp">yes</span> will result in
- skipping the
- system dialogs related to the saving and loading of data.
- This can be useful to speed up the input/output processes.
- </dd>
- <dt><code>skip_progress_bar</code>
- (default: <span class="emp">no</span>)</dt>
- <dd>If set to <span class="emp">yes</span>, this will cause the disappearing of the
- progress bar which is usually shown when saving data to file.
- If set to <span class="emp">no</span>, this bar will be displayed, together with
- the name of the file being saved
- (see section <a href="#basics_files"><code>calcurse</code> files</a>).
- </dd>
- <dt><code>calendar_default_view</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>If set to <span class="emp">0</span>, the monthly calendar view will be
- displayed by default otherwise it is the weekly view that will be displayed.
- </dd>
- <dt><code>week_begins_on_monday</code>
- (default: <span class="emp">yes</span>)</dt>
- <dd>One can choose between Monday and Sunday as the first day of the
- week. If the option <code>week_begins_on_monday</code> is set to
- <span class="emp">yes</span>, Monday will be first in the calendar view. Else if
- the option is set to <span class="emp">no</span>, then Sunday will be the first
- day of the week.</dd>
- <dt><code>output_datefmt</code>
- (default: <span class="emp">%D</span>)</dt>
- <dd>This option indicates the format to be used when displaying dates
- in non-interactive mode. Using the default values, dates are displayed the
- following way: <span class="emp">mm/dd/aa</span>.
- You can see all of the possible formats by typing <code>man 3 strftime</code>
- inside a terminal.</dd>
- <dt><code>input_datefmt</code>
- (default: <span class="emp">1</span>)</dt>
- <dd>This option indicates the format that will be used to enter dates in
- <span class="emp">calcurse</span>. Four choices are available:
- <ol>
- <li>mm/dd/yyyy</li>
- <li>dd/mm/yyyy</li>
- <li>yyyy/mm/dd</li>
- <li>yyyy-mm-dd</li>
- </ol>
- </dd>
- </dl>
-
-
-<h2>5.2 Key bindings<a name="options_keys"></a></h2>
-<p>
- One can define it's own keybindings within the 'Keys' configuration
- menu. The default keys look like the one used by the <code>vim</code>
- editor, especially the displacement keys. Anyway, within this
- configuration menu, users can redefine all of the keys available from
- within calcurse's user interface.</p>
-<p>
- To define new keybindings, first highlight the action to which it will
- apply. Then, delete the actual key binding if necessary, and add a new
- one. You will then be asked to press the key corresponding to the new
- binding. It is possible to define more than one key binding for a single
- action.</p>
-<p>
- An automatic check is performed to see if the new key binding
- is not already set for another action. In that case, you will be asked
- to choose a different one. Another check is done when exiting from this
- menu, to make sure all possible actions have a key associated with it.</p>
-<p>
- The following keys can be used to define bindings:
- <ul>
- <li>lower-case, upper-case letters and numbers, such as 'a', 'Z', '0'</li>
- <li>CONTROL-key followed by one of the above letters</li>
- <li>escape, horizontal tab, and space keys</li>
- <li>arrow keys (up, down, left, and right)</li>
- <li>'HOME' and 'END' keys</li>
- </ul> </p>
-<p>
- While inside the key configuration menu, an online help is available for
- each one of the available actions. This help briefly describes what the
- highlighted action is used for.</p>
-
-
-<h2>5.3 Color themes<a name="options_colors"></a></h2>
-<p>
- <code>calcurse</code> color theme can be customized to suit user's
- needs. To change the default theme, the configuration page
- displays possible choices for foreground and background colors.
- Using arrows or calcurse displacement keys to move, and 'X' or space
- to select a color, user can preview the theme which will be applied.
- It is possible to keep the terminal's default colors by selecting the
- corresponding choice in the list.</p>
-<p>
- 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 bar. A black and white theme is also
- available, in order to support non-color terminals.</p>
- <p class="rq"><span class="valorise">Notes:</span>
- Depending on your terminal type and on the value of the
- <code>$TERM</code> environnement variable, color could or
- could not be supported. An error message will appear if you
- try to change colors whereas your terminal does not support
- this feature.
- If you do know your terminal supports colors but could
- not get <code>calcurse</code> to display them, try to set your
- <code>$TERM</code> variable to another value (such as
- <span class="emp">xterm-xfree86</span> for instance).
- </p>
-
-
-<h2>5.4 Layout configuration<a name="options_layout"></a></h2>
-<p>
- The layout corresponds to the position of the panels inside
- <code>calcurse</code> screen. The default layout makes the
- calendar panel to be displayed on the top-right corner of the
- terminal, the todo panel on the bottom-right corner, while the
- appointment panel is displayed on the left hand-side of the
- screen (see the figure in section
- <a href="#basics_interface_interactive">Interactive mode</a>
- for an exemple of the default layout).
- By choosing another layout in the configuration screen, user
- can customize <code>calcurse</code> appearence to best suit
- his needs by placing the different panels where needed.</p>
-<p>
- The following option is used to modify the layout configuration:</p>
- <dl>
- <dt><code>layout</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>Eight different layouts are to be chosen from (see layout
- configuration screen for the description of the available layouts).</dd>
- </dl>
-
-<h2>5.5 Sidebar configuration<a name="options_sidebar"></a></h2>
-<p>
- The sidebar is the part of the screen which contains two panels:
- the calendar and, depending on the chosen layout, either the todo
- list or the appointment list.</p>
-<p>
- The following option is used to change the width of the sidebar:</p>
- <dl>
- <dt><code>side-bar_width</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>Width (in percentage, 0 being the minimum width) of the side bar.</dd>
- </dl>
-
-
-<h2>5.6 Notify-bar settings<a name="options_notify"></a></h2>
-<p>
- The following options are used to modify the notify-bar behavior:</p>
- <dl>
- <dt><code>notify-bar_show</code>
- (default: <span class="emp">yes</span>)</dt>
- <dd>This option indicates if you want the notify-bar to be displayed
- or not.</dd>
- <dt><code>notify-bar_date</code>
- (default: <span class="emp">%a %F</span>)</dt>
- <dd>With this option, you can specify the format to be used to
- display the current date inside the notification bar. You can
- see all of the possible formats by typing <code>man 3 strftime</code>
- inside a terminal.</dd>
- <dt><code>notify-bar_time</code>
- (default: <span class="emp">%T</span>)</dt>
- <dd>With this option, you can specify the format to be used to
- display the current time inside the notification bar. You can
- see all of the possible formats by typing <code>man 3 strftime</code>
- inside a terminal.</dd>
- <dt><code>notify-bar_warning</code>
- (default: <span class="emp">300</span>)</dt>
- <dd>When there is an appointment which is flagged as 'important'
- within the next 'notify-bar_warning'
- seconds, the display of that appointment inside the notify-bar
- starts to blink.
- Moreover, the command defined by the <code>notify-bar_command</code>
- option will be launched.
- That way, the user is warned and knows there
- will be soon an upcoming appointment.
- </dd>
- <dt><code>notify-bar_command</code>
- (default: <span class="emp">printf '\a'</span>)</dt>
- <dd>This option indicates which command is to be launched when there is an
- upcoming appointment flagged as 'important'. This command will be
- passed to the user's shell which will interpret it. To know what shell
- must be used, the content of the <code>$SHELL</code> environment variable
- is used. If this variable is not set, <code>/bin/sh</code> is used
- instead.
- <p class="rq"><span class="valorise">Example:</span>
- Say the <code>mail</code> command is available on
- the user's system, one can use the following command to get notified by
- mail of an upcoming appointment (the appointment description will also
- be mentioned in the mail body):</p>
- <code>
-calcurse --next | mail -s "[calcurse] upcoming appointment!" user@host.com
- </code>
- </dd>
- <dt><code>notify-daemon_enable</code>
- (default: <span class="emp">no</span>)</dt>
- <dd>If set to yes, daemon mode will be enabled, meaning <code>calcurse</code>
- will run into background when the user's interface is exited. This will allow the
- notifications to be launched even when the interface is not running. More details
- can be found in section <a href="#basics_daemon">'Background mode'</a>.
- </dd>
- <dt><code>notify-daemon_log</code>
- (default: <span class="emp">no</span>)</dt>
- <dd>If set to yes, <code>calcurse</code> daemon activity will be logged (see section
- <a href="#basics_files">files</a>).
- </dd>
- </dl>
-
-<h1>6. Known bugs<a name="known_bugs"></a></h1>
-<p>
- Incorrect highlighting of items appear when using calcurse
- black and white theme together with a <code>$TERM</code>
- variable set to <span class="emp">xterm-color</span>.
- To fix this bug, and as advised by Thomas E. Dickey
- (<code>xterm</code> maintainer), <span class="emp">xterm-xfree86</span>
- should be used instead of <span class="emp">xterm-color</span> to set
- the <code>$TERM</code> variable:</p>
- <blockquote class="rq">
- "The xterm-color value for $TERM is a bad choice for XFree86 xterm
- because it is commonly used for a terminfo entry which happens to
- not support bce. Use the xterm-xfree86 entry which is distributed
- with XFree86 xterm (or the similar one distributed with ncurses)."
- </blockquote>
-
-<h1>7. Reporting bugs and feedback<a name="bugs"></a></h1>
-<p>
- Please send bug reports and feedback to:</p>
- <pre>calcurse .at. culot .dot. org</pre>
-<p>
- or to the author:</p>
- <pre>frederic .at. culot .dot. org</pre>
-
-<h1>8. How to contribute?<a name="contribute"></a></h1>
-<p>
- If you would like to contribute to the project,
- you can first send your feedback on what you like or dislike,
- and if there are features you miss in <code>calcurse</code>.
- For now on, possible contributions concern the translation
- of <code>calcurse</code> messages and documentation. </p>
- <p class="rq"><span class="valorise">Note:</span>
- any help in getting <code>calcurse</code>
- internationalized would be very welcomed, but before
- contributing, send a mail to
- <code>calcurse-i18n .at. culot .dot. org</code> to know if someone
- already started the translation process into your language.</p>
-
-<h2>8.1 Translating documentation<a name="contribute_documentation"></a></h2>
-<p>
- The <span class="emp">doc/</span> directory of the source package already
- contains translated version of <code>calcurse</code>
- manual. However, if the manual is not yet available into your
- native language, it would be appreciated if you could help
- translating it.</p>
-<p>
- To do so, just copy one of the existing manual
- file to <code>manual_XX.html</code>, where <span class="emp">XX</span>
- identifies your language. Then translate this newly created
- file and send it to the author (see <a href="#bugs">Reporting
- bugs and feeback</a>), so that it can be included in the
- next <code>calcurse</code> release.</p>
-
-<h2>8.2 <code>calcurse</code> i18n<a name="contribute_i18n"></a></h2>
-<p>
- As already mentioned, <code>gettext</code> utilities are used
- by <code>calcurse</code> to produce multi-lingual
- messages. This section provides informations about how to
- translate those messages into your native language. However,
- this howto is deliberately incomplete, focusing on working
- with <code>gettext</code> for <code>calcurse</code>
- specifically. For more comprehensive informations or to grasp
- the Big Picture of Native Language Support, you should refer
- to the <code>GNU gettext</code> manual at:</p>
- <pre>http://www.gnu.org/software/gettext/manual/ </pre>
-<p>
- Basically, three different people get involved in the
- translation chain: coders, language coordinator, and
- translators. After a quick overview of how things work, the
- translator tasks will be described hereafter.</p>
-
-
-<h3>8.2.1 Overview<a name="contribute_i18n_overview"></a></h3>
-<p>
- To be able to display texts in the native language of the
- user, two steps are required: <span class="emp">internationalization</span>
- (i18n) and <span class="emp">localization</span> (l10n).</p>
-<p>
- i18n is about making
- <code>calcurse</code> support multiple languages. It is
- performed by coders, who will mark translatable texts and
- provide a way to display them translated at runtime.</p>
-<p>
- l10n is
- about making the i18n'ed <code>calcurse</code> adapt to the
- specific language of the user, ie translating the strings
- previously marked by the developers, and setting the
- environment correctly for <code>calcurse</code> to use the
- result of this translation.</p>
-<p>
- So, translatable strings are first marked by the coders within
- the <code>C</code> source files, then gathered in a template
- file (<span class="emp">calcurse.pot</span> - the <span class="emp">pot</span> extension
- meaning <span class="emp">portable object template</span>). The content of
- this template file is then merged with the translation files
- for each language (<span class="emp">fr.po</span> for french, for instance -
- with <span class="emp">po</span> standing for <span class="emp">portable object</span>, ie
- meant to be read and edited by humans). A given translation
- team will take this file, translate its strings, and send it
- back to the developers. At compilation time, a binary version
- of this file (for efficiency reasons) will be produced
- (<span class="emp">fr.mo</span> - <span class="emp">mo</span> stands for
- <span class="emp">machine
- object</span>, ie meant to be read by programs), and then
- installed. Then <code>calcurse</code> will use this file at
- runtime, translating the strings according to the locale
- settings of the user.</p>
-
-
-<h3>8.2.2 Translator tasks<a name="contribute_i18n_translator"></a></h3>
-<p>
- Suppose someone wants to initiate the translation of a new
- language. Here are the steps to follow:</p>
- <ul>
- <li>First, find out what the locale name is. For instance, for
- french, it is 'fr_FR', or simply 'fr'. This is the value the
- user will have to put in his <code>LC_ALL</code> environment
- variable for software to be translated (see <a
- href="#basics_invocation_variable">Environment variable for
- i18n</a>).</li>
- <li>Then, go into the <span class="emp">po/</span> directory, and create a new po-file
- from the template file using the following command:
- <code>'msginit -i calcurse.pot -o fr.po -l fr --no-translator'</code>
- If you do not have <code>msginit</code> installed on your
- system, simply copy the <span class="emp">calcurse.pot</span> file to
- <span class="emp">fr.po</span> and edit the header by hand.</li>
- </ul>
-<p>
- Now, having this <span class="emp">fr.po</span> file, the translator is ready
- to begin.</p>
-
-
-<h3>8.2.3 po-files<a name="contribute_i18n_po-files"></a></h3>
-<p>
- The format of the po-files is quite simple. Indeed, po-files
- are made of four things:</p>
- <ol>
- <li><span class="emp">location lines:</span> tells you where the strings can
- be seen (name of file and line number), in case you need to
- see a bit of context.</li>
- <li><span class="emp">msgid lines:</span> the strings to translate.</li>
- <li><span class="emp">msgstr lines:</span> the translated strings.</li>
- <li><span class="emp">lines prefixed with '#':</span> comments (some with a
- special meaning, as we will see below).</li>
- </ol>
-<p>
- Basically, all you have to do is fill the <span class="emp">msgstr</span>
- lines with the translation of the above <span class="emp">msgid</span>
- line.</p>
-<p>
- <span class="valorise">A few notes:</span>
- <dl>
- <dt><span class="emp">Fuzzy strings</span></dt>
- <dd>You will meet strings marked with a <code>"#, fuzzy"</code>
- comment. <code>calcurse</code> won't use the translations of
- such strings until you do something about them. A string
- being fuzzy means either that the string has already been
- translated but has since been changed in the sources of the
- program, or that this is a new string for which
- <code>gettext</code> made a 'wild guess' for the translation,
- based on other strings in the file. It means you have to
- review the translation. Sometimes, the original string has
- changed just because a typo has been fixed. In this case, you
- won't have to change anything. But sometimes, the translation
- will no longer be accurate and needs to be changed. Once you
- are done and happy with the translation, just remove the
- <code>"#, fuzzy"</code> line, and the translation will be used
- again in <code>calcurse</code>.</dd>
- <dt><span class="emp">c-format strings and special sequences</span></dt>
- <dd>Some strings have the following comment: <code>"#,
- c-format"</code>. This tells that parts of the string to
- translate have a special meaning for the program, and that you
- should leave them alone. For instance, %-sequences, like
- <code>"%s"</code>. These means that <code>calcurse</code> will
- replace them with another string. So it is important it
- remains. There are also \-sequences, like <code>\n</code> or
- <code>\t</code>. Leave them, too. The former represents an end
- of line, the latter a tabulation.</dd>
- <dt><span class="emp">Translations can be wrapped</span></dt>
- <dd>If lines are too long, you can just break them like this:
- <pre>
-msgid ""
-"some very long line"
-"another line"
- </pre></dd>
- <dt><span class="emp">po-file header</span></dt>
- <dd>At the very beginning of the po-file, the first string form a
- header, where various kind of information has to be filled
- in. Most important one is the charset. It should resemble
- <pre>
-"Content-Type: text/plain; charset=utf-8\n"
- </pre>
- 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:
- <pre>
-"Last-Translator: Frederic Culot &lt;frederic@culot.org&gt;\n"
- </pre></dd>
- <dt><span class="emp">Comments</span></dt>
- <dd>Adding comments (lines begining with the '#' character) can be
- a good way to point out problems or translation difficulties
- to proofreaders or other members of your team.</dd>
- <dt><span class="emp">Strings size</span></dt>
- <dd><code>calcurse</code> is a curses/console program, thus it can
- be heavily dependant 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 be displayed to adapt your translation.</dd>
- <dt><span class="emp">A few useful tools</span></dt>
- <dd>The po-file format is very simple, and the file can be edited
- with a standard text editor. But if you prefer, there are few
- specialized tools you may find convenient for translating:
- <ul>
- <li><code>poEdit</code> (<a
- href="http://www.poedit.org/" target="_blank">
- http://www.poedit.org/</a>)</li>
- <li><code>KBabel</code> (<a
- href="http://i18n.kde.org/tools/kbabel/" target="_blank">
- http://i18n.kde.org/tools/kbabel/</a>)</li>
- <li><code>GTranslator</code> (<a
- href="http://gtranslator.sourceforge.net/" target="_blank">
- http://gtranslator.sourceforge.net/</a>)</li>
- <li><code>Emacs</code> po mode</li>
- <li><code>Vim</code> po mode</li>
- </ul>
- </dd>
- <dt><span class="emp">And finally</span></dt>
- <dd>I hope you'll have fun contributing to a more
- internationalized world. :) If you have any more questions,
- don't hesitate to contact me at
- <span class="emp">frederic .at. culot .dot. org</span>.</dd>
- </dl>
-
-
-<h1>9. Links<a name="links"></a></h1>
-<p>
- This section contains links and references that may be of
- interest to you.</p>
-
-<h2>9.1 <code>calcurse</code> homepage<a name="links_homepage"></a></h2>
-<p>
- The <code>calcurse</code> homepage can be found at </p>
- <pre>http://culot.org/calcurse</pre>
-
-<h2>9.2 <code>calcurse</code> announce list<a name="links_list"></a></h2>
-<p>
- If you are interested in the project and want to be warned
- when a new release comes out, you can subscribe to the
- <code>calcurse</code> announce list. In doing so, you will
- receive an email as soon as a new feature appears in
- <code>calcurse</code>.</p>
-<p>
- To subscribe to this list, send a message to
- <span class="emp">calcurse-announce .at. culot .dot. org</span>
- with "subscribe" in the subject field.</p>
-
-<h2>9.3 <code>calcurse</code> RSS feed<a name="links_rss"></a></h2>
-<p>
- Another possibility to get warned when new releases come out
- is to follow the RSS feed at:</p>
- <pre>http://culot.org/calcurse/news_rss.xml</pre>
-<p>
- This RSS feed is updated each time a new version of calcurse is
- available, describing newly added features.</p>
-
-<h2>9.4 Other links<a name="links_others"></a></h2>
-<p>
- You may want to look at the ical format specification (rfc2445) at:
- <pre>http://tools.ietf.org/html/rfc2445</pre>
-<p>
- The pcal project page can be found at:
- <pre>http://pcal.sourceforge.net/</pre>
-
-<h1>10. Thanks<a name="thanks"></a></h1>
-<p>
- 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 :
- <ul>
- <li>Alex for its patches, help and advices with <code>C</code> programming</li>
- <li>Gwen for testing and general discussions about how to
- improve <code>calcurse</code></li>
- <li>Herbert for packaging <code>calcurse</code> for FreeBSD</li>
- <li>Zul for packaging <code>calcurse</code> for NetBSD</li>
- <li>Wain, Steffen and Ronald for packaging <code>calcurse</code> for Archlinux</li>
- <li>Kevin, Ryan, and fEnIo for packaging <code>calcurse</code> for Debian
- and Ubuntu</li>
- <li>Pascal for packaging <code>calcurse</code> for Slackware</li>
- <li>Alexandre and Markus for packaging <code>calcurse</code> for Mac OsX
- and Darwin</li>
- <li>Igor for packaging <code>calcurse</code> for ALT Linux</li>
- <li>Joel for its calendar script which inspired <code>calcurse</code>
- calendar view</li>
- <li>Michael Schulz and Chris M. for the german translation of
- <code>calcurse</code> and its manual</li>
- <li>Jose Lopez for the spanish translation of
- <code>calcurse</code> and its manual</li>
- <li>Neil Williams for the english translation</li>
- <li>Leandro Noferini for the italian translation</li>
- <li>Tony for its patch which helped improving the
- recur_item_inday() function, and for implementing the date format configuration
- options</li>
- <li>Jeremy Roon for the dutch translation</li>
- <li>Erik Saule for its patch implementing the '-N', '-s', '-S', '-r' and '-D' flags</li>
- <li>people who write softwares I like and which inspired me,
- especially :
- <ul>
- <li><code>vim</code> for the displacement keys</li>
- <li><code>orpheus</code> and <code>abook</code> for documentation</li>
- <li><code>pine</code> and <code>aptitude</code>
- for the text user interface</li>
- <li><code>tmux</code> for coding style</li>
- </ul></li>
- </ul>
-</p>
-<p>
- And last, many many thanks to all of the <code>calcurse</code>
- users who sent me their feedback.</p>
-
-<div class="footer">
- Copyright &copy; 2004-2010 Frédéric Culot<br>
- Calcurse version 2.8 - Last change: March 29, 2010<br>
-</div>
-</div>
-
-</body>
-</html>
diff --git a/doc/manual_es.html b/doc/manual_es.html
deleted file mode 100644
index 2787b2c..0000000
--- a/doc/manual_es.html
+++ /dev/null
@@ -1,1347 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<!--
-/*
- * $calcurse: manual_es.html,v 1.25 2010/03/29 18:18:02 culot Exp $
- *
- * Copyright (c) 2004-2010 Frederic Culot <frederic@culot.org>
- * All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * - Redistributions of source code must retain the above
- * copyright notice, this list of conditions and the
- * following disclaimer.
- *
- * - Redistributions in binary form must reproduce the above
- * copyright notice, this list of conditions and the
- * following disclaimer in the documentation and/or other
- * materials provided with the distribution.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- *
- */
--->
-
-<html>
-<head>
-<title>CALCURSE documentación</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css" media="all">
- @import url(manual.css);
-</style>
-</head>
-<body>
-
-<div id="mainContent">
-
-<h1 id="title">
-<span class="main">CALCURSE - organizador basado en modo texto</span></h1>
-
-<div class="warn">
-<div class="todo">
-<h1>Abstract</h1> This manual describes <code>calcurse</code> functionnalities,
-and how to use them. The installation from source is first described, together
-with the available command line arguments. The user interface
-is then presented, with all of the customizable options that change
-<code>calcurse</code> behavior. Last, bug reporting procedure is explained, as
-well as the way one can contribute to <code>calcurse</code> development.
-</div>
-</div>
-
-<div id="toc">
-<h1>Tabla de Contenidos</h1>
-<ul>
- <li><a href="#intro">1. Introducción</a></li>
- <li><a href="#overview">2. Descripción</a>
- <ul>
- <li><a href="#overview_history">2.1 Historia</a></li>
- <li><a href="#overview_features">2.2 Características importantes</a></li>
- </ul></li>
- <li><a href="#install">3. Instalación</a>
- <ul>
- <li><a href="#install_requirements">3.1 Requerimientos</a>
- <ul>
- <li><a href="#install_requirements_ncurses">3.1.1 librería <code>ncurses</code></a></li>
- <li><a href="#install_requirements_gettext">3.1.2 librería <code>gettext</code></a></li>
- </ul></li>
- <li><a href="#install_process">3.2 Proceso de instalación</a></li>
- </ul></li>
- <li><a href="#basics">4. <code>calcurse</code> básicos</a>
- <ul>
- <li><a href="#basics_invocation">4.1 Invocación</a>
- <ul>
- <li><a href="#basics_invocation_commandline">4.1.1 Argumentos de la linea de comandos</a></li>
- <li><a href="#basics_invocation_variable">4.1.2 Variable de entorno para i18n</a></li>
- <li><a href="#basics_invocation_environment"><span class="todo">4.1.3 Other environment
- variables</span></a></li>
- </ul></li>
- <li><a href="#basics_interface">4.2 Interfaz de usuario</a>
- <ul>
- <li><a href="#basics_interface_noninteractive">4.2.1 Modo no-interactivo</a></li>
- <li><a href="#basics_interface_interactive">4.2.2 Modo interactivo</a></li>
- </ul></li>
- <li><a href="#basics_daemon"><span class="todo">4.3 Background mode</span></a></li>
- <li><a href="#basics_files">4.4 Archivos de <code>calcurse</code></a></li>
- <li><a href="#basics_import_export"><span class="todo">4.5 Import/Export capabilities</span></a>
- <ul>
- <li><a href="#basics_import"><span class="todo">4.5.1 Import</span></a></li>
- <li><a href="#basics_export"><span class="todo">4.5.2 Export</span></a></li>
- </ul></li>
- <li><a href="#basics_help">4.6 Ayuda en linea</a></li>
- </ul></li>
- <li><a href="#options">5. Opciones</a>
- <ul>
- <li><a href="#options_general">5.1 Opciones generales</a></li>
- <li><a href="#options_keys"><span class="todo">5.2 Key bindings</span></a>
- <li><a href="#options_colors">5.3 Color (temas)</a></li>
- <li><a href="#options_layout">5.4 Configuración de la disposición</a></li>
- <li><a href="#options_sidebar"><span class="todo">5.5 Sidebar configuration</span></a></li>
- <li><a href="#options_notify">5.6 Ajustes de la barra de notificaciones</a></li>
- </ul></li>
- <li><a href="#known_bugs">6. Bugs conocidos</a></li>
- <li><a href="#bugs">7. Informar de bugs y comentarios</a></li>
- <li><a href="#contribute">8. ¿Como contribuir?</a>
- <ul>
- <li><a href="#contribute_documentation">8.1 Traduciendo la documentación</a></li>
- <li><a href="#contribute_i18n">8.2 <code>calcurse</code> i18n</a>
- <ul>
- <li><a href="#contribute_i18n_overview">8.2.1 Descripción</a></li>
- <li><a href="#contribute_i18n_translator">8.2.2 Tareas del traductor</a></li>
- <li><a href="#contribute_i18n_po-files">8.2.3 Archivos-po</a></li>
- </ul></li>
- </ul></li>
- <li><a href="#links">9. Enlaces</a>
- <ul>
- <li><a href="#links_homepage">9.1 Pagina web de <code>calcurse</code></a></li>
- <li><a href="#links_list">9.2 Lista de anuncios de <code>calcurse</code></a></li>
- <li><a href="#links_rss">9.3 <code>calcurse</code> RSS feed</a></li>
- <li><a href="#links_others"><div class="todo">9.4 Other links</div></a></li>
- </ul></li>
- <li><a href="#thanks">10. Gracias a ...</a></li>
-</ul>
-</div>
-
-<h1>1. Introducción<a name="intro"></a></h1>
-<p>
- <code>calcurse</code> es un calendario y organizador de tareas personal basado en
- modo texto. Te ayuda a mantener un seguimiento de tus eventos, citas y tareas diarias.
- Un sistema de notificacion recuerda al usuario sus proximas citas y la interfaz de
- usuario basanda en ncurses puede ser personalizada para cubrir las necesidades del usuario.
- Todos los comandos están documentados a través de un sistema de ayuda en linea.
-</p>
-
-<h1>2. Descripción<a name="overview"></a></h1>
-<h2>2.1 Historia<a name="overview_history"></a></h2>
-<p>
- Comencé a pensar en este proyecto cuando estaba acabando mi doctorado
- en Astrofísica... Empezaba a ser un poco complicado el organizarme
- y realmente necesitaba una buena herramienta que me ayudase
- en esa difícil tarea ;-)
-</p>
-<p>
- Me gustan los programas que utilizan las interfaces de
- usuario en modo texto porque son simples, rápidos y
- eficientes, por eso pensé en programar un calendario simple en
- ese tipo de interfaz. Por otra parte, esperaba aprender el
- lenguaje <code>C</code> que había utilizado solo a ratos
- durante mi época de estudiante. Por eso pensé que podía ser un
- buen proyecto para empezar a estar organizado y ¡ aprender algunas
- cosas sobre <code>C</code> !
-</p>
-<p>
- Por desgracia acabe mi doctorado antes de
- acabar <code>calcurse</code>, pero de todas formas aun quería
- trabajar en el y esperaba que pudiese ser de ayuda a otra gente.
- Y aquí esta...
-</p>
-<p>
- Pero ¿por que 'calcurse'? Bien, es simplemente una concatenación
- de CALendar y nCURSEs, el nombre de la librería utilizada para
- construir la interfaz de usuario.
-</p>
-
-<h2>2.2 Características importantes<a name="overview_features"></a></h2>
-<p>
- <code>Calcurse</code> es multi-plataforma e intenta ser ligero,
- rápido y fiable. Esta hecho para ser usado en consola o terminal,
- tanto en local como en una maquina remota a través de ssh o una
- conexión similar.
-</p>
-<p>
- <code>Calcurse</code> puede funcionar de dos modos diferentes :
- modo interactivo o no-interactivo. El primero permite a un usuario
- ver su organizador en casi cualquier maquina gracias a la interfaz
- basada en modo texto. El segundo modo permite crear recordatorios
- de una forma muy fácil, únicamente añadiendo <code>calcurse</code>,
- con los argumentos apropiados en la linea de comando, en el crontab
- o mediante un sell init script.
-</p>
-<p>
- Por otra parte, <code>calcurse</code> fue creado pensando en el usuario
- final y trata de ser lo mas amigable posible. Esto significa un
- completo sistema de ayuda en linea, conjuntamente con tener todas
- las posibles acciones visualizadas en todo momento en la barra de
- estado. La interfaz de usuario también es configurable y uno puede
- elegir entre combinaciones de colores y disposiciones.
-<span class="todo">Key bindings are also configurable, to fit everyone's needs.</span>
- Finalmente, un sistema de notificacion recuerda al usuario sus proximas citas.
-<span class="todo">The reminders are sent even if the user's interface
-is not running, as calcurse is able to run in background.</span>
-</p>
-
-<h1>3. Instalación<a name="install"></a></h1>
-<h2>3.1 Requerimientos<a name="install_requirements"></a></h2>
-<h3>3.1.1 librería <code>ncurses</code><a name="install_requirements_ncurses"></a></h3>
-<p>
- <code>Calcurse</code> requiere solo un compilador <code>C</code>, como
- <code>cc</code> o <code>gcc</code>, y la librería <code>ncurses</code>.
- Sería muy sorprendente no tener una librería <code>ncurses</code>
- valida ya instalada en tu ordenador, pero si no la tienes, puedes
- encontrarla en la siguiente dirección :</p>
- <pre>http://ftp.gnu.org/pub/gnu/ncurses/</pre>
-
-<div class="todo">
-<p>
- <p class="rq"><span class="valorize">Note:</span>
- It is also possible to link <code>calcurse</code> against the
- <code>ncursesw</code> library (ncurses with support for unicode).
- However, UTF-8 is not yet supported by <code>calcurse</code>.</p>
-</div>
-
-<h3>3.1.2 librería <code>gettext</code><a name="install_requirements_gettext"></a></h3>
-<p>
- <code>calcurse</code> soporta internacionalización
- (de aquí en adelante <span class="emp">i18n</span>) con las
- utilidades <code>gettext</code>.
- Esto significa que <code>calcurse</code> puede producir
- mensajes en diferentes lenguas si esta compilado con el soporte
- para lengua nativa (p.e. <span class="emp">NLS</span>).
-</p>
-<p>
- Por otra parte,
- <span class="emp">NLS</span> es opcional, si tu no quieres tener soporte
- para esta característica, basta con que utilices la opción <code>--disable-nls</code>
- en el comando <code>configure</code> (ver la sección <a
- href="#install_process">Proceso de instalación</a>).
- Para comprobar si las utilidades <code>gettext</code> están
- instaladas en tu sistema, puedes buscar el archivo cabecera
- <code>libintl.h</code>, por ejemplo :</p>
- <pre>locate libintl.h</pre>
-<p>
- Si este archivo cabecera no se encuentra, entonces puedes obtener
- las fuentes de <code>gettext</code> en la siguiente dirección :</p>
- <pre>http://ftp.gnu.org/pub/gnu/gettext/</pre>
-<p>
- <p class="rq"><span class="valorize">Nota:</span>
- Incluso si <code>libintl.h</code> se encuentra en tu
- sistema, puede ser necesario especificar su localización durante el <a
- href="#install_process">proceso de instalación</a>, utilizando la opción
- <code>--with-libintl-prefix</code> en el comando
- <code>configure</code>. De hecho, el comando <code>configure</code>
- puede fallar al tratar de localizar esta librería si esta instalada en
- un lugar infrecuente.
-</p>
-
-<h2>3.2 Proceso de instalación<a name="install_process"></a></h2>
-<p>
- Primero necesitas descomprimir ( gunzip y untar) el archivo fuente:</p>
- <pre>tar zxvf calcurse-2.8.tar.gz</pre>
-<p>
- Una vez has resuelto los requisitos y has extraído el archivo,
- el proceso de instalación es muy simple y sigue los tres pasos habituales:
- <ol>
- <li><code>./configure</code></li>
- <li><code>make</code></li>
- <li><code>make install</code> (puede requerir privilegios de administrador)</li>
- </ol>
-</p>
-<p>
- Utiliza <code>./configure --help</code> para obtener una lista de posibles
- opciones.
-</p>
-
-<h1>4. <code>calcurse</code> básicos<a name="basics"></a></h1>
-<h2>4.1 Invocación (arranque del programa)<a name="basics_invocation"></a></h2>
-<h3>4.1.1 Argumentos de la linea de comando<a name="basics_invocation_commandline"></a></h3>
-<p>
- <code>calcurse</code> acepta las siguientes opciones en la
- linea de comando (ambas opciones, cortas y largas estan soportadas):</p>
- <p>
-
- <dl>
- <dt><code>-a, --appointment</code></dt>
- <dd>
- Imprime las citas y eventos para el día actual y sale.
- <p class="rq"><span class="valorise">Nota:</span>
- el calendario desde donde leerán
- puede ser especificado usando la opción '-c'.</p>
- </dd>
- <dt><code>-c &lt;file&gt;, --calendar &lt;file&gt;</code></dt>
- <dd>
- Especifica el archivo de calendario a usar.
- El calendario por defecto es <code>~/.calcurse/apts</code>
- (ver la sección <a href="#basics_files">Archivos de <code>calcurse</code></a>).
- </dd>
- <dt><code>-d &lt;date|num&gt;, --day &lt;date|num&gt;</code></dt>
- <dd>
- Imprime las citas y eventos para la fecha dada o para el numero dado de días
- próximos, dependiendo del formato del argumento.
- Soporta dos posible formatos :
- <ul>
- <li>una fecha <span class="todo">(possible formats described below).</span></li>
- <li>un numero 'n'.</li>
- </ul>
- En el primer caso, devolverá la lista de citas y eventos para la fecha especificada
- mientras que en el segundo caso devolverá la lista de citas y eventos
- para los 'n' próximos días.
- Por ejemplo, tecleando <code>calcurse -d 3</code>
- mostrara tus citas y eventos para hoy, mañana y pasado mañana.
- <div class="todo">
- Possible formats for specifying the date are defined inside the
- general configuration menu (see
- <a href="#options_general">General options</a>), using the
- <code>input_datefmt</code> variable.
- </div>
- <p class="rq"><span class="valorise">Nota:</span>
- al igual que para la opción '-a' , el calendario desde donde se
- leerán puede ser especificado usando la opción '-c' .</p>
- </dd>
- <dt><code>-D &lt;dir&gt;, --directory &lt;dir&gt;</code></dt>
- <dd>
- <div class="todo">
- Specify the data directory to use. This option is
- incompatible with -c. If not specified, the
- default directory is <code>'~/.calcurse/'</code>.
- </div>
- </dd>
- <dt><code>-h, --help</code></dt>
- <dd>
- Imprime un breve texto de ayuda describiendo las opciones soportadas en la
- linea de comando y sale.
- </dd>
- <dt><code>-i &lt;file&gt;, --import &lt;file&gt;</code></dt>
- <dd>
- <div class="todo">
- Import the icalendar data contained in <code>file</code>.
- </div>
- </dd>
- <dt><code>-n, --next</code></dt>
- <dd>
- Imprime las citas para las próximas 24 horas y sale.
- El tiempo indicado es el numero de horas y minutos que faltan hasta
- la proxima cita.
- <p class="rq"><span class="valorise">Nota:</span>
- el calendario desde donde se leeran las citas puede ser especificado usando la opcion '-c'.</p>
- </dd>
- <dt><code>-N, --note</code></dt>
- <dd>
- <div class="todo">
- When used with the '-a' or '-t' flag, also print note content
- if one is associated with the displayed item.
- </div>
- </dd>
- <dt><code>-r[num], --range[=num]</code></dt>
- <dd>
- <div class="todo">
- Print events and appointments for the num number of
- days and exit. If no num is given, a range of 1 day
- is considered.
- </div>
- </dd>
- <dt><code>-s[date], --startday[=date]</code></dt>
- <dd>
- <div class="todo">
- Print events and appointments from date and exit.
- If no date is given, the current day is considered.
- </div>
- </dd>
- <dt><code>-S&lt;regex&gt;, --search=&lt;regex&gt;</code></dt>
- <dd>
- <div class="todo">
- When used with the '-a', '-d', '-r', '-s', or '-t' flag,
- print only the items having a description that matches the given
- regular expression.
- </div>
- </dd>
- <dt><code>--status</code></dt>
- <dd>
- <div class="todo">
- Display the status of running instances of calcurse. If
- calcurse is running, this will tell if the interactive
- mode was launched or if calcurse is running in background.
- The process pid will also be indicated.
- </div>
- </dd>
- <dt><code>-t[num], --todo[=num]</code></dt>
- <dd>
- Imprime la lista de tareas pendientes ('ToDo') y sale.
- Si se especifica la opcion <code>numero</code>, se mostraran todas las tareas pendientes que tengan la prioridad
- igual a <code>numero</code>.
- <div class="todo">
- The priority number must be between 1 (highest) and 9 (lowest). It is also possible
- to specify '0' for the priority, in which case only completed tasks will be shown.</p>
- </div>
- </dd>
- <dt><code>-v, --version</code></dt>
- <dd>
- Muestra la versión de <code>calcurse</code> y sale.
- </dd>
- <dt><code>-x[format], --export[=format]</code></dt>
- <dd>
- <div class="todo">
- Export user data to specified format. Events, appointments and
- todos are converted and echoed to stdout.
- Two possible formats are available: ical and pcal
- (see section <a href="#links_others">Links</a> below).
- If the optional argument <code>format</code> is not given,
- ical format is selected by default.
- </div>
- <p class="rq"><span class="valorise">Nota:</span>
- redirecciona la salida standard para exportar los datos a un archivo usando
- un comando como este:
- <code>$ calcurse --export > my_data.dat</code></p>
- </dd>
- </dl>
-
-<h3>4.1.2 Variable de entorno para i18n<a name="basics_invocation_variable"></a></h3>
-<p>
- <code>calcurse</code> puede ser compilado son soporte para lenguaje
- nativo (ver <a href="#install_requirements_gettext">librería <code>gettext</code>
- </a>). Así, si quieres ver los mensajes en tu lengua nativa, primero comprueba
- que esta disponible mirando en el fichero <code>po/LINGUAS</code>.
- Este fichero indica la lista de lenguas disponibles mostrando el código de dos
- letras correspondiente (por ejemplo, <span class="emp">es</span> sería para español).
- Si no encuentras tu lengua, tu ayuda seria muy apreciada si pudieses traducir
- <code>calcurse</code> (ver la sección <a href="#contribute">¿Como puedo
- ayudar?</a>.</p>
-<p>
- Si tu lengua esta disponible, arranca <code>calcurse</code> con el siguiente comando:</p>
- <pre>LC_ALL=es_ES calcurse</pre>
-<p>
- donde <span class="emp">es_ES</span> es el nombre locale en este ejemplo, pero puede ser remplazado
- por el locale correspondiente a la lengua deseada.</p>
-<p>
- Debes especificar también tipo de caracteres 'charset' que se usara porque en
- algunos casos los acentos podrían no mostrarse correctamente.
- Este tipo de caracteres o 'charset' esta indicado al principio del archivo po
- correspondiente al lenguaje deseado. Como puedes ver en el archivo es.po
- se usa el tipo de caracteres iso-8859-1, entonces puedes iniciar <code>calcurse</code>
- utilizando el siguiente comando:</p>
- <pre>LC_ALL=es_ES.ISO8859-1 calcurse</pre>
-
-<div class="todo">
-<h3>4.1.3 Other environment variables<a name="basics_invocation_environment"></a></h3>
-<p>
- The following environment variables affect the way <code>calcurse</code>
- operates:</p>
- <dl>
- <dt><code>VISUAL</code></dt>
- <dd>Specifies the external editor to use for writing notes.
- </dd>
- <dt><code>EDITOR</code></dt>
- <dd>If the <code>VISUAL</code> environment variable
- is not set, then <code>EDITOR</code> will be used as
- the default external editor. If none of those variables are set,
- then <code>/usr/bin/vi</code> is used instead.
- </dd>
- <dt><code>PAGER</code></dt>
- <dd>Specifies the default viewer to be used for reading notes.
- If this variable is not set, then <code>/usr/bin/less</code> is used.
- </dd>
- </dl>
-</div>
-
-<h2>4.2 Interfaz de usuario<a name="basics_interface"></a></h2>
-<h3>4.2.1 Modo no-interactivo<a name="basics_interface_noninteractive"></a></h3>
-<p>
- Cuando es llamado por lo menos con uno de los siguientes argumentos:
- <code>-a</code>, <code>-d</code>, <code>-h</code>,
- <code>-n</code>, <code>-t</code>, <code>-v</code>, <code>-x</code>,
- <code>calcurse</code> arranca en modo no-interactivo.
- Esto significa que se mostrara la información deseada, y
- después de esto, <code>calcurse</code> simplemente se cierra y eres
- de nuevo devuelto al prompt del shell.</p>
-<p>
- De esta forma, uno puede añadir una linea como
- <code>'calcurse --todo --appointment'</code>
- en el archivo de inicialización de su entorno gráfico (X o consola) para ver,
- cuando entras en el sistema; la lista de tareas, citas y eventos
- programadas para el día actual.</p>
-
-<h3>4.2.2 Modo interactivo<a name="basics_interface_interactive"></a></h3>
-<div class="todo">
- <p class="rq"><span class="valorise">Note:</span>
- Key bindings that are indicated in this manual correspond to
- the default ones, defined when <code>calcurse</code> is launched
- for the first time. If those key bindings do not suit user's needs,
- it is possible to change them within the keys configuration menu
- (see <a href="#options_keys">key bindings</a>).</p>
-</div>
-<p>
- Cuando es llamado sin ningún argumento o solo con la opción
- <code>-c</code>, <code>calcurse</code> arranca en modo interactivo.
- En este modo, se muestra una interfaz conteniendo tres
- paneles diferentes por los cuales puedes navegar usando la tecla
- 'TAB' (tabulador), mas una barra de notificaciones, mas una barra
- de estado (ver la figura de abajo).</p>
- <pre>
-
- panel de citas y eventos ---. .--- panel de calendario
- | |
- v v
- +------------------------------------++----------------------------+
- | Citas y eventos || Calendario |
- |------------------------------------||----------------------------|
- | (|) Abril 6, 2006 || Abril 2006 |
- | ||Lun Mar Mie Jue Vie Sab Dom |
- | || 1 2 |
- | || 3 4 5 6 7 8 9 |
- | || 10 11 12 13 14 15 16 |
- | || 17 18 19 20 21 22 23 |
- | || 24 25 26 27 28 29 30 |
- | || |
- | |+----------------------------+
- | |+----------------------------+
- | || Tareas Pendientes |
- | ||----------------------------| panel de tareas pendientes
- | || | |
- | || | |
- | || |&lt;--.
- | || |
- +------------------------------------++----------------------------+
- |---[ Lun 6-4-2006 | 10:11:43 ]---(citas)----&gt; 01:20 :: comida &lt;---|&lt;--.
- +------------------------------------------------------------------+ barra de notificaciones
- | ? Ayuda R Redibujar H/L -/+1 Dia G Ir a C Config |
- | Q Salir S Guardar J/K -/+1 Semana Tab Cambiar vista |&lt;-.
- +------------------------------------------------------------------+ |
- |
- barra de estado
-
- </pre>
-<p>
- El primer panel representa un calendario que permite iluminar un
- día en particular, el segundo contiene la lista de citas y eventos
- pertenecientes a ese día, y el ultimo contiene una lista
- de tareas pendientes (ToDo) pero que no están asignadas a ningún día
- especifico.</p>
-<div class="todo">
-<p>
- Depending on the selected view, the calendar could either display
- a monthly (default as shown in previous figure) or weekly view.
- The weekly view would look like the following:</p>
- <pre>
-
-+------------------------------------+
-| Calendar |
-|----------------------------(# 13)--|
-| Mon Tue Wed Thu Fri Sat Sun |
-| 29 30 31 01 02 03 04 |
-| <----+-- slice 1: 00:00 to 04:00 AM
-| -- -- -- -- -- -- |
-| <----+-- slice 2: 04:00 to 08:00 AM
-| -- -- -- -- -- -- |
-| <----+-- slice 3: 08:00 to 12:00 AM
-| - -- -- -- -- -- -- - <-+-- midday
-| <----+-- slice 4: 12:00 to 04:00 PM
-| -- -- -- -- -- -- |
-| <----+-- slice 5: 04:00 to 08:00 PM
-| -- -- -- -- -- -- |
-| <----+-- slice 6: 08:00 to 12:00 PM
-+------------------------------------+
-
- </pre>
-<p>
- The current week number is displayed on the top-right side of the panel
- (<span class="emp"># 13</span> meaning it is the 13th week of the year
- in the above example). The seven days of the current week are displayed
- in column. Each day is divided into slices of 4 hours each (6 slices in
- total, see figure above). A slice will appear in a different color if
- an appointment falls into the corresponding time-slot.
-</p>
-</div>
-
-<div class="todo">
-<p>
- In the appointment panel, one can notice the <span class="emp">'(|)'</span> sign
- just in front of the date. This indicates the current phase of the moon.
- Depending on which is the current phase, the following signs can be
- seen:</p>
- <dl class="compact">
- <dt>'<code> |) </code>':</dt>
- <dd>first quarter</dd>
- <dt>'<code> (|) </code>':</dt>
- <dd>full moon</dd>
- <dt>'<code> (| </code>':</dt>
- <dd>last quarter</dd>
- <dt>'<code> | </code>':</dt>
- <dd>new moon</dd>
- <dt>no sign:</dt>
- <dd>phase of the moon does not correspond to any of
- the above ones</dd>
- </dl>
-</p>
-</div>
-<p>
- En la parte inferior de la pantalla hay una barra de estado, que
- indica las posibles acciones y sus correspondientes atajos de
- teclado.</p>
-<p>
- Justo encima de esta barra de estado esta la barra de notificaciones, que indica
- de izquierda a derecha : la fecha actual, la hora actual, el archivo de
- calendario actualmente en uso (en el ejemplo de arriba, el de citas, que es
- el fichero de calendario por defecto, ver la sección siguiente), y la
- cita mas cercana para las proximas 24 horas. En el ejemplo seria una comida
- dentro de una hora y 20 minutos.</p>
- <p class="rq"><span class="valorise">Nota:</span>
- Algunas acciones, como editar o añadir un elemento,
- requieren teclear algo de texto. Esto se hace con la ayuda del editor
- incorporado.</p>
-<p>
- Dentro de este editor, si una linea es mas larga que el ancho de la pantalla,
- se mostrara un caracter como '&gt;', '*', o '&lt;' al final de la columna
- indicando que hay mas caracteres despues, antes y despues, o antes de la posicion actual, respectivamente.
- La linea se movera horizontalmente si es necesario.</p>
-<p>
- Por otra parte, hay algunos caracteres que se utilizan para editar.
- Aqui se indican los comandos de edicion disponibles
- ('^' significa la tecla "control"):
- <dl class="compact">
- <dt><code>^a</code>:</dt>
- <dd>mueve el cursor al principio de la linea</dd>
- <dt><code>^b</code>:</dt>
- <dd>mueve el cursor para atras</dd>
- <dt><code>^d</code>:</dt>
- <dd>borra un caracter por delante</dd>
- <dt><code>^e</code>:</dt>
- <dd>mueve el cursor al final de la linea</dd>
- <dt><code>^f</code>:</dt>
- <dd>mueve el cursor para alante</dd>
- <dt><code>^h</code>:</dt>
- <dd>borra un caracter hacia atras</dd>
- <dt><code>^k</code>:</dt>
- <dd>borra desde el cursor hasta el final de la linea</dd>
- <dt><code>ESCAPE</code></dt>
- <dd>b>: cancela la edicion</dd>
- </dl>
-</p>
-
-<div class="todo">
-<h2>4.3 Background mode<a name="basics_daemon"></a></h2>
-
-<p>When the daemon mode is enabled in the notification configuration menu
-(see <a href="#options_notify">Notify-bar settings</a>), <code>calcurse</code> will stay
-in background when the user interface is not running. In background mode,
-<code>calcurse</code> checks for upcoming appointments and runs the user-defined
-notification command when necessary. When the user interface is started again,
-the daemon automatically stops.</p>
-
-<p><code>calcurse</code> background activity can be logged (set the
-<code>notify-daemon_log</code> variable in the notification configuration
-<a href="#options_notify">menu</a>), and in that case, information about the daemon
-start and stop time, reminders' command launch time, signals received... will be written
-in the <code>daemon.log</code> file (see section <a href="#basics_files">files</a>).</p>
-
-<p>
-Using the <code>--status</code> command line option (see section
-<a href="#basics_invocation_commandline">Command line arguments</a>),
-one can know if <code>calcurse</code> is currently running in background or not.
-If the daemon is running, a message like the following one will be displayed (the pid of
-the daemon process will be shown):
-<pre>calcurse is running in background (pid 14536)</pre>
-
-<p class="rq"><span class="valorise">Note:</span>
-To stop the daemon, just send the <code>TERM</code> signal to it, using a command such as:
-<code>'kill daemon_pid'</code>, where <span class="emp">daemon_pid</span> is the process id
-of the daemon (14536 in the above example).
-</p>
-</div>
-
-<h2>4.4 Archivos de <code>calcurse</code><a name="basics_files"></a></h2>
-<p>
- La siguiente estructura se crea en tu directorio <code>$HOME</code>
- <div class="todo">(or in the directory you specified with the -D option)</div>
- la primera vez que se ejecuta <code>calcurse</code> :</p>
- <pre>
-$HOME/.calcurse/
- |___notes/
- |___conf
- |___keys
- |___apts
- |___todo
- </pre>
- <dl class="compact">
- <dt><code>notes/</code>:</dt>
- <dd><span class="todo">this subdirectory contains descriptions of the notes
- which are attached to appointments, events or todos. One text file is
- created per note, whose name is built using mkstemp(3) and should be
- unique, but with no relation with the corresponding item's description.</span></dd>
- <dt><code>conf</code>:</dt>
- <dd>contiene la configuración del usuario.</dd>
- <dt><code>keys</code>:</dt>
- <dd><span class="todo">this file contains the user-defined key bindings</span></dd>
- <dt><code>apts</code>:</dt>
- <dd>contiene todos los eventos y citas del usuario.</dd>
- <dt><code>todo</code>:</dt>
- <dd>contiene la lista de tareas pendientes.</dd>
- </dl>
-
-<div class="todo">
- <p class="rq"><span class="valorise">Note:</span>
- If the logging of calcurse daemon activity was set in the notification
- configuration menu, the extra file <code>daemon.log</code> will appear
- in calcurse data directory. This file contains logs about calcurse activity
- when running in background.
- </p>
-</div>
-
-<div class="todo">
-<h2>4.5 Import/Export capabilities<a name="basics_import_export"></a></h2>
-<p>
- The import and export capabilities offered by <code>calcurse</code>
- are described below.
-</p>
-
-<h3>4.5.1 Import<a name="basics_import"></a></h3>
-<p>
- Data in icalendar format as described in the rfc2445 specification
- (see <a href="#links_others">links</a> section below) can be imported
- into calcurse. Calcurse ical parser is based on version 2.0 of this
- specification, but for now on, only a subset of it is supported.
-</p>
-<p>
- The following icalendar properties are handled by calcurse:
- <ul>
- <li><code>VTODO</code> items:<br>
- "PRIORITY", "VALARM", "SUMMARY", "DESCRIPTION"</li>
- <li><code>VEVENT</code> items:<br>
- "DTSTART", "DTEND", "DURATION", "RRULE", "EXDATE", "VALARM", "SUMMARY",
- "DESCRIPTION"</li>
- </ul>
-</p>
-<p>
- The icalendar "DESCRIPTION" property will be converted into calcurse format
- by adding a note to the item. If a "VALARM" property is found, the item
- will be flagged as important and the user will get a notification (this is
- only applicable to appointments).
-</p>
-<p>
- Here are the properties that are not implemented:
- <ul>
- <li>negative time durations are not taken into account (item is skipped)</li>
- <li>some recurence frequences are not recognize:<br>
- "SECONDLY" / "MINUTELY" / "HOURLY"</li>
- <li>some recurrence keywords are not recognized
- (all those starting with 'BY'):<br>
- "BYSECOND" / "BYMINUTE" / "BYHOUR" / "BYDAY" / "BYMONTHDAY"<br>
- "BYYEARDAY" / "BYWEEKNO" / "BYMONTH" / "BYSETPOS"<br>
- plus "WKST"</li>
- <li>the recurrence exception keyword "EXRULE" is not recognized</li>
- <li>timezones are not taken into account</li>
- </ul>
-</p>
-
-<h3>4.5.2 Export<a name="basics_export"></a></h3>
-<p>
- Two possible export formats are available: <code>ical</code> and
- <code>pcal</code> (see section <a href="#links_others">Links</a> below
- to find out about those formats).
-</p>
-</div>
-
-<h2>4.6 Ayuda en linea<a name="basics_help"></a></h2>
-<p>
- En cualquier momento, puedes consultar el sistema de ayuda integrado
- presionando la tecla '?'. Una vez en la pantalla de ayuda,
- puedes acceder a la información acerca de un comando especifico presionando
- la tecla correspondiente a ese comando.
-</p>
-
-<h1>5. Opciones<a name="options"></a></h1>
-<p>
- Todos los parámetros de <code>calcurse</code> se peden configurar desde
- el menú de Configuración disponible pulsando 'C'. Entonces aparecerá un
- submenu con tres posibilidades :
- pulsando 'C' de nuevo, te lleva a la configuración del esquema de colores.
- Pulsando 'L' te permite elegir la disposición de la pantalla principal
- de <code>calcurse</code> (en otras palabras, donde colocar los tres diferentes
- paneles en pantalla),
- <span class="todo">pressing 'K' opens the key bindings configuration
- menu,</span>
- y finalmente puedes elegir entre diferentes opciones
- generales pulsando 'G'.
-</p>
-
-<h2>5.1 Opciones generales<a name="options_general"></a></h2>
-<p>
- Estas opciones controlan el comportamiento general en la forma
- que se describe a continuación:</p>
- <dl>
- <dt><code>auto_guardar</code>
- (por defecto: <span class="emp">si</span>)</dt>
- <dd>Esta opción permite salvar automáticamente los datos del usuario
- (si esta fijada en <span class="emp">si</span>) cuando se sale
- del programa.
- <p class="rq"><span class="valorise">aviso:</span>
- Los datos no serán guardados automáticamente si
- <code>auto_guardar</code> esta fijada en <span class="emp">no</span>.
- Esto significa que el usuario debe pulsar 'S' (guardar) para guardar
- sus modificaciones antes de salir.</p>
- </dd>
-
- <dt><code><span class="todo">periodic_save</code>
- (default: <span class="emp">0</span>)</span></dt>
- <dd><span class="todo">If different from '0', user's data will be automatically
- saved every <span class="emp">periodic_save</span> minutes.
- When an automatic save is performed, two asterisks
- (i.e. '<code>**</code>') will appear on the top right-hand side
- of the screen).</span>
- </dd>
-
- <dt><code>confirmar_salir</code>
- (por defecto: <span class="emp">si</span>)</dt>
- <dd>Si se fija en <span class="emp">si</span>, se requerirá confirmación antes de salir,
- de otra forma cuando se pulse 'Q' causara que <code>calcurse</code>
- se cierre sin esperar confirmación del usuario.
- </dd>
- <dt><code>confirmar_borrar</code>
- (por defecto: <span class="emp">si</span>)</dt>
- <dd>Si se fija esta opción en <span class="emp">si</span>, cuando se pulse 'D' para
- borrar una anotación (bien sea un <span class="emp">ToDo
- (tarea pendiente)</span>, <span class="emp">cita</span>,
- o <span class="emp">evento</span>), se requerirá confirmación del usuario antes de borrar
- de la lista la anotación seleccionada.
- De otra forma, no será necesaria confirmación antes de borrar la anotación.
- </dd>
- <dt><code>saltar_dialogos_sistema</code>
- (por defecto: <span class="emp">no</span>)</dt>
- <dd>Fijando esta opción en <span class="emp">si</span> causará la omisión de los diálogos
- del sistema relativos al guardado y carga de los datos.
- Esto puede ser útil para acelerar los procesos de entrada y salida al programa.
- </dd>
- <dt><code>saltar_barra_progreso</code>
- (por defecto: <span class="emp">no</span>)</dt>
- <dd>Si se fija en <span class="emp">si</span>, ocasionara la desaparición de la barra de progreso
- que normalmente se muestra cuando se salvan datos a un archivo.
- Si esta fijada en <span class="emp">no</span>, se mostrará esta barra, conjuntamente con
- el nombre del archivo que se esta guardando
- (ver sección <a href="#basics_files">Archivos de <code>calcurse</code></a>).
- </dd>
-
- <dt><code><span class="todo">calendar_default_view</span></code>
- (default: <span class="emp">0</span>)</dt>
- <dd><span class="todo">If set to <span class="emp">0</span>, the monthly calendar view will be
- displayed by default otherwise it is the weekly view that will be displayed.</span>
- </dd>
-
- <dt><code>empezar_semana_en_lunes</code>
- (por defecto: <span class="emp">si</span>)</dt>
- <dd>Uno puede elegir entre el Lunes o el Domingo como primer día de la semana.
- Si la opción <span class="emp">empezar_semana_en_lunes</span> esta fijada en
- <span class="emp">si</span>, el Lunes será el primer día de la semana en la vista del calendario.
- Por el contrario, si esta opción esta fijada en <span class="emp">no</span>, entonces el Domingo
- será el primer día de la semana.
- </dd>
-
- <dt><code><span class="todo">output_datefmt</code>
- (default: <span class="emp">%D</span>)</span></dt>
- <dd><span class="todo">This option indicates the format to be used when displaying dates
- in non-interactive mode. Using the default values, dates are displayed the
- following way: <span class="emp">mm/dd/aa</span>.
- You can see all of the possible formats by typing <code>man 3 strftime</code>
- inside a terminal.</span></dd>
-
- <dt><code><span class="todo">input_datefmt</code>
- (default: <span class="emp">1</span>)</span></dt>
- <dd><span class="todo">This option indicates the format that will be used to enter dates in
- <span class="emp">calcurse</span>. Four choices are available:</span>
- <ol>
- <li>mm/dd/yyyy</li>
- <li>dd/mm/yyyy</li>
- <li>yyyy/mm/dd</li>
- <li>yyyy-mm-dd</li>
- </ol>
- </dd>
-
- </dl>
-
-<div class="todo">
-<h2>5.2 Key bindings<a name="options_keys"></a></h2>
-<p>
- One can define it's own keybindings within the 'Keys' configuration
- menu. The default keys look like the one used by the <code>vim</code>
- editor, especially the displacement keys. Anyway, within this
- configuration menu, users can redefine all of the keys available from
- within calcurse's user interface.</p>
-<p>
- To define new keybindings, first highlight the action to which it will
- apply. Then, delete the actual key binding if necessary, and add a new
- one. You will then be asked to press the key corresponding to the new
- binding. It is possible to define more than one key binding for a single
- action.</p>
-<p>
- An automatic check is performed to see if the new key binding
- is not already set for another action. In that case, you will be asked
- to choose a different one. Another check is done when exiting from this
- menu, to make sure all possible actions have a key associated with it.</p>
-<p>
- The following keys can be used to define bindings:
- <ul>
- <li>lower-case, upper-case letters and numbers, such as 'a', 'Z', '0'</li>
- <li>CONTROL-key followed by one of the above letters</li>
- <li>escape, horizontal tab, and space keys</li>
- <li>arrow keys (up, down, left, and right)</li>
- <li>'HOME' and 'END' keys</li>
- </ul> </p>
-<p>
- While inside the key configuration menu, an online help is available for
- each one of the available actions. This help briefly describes what the
- highlighted action is used for.</p>
-</div>
-
-<h2>5.3 Color (temas)<a name="options_colors"></a></h2>
-<p>
- El tema de color de <code>calcurse</code> puede se configurado para
- cubrir las necesidades del usuario. Para cambiar el tema por defecto, la
- pagina de configuracion muestra las posibles opciones para el color de fondo
- y del texto.
- Usando las teclas de las flechas o las teclas de desplazamiento de calcurse
- para moverse y 'X'o la barra espaciadora para seleccionar el color, el usuario
- puede previsualizar el tema que se aplicara.
- Tambien es posible mantener los colores por defecto del terminal seleccionando
- la opcion correspondiente en la lista.</p>
-<div class="todo">
-<p>
- 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 bar. A black and white theme is also
- available, in order to support non-color terminals.</p>
-</div>
- <p class="rq"><span class="valorise">Notas:</span>
- Dependiendo de tu tipo de terminal y del valor de la variable de
- entorno <code>$TERM</code>, color puede no estar soportado.
- En ese caso, si intentas cambiar los colores aparecerá un mensaje de error
- puesto que tu terminal no soporta esta característica.
- Si sabes que tu terminal soporta colores pero no puedes conseguir
- que <code>calcurse</code> los muestre, intenta fijar tu variable <code>$TERM</code>
- a otro valor. (como por ejemplo <span class="emp">xterm-xfree86</span>).
- </p>
-
-<h2>5.4 Configuración de la disposición<a name="options_layout"></a></h2>
-<p>
- La disposición corresponde a la posición de los paneles
- dentro de la pantalla de <code>calcurse</code>. La disposición por defecto
- hace que el calendario se muestre en la esquina superior derecha
- del terminal, el panel de 'ToDo' (tareas pendientes) en la esquina inferior
- derecha, mientras que el panel de citas se muestra en la parte izquierda
- de la pantalla (ver la figura de la sección <a href="#basics_interface_interactive">Modo interactivo</a>
- como ejemplo de la disposición por defecto).
- Eligiendo otra disposición en la pantalla de configuración, el usuario puede
- modificar la apariencia de <code>calcurse</code> que mejor se adapte a sus
- necesidades colocando los diferentes paneles donde los necesite.</p>
-
-<div class="todo">
-<p>
- The following option is used to modify the layout configuration:</p>
- <dl>
- <dt><code>layout</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>Eight different layouts are to be chosen from (see layout
- configuration screen for the description of the available layouts).</dd>
- </dl>
-</div>
-
-
-<div class="todo">
-<h2>5.5 Sidebar configuration<a name="options_sidebar"></a></h2>
-<p>
- The sidebar is the part of the screen which contains two panels:
- the calendar and, depending on the chosen layout, either the todo
- list or the appointment list.</p>
-<p>
- The following option is used to change the width of the sidebar:</p>
- <dl>
- <dt><code>side-bar_width</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>Width (in percentage, 0 being the minimum width) of the side bar.</dd>
- </dl>
-</div>
-
-<h2>5.6 Ajustes de la barra de notificaciones<a name="options_notify"></a></h2>
-<p>
- Las siguientes opciones se usan para modificar el comportamiento de la barra de notificaciones:</p>
- <dl>
- <dt><code>mostrar-barra-notificaciones</code>
- (por defecto: <span class="emp">si</span>)</dt>
- <dd>Esta opción indica si quieres que se muestre la barra de notificaciones o no.
- </dd>
- <dt><code>fecha_barra-notificaciones</code>
- (por defecto: <span class="emp">%a %F</span>)</dt>
- <dd>Con esta opcion puedes especificar el formato que se usara para mostrar la fecha
- actual dentro de la barra de notificaciones. Puedes ver todos los formatos posibles
- tecleando <code>man 3 strftime</code> en un terminal.
- </dd>
- <dt><code>hora_barra-notificaciones</code>
- (por defecto: <span class="emp">%T</span>)</dt>
- <dd>Con esta opcion puedes especificar el formato que se usara para mostrar la
- hora actual dentro de la barra de notificaciones. Puedes ver todos los formatos
- posibles tecleando <code>man 3 strftime</code> dentro de un terminal.
- </dd>
- <dt><code>alarma_barra-notificaciones</code>
- (por defecto: <span class="emp">300</span>)</dt>
- <dd>Cuando tienes una cita dentro de los siguientes 'alarma_barra-notificaciones'
- segundos, la referencia a esa cita dentro de la barra de notificaciones
- comienza a parpadear.
- Además, se lanzara el comando definido por la opcion <span class="emp">comando_barra-notificaciones</span>.
- De esta forma, se alerta al usuario y este sabe que
- detro de poco tiene una cita.
- </dd>
- <dt><code>comando_barra-notificaciones</code>
- (por defecto: <span class="emp">printf '\a'</span>)</dt>
- <dd>Esta opcion indica que comando se lanzara cuando haya una cita proxima marcada como
- "inportante". Este comando sera pasado al shell del usuario que lo interpretara.
- Para saber que tipo de shell debe usarse, se utilizara el contenido dela variable de
- entorno <code>$SHELL</code>. Si esta variable no esta seleccionada, se usara <code>/bin/sh</code>.
- <p class="rq"><span class="valorise">Ejemplo:</span>
- Digamos que el comando <code>mail</code> esta disponible en el sistema del usuario, uno
- puede usar este comando para ser notificado por correo electronico cuando se acerque la cita
- (la descripcion de la cita se mencionara en el cuerpo del mensaje):</p>
- <code>
-calcurse --next | mail -s "[calcurse] upcoming appointment!" user@host.com
- </code>
- </dd>
-
- <dt><code><span class="todo">notify-daemon_enable</code>
- (default: <span class="emp">no</span>)</span></dt>
- <dd><span class="todo">If set to yes, daemon mode will be enabled, meaning <code>calcurse</code>
- will run into background when the user's interface is exited. This will allow the
- notifications to be launched even when the interface is not running. More details
- can be found in section <a href="#basics_daemon">'Background mode'</a>.</span>
- </dd>
- <dt><code><span class="todo">notify-daemon_log</code>
- (default: <span class="emp">no</span>)</span></dt>
- <dd><span class="todo">If set to yes, <code>calcurse</code> daemon activity will be logged (see section
- <a href="#basics_files">files</a></span>).
- </dd>
-
- </dl>
-
-<h1>6. Bugs conocidos<a name="known_bugs"></a></h1>
-<p>
- Aparece una incorrecta iluminación de las anotaciones cuando se usa el tema
- calcurse blanco y negro conjuntamente con la variable <code>$TERM</code>
- fijada a <span class="emp">xterm-color</span>.
- Para solucionar este bug, y tal como fue anunciado por Thomas E. Dickey
- (que mantiene <code>xterm</code>), <span class="emp">xterm-xfree86</span>
- puede ser usado en vez de <span class="emp">xterm-color</span> para
- fijar la variable <code>$TERM</code>:</p>
- <blockquote class="rq">
- "The xterm-color value for $TERM is a bad choice for XFree86 xterm
- because it is commonly used for a terminfo entry which happens to
- not support bce. Use the xterm-xfree86 entry which is distributed
- with XFree86 xterm (or the similar one distributed with ncurses)."
- </blockquote>
-
-<h1>7. Informar de bugs y comentarios<a name="bugs"></a></h1>
-<p>
- Por favor envía los informes de bugs y tus comentarios a :</p>
- <pre>calcurse @ culot . org</pre>
-<p>
- o al autor:</p>
- <pre>frederic @ culot . org</pre>
-
-<h1>8. ¿Como contribuir?<a name="contribute"></a></h1>
-<p>
- Si te gustaría contribuir al proyecto, puedes enviar tus comentarios
- acerca de lo que te gusta o no te gusta, y si hay alguna
- funcionalidad que echas de menos en <code>calcurse</code>.
- Por ahora, las posibles contribuciones están limitadas a la traducción
- de la documentación y mensajes de error de <code>calcurse</code>. </p>
- <p class="rq"><span class="valorise">Nota:</span>
- Cualquier ayuda para la internacionalización de <code>calcurse</code>
- será muy bienvenida, pero antes de contribuir envía en email a :
- <code>calcurse-i18n @ culot . org</code> para saber si alguien ha empezado ya
- el proceso de traducción a tu lengua.</p>
-
-<h2>8.1 Traduciendo la documentación<a name="contribute_documentation"></a></h2>
-<p>
- El directorio <span class="emp">doc/</span> del paquete fuente ya contiene versiones traducidas
- del manual de <code>calcurse</code>. Aunque si el manual no esta aun disponible
- en tu lengua nativa, sería de gran ayuda si tu pudieses traducirlo.</p>
-<p>
- Para hacerlo, únicamente copia uno de los archivos de los manuales existentes
- de <code>manual_XX.html</code>, donde <span class="emp">XX</span> identifica tu lengua. Entonces
- traduce este nuevo archivo creado y envía un email al autor (ver <a href="#bugs">Informar
- de bugs y comentarios</a>), para que pueda ser incluido en la nueva
- edición de <code>calcurse</code>.</p>
-
-<h2>8.2 <code>calcurse</code> i18n<a name="contribute_i18n"></a></h2>
-<p>
- Como ya se ha mencionado, las utilidades de <code>gettext</code> son usadas
- por <code>calcurse</code> para producir mensajes en diferentes lenguas.
- Esta sección proporciona información acerca de como traducir estos mensajes
- a tu lengua nativa. Por otra parte este 'como' es deliberadamente incompleto,
- centrado específicamente en trabajar con <code>gettext</code> para <code>calcurse</code>.
- Para una información mas completa deberás dirigirte al manual de <code>GNU gettext</code> en:</p>
- <pre>http://www.gnu.org/software/gettext/manual/</pre>
-<p>
- Básicamente, hay tres tipos de personas diferentes que están involucradas en la cadena de traducción:
- programadores, coordinadores de lenguaje y traductores.
- Después de una rápida descripción de como funcionan las cosas, las tareas del
- traductor se describen a continuación.</p>
-
-<h3>8.2.1 Descripción<a name="contribute_i18n_overview"></a></h3>
-<p>
- Para que se muestren mensajes en la lengua nativa del usuario, se requieren
- dos pasos: <span class="emp">internacionalización</span>
- (i18n) y <span class="emp">localización</span> (l10n).</p>
-<p>
- i18n se refiere a como hacer que
- <code>calcurse</code> soporte múltiples lenguas. Esto es realizado por
- programadores, quienes seleccionan los textos traducibles y
- proporcionan una manera de que se muestren traducidos en el
- arranque.</p>
-<p>
- l10n se
- refiere a como hacer que el <code>calcurse</code> internacionalizado se adapte a la
- lengua especifica del usuario, p.e. traduciendo las sentencias previamente
- marcadas por los desarrolladores y seleccionando el entorno correcto
- para que <code>calcurse</code> utilice el resultado de esta traducción.</p>
-<p>
- Entonces, las sentencias traducibles son primero marcadas por los programadores dentro
- de el código fuente de los archivos en código <code>C</code>, y después recogidas en un archivo
- plantilla (<span class="emp">calcurse.pot</span> - la extensión <span class="emp">pot</span> significa
- <span class="emp">portable object template</span>). El contenido de
- esta plantilla es entonces combinado con los ficheros de traducción
- para cada lengua (<span class="emp">fr.po</span> para francés por ejemplo -
- donde <span class="emp">po</span> significa <span class="emp">portable object</span>, lo cual quiere decir
- que puede ser leído y editado por humanos). Un equipo de traducción dado,
- cogería este archivo, traduciría estas sentencias y se las mandaría de nuevo
- a los desarrolladores. En el momento de la compilación, una versión binaria
- de esta archivo (por razones de eficacia) producirá
- (<span class="emp">fr.mo</span> - donde <span class="emp">mo</span> significa <span class="emp">machine
- object</span>, lo que quiere decir que puede ser leído por programas), y entonces
- instalado. Ahora <code>calcurse</code> utilizara este archivo en el arranque,
- traduciendo las sentencias acorde con la configuración del locale del usuario.
-</p>
-
-<h3>8.2.2 Tareas del traductor<a name="contribute_i18n_translator"></a></h3>
-<p>
- Supongamos que alguien quiere iniciar la traducción de una nueva lengua.
- Estos son los pasos a seguir:</p>
- <ul>
- <li>Primero, localiza cual es el nombre del locale. Por ejemplo, para francés
- es 'fr_FR', o simplemente 'fr'. Este es el valor que el usuario deberá poner
- es su variable de entorno <code>LC_ALL</code> para que el software sea traducido
- (ver <a href="#basics_invocation_variable">Variable de entorno para i18n</a>).</li>
- <li>Entonces, entra en el directorio <span class="emp">po/</span> y crea un nuevo archivo-po
- desde el archivo plantilla usando el siguiente comando:
- <code>'msginit -i calcurse.pot -o fr.po -l fr --no-translator'</code>
- Si no tienes instalado <code>msginit</code> en tu sistema,
- simplemente copia el archivo <span class="emp">calcurse.pot</span> a
- <span class="emp">fr.po</span> y edita la cabecera a mano.</li>
- </ul>
-<p>
- Ahora, teniendo el archivo <span class="emp">fr.po</span>, estas preparado para empezar.
-</p>
-
-<h3>8.2.3 Archivos-po<a name="contribute_i18n_po-files"></a></h3>
-<p>
- El formato de los archivos-po es muy simple. De hecho, los archivos-po
- están formados de cuatro cosas:</p>
- <ol>
- <li><span class="emp">lineas de localización:</span> te dicen donde están las sentencias
- (nombre del archivo y numero de linea), en caso de que necesites un poco
- mas de contexto.</li>
- <li><span class="emp">lineas msgid:</span> las sentencias a traducir.</li>
- <li><span class="emp">lineas msgstr:</span> las sentencias traducidas.</li>
- <li><span class="emp">lineas con prefijo '#':</span> comentarios (algunos con un significado
- especial, como veremos más abajo).</li>
- </ol>
-<p>
- Básicamente, todo lo que tienes que hacer es llenar las lineas <span class="emp">msgstr</span>
- con la traducción de la linea <span class="emp">msgid</span> de encima.</p>
-<p>
- <span class="valorise">Algunas notas:</span>
- <dl>
- <li><span class="emp">Sentencias Fuzzy</span></dt>
- <dd>Encontraras sentencias marcadas con un comentario <code>"#, fuzzy"</code>.
- <code>calcurse</code> no utilizara las traducciones de ese tipo de sentencias
- hasta que tu elimines este comentario. Si una sentencia es fuzzy
- significa que ya ha sido traducida pero que desde entonces ha sido
- cambiada en el código fuente del programa, o que es una nueva sentencia para la cual
- <code>gettext</code> ha hecho una traducción 'forzosa' basada en otras sentencias
- del archivo. Esto quiere decir que tu debes revisar la traducción.
- Algunas veces, la sentencia original ha cambiado solo porque se ha arreglado
- una tipografía. En ese caso, tu no tienes que cambiar nada. Pero a veces, la
- traducción puede no ser muy precisa y necesitara ser modificada.
- Una vez que has acabado y estas satisfecho con la traducción, tan solo elimina
- el comentario <code>"#, fuzzy"</code> y la traducción podrá ser usada de nuevo
- en <code>calcurse</code>.</dd>
- <dt><span class="emp">Sentencias c-format y sentencias especiales</span></dt>
- <dd>Algunas sentencias tienen el siguiente comentario: <code>"#,
- c-format"</code>. Esto te esta diciendo que partes de la sentencia a traducir
- tienen un significado especial para el programa, puede ser que la sentencia
- contenga alguna variable, como por ejemplo % , si ves algo como esto <code>"%s"</code>,
- eso quiere decir que el programa remplazara esta variable por algún valor o por otra
- sentencia. En ese caso, puedes traducir el resto de la sentencia pero sin modificar las
- variables que pueda contener. También hay sentencias que contienen \ , como por ejemplo
- <code>\n</code> o <code>\t</code>, lo primero significa un final de linea y
- lo otro una tabulación, así pues, puedes traducir la sentencia pero con cuidado de no
- modificar estos símbolos.</dd>
- <dt><span class="emp">Las traducciones pueden ser excesivamente largas</span></dt>
- <dd>Si las lineas son demasiado largas, pueden ser partidas de la siguiente forma:
- <pre>
-msgid ""
-"alguna linea muy larga"
-"otra linea"
- </pre></dd>
- <dt><span class="emp">Cabecera del archivo-po</span></dt>
- <dd>Al principio del archivo-po, la primera sentencia forma una cabecera,
- donde hay varios tipos de información. Lo mas importante es el 'charset'. Suele parecerse
- a esto:
- <pre>
-"Content-Type: text/plain; charset=utf-8\n"
- </pre>
- Debes cumplimentar también el campo 'Last-Translator' (último traductor), para que
- los potenciales contribuidores puedan contactar contigo si ellos quieren colaborar
- en el equipo de traducción, o hacer algún tipo de corrección sobre las traducciones.
- Puedes poner solo tu nombre/nick o añadir tu dirección de email, por ejemplo:
- <pre>
-"Last-Translator: Frederic Culot &lt;frederic@culot.org&gt;\n"
- </pre></dd>
- <dt><span class="emp">Comentarios</span></dt>
- <dd>Añadir comentarios (lineas que comiencen con el carácter '#') puede ser una buena manera
- de evitar problemas o dificultades a los correctores u otros miembros de tu equipo.</dd>
- <dt><span class="emp">Tamaño de las sentencias</span></dt>
- <dd><code>calcurse</code> es un programa basado en curses/consola, así que puede ser muy dependiente
- del tamaño del terminal donde se ejecute (numero de columnas). Piensa en ello cuando lo traduzcas.
- A menudo una sentencia puede colocarse en una sola linea (la longitud standard es de 80 caracteres).
- No traduzcas a lo loco, intenta ver donde se mostrara la sentencia y adapta a ello tu traducción.
- </dd>
- <dt><span class="emp">Algunas herramientas útiles</span></dt>
- El formato de los archivos-po es muy simple, y puede ser editado con casi cualquier editor, pero
- si lo prefieres, hay unas pocas herramientas especializadas que pueden resultarte
- interesantes para traducir:
- <ul>
- <li><code>poEdit</code> (<a
- href="http://www.poedit.org/" target="_blank">
- http://www.poedit.org/</a>)</li>
- <li><code>KBabel</code> (<a
- href="http://i18n.kde.org/tools/kbabel/" target="_blank">
- http://i18n.kde.org/tools/kbabel/</a>)</li>
- <li><code>GTranslator</code> (<a
- href="http://gtranslator.sourceforge.net/" target="_blank">
- http://gtranslator.sourceforge.net/</a>)</li>
- <li><code>Emacs</code> en modo po</li>
- <li><code>Vim</code> en modo po</li>
- </ul>
- </dd>>
- <dt><span class="emp">Y finalmente</span></dt>
- <dd>Espero que te hayas divertido contribuyendo a un mundo mas internacionalizado :) Si tienes alguna
- pregunta no dudes en contactar conmigo en
- <span class="emp">frederic @ culot . org</span>.</dd>
- </dl>
-
-<h1>9.Enlaces<a name="links"></a></h1>
-<p>
- Esta sección contiene enlaces y referencias que pueden ser de tu interés.
-</p>
-
-<h2>9.1 Pagina web de <code>calcurse</code><a name="links_homepage"></a></h2>
-<p>
- La pagina web de <code>calcurse</code> es: </p>
- <pre>http://culot.org/calcurse</pre>
-
-<h2>9.2 Lista de anuncios de <code>calcurse</code><a name="links_list"></a></h2>
-<p>
- Si estas interesado en el proyecto y quieres ser avisado
- cuando salga una nueva versión, puedes suscribirte a la
- lista de anuncios de <code>calcurse</code>. Si lo haces, recibirás
- un email tan pronto como una nueva funcionalidad se añada a
- <code>calcurse</code>.</p>
-<p>
- Para suscribirte a la lista, envía un email a :
- <span class="emp">calcurse-announce @ culot . org</span> poniendo "subscribe"
- en el asunto.</p>
-
-<h2>9.3 <code>calcurse</code> RSS feed<a name="links_rss"></a></h2>
-<p>
- Otra posibilidad para enterarte de cuando aparecen nuevas versiones de Calcurse
- es seguir el RSS feed en:</p>
- <pre>http://culot.org/calcurse/news_rss.xml</pre>
-<p>
- Este RSS feed es actualizado cada vez que hay una nueva version de Calcurse disponible
- describiendo las nuevas caracteristicas.</p>
-
-<h2><div class="todo">9.4 Other links</div><a name="links_others"></a></h2>
-<div class="todo">
-<p>
- You may want to look at the ical format specification (rfc2445) at:
- <pre>http://tools.ietf.org/html/rfc2445</pre>
-<p>
- The pcal project page can be found at:
- <pre>http://pcal.sourceforge.net/</pre>
-</div>
-
-<h1>10. Gracias a ...<a name="thanks"></a></h1>
-<p>
- Es la hora de dar las gracias a personas sin las que este programa
- ¡ no existiría ! Por eso esta es una lista de las personas que contribuyeron
- y a las que me gustaría dar las gracias :
- <ul>
- <li>Alex por sus patches, ayuda y notas con la programación <code>C</code></li>
- <li>Gwen por probarlo y las discusiones sobre como mejorar <code>calcurse</code></li>
- <li>Herbert por hacer el paquete <code>calcurse</code> para FreeBSD</li>
- <li>Zul por hacer el paquete <code>calcurse</code> para NetBSD</li>
- <li>Wain, Steffen y Ronald por hacer el paquete <code>calcurse</code> para Archlinux</li>
- <li>Kevin, Ryan, y fEnIo por hacer el paquete para <code>calcurse</code>
- para Debian y Ubuntu</li>
- <li>Pascal por hacer el paquete <code>calcurse</code> para Slackware</li>
- <li>Alexandre por hacer el paquete <code>calcurse</code> para Mac OsX y
- Darwin</li>
- <li>Igor por hacer el paquete <code>calcurse</code> para ALT Linux</li>
- <li>Joel por su script del calendario que inspiro la vista de calendario de <code>calcurse</code> </li>
- <li>Michael Schulz y Chris M. por la traducción al alemán de <code>calcurse</code> y su manual</li>
- <li>Neil Williams por la traducción al ingles</li>
- <li>Tony por el patch que me ha ayudado a implementar la funcion recur_item_inday()
- <span class="todo">, and for implementing the date format configuration options</span></li>
- <li>José López por la traducción al Español de <code>calcurse</code> y su manual</li>
- <li>Jeremy Roon por la traducción al holandes</li>
- <li>Leandro Noferini por la traducción al italiano</li>
- <li><div class="todo">Erik Saule for its patch implementing the '-N', '-s', '-S', '-r' and '-D' flags</div></li>
- <li>a la gente que ha escrito softwares que me gustan y que me inspiraron, especialmente :
- <ul>
- <li><code>vim</code> por las teclas de desplazamiento</li>
- <li><code>orpheus</code> y <code>abook</code> por la documentación</li>
- <li><code>pine</code> and <code>aptitude</code>
- por la interfaz de usuario</li>
- <li><span class="todo"><code>tmux</code> for coding style</span></li>
- </ul></li>
- </ul>
-</p>
-<p>
- Y por último, muchas muchas gracias a todos los usuarios de <code>calcurse</code>
- que me han enviado sus comentarios.</p>
-
-<div class="footer">
- Copyright &copy; 2004-2010 Frédéric Culot<br>
- Traducido al Español por José López
- <code>&lt;testinground .at. gmail .dot. com&gt;</code><br>
- Calcurse version 2.8 - Last change: March 29, 2010<br>
-</div>
-</div>
-
-</body>
-</html>
diff --git a/doc/manual_fr.html b/doc/manual_fr.html
deleted file mode 100644
index 822f714..0000000
--- a/doc/manual_fr.html
+++ /dev/null
@@ -1,1505 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<!--
-/*
- * $calcurse: manual_fr.html,v 1.29 2010/03/29 18:18:02 culot Exp $
- *
- * Copyright (c) 2004-2010 Frederic Culot <frederic@culot.org>
- * All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * - Redistributions of source code must retain the above
- * copyright notice, this list of conditions and the
- * following disclaimer.
- *
- * - Redistributions in binary form must reproduce the above
- * copyright notice, this list of conditions and the
- * following disclaimer in the documentation and/or other
- * materials provided with the distribution.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- *
- */
--->
-
-<html>
-<head>
-<title>documentation de CALCURSE</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css" media="all">
- @import url(manual.css);
-</style>
-</head>
-<body>
-
-<div id="mainContent">
-
-<h1 id="title">
-<span class="main">CALCURSE - organiseur en mode texte</span></h1>
-
-<div class="warn">
-<h1>Résumé</h1> Ce manuel présente l'ensemble des fonctionnalités du
-logiciel <code>calcurse</code> et la manière dont on peut les
-utiliser. La procédure d'installation du programme depuis ses sources
-est tout d'abord décrite, ainsi que les différentes façon dont
-<code>calcurse</code> peut être lancé. L'interface du programme est
-ensuite présentée, avec l'ensemble des options qui permettent la
-configuration du logiciel. Sont enfin expliquées les procédures à suivre
-pour faire remonter les bogues et pour contribuer au développement de
-<code>calcurse</code>.
-</div>
-
-<div id="toc">
-<h1>Table des matières</h1>
-<ul>
- <li><a href="#intro">1. Introduction</a></li>
- <li><a href="#overview">2. Aperçu du logiciel</a>
- <ul>
- <li><a href="#overview_history">2.1 Origine de Calcurse</a></li>
- <li><a href="#overview_features">2.2 Caractéristiques importantes</a></li>
- </ul></li>
- <li><a href="#install">3. Installation</a>
- <ul>
- <li><a href="#install_requirements">3.1 Pré-requis</a>
- <ul>
- <li><a href="#install_requirements_ncurses">3.1.1 Librairie <code>ncurses</code></a></li>
- <li><a href="#install_requirements_gettext">3.2.2 Librairie <code>gettext</code></a></li>
- </ul></li>
- <li><a href="#install_process">3.2 Processus d'installation</a></li>
- </ul></li>
- <li><a href="#basics">4. Présentation générale</a>
- <ul>
- <li><a href="#basics_invocation">4.1 Invocation</a>
- <ul>
- <li><a href="#basics_invocation_commandline">4.1.1 Arguments en ligne de commande</a></li>
- <li><a href="#basics_invocation_variable">4.1.2 Variable d'environnement pour l'i18n</a></li>
- <li><a href="#basics_invocation_environment">4.1.3 Autres variables d'environnement</a></li>
- </ul></li>
- <li><a href="#basics_interface">4.2 Interface utilisateur</a>
- <ul>
- <li><a href="#basics_interface_noninteractive">4.2.1 Mode non-interactif</a></li>
- <li><a href="#basics_interface_interactive">4.2.2 Mode Interactif</a></li>
- </ul></li>
- <li><a href="#basics_daemon"><span class="todo">4.3 Background mode</span></a></li>
- <li><a href="#basics_files">4.4 Fichiers</a></li>
- <li><a href="#basics_import_export">4.5 Fonctions d'import/export</a>
- <ul>
- <li><a href="#basics_import">4.5.1 Import</a></li>
- <li><a href="#basics_export">4.5.2 Export</a></li>
- </ul></li>
- <li><a href="#basics_help">4.6 Aide en ligne</a></li>
- </ul></li>
- <li><a href="#options">5. Options</a>
- <ul>
- <li><a href="#options_general">5.1 Options générales</a></li>
- <li><a href="#options_keys">5.2 Raccourcis clavier</a>
- <li><a href="#options_colors">5.3 Thèmes graphiques</a></li>
- <li><a href="#options_layout">5.4 Disposition des panneaux</a></li>
- <li><a href="#options_sidebar"><span class="todo">5.5 Sidebar configuration</span></a></li>
- <li><a href="#options_notify">5.6 Réglages de la barre de notification</a></li>
- </ul></li>
- <li><a href="#known_bugs">6. Bogues connus</a></li>
- <li><a href="#bugs">7. Rapporter les bogues et commentaires</a></li>
- <li><a href="#contribute">8. Comment contribuer?</a>
- <ul>
- <li><a href="#contribute_documentation">8.1 Traduction de la documentation</a></li>
- <li><a href="#contribute_i18n">8.2 Traduction de <code>calcurse</code></a>
- <ul>
- <li><a href="#contribute_i18n_overview">8.2.1 Aperçu</a></li>
- <li><a href="#contribute_i18n_translator">8.2.2 Etapes de la traducion</a></li>
- <li><a href="#contribute_i18n_po-files">8.2.3 Fichiers <code>po</code></a></li>
- </ul></li>
- </ul></li>
- <li><a href="#links">9. Liens</a>
- <ul>
- <li><a href="#links_homepage">9.1 Site internet de <code>calcurse</code></a></li>
- <li><a href="#links_list">9.2 Liste de diffusion de <code>calcurse</code></a></li>
- <li><a href="#links_rss">9.3 Flux RSS</a></li>
- <li><a href="#links_others">9.4 Autres liens</a></li>
- </ul></li>
- <li><a href="#thanks">10. Remerciements</a></li>
-</ul>
-</div>
-
-
-<h1>1. Introduction<a name="intro"></a></h1>
-<p>
-<code>calcurse</code> est un logiciel composé d'un calendrier et d'un organiseur
-personnel en mode texte. Il permet de stocker les évènements et rendez-vous,
-ainsi qu'une liste de tâches à effectuer. Un système de notification,
-entièrement configurable par l'utilisateur, permet d'être prévenu lorsque
-l'heure d'un rendez-vous approche. L'interface utilisateur est elle aussi
-configurable, et peut s'adapter aux besoins de chacun. Enfin, un système d'aide
-en ligne permet d'obtenir des renseignements sur toutes les commandes
-disponibles.
-</p>
-
-<h1>2. Aperçu du logiciel<a name="overview"></a></h1>
-<h2>2.1 Origine de Calcurse<a name="overview_history"></a></h2>
-<p>
- J'ai commencé à penser à ce projet à la fin de mon doctorat
- en astrophysique... Je commençais en effet à avoir de plus
- en plus de mal à m'organiser, et j'avais vraiment besoin d'un
- bon outil pour m'aider dans cette tâche difficile ;)
-</p>
-<p>
- D'autre part, j'apprécie beaucoup les logiciels qui font appel
- à des Interfaces en Mode Texte, parce que je les trouve plus
- simples, plus rapides, plus portables et plus efficaces. J'ai
- alors commencé à programmer un calendrier rudimentaire qui
- utilisait une interface de ce type. En plus de cela, je
- voulais améliorer mes connaissances en <code>C</code>, langage
- de programmation que je n'avais utilisé jusqu'alors que dans
- le cadre de petits projets pendant mes études. J'ai donc pensé
- que ce serait une bonne chose de me lancer dans ce projet,
- puisque cela me permettrait à la fois de mieux m'organiser, et
- d'apprendre à mieux programmer en <code>C</code>!
-</p>
-<p>
- Malheureusement, j'ai obtenu mon doctorat avant de terminer
- <code>calcurse</code>, mais j'ai tout de même voulu continuer
- à travailler sur ce projet, en espérant que ce
- programme serait utile à d'autres
- personnes. Voilà comment est né
- <code>calcurse</code>...
-</p>
-<p>
- Mais au fait, pourquoi 'calcurse' ? Et bien ce nom provient
- simplement de la concaténation de 'CALendrier' et de
- 'nCURSEs', qui est le nom de la librairie utilisée pour
- construire l'interface utilisateur.
-</p>
-
-<h2>2.2 Caractéristiques importantes<a name="overview_features"></a></h2>
-<p>
- <code>Calcurse</code> est multi-plateformes et est conçu pour
- être léger, rapide et fiable. Il doit être utilisé dans un
- terminal ou une console, soit localement ou bien sur une
- machine distante par l'intermediaire d'une liaison ssh (ou
- similaire).
-</p>
-<p>
- <code>Calcurse</code> peut être lancé dans deux modes différents:
- soit interactif, soit non-interactif. Le premier mode permet
- de visualiser son organiseur personnel pratiquement sous
- n'importe quel environnement, grâce à l'interface en mode texte.
- Le deuxième mode permet de créer facilement des penses-bête en
- ajoutant <code>calcurse</code> avec les arguments appropriés dans
- la table cron ou dans le script d'initialisation du shell.
-</p>
-<p>
- De plus, <code>calcurse</code> a été créé en prenant en compte
- l'utilisateur final à chaque étape de sa conception,
- c'est-à-dire en essayant d'être le plus intuitif
- possible. Cela implique la présence d'une aide en ligne
- exhaustive, ainsi que le rappel de toutes les commandes
- possibles dans la barre de status. L'interface utilisateur
- est également configurable, et l'on peut choisir parmi de
- nombreuses combinaisons possibles de couleurs et de positions
- des fenêtres. Les raccourcis clavier peuvent être définis aussi
- par l'utilisateur, pour correspondre aux besoins de chacun.
- Enfin, le système de notification est
- entièrement configurable, l'utilisateur peut donc choisir la
- manière dont il veut être prévenu de l'approche d'un
- rendez-vous. Les notifications peuvent également être envoyées
- même si l'interface utilisateur n'est pas lancée, car
- <code>calcurse</code> peut tourner en tâche de fond (mode démon).
-</p>
-
-<h1>3. Installation<a name="install"></a></h1>
-<h2>3.1 Pré-requis<a name="install_requirements"></a></h2>
-<h3>3.1.1 Librairie <code>ncurses</code><a name="install_requirements_ncurses"></a></h3>
-<p>
- L'installation de <code>Calcurse</code> ne nécessite qu'un
- compilateur <code>C</code>, comme <code>cc</code> ou <code>gcc</code>,
- et la librairie <code>ncurses</code>.
- Il serait très surprenant que vous n'ayez pas déjà la librairie
- <code>ncurses</code> d'installée sur votre machine, mais si
- c'est le cas, vous pourrez la trouver à l'adresse suivante :
-</p>
-<pre>http://ftp.gnu.org/pub/gnu/ncurses/</pre>
-
-<div class="todo">
- <p class="rq"><span class="valorize">Note:</span>
- It is also possible to link <code>calcurse</code> against the
- <code>ncursesw</code> library (ncurses with support for unicode).
- However, UTF-8 is not yet supported by <code>calcurse</code>.</p>
-</div>
-
-<h3>3.1.2 Librairie <code>gettext</code><a name="install_requirements_gettext"></a></h3>
-<p>
- <code>calcurse</code> s'aide de la librairie
- <code>gettext</code> pour le support de l'internationalisation
- (noté <span class="emp">i18n</span> ci-après). Cela signifie que
- <code>calcurse</code> peut fournir des messages multilingues
- s'il est compilé avec le support NLS (<span class="emp">Native
- Language Support</span> - <span class="emp">Support de Langage
- Natif</span>).
-</p>
-<p>
- Cependant, ce support est optionnel et si vous n'avez pas
- besoin de la traduction des messages affichés, vous pouvez
- désactiver cette option. La désactivation du support
- <span class="emp">NLS</span> s'effectue en passant l'option
- <code>--disable-nls</code> à <code>configure</code>
- (voir la section <a href="#install_process">Processus
- d'Installation</a>).
-</p>
-<p>
- Pour vérifier que les utilitaires <code>gettext</code> sont
- bien installés sur votre systsème, vous pouvez
- par exemple vérifier la présence du fichier
- <code>libintl.h</code> en tapant : </p>
- <pre>locate libintl.h</pre>
-<p>
- Dans l'éventualité où ce fichier ne serait pas trouvé,
- vous pouvez obtenir les sources de <code>gettext</code>
- à l'adresse suivante :</p>
- <pre>http://ftp.gnu.org/pub/gnu/gettext/</pre>
-<p>
- <p class="rq"><span class="valorise">Remarque :</span> Même si
- <code>libintl.h</code> est bien localisé par la commande
- précédente, il peut être utile de spécifier son emplacement au
- moment de lancer le <a href="#install_process">processus
- d'installation</a>, en passant l'option
- <code>--with-libintl-prefix</code> au script
- <code>configure</code>. En effet, ce script pourrait ne pas
- trouver le fichier <code>libintl.h</code> si celui-ci n'est
- pas installé dans un endroit usuel.</p>
-
-
-<h2>3.2 Processus d'installation<a name="install_process"></a></h2>
-<p>
- Vous devez tout d'abord décompresser l'archive source de la
- manière suivante :</p>
- <pre>tar zxvf calcurse-2.8.tar.gz</pre>
-<p>
- Une fois que vous remplissez tous les pré-requis nécessaires à
- l'installation, le processus de compilation est simple et suit
- les trois étapes usuelles :
- <ol>
- <li><code>./configure</code></li>
- <li><code>make</code></li>
- <li><code>make install</code> (peut nécessiter les privilèges
- super-utilisateur)</li>
- </ol>
-</p>
-<p>
- Vous pouvez obtenir la liste des options possibles en tapant
- <code>./configure --help</code>.
-</p>
-
-
-<h1>4. Présentation générale<a name="basics"></a></h1>
-<h2>4.1 Invocation<a name="basics_invocation"></a></h2>
-<h3>4.1.1 Arguments en ligne de commande<a name="basics_invocation_commandline"></a></h3>
-<p>
- Lors de son appel en ligne de commande, <code>calcurse</code>
- accepte les arguments suivants (les arguments courts ou longs
- sont supportés) :</p>
- <p>
-
- <dl>
- <dt><code>-a, --appointment</code></dt>
- <dd>
- Affiche les rendez-vous pour la date du jour, puis quitte.
- <p class="rq"><span class="valorise">Remarque:</span> le calendrier à utiliser peut être
- spécifié en utilisant l'option '-c'.</p>
- </dd>
- <dt><code>-c &lt;fichier&gt;, --calendar &lt;fichier&gt;</code></dt>
- <dd>
- Spécifie le fichier calendrier à utiliser.
- Le calendrier par défaut est celui contenu dans
- <code>~/.calcurse/apts</code>
- (voir la section <a href="#basics_files">Fichiers</a>).
- </dd>
- <dt><code>-d &lt;date|num&gt;, --day &lt;date|num&gt;</code></dt>
- <dd>
- Affiche les rendez-vous pour la date ou pour le nombre de
- jours indiqués, suivant le format de l'argument. Deux
- formats différents sont acceptés :
- <ul>
- <li>une date (voir ci-dessous pour les formats disponibles).</li>
- <li>un nombre 'n'.</li>
- </ul>
- Dans le premier cas, la liste des rendez-vous pour la
- date spécifiée sera affichée, alors que dans le
- deuxième cas, la liste des rendez-vous pour les 'n'
- jours à venir sera retournée.
- Par exemple, taper <code>calcurse -d 3</code> fera
- s'afficher les rendez-vous pour aujourd'hui, demain
- et après-demain.
- <div class="todo">
- Possible formats for specifying the date are defined inside the
- general configuration menu (see
- <a href="#options_general">General options</a>), using the
- <code>input_datefmt</code> variable.
- </div>
- <p class="rq"><span class="valorise">Remarque:</span>
- comme pour l'option '-a', le fichier contenant le calendrier
- à lire peut être spécifié en utilisant l'option '-c'.</p>
- </dd>
- <dt><code>-D &lt;dir&gt;, --directory &lt;dir&gt;</code></dt>
- <dd>
- Indique le répertoire dans lequel seront stockées les données.
- Cette option n'est pas compatible avec l'option '-c'. Si ce
- répertoire n'est pas spécifié, celui utilisé par défaut est
- <code>'~/.calcurse/'</code>.
- </dd>
- <dt><code>-h, --help</code></dt>
- <dd>
- Affiche l'aide décrivant les options en ligne de commande,
- puis quitte.</dd>
- <dt><code>-i &lt;file&gt;, --import &lt;file&gt;</code></dt>
- <dd>
- Importe les données au format icalendar contenues dans le fichier
- <code>file</code>.
- </dd>
- <dt><code>-n, --next</code></dt>
- <dd>
- Affiche le rendez-vous suivant dans les prochaines 24 heures, puis
- quitte.
- Le temps indiqué représente le nombre d'heures et de
- minutes restantes avant le rendez-vous.
- <p class="rq"><span class="valorise">remarque:</span>
- le fichier contenant le calendrier à lire peut
- être spécifié en utilisant l'option '-c'.</p>
- </dd>
- <dt><code>-N, --note</code></dt>
- <dd>
- Lorsque cette option est utilisée avec les options '-a' ou '-t',
- le contenu des notes associées aux rendez-vous et aux tâches sera
- également affiché.
- </dd>
- <dt><code>-r[num], --range[=num]</code></dt>
- <dd>
- Affiche les rendez-vous et les événements pour le nombre num de
- jours puis quitte. Si l'argument optionnel num n'est pas donné,
- une plage d'une seule journée sera utilisée.
- </dd>
- <dt><code>-s[date], --startday[=date]</code></dt>
- <dd>
- Affiche les rendez-vous et les événements depuis la date indiquée
- puis quitte. Si l'argument optionnel date n'est pas donné, la journée
- courante sera utilisée.
- </dd>
- <dt><code>-S&lt;regex&gt;, --search=&lt;regex&gt;</code></dt>
- <dd>
- Lorsque cette option est utilisée avec les options '-a', '-d', '-r',
- '-s' ou '-t', seuls les éléments dont la description correspond à
- l'expression régulière passée en argument seront affichés.
- </dd>
- <dt><code>--status</code></dt>
- <dd>
- <div class="todo">
- Display the status of running instances of calcurse. If
- calcurse is running, this will tell if the interactive
- mode was launched or if calcurse is running in background.
- The process pid will also be indicated.
- </div>
- </dd>
- <dt><code>-t[num], --todo[=num]</code></dt>
- <dd>
- Affiche la liste des 'todo', puis quitte. Si le nombre optionnel
- <code>num</code> est indiqué, alors uniquement les tâches
- ayant une priorité égale à <code>num</code> seront
- affichées.
- La priorité doit être comprise entre 1 (priorité la plus haute) et 9
- (priorité la plus basse). Il est également possible de spécifier 0
- pour la priorité, auquel cas seules les tâches completées seront
- affichées.</p>
- </dd>
- <dt><code>-v, --version</code></dt>
- <dd>
- Affiche la version de <code>calcurse</code>, puis quitte.
- </dd>
- <dt><code>-x[format], --export[=format]</code></dt>
- <dd>
- Exporte les données utilisateur au format spécifié. Les évènements,
- rendez-vous et tâches sont convertis et imprimés sur la sortie
- standard. Deux formats d'export différents sont disponibles :
- le format ical et le format pcal (voir la section
- <a href="#links_others">Liens</a> ci-dessous).
- Si l'argument optionnel <code>format</code> n'est pas indiqué par
- l'utilisateur, alors le format ical sera utilisé par défaut.
- <p class="rq"><span class="valorise">Note:</span>
- afin de sauvegarder les données exportées dans un fichier,
- il est nécessaire de rediriger la sortie standard en utilisant une
- commande comme celle-ci:
- <code>$ calcurse --export &gt; mon_fichier.dat</code></p>
- </dd>
- </dl>
-
-
-<h3>4.1.2 Variable d'environnement pour l'i18n<a name="basics_invocation_variable"></a></h3>
-<p>
- <code>calcurse</code> peut être compilé avec le support
- <span class="emp">NLS</span> (voir <a
- href="#install_requirements_gettext">Librairie
- <code>gettext</code></a>). Ainsi, si vous voulez que les
- messages affichés apparaissent dans votre langue natale,
- assurez-vous tout d'abord que celle-ci est présente dans le
- fichier <code>po/LINGUAS</code>. Ce fichier indique toutes
- les traductions disponibles par l'intermédiaire d'un code de
- deux lettres (par exemple, <span class="emp">fr</span>
- représente le français). Si vous ne trouvez pas votre langue,
- il serait très apprécié que vous apportiez votre aide pour
- traduire <code>calcurse</code> (voir la partie <a
- href="#contribute">Comment contribuer?</a>).</p>
-<p>
- Si votre langue est disponible, lancez <code>calcurse</code>
- en utilisant la commande suivante : </p>
- <pre>LC_ALL=fr_FR calcurse</pre>
- <p>où <span class="emp">fr_FR</span> doit être remplacé par la
- <span class="emp">locale</span> (code de la langue suivi du
- code pays) correspondant à la traduction voulue.</p>
-<p>
- Il est également recommandé de spécifier le codage à utiliser,
- car dans certains cas des problèmes d'affichage des accents
- peuvent survenir. Ce codage est indiqué au début du fichier po
- correspondant à la langue voulue. Par exemple, vous pouvez
- remarquer dans le fichier fr.po que le codage utilisé est
- iso-8859-1. Vous pouvez donc le préciser au lancement de
- <code>calcurse</code>:</p>
- <pre>LC_ALL=fr_FR.ISO8859-1 calcurse</pre>
-
-<h3>4.1.3 Autres variables d'environnement<a name="basics_invocation_environment"></a></h3>
-<p>
- Les variables d'environnement suivantes agissent sur le comportement de
- <code>calcurse</code>:</p>
- <dl>
- <dt><code>VISUAL</code></dt>
- <dd>Indique l'éditeur externe qui sera utilisé pour rédiger des notes.
- </dd>
- <dt><code>EDITOR</code></dt>
- <dd>Si la variable d'environnement <code>VISUAL</code> n'est pas
- renseignée, l'éditeur externe qui sera utilisé par défaut est celui
- contenu dans la variable <code>EDITOR</code>. Si aucune de ces deux
- variables n'est renseignée, alors <code>/usr/bin/vi</code> sera
- appelé par défaut.
- </dd>
- <dt><code>PAGER</code></dt>
- <dd>Indique le visualiseur utilisé par défaut pour consulter les
- notes. Si cette variable n'est pas renseignée, alors
- <code>/usr/bin/less</code> sera utilisé.
- </dd>
- </dl>
-
-<h2>4.2 Interface utilisateur<a name="basics_interface"></a></h2>
-<h3>4.2.1 Mode non-interactif<a name="basics_interface_noninteractive"></a></h3>
-<p>
- Lorsque il est appelé avec au moins un des arguments suivants:
- <code>-a</code>, <code>-d</code>, <code>-h</code>,
- <code>-n</code>, <code>-t</code>, <code>-v</code>, <code>-x</code>,
- <code>calcurse</code> est lancé en mode non-interactif.
- Cela signifie que l'information demandée sera affichée,
- puis <code>calcurse</code> quittera et vous serez ramené
- au prompt de l'interpréteur de commandes.</p>
-<p>
- De cette manière, il est possible de rajouter une ligne telle
- que <code>'calcurse --todo --appointment'</code> dans le fichier d'initialisation
- de son environnement, afin de faire s'afficher à chaque
- début de session la liste des tâches à faire et des rendez-vous
- planifiés pour la journée.</p>
-
-
-<h3>4.2.2 Mode interactif<a name="basics_interface_interactive"></a></h3>
-<div class="todo">
- <p class="rq"><span class="valorise">Note:</span>
- Key bindings that are indicated in this manual correspond to
- the default ones, defined when <code>calcurse</code> is launched
- for the first time. If those key bindings do not suit user's needs,
- it is possible to change them within the keys configuration menu
- (see <a href="#options_keys">key bindings</a>).</p>
-</div>
-<p>
- Lorsqu'il est appelé sans aucun argument ou uniquement avec
- l'option <code>'-c'</code>, <code>calcurse</code> est lancé
- en mode interactif. Dans ce mode s'affiche une interface qui
- contient trois panneaux différents, qu'il est possible de
- sélectionner cycliquement en utilisant la touche 'TAB', ainsi
- que d'une barre de notification et une autre de status
- (voir la figure ci-dessous).</p>
- <pre>
-
- panneau rendez-vous---. .---panneau calendrier
- | |
- v v
- +------------------------------------++----------------------------+
- | Rendez-vous || Calendrier |
- |------------------------------------||----------------------------|
- | (|) Avril 6, 2006 || Avril 2006 |
- | ||Lun Mar Mer Jeu Ven Sam Dim |
- | || 1 2 |
- | || 3 4 5 6 7 8 9 |
- | || 10 11 12 13 14 15 16 |
- | || 17 18 19 20 21 22 23 |
- | || 24 25 26 27 28 29 30 |
- | || |
- | |+----------------------------+
- | |+----------------------------+
- | || Tâches | panneau
- | ||----------------------------| tâches à
- | || | faire
- | || | |
- | || |&lt;--.
- | || |
- +------------------------------------++----------------------------+
- |---[ Lun 22-11-2006 | 18:11:43 ]---(apts)----&gt; 01:20 :: dîner &lt;---|&lt;--.
- +------------------------------------------------------------------+ barre de
- | ? Aide R Retracer H/L -+1 Jour G Aller à C Config | notification
- | Q Quitter S Sauver J/K -+1 Sem. Tab Chg vue |&lt;-.
- +------------------------------------------------------------------+ |
- |
- barre de status
-
- </pre>
-<p>
- Le premier panneau représente un calendrier qui permet de
- sélectionner un jour en particulier. Le second panneau contient
- une liste d'évènements et les rendez-vous du jour, et le dernier
- contient une liste des tâches à faire, mais qui ne sont pas
- assignées à une journée en particulier.</p>
-<div class="todo">
-<p>
- Depending on the selected view, the calendar could either display
- a monthly (default as shown in previous figure) or weekly view.
- The weekly view would look like the following:</p>
- <pre>
-
-+------------------------------------+
-| Calendar |
-|----------------------------(# 13)--|
-| Mon Tue Wed Thu Fri Sat Sun |
-| 29 30 31 01 02 03 04 |
-| <----+-- slice 1: 00:00 to 04:00 AM
-| -- -- -- -- -- -- |
-| <----+-- slice 2: 04:00 to 08:00 AM
-| -- -- -- -- -- -- |
-| <----+-- slice 3: 08:00 to 12:00 AM
-| - -- -- -- -- -- -- - <-+-- midday
-| <----+-- slice 4: 12:00 to 04:00 PM
-| -- -- -- -- -- -- |
-| <----+-- slice 5: 04:00 to 08:00 PM
-| -- -- -- -- -- -- |
-| <----+-- slice 6: 08:00 to 12:00 PM
-+------------------------------------+
-
- </pre>
-<p>
- The current week number is displayed on the top-right side of the panel
- (<span class="emp"># 13</span> meaning it is the 13th week of the year
- in the above example). The seven days of the current week are displayed
- in column. Each day is divided into slices of 4 hours each (6 slices in
- total, see figure above). A slice will appear in a different color if
- an appointment falls into the corresponding time-slot.
-</p>
-</div>
-<p>
- On peut remarquer dans le panneau des rendez-vous le signe
- <span class="emp">'(|)'</span>
- placé juste devant la date. Ce signe représente la phase de la lune.
- En fonction de la phase actuelle de celle-ci, un des signes suivants
- peut-être indiqué :
- <dl class="compact">
- <dt>'<code> |) </code>':</dt>
- <dd>premier quartier</dd>
- <dt>'<code> (|) </code>':</dt>
- <dd>pleine lune</dd>
- <dt>'<code> (| </code>':</dt>
- <dd>dernier quartier</dd>
- <dt>'<code> | </code>':</dt>
- <dd>nouvelle lune</dd>
- <dt>aucun signe:</dt>
- <dd>la phase actuelle de la lune ne correspond à
- aucune des phases ci-dessus</dd>
- </dl>
- </p>
- <p>
- Tout en bas de l'écran on retrouve une barre de status, qui indique
- les actions possibles en fonction du contexte, ainsi que la
- touche qui doit être pressée pour effectuer cette action.</p>
- <p>
- Juste au-dessus de cette barre se trouve la barre de notification, qui
- indique les informations suivantes, de gauche à droite : la date du jour,
- l'heure courante, le fichier calendrier actuellement ouvert (il s'agit
- de apts dans la copie d'écran, qui est le fichier par défaut, comme indiqué
- dans la section suivante), et le premier rendez-vous programmé dans les
- prochaines 24 heures. Dans cet exemple, il s'agit d'un dîner qui aura lieu
- dans une heure et vingt minutes.</p>
- <p class="rq"><span class="valorise">Remarque:</span>
- Certaines actions, comme éditer ou ajouter un
- elément, nécessitent de renseigner du texte par
- l'intermédiaire de l'éditeur de ligne de commande
- fournit avec <code>calcurse</code>.</p>
- <p>
- Dans cet éditeur, si la ligne de commande est plus longue que la
- largeur de l'écran, le caractère '&gt;', '*', ou '&lt;'
- sera rajouté dans la dernière colonne s'il reste du texte
- après, avant et après, ou avant la position courante,
- respectivement. La ligne défile horizontalement si
- nécessaire.</p>
- <p>
- De plus, il existe des combinaisons de touches pour
- effectuer certaines actions courantes utiles lors de l'édition
- de textes. Voici ces raccourcis:
- <dl class="compact">
- <dt><code>^a</code>:</dt>
- <dd>déplacer le curseur au début de la ligne</dd>
- <dt><code>^b</code>:</dt>
- <dd>déplacer le curseur d'une position en arrière</dd>
- <dt><code>^d</code>:</dt>
- <dd>effacer le caractère sous le curseur</dd>
- <dt><code>^e</code>:</dt>
- <dd>déplacer le curseur en fin de ligne</dd>
- <dt><code>^f</code>:</dt>
- <dd>déplacer le curseur d'une position en avant</dd>
- <dt><code>^h</code>:</dt>
- <dd>effacer le caractère précédent</dd>
- <dt><code>^k</code>:</dt>
- <dd>effacer le texte depuis la position courante
- jusqu'à la fin de la ligne</dd>
- <dt><code>ESC</code>:</dt>
- <dd>annuler l'édition du texte courant</dd>
- </dl>
-</p>
-
-<div class="todo">
-<h2>4.3 Background mode<a name="basics_daemon"></a></h2>
-
-<p>When the daemon mode is enabled in the notification configuration menu
-(see <a href="#options_notify">Notify-bar settings</a>), <code>calcurse</code> will stay
-in background when the user interface is not running. In background mode,
-<code>calcurse</code> checks for upcoming appointments and runs the user-defined
-notification command when necessary. When the user interface is started again,
-the daemon automatically stops.</p>
-
-<p><code>calcurse</code> background activity can be logged (set the
-<code>notify-daemon_log</code> variable in the notification configuration
-<a href="#options_notify">menu</a>), and in that case, information about the daemon
-start and stop time, reminders' command launch time, signals received... will be written
-in the <code>daemon.log</code> file (see section <a href="#basics_files">files</a>).</p>
-
-<p>
-Using the <code>--status</code> command line option (see section
-<a href="#basics_invocation_commandline">Command line arguments</a>),
-one can know if <code>calcurse</code> is currently running in background or not.
-If the daemon is running, a message like the following one will be displayed (the pid of
-the daemon process will be shown):
-<pre>calcurse is running in background (pid 14536)</pre>
-
-<p class="rq"><span class="valorise">Note:</span>
-To stop the daemon, just send the <code>TERM</code> signal to it, using a command such as:
-<code>'kill daemon_pid'</code>, where <span class="emp">daemon_pid</span> is the process id
-of the daemon (14536 in the above example).
-</p>
-</div>
-
-<h2>4.4 Fichiers<a name="basics_files"></a></h2>
-<p>
- La structure de fichiers suivante est créée dans le répertoire
- <code>$HOME</code> de l'utilisateur (ou bien dans le répertoire
- indiqué par l'option '-D') la première fois que
- <code>calcurse</code> est lancé :</p>
- <pre>
-$HOME/.calcurse/
- |___notes/
- |___conf
- |___keys
- |___apts
- |___todo
- </pre>
- <dl class="compact">
- <dt><code>notes/</code>:</dt>
- <dd>ce sous-répertoire contient la description des notes
- rattachées aux rendez-vous, événements ou tâches. Un fichier
- texte est créé par note, et son nom est construit à l'aide de
- la fonction mkstemp(3). Ainsi, l'unicité de ce nom est assurée,
- mais il n'a pas de relation avec l'élément auquel la note est
- rattachée.</dd>
- <dt><code>conf</code>:</dt>
- <dd>ce fichier contient la configuration de l'utilisateur</dd>
- <dt><code>keys</code>:</dt>
- <dd>ce fichier contient les raccourcis clavier définis par l'utilisateur</dd>
- <dt><code>apts</code>:</dt>
- <dd>ce fichier contient tous les événements ainsi que les
- rendez-vous de l'utilisateur</dd>
- <dt><code>todo</code>:</dt>
- <dd>ce fichier contient la liste des tâches à effectuer</dd>
- </dl>
-
-<div class="todo">
- <p class="rq"><span class="valorise">Note:</span>
- If the logging of calcurse daemon activity was set in the notification
- configuration menu, the extra file <code>daemon.log</code> will appear
- in calcurse data directory. This file contains logs about calcurse activity
- when running in background.
- </p>
-</div>
-
-<h2>4.5 Fonctions d'import/export<a name="basics_import_export"></a></h2>
-<p>
- Les possibilités offertes par <code>calcurse</code> pour importer et exporter
- des données sont décrites ci-dessous.
-</p>
-
-<h3>4.5.1 Import<a name="basics_import"></a></h3>
-<p>
- Les données au format icalendar tel que décrit dans la spécification
- rfc2445 (voir la section <a href="#links_others">liens</a> ci-dessous)
- peuvent être importées dans calcurse. L'import ical de calcurse est basé
- sur la version 2.0 de la norme rfc2445, mais pour le moment, seul un
- sous-ensemble de cette spécification a été implémenté.
-</p>
-<p>
- Les propriétés suivantes sont gérées par calcurse:
- <ul>
- <li>éléments <code>VTODO</code>:<br>
- "PRIORITY", "VALARM", "SUMMARY", "DESCRIPTION"</li>
- <li>éléments <code>VEVENT</code>:<br>
- "DTSTART", "DTEND", "DURATION", "RRULE", "EXDATE", "VALARM", "SUMMARY",
- "DESCRIPTION"</li>
- </ul>
-</p>
-<p>
- La propriété "DESCRIPTION" du format icalendar sera convertie dans calcurse
- en ajoutant une note à l'élément. Si une propriété "VALARM" est trouvée,
- l'élément sera marqué comme étant important et l'utilisateur recevra une
- notification (ceci ne fonctionne que pour les rendez-vous).
-</p>
-<p>
- Voici la liste des propriétés qui ne sont pas encore implémentées:
- <ul>
- <li>les durées négatives ne sont pas prises en compte (l'élément n'est
- pas importé)</li>
- <li>certaines fréquences de répétition ne sont pas reconnues:<br>
- "SECONDLY" / "MINUTELY" / "HOURLY"</li>
- <li>Certains mots-clés liés aux répétitions ne sont pas reconnus
- (ceux commençant par 'BY'):<br>
- "BYSECOND" / "BYMINUTE" / "BYHOUR" / "BYDAY" / "BYMONTHDAY"<br>
- "BYYEARDAY" / "BYWEEKNO" / "BYMONTH" / "BYSETPOS"<br>
- plus "WKST"</li>
- <li>le mot-clé "EXRULE" n'est pas reconnu</li>
- <li>les fuseaux horaires ne sont pas pris en compte</li>
- </ul>
-</p>
-
-<h3>4.5.2 Export<a name="basics_export"></a></h3>
-<p>
- Deux formats peuvent êtres utilisés pour l'export des données:
- <code>ical</code> et <code>pcal</code> (voir la section
- <a href="#links_others">Liens</a> ci-dessous pour avoir plus d'informations
- concernant ces formats).
-</p>
-
-<h2>4.6 Aide en ligne<a name="basics_help"></a></h2>
-<p>
- A n'importe quel moment, le système d'aide en ligne peut être
- appelé en pressant la touche '?'. Une fois rentré dans l'aide,
- les informations sur une commande spécifique peuvent être
- obtenues en appuyant sur la touche correspondant à cette
- commande.
- </p>
-
-<h1>5. Options<a name="options"></a></h1>
-<p>
- Tous les paramètres de <code>calcurse</code> sont configurables
- à partir du menu <code>Configuration</code>, accessible en appuyant
- sur 'C'. L'utilisateur se voit alors présenté un second menu
- avec trois choix possibles : appuyer à nouveau sur 'C' amène
- au menu de sélection des couleurs de l'interface, appuyer sur
- 'L' permet de choisir parmi différents emplacements pour les
- panneaux de la fenêtre principale de <code>calcurse</code>,
- appuyer sur 'G' vous permet de fixer les options générales, 'K'
- vous permet d'accéder au menu de configuration des raccourcis clavier,
- et enfin
- les paramètres de la barre de notification peuvent être fixés
- en appuyant sur 'N'.</p>
-
-
-<h2>5.1 Options générales<a name="options_general"></a></h2>
-<p>
- Ces options contrôlent le comportement général de
- <code>calcurse</code>, comme décrit ci-dessous :</p>
- <dl>
- <dt><code>sauvegarde_automatique</code>
- (valeur par défaut: <span class="emp">oui</span>)</dt>
- <dd>Cette option permet de sauvegarder automatiquement
- les données de l'utilisateur avant de quitter, si elle est
- fixée à <span class="emp">oui</span>.
- <p class="rq"><span class="valorise">attention:</span>
- Aucune donnée ne sera automatiquement
- sauvegardée si cette variable est fixée à <code>non</code>.
- Cela signifie que l'utilisateur doit appuyer sur 'S'
- (pour sauvegarder) pour retrouver ses modifications au prochain
- lancement de <code>calcurse</code>.</p>
- </dd>
-
- <dt><code><span class="todo">periodic_save</code>
- (default: <span class="emp">0</span>)</span></dt>
- <dd><span class="todo">If different from '0', user's data will be automatically
- saved every <span class="emp">periodic_save</span> minutes.
- When an automatic save is performed, two asterisks
- (i.e. '<code>**</code>') will appear on the top right-hand side
- of the screen).</span>
- </dd>
-
- <dt><code>confirmer_pour_quitter</code>
- (valeur par défaut: <span class="emp">oui</span>)</dt>
- <dd>Si cette option est fixée à <span class="emp">oui</span>,
- la confirmation
- de l'utilisateur est nécessaire avant de pouvoir quitter.
- Autrement, appuyer sur 'Q' provoquera l'arrêt de
- <code>calcurse</code> sans demander confirmation.
- </dd>
- <dt><code>confirmer_pour_effacer</code>
- (valeur par défaut: <span class="emp">oui</span>)</dt>
- <dd>Si cette option est fixée à <span class="emp">oui</span>, appuyer sur 'D'
- pour effacer un élement (soit une tâche, un rendez-vous ou bien
- un évenement) provoquera l'apparition d'un message demandant
- la confirmation de l'utilisateur avant d'effacer cet élement.
- Si cette option est fixée à <span class="emp">non</span>, aucune confirmation
- ne sera demandée avant l'effacement d'un élement.
- </dd>
- <dt><code>masquer_messages_système</code>
- (valeur par défaut: <span class="emp">non</span>)</dt>
- <dd>Fixer cette option à <span>oui</span> provoque la disparition des
- messages relatifs aux enregistrements ou lectures des fichiers
- de données. Ceci peut être utile pour accélerer les processus
- d'entrées/sorties.
- </dd>
- <dt><code>masquer_barre_progression</code>
- (valeur par défaut: <span class="emp">non</span>)</dt>
- <dd>Si elle est fixée à <span class="emp">oui</span>, cette option provoque la
- disparition de la barre de progression qui est normalement chargée
- d'indiquer l'état d'avancement de l'enregistrement des fichiers
- de données. Si cette option est fixée à <span class="emp">non</span>,
- cette barre
- sera affichée, en même temps que le nom du fichier de données
- actuellement en cours d'écriture
- (voir la section <a href="#basics_files">Fichiers</a>).
- </dd>
- <dt><code><span class="todo">calendar_default_view</span></code>
- (default: <span class="emp">0</span>)</dt>
- <dd><span class="todo">If set to <span class="emp">0</span>, the monthly calendar view will be
- displayed by default otherwise it is the weekly view that will be displayed.</span>
- </dd>
- <dt><code>semaine_commence_lundi</code>
- (valeur par défaut: <span class="emp">oui</span>)</dt>
- <dd>Il est possible dans <span class="emp">calcurse</span> d'indiquer quel est le
- premier jour de la semaine, à savoir soit le lundi, soit le dimanche.
- Si l'option <code>semaine_commence_lundi</code> est fixée à
- <span class="emp">oui</span>, les semaines du calendrier commenceront le lundi.
- Par contre si cette option est fixée à <span class="emp">non</span>,
- les semaines débuteront le dimanche.
- </dd>
- <dt><code>format_date_sortie</code>
- (valeur par défaut: <span class="emp">%D</span>)</dt>
- <dd>Indique le format qui sera utilisé pour afficher les dates en mode
- non-interactif. Par défaut, les dates sont affichées comme suit :
- <span class="emp">mm/jj/aa</span>.
- Les différents formats disponibles sont visibles en
- tapant la commande suivante dans un terminal: <code>man 3 strftime</code>.
- </dd>
- <dt><code>format_date_entrée</code>
- (valeur par défaut: <span class="emp">1</span>)</dt>
- <dd>Indique le format qui sera utilisé pour entrer les dates dans
- <span class="emp">calcurse</span>. Quatre choix sont possibles :
- <ol>
- <li>mm/jj/aaaa</li>
- <li>jj/mm/aaaa</li>
- <li>aaaa/mm/jj</li>
- <li>aaaa-mm-jj</li>
- </ol>
- </dd>
- </dl>
-
-<div class="todo">
-<h2>5.2 Key bindings<a name="options_keys"></a></h2>
-<p>
- One can define it's own keybindings within the 'Keys' configuration
- menu. The default keys look like the one used by the <code>vim</code>
- editor, especially the displacement keys. Anyway, within this
- configuration menu, users can redefine all of the keys available from
- within calcurse's user interface.</p>
-<p>
- To define new keybindings, first highlight the action to which it will
- apply. Then, delete the actual key binding if necessary, and add a new
- one. You will then be asked to press the key corresponding to the new
- binding. It is possible to define more than one key binding for a single
- action.</p>
-<p>
- An automatic check is performed to see if the new key binding
- is not already set for another action. In that case, you will be asked
- to choose a different one. Another check is done when exiting from this
- menu, to make sure all possible actions have a key associated with it.</p>
-<p>
- The following keys can be used to define bindings:
- <ul>
- <li>lower-case, upper-case letters and numbers, such as 'a', 'Z', '0'</li>
- <li>CONTROL-key followed by one of the above letters</li>
- <li>escape, horizontal tab, and space keys</li>
- <li>arrow keys (up, down, left, and right)</li>
- <li>'HOME' and 'END' keys</li>
- </ul> </p>
-<p>
- While inside the key configuration menu, an online help is available for
- each one of the available actions. This help briefly describes what the
- highlighted action is used for.</p>
-</div>
-
-<h2>5.3 Thèmes graphiques<a name="options_colors"></a></h2>
-<p>
- Le thème graphique de <code>calcurse</code> peut être adapté aux besoins de
- l'utilisateur. Pour changer les options par défaut, la page de configuration
- permet de sélectionner la couleur voulue pour l'interface (premier plan et
- fond). L'utilisateur doit pour cela se déplacer sur la bonne couleur en
- utilisant les touches flèches ou les touches de déplacement par défaut, et
- appuyer sur 'X' ou la barre d'espace pour sélectionner la couleur. Il est
- également possible de conserver la couleur par défaut du terminal de
- l'utilisateur en sélectionnant le choix corresondant dans la liste.</p>
-<p>
- Cette couleur est alors appliquée à la bordure des
- panneaux, aux titres, aux combinaisons de touches, et aux
- informations générales affichées dans la
- barre de status. Un thème en noir et blanc est
- également disponible, afin de supporter les terminaux
- monochromes.</p>
- <p class="rq"><span class="valorise">Remarque:</span>
- Suivant le type de terminal que vous utilisez, et suivant
- la valeur de la variable d'environnement <code>$TERM</code>,
- la couleur peut être supportée ou non. Un message
- d'erreur apparaîtra si vous essayez d'appliquer un
- thème graphique en couleur alors que votre terminal est
- monochrome. Si vous savez que votre terminal supporte les couleurs
- mais que <code>calcurse</code> ne veut pas les afficher,
- essayez de changer la valeur de la variable d'environnement
- <code>$TERM</code> (appliquez par exemple la valeur
- <span class="emp">xterm-xfree86</span>).
- </p>
-
-<h2>5.4 Disposition des panneaux<a name="options_layout"></a></h2>
-<p>
- La disposition des panneaux à l'intérieur de la fenêtre de
- <code>calcurse</code> peut être paramétrée. Par défaut, le
- panneau contenant le calendrier se situe en haut à droite de
- la fenêtre, le panneau contenant la liste des tâches est situé
- en bas à droite, et le panneau contenant les rendez-vous se
- trouve sur la partie gauche de l'écran (voir la figure dans la
- section <a href="#basics_interface_interactive">Mode interactif</a>
- pour un exemple de la disposition par défaut).
- En choisissant une autre disposition pour les éléments composants
- la fenêtre de <code>calcurse</code>, l'utilisateur peut adapter
- à ses besoins l'interface du programme.</p>
-
-<div class="todo">
-<p>
- The following option is used to modify the layout configuration:</p>
- <dl>
- <dt><code>layout</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>Eight different layouts are to be chosen from (see layout
- configuration screen for the description of the available layouts).</dd>
- </dl>
-</div>
-
-
-<div class="todo">
-<h2>5.5 Sidebar configuration<a name="options_sidebar"></a></h2>
-<p>
- The sidebar is the part of the screen which contains two panels:
- the calendar and, depending on the chosen layout, either the todo
- list or the appointment list.</p>
-<p>
- The following option is used to change the width of the sidebar:</p>
- <dl>
- <dt><code>side-bar_width</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>Width (in percentage, 0 being the minimum width) of the side bar.</dd>
- </dl>
-</div>
-
-
-<h2>5.6 Réglages de la barre de notification<a name="options_notify"></a></h2>
-<p>
- Les options suivantes permettent de modifier les réglages de la
- barre de notification:</p>
- <dl>
- <dt><code>barre-notification_afficher</code>
- (valeur par défaut: <span class="emp"oui</span>)</dt>
- <dd>Cette option indique si la barre de notification doit être
- affichée ou pas.</dd>
- <dt><code>barre-notification_date</code>
- (valeur par défaut: <span class="emp">%a %F</span>)</dt>
- <dd>Avec cette option, il vous est possible de spécifier le format qui
- doit être utilisé pour afficher la date du jour dans la barre de
- notification. Les différents formats possibles sont visibles en
- tapant la commande suivante dans un terminal: <code>man 3 strftime</code>.
- </dd>
- <dt><code>barre-notification_heure</code>
- (valeur par défaut: <span class="emp">%T</span>)</dt>
- <dd>Avec cette option, il vous est possible de spécifier le format qui
- doit être utilisé pour afficher l'heure courante dans la barre de
- notification. Les différents formats possibles sont visibles en
- tapant la commande suivante dans un terminal: <code>man 3 strftime</code>.
- </dd>
- <dt><code>barre-notification_alerte</code>
- (valeur par défaut: <span class="emp">300</span>)</dt>
- <dd>Si l'utilisateur a programmé un rendez-vous dans les prochaines
- 'barre-notification_alerte' secondes, et qu'il a marqué celui-ci
- comme étant important, l'affichage de ce rendez-vous clignotera dans
- la barre de notification.
- De plus, la commande définie par <code>barre-notification_commande</code>
- sera executée.
- De cette manière, l'utilisateur sera alerté et saura que l'heure du rendez-vous
- approche.</dd>
- <dt><code>barre-notification_commande</code>
- (valeur par défaut: <span class="emp">printf '\a'</span>)</dt>
- <dd>Cette option indique la commande qui sera lancée lorsque l'heure d'un
- rendez-vous approchera, et que ce rendez-vous a été marqué comme
- 'important'. La commande spécifiée par cette option sera passée au shell
- de l'utilisateur, qui l'interpretera. Pour savoir quel shell doit être
- utilisé, <code>calcurse</code> lit le contenu de la variable
- d'environnement <code>$SHELL</code>, et si cette variable est vide, la
- commande sera passée à <code>/bin/sh</code>.
- <p class="rq"><span class="valorise">Exemple:</span>
- Supposons que le programme <code>mail</code> soit
- disponible sur l'ordinateur de l'utilisateur, celui-ci peut indiquer la
- commande suivante afin d'être prévenu par mail lorsqu'un rendez-vous
- approche (la description de ce rendez-vous sera également mentionnée
- dans le corps du mail):</p>
- <code>
-calcurse --next | mail -s "[calcurse] nouveau rendez-vous!" user@host.com
- </code>
- </dd>
-
- <dt><code><span class="todo">notify-daemon_enable</code>
- (default: <span class="emp">no</span>)</span></dt>
- <dd><span class="todo">If set to yes, daemon mode will be enabled, meaning <code>calcurse</code>
- will run into background when the user's interface is exited. This will allow the
- notifications to be launched even when the interface is not running. More details
- can be found in section <a href="#basics_daemon">'Background mode'</a>.</span>
- </dd>
- <dt><code><span class="todo">notify-daemon_log</code>
- (default: <span class="emp">no</span>)</span></dt>
- <dd><span class="todo">If set to yes, <code>calcurse</code> daemon activity will be logged (see section
- <a href="#basics_files">files</a></span>).
- </dd>
-
- </dl>
-
-<h1>6. Bogues connus<a name="known_bugs"></a></h1>
-<p>
- Une coloration incorrecte des objets peut résulter
- d'une utilisation conjointe d'un thème graphique en
- noir et blanc et d'une variable <code>$TERM</code>
- fixée à <span class="emp">xterm-color</span>. Pour supprimer ce
- bogue, et comme le conseille Thomas E. Dickey (le
- résponsable du projet <code>xterm</code>),
- <span class="emp">xterm-xfree86</span> devrait être assigné
- à la variable <code>$TERM</code> en lieu et place de
- <span class="emp">xterm-color</span> :</p>
- <blockquote class="rq">
- "La valeur xterm-color pour la variable $TERM est un mauvais
- choix pour les terminaux XFree86 parce qu'elle est couramment
- utilisée pour les entrées terminfo qui ne
- supportent pas bce. Utilisez plut&ocirc;t l'entrée
- xterm-xfree86 qui est distribuée avec le xterm
- d'XFree86 (ou par celui, similaire, distribué avec ncurses)."
- </blockquote>
-
-
-<h1>7. Rapporter les bogues et commentaires<a name="bugs"></a></h1>
-<p>
- Merci de renvoyer vos rapports de bogues et vos commentaires à
- l'adresse suivante :</p>
- <pre>calcurse .à. culot .point. org </pre>
-<p>
- ou directement à l'auteur :</p>
- <pre>frederic .à. culot .point. org </pre>
-
-<h1>8. Comment contribuer?<a name="contribute"></a></h1>
-<p>
- Si vous désirez contribuer au projet, vous pouvez tout d'abord
- envoyer vos commentaires sur ce qui vous plaît ou déplaît ou sur
- ce qui vous manque dans <code>calcurse</code>.
- Pour le moment, les contributions possibles concernent
- la traduction des messages de <code>calcurse</code> ainsi que
- de la documentation.</p>
- <p class="rq"><span class="valorise">Remarque:</span>
- toute contribution à la traduction de
- <code>calcurse</code> serait très
- appréciée, mais avant tout, envoyez un mail
- à <code>calcurse-i18n .à. culot .point. org</code> pour savoir si
- quelqu'un a déjà commencé le processus de
- traduction dans votre langue.</p>
-
-
-<h2>8.1 Traduction de la documentation<a name="contribute_documentation"></a></h2>
-<p>
- Le répertoire <span class="emp">doc/</span> du paquet source contient
- déjà des versions traduites de la documentation.
- Cependant, si celle-ci n'est pas encore disponible dans votre
- langue, votre aide pour sa traduction serait très
- appréciée.</p>
-<p>
- Pour cela, il suffit de copier un des fichiers existant et de
- renommer cette copie en <code>manual_XX.html</code>, où
- <span class="emp">XX</span> représente votre langue. Il faut ensuite
- traduire ce fichier nouvellement créé et de
- l'envoyer à l'auteur (voir <a href="#bugs">Rapporter
- les bogues et commentaires</a>), pour qu'il soit inclus dans
- la prochaine version de <code>calcurse</code>.</p>
-
-
-<h2>8.2 Traduction de <code>calcurse</code><a name="contribute_i18n"></a></h2>
-<p>
- Comme mentionné plus haut, les utilitaires
- <code>gettext</code> sont utilisés par
- <code>calcurse</code> pour produire des messages
- multilingues. Cette section explique comment traduire ces
- messages dans votre langue. Cependant, cette notice est
- délibérément incomplète,
- puisqu'elle ne se concentre que sur l'utilisation de
- <code>gettext</code> avec <code>calcurse</code>. Pour avoir
- une vision plus large du Support de Langage Natif
- (<code>NLS</code>), il est préférable de se
- référer au manuel de <code>GNU gettext</code>
- que l'on peut trouver à l'adresse suivante :</p>
- <pre>http://www.gnu.org/software/gettext/manual/</pre>
-<p>
- Pour résumer, trois catégories de personnes sont
- impliquées dans la chaîne de traduction : les
- programmeurs, les coordinateurs de la traduction, et les
- traducteurs. Après un rapide aperçu de la
- manière de procéder pour traduire le logiciel,
- nous décrirons plus en détails les tâches du
- traducteur.</p>
-
-
-<h3>8.2.1 Aperçu<a name="contribute_i18n_overview"></a></h3>
-<p>
- Afin de pouvoir afficher du texte dans la langue natale de
- l'utilisateur, deux étapes sont nécessaires :
- l'<span class="emp">internationalisation</span> (i18n), et la
- <span class="emp">localisation</span> (l10n).</p>
-<p>
- L'i18n permet à <code>calcurse</code> d'être
- multilingue. C'est un processus qui est mis en place par les
- programmeurs, qui marquent les phrases à traduire au
- sein du code source, et qui fournissent les outils pour que
- ces phrases soient traduites automatiquement pendant le
- déroulement du programme.</p>
-<p>
- La l10n correspond quant à elle au processus qui permet
- à <code>calcurse</code> de s'adapter à la langue
- de l'utilisateur. C'est-à-dire qu'il traduit les
- phrases précédemment marquée par les
- programmeurs, et qu'il fixe correctement les variables
- d'environnement afin que <code>calcurse</code> puisse utiliser
- les résultats de cette traduction.</p>
-<p>
- Ainsi, les phrases traduisibles sont tout d'abord
- marquées par les programmeurs dans le code source, puis
- rassemblées dans un fichier référence
- (<span class="emp">calcurse.pot</span> - l'extension
- <span class="emp">pot</span> signifiant
- <span class="emp">portable object template</span>, objet portable de
- référence). Le contenu de ce fichier est alors
- associé aux fichiers contenant la traduction pour
- chacune des différentes langues (fichier <span class="emp">fr.po</span>
- pour le français par exemple - <span class="emp">po</span> siginifiant
- <span class="emp">portable object</span>, objet portable - qui peut être
- lu par les humains). Le traducteur devra se servir de ce
- fichier, et traduira les phrases qu'il contient, puis
- l'enverra aux développeurs. Ensuite, au niveau de la
- compilation du programme, une version binaire de ce fichier
- sera produite (pour des raisons d'efficacité), puis
- installée. Cette version binaire a pour extension
- <span class="emp">.mo</span>, où <span class="emp">mo</span>
- signifie <span class="emp">machine
- object</span> - objet machine, c'est-à-dire qui peut
- être lu par le programme. Pour finir,
- <code>calcurse</code> se servira de ce fichier <span class="emp">mo</span>
- lors de son exécution pour traduire les phrases dans la langue
- de l'utilisateur.</p>
-
-
-<h3>8.2.2 Etapes de la traduction<a name="contribute_i18n_translator"></a></h3>
-<p>
- Supposons que quelqu'un veuille commencer une traduction dans
- une nouvelle langue. Voici les étapes à suivre
- pour ce faire :</p>
- <ul>
- <li>Premièrement, trouver quel est le nom de la locale
- correspondant à la langue à traduire. Par
- exemple, pour le français, il s'agit de 'fr_FR', ou
- simplement 'fr'. C'est cette valleur que l'utilisateur devra
- mettre dans la variable d'environnement <code>LC_ALL</code>
- pour obtenir la version traduite du logiciel (voir <a
- href="#basics_invocation_variable">Variable d'environnement
- pour l'i18n</a>).</li>
- <li>Ensuite, il faut se rendre dans le répertoire
- <span class="emp">po/</span>, et créer un nouveau fichier <span class="emp">.po</span>
- à partir du fichier de référence en utilisant la commande suivante :
- <code>'msginit -i calcurse.pot -o fr.po -l fr --no-translator'</code>
- Si vous n'avez pas <code>msginit</code> installé sur
- votre système, vous pouvez plus simplement copier
- <span class="emp">calcurse.pot</span> en <span class="emp">fr.po</span>
- par exemple, et éditer l'en-tête du fichier nouvellement créé
- manuellement.</li>
- </ul>
-<p>
- Maintenant, ayant à disposition ce fichier
- <span class="emp">fr.po</span>, la traduction peut commencer.</p>
-
-
-<h3>8.2.3 Fichiers <code>po</code><a name="contribute_i18n_po-files"></a></h3>
-<p>
- Le format des fichiers <code>po</code> est assez simple. En effet,
- ils ne contiennent que quatre éléments
- différents :</p>
- <ol>
- <li><span class="emp">ligne d'emplacement:</span> renseigne sur l'emplacement
- de la phrase dans le fichier source (donne le nom du fichier
- ainsi que le numéro de ligne), afin de retrouver
- simplement le contexte d'où est issu la phrase à
- traduire.</li>
- <li><span class="emp">ligne msgid:</span> indique la phrase à traduire.</li>
- <li><span class="emp">ligne msgstr:</span> ligne indiquant la phrase traduite.</li>
- <li><span class="emp">lignes commençant par '#'</span>: indiquent des
- commentaires (certains ont une signification spéciale,
- comme nous le verrons plus tard).</li>
- </ol>
-<p>
- Pour résumer, un traducteur doit simplement remplir les
- champs <span class="emp">msgstr</span> avec la traduction des lignes
- trouvées juste au-dessus dans la partie <span class="emp">msgid</span>.</p>
-<p>
- <span class="valorise">Remarques:</span>
- <dl>
- <dt><span class="emp">Phrases marquées Fuzzy</span></dt>
- <dd>Vous pourrez rencontrer des phrases commençant par le
- commentaire <code>"#, fuzzy"</code>.
- <code>calcurse</code> n'utilisera pas les traductions
- commençant par ce commentaire, à moins que vous
- ne transformiez ces phrases. En effet, le commentaire
- <code>fuzzy</code> signifie que la phrase a déjà
- été traduite mais qu'elle a depuis
- été changée dans le source du programme,
- ou bien que <code>gettext</code> a effectué lui-même
- une traduction, en se basant sur une phrase similaire. Cela
- implique donc que vous devez vérifier la traduction.
- Parfois, la phrase originale a changé suite à
- une correction de faute de frappe. Dans ce cas, vous n'aurez
- pas besoin de modifier la traduction. Mais dans d'autres cas,
- cette traduction peut ne plus être valable et
- nécessitera alors une mise à jour. Une fois
- cette mise à jour effectuée, vous pouvez
- supprimer
- le commentaire <code>"#, fuzzy"</code>, et la traduction sera
- alors à nouveau prise en compte par <code>calcurse</code>.
- </dd>
- <dt><span class="emp">Lignes au format C et séquences spéciales</span></dt>
- <dd>Certaines phrases ont le commentaire suivant: <code>"#,
- c-format"</code>. Cela signifie que des parties du texte
- à traduire ont une signification particulière
- pour le programme, et qu'il ne faut pas les modifier. Par
- exemple, les séquences contenant des <code>%</code>, comme
- <code>"%s"</code>. Cela signifie que <code>calcurse</code>
- remplacera ces séquences par d'autres expressions. Il
- est donc important de ne pas les modifier. Il existe
- également des séquences contenant des
- <code>\</code>, comme <code>\n</code> ou <code>\t</code>. Il ne
- faut pas les modifier non plus. En effet, la première
- séquence représente une fin de ligne, et la
- deuxième une tabulation.</dd>
- <dt><span class="emp">Découpage des traductions</span></dt>
- <dd>Si certaines lignes sont trop longues, il est possible de
- découper les phrases comme dans l'exemple ci-après:
- <pre>
-msgid ""
-"une ligne très longue"
-"une autre ligne"
- </pre></dd>
- <dt><span class="emp">En-tête des fichiers po</span></dt>
- <dd>Au tout début du fichier <span class="emp">po</span>, la
- première phrase forme un en-tête où
- différentes informations doivent être
- renseignées. La plus importante est le jeu de
- caractères utilisé. Cette information devrait
- ressembler à
- <pre>
-"Content-Type: text/plain; charset=utf-8\n"
- </pre>
- Il est également nécessaire de remplir le champ
- <span class="emp">Last-Translator</span> -
- <span class="emp">Dernier Traducteur</span>, afin
- que d'autres traducteurs potentiels puissent se mettre en
- relation avec la dernière personne ayant
- retouché le fichier. De cette manière, il est
- plus simple de coordonner les efforts de traduction. Il est
- possible de rajouter son adresse de courrier
- électronique, par exemple:
- <pre>
-"Last-Translator: Frederic Culot &lt;frederic@culot.org&gt;\n"
- </pre></dd>
- <dt><span class="emp">Commentaires</span></dt>
- <dd>Ajouter des commentaires (lignes commençant par '#')
- peut être un bon moyen de signaler des problèmes ou
- difficultés de traduction aux autres traducteurs.</dd>
- <dt><span class="emp">Taille des phrases</span></dt>
- <dd><code>calcurse</code> est un programme comportant une
- interface console/curses, il dépend donc de la taille
- du terminal utilisé (plus particulièrement du
- nombre de colonnes). Il est important de garder ceci en
- mémoire au moment de la traduction. Souvent, la phrase
- à traduire doit tenir dans une seule ligne (soit en
- général 80 caractères). Il faut en tenir
- compte, et essayer de voir où la phrase sera
- placée pour adapter sa traduction.</dd>
- <dt><span class="emp">Quelques outils utiles</span></dt>
- <dd>Le format des fichiers <code>po</code> est relativement simple, et
- ils peuvent être modifiés avec un éditeur
- de texte standard. Mais il est également possible
- d'utiliser des outils spécialisés pour cette
- tâche:
- <ul>
- <li><code>poEdit</code> (<a
- href="http://www.poedit.org/" target="_blank">
- http://www.poedit.org/</a>)</li>
- <li><code>KBabel</code> (<a
- href="http://i18n.kde.org/tools/kbabel/" target="_blank">
- http://i18n.kde.org/tools/kbabel/</a>)</li>
- <li><code>GTranslator</code> (<a
- href="http://gtranslator.sourceforge.net/" target="_blank">
- http://gtranslator.sourceforge.net/</a>)</li>
- <li><code>Emacs</code> et son mode <code>po</code></li>
- <li><code>Vim</code> et son mode <code>po</code></li>
- </ul>
- </dd>
- <dt><span class="emp">Finalement...</span></dt>
- <dd>J'espère que vous prendrez plaisir à
- contribuer à l'internationalisation du monde des
- logiciels libres. :) Si vous avez d'autres questions
- concernant ce processus, n'hésitez pas à me
- contacter à l'adresse
- <span class="emp">frederic .à. culot .point. org</span>.</dd>
- </dl>
-
-
-<h1>9. Liens<a name="links"></a></h1>
-<p>
- Cette section contient des liens en relation avec
- <code>calcurse</code> qui peuvent vous être utiles.</p>
-
-
-<h2>9.1 Site internet de <code>calcurse</code><a name="links_homepage"></a></h2>
-<p>
- La page web de <code>calcurse</code> est à l'adresse suivante :</p>
- <pre>http://culot.org/calcurse</pre>
-
-<h2>9.2 Liste de diffusion de <code>calcurse</code><a name="links_list"></a></h2>
-<p>
- Si vous êtes interessé par ce projet et que vous souhaitez
- être prévenu lorsqu'une nouvelle version est diffusée, vous
- pouvez souscrire à la liste de diffusion de <code>calcurse</code>.
- De cette manière, vous recevrez un mél dès qu'une nouvelle
- version est disponible.</p>
-<p>
- Pour souscrire à cette liste, envoyez un message à l'adresse
- <span class="emp">calcurse-announce .à. culot .point. org</span>
- avec "subscribe" dans le sujet du mél.</p>
-
-<h2>9.3 Flux RSS<a name="links_rss"></a></h2>
-<p>
- Une autre possibilité pour être prévenu lorsqu'une
- nouvelle version de <code>calcurse</code> est disponible est de
- s'abonner au flux RSS suivant :</p>
- <pre>http://culot.org/calcurse/news_rss.xml</pre>
-<p>
- Ce flux RSS est mis à jour dès qu'une nouvelle version de
- <code>calcurse</code> est diffusée, et indique quelles sont les
- modifications qui ont été apportées.</p>
-
-<h2>9.4 Autres liens<a name="links_others"></a></h2>
-<p>
- La spécification du format ical (rfc2445) peut être trouvée à l'adresse
- suivante :
- <pre>http://tools.ietf.org/html/rfc2445</pre>
-<p>
- La page du projet pcal se trouve quant à elle à l'adresse suivante :
- <pre>http://pcal.sourceforge.net/</pre>
-
-<h1>10. Remerciements<a name="thanks"></a></h1>
-<p>
- Je voudrais remercier ici toutes les personnes sans qui ce projet
- n'aurait jamais pu voir le jour! En particulier :
- <ul>
- <li>Alex pour ses patches, aides et conseils sur la programmation en
- <code>C</code></li>
- <li>Gwen pour les tests et les discussions sur la mani&egrave;re d'améliorer
- <code>calcurse</code></li>
- <li>Herbert pour la maintenance du paquet <code>calcurse</code> pour
- FreeBSD</li>
- <li>Zul pour la maintenance du paquet <code>calcurse</code> pour
- NetBSD</li>
- <li>Kevin, Ryan, et fEnIo pour la maintenance du paquet <code>calcurse</code>
- pour Debian et Ubuntu</li>
- <li>Wain, Steffen and Ronald pour la maintenance du paquet <code>calcurse</code> pour
- Archlinux</li>
- <li>Pascal pour la maintenance du paquet <code>calcurse</code> pour
- Slackware</li>
- <li>Alexandre pour la maintenance du paquet <code>calcurse</code> pour
- Mac OsX et Darwin</li>
- <li>Igor pour la maintenance du paquet <code>calcurse</code> pour
- ALT Linux</li>
- <li>Joel pour son script de calendrier qui a inspiré celui de
- <code>calcurse</code></li>
- <li>Michael Schulz et Chris M. pour la traduction allemande de <code>calcurse</code>
- et de son manuel</li>
- <li>Jose Lopez pour la traduction espagnole de <code>calcurse</code>
- et de son manuel</li>
- <li>Neil Williams pour la traduction anglaise</li>
- <li>Tony pour son patch qui a permis d'améliorer la fonction
- recur_item_inday(), et pour l'implémentation des options de configuration
- concernant les formats de date</li>
- <li>Jeremy Roon pour la traduction en Néerlandais</li>
- <li>Leandro Noferini pour la traduction en Italien</li>
- <li>Erik Saule pour son patch qui a permis d'implémenter les options '-N',
- '-s', '-S', '-r', et '-D' de la ligne de commande</li>
- <li>les personnes qui écrivent des logiciels que j'apprécie et qui
- m'ont inspiré lors de la conception de ce projet, en particulier:
- <ul>
- <li><code>vim</code> pour les touches de déplacement</li>
- <li><code>orpheus</code> et <code>abook</code> pour la documentation</li>
- <li><code>pine</code> et <code>aptitude</code>
- pour l'interface en mode texte</li>
- <li><span class="todo"><code>tmux</code> for coding style</span></li>
- </ul></li>
- </ul>
-</p>
-<p>
- Et pour terminer, un très grand merci à tous les utilisateurs de
- <code>calcurse</code> qui m'ont fait parvenir leurs commentaires.</p>
-
-<div class="footer">
- Copyright &copy; 2004-2010 Frédéric Culot<br>
- Calcurse version 2.8 - Dernière modification: 29 Mars 2010<br>
-</div>
-</div>
-
-</body>
-</html>
diff --git a/doc/manual_it.html b/doc/manual_it.html
deleted file mode 100644
index 11f7f80..0000000
--- a/doc/manual_it.html
+++ /dev/null
@@ -1,1587 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<!--
-/*
- * $calcurse: manual_it.html,v 1.14 2010/03/29 18:18:04 culot Exp $
- *
- * Copyright (c) 2004-2010 Frederic Culot <frederic@culot.org>
- * All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * - Redistributions of source code must retain the above
- * copyright notice, this list of conditions and the
- * following disclaimer.
- *
- * - Redistributions in binary form must reproduce the above
- * copyright notice, this list of conditions and the
- * following disclaimer in the documentation and/or other
- * materials provided with the distribution.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- *
- */
--->
-
-<html>
-<head>
-<title>Documentazione di <code>calcurse</code></title>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<style type="text/css" media="all">
- @import url(manual.css);
-</style>
-</head>
-<body>
-
-<div id="mainContent">
-
-<h1 id="title">
-<span class="main"><code>calcurse</code> - un organizer testuale</span></h1>
-
-<div class="warn">
-<h1>Abstract</h1> Questo manuale descrive le funzionalità
-di <code>calcurse</code>, e il suo utilizzo. Innanzitutto vengono
-descritti la procedura di installazione a partire dai sorgenti e le
-opzioni della linea di comando; successivamente viene presentata
-l'interfaccia utente e tutte le opzioni di configurazione che
-modificano il comportamento di <code>calcurse</code>. Infine viene
-descritta la procedura per la segnalazione dei bachi e come
-partecipare allo sviluppo di calcurse.
-</div>
-
-<div id="toc">
-<h1>Table of Contents</h1>
-<ul>
- <li><a href="#intro">1. Introduzione</a></li>
- <li><a href="#overview">2. Panoramica</a>
- <ul>
- <li><a href="#overview_history">2.1 Storia dello sviluppo</a></li>
- <li><a href="#overview_features">2.2 Principali caratteristiche</a></li>
- </ul></li>
- <li><a href="#install">3. Installazione</a>
- <ul>
- <li><a href="#install_requirements">3.1 Requisiti</a>
- <ul>
- <li><a href="#install_requirements_ncurses">3.1.1 Librerie <code>ncurses</code></a></li>
- <li><a href="#install_requirements_gettext">3.1.2 Librerie <code>gettext</code></a></li>
- </ul></li>
- <li><a href="#install_process">3.2 Procedura di installazione</a></li>
- </ul></li>
- <li><a href="#basics">4. Elementi di base di <code>calcurse</code></a>
- <ul>
- <li><a href="#basics_invocation">4.1 Avvio</a>
- <ul>
- <li><a href="#basics_invocation_commandline">4.1.1 Argomenti della linea di comando</a></li>
- <li><a href="#basics_invocation_variable">4.1.2 Variabili d'ambiente per l'i18n</a></li>
- <li><a href="#basics_invocation_environment">4.1.3 Altre variabili d'ambiente</a></li>
- </ul></li>
- <li><a href="#basics_interface">4.2 Interfaccia utente</a>
- <ul>
- <li><a href="#basics_interface_noninteractive">4.2.1 Modo non interattivo</a></li>
- <li><a href="#basics_interface_interactive">4.2.2 Modo interattivo</a></li>
- </ul></li>
- <li><a href="#basics_daemon"><span class="todo">4.3 Background mode</span></a></li>
- <li><a href="#basics_files">4.4 Files di <code>calcurse</code></a></li>
- <li><a href="#basics_import_export"><span class="todo">4.5 Import/Export capabilities</span></a>
- <ul>
- <li><a href="#basics_import"><span class="todo">4.5.1 Import</span></a></li>
- <li><a href="#basics_export"><span class="todo">4.5.2 Export</span></a></li>
- </ul></li>
- <li><a href="#basics_help">4.6 Aiuto in linea</a></li>
- </ul></li>
- <li><a href="#options">5. Opzioni</a>
- <ul>
- <li><a href="#options_general">5.1 Opzioni generali</a></li>
- <li><a href="#options_keys"><span class="todo">5.2 Key bindings</span></a>
- <li><a href="#options_colors">5.3 Temi dei colori</a></li>
- <li><a href="#options_layout">5.4 Configurazione dell'interfaccia</a></li>
- <li><a href="#options_sidebar"><span class="todo">5.5 Sidebar configuration</span></a></li>
- <li>
- <a href="#options_notify">5.6 Configurazioni della barra di
- notifica</a>
- </li>
- </ul></li>
- <li><a href="#known_bugs">6. Bachi conosciuti</a></li>
- <li><a href="#bugs">7. Riportare i bachi e feedback</a></li>
- <li><a href="#contribute">8. Come contribuire</a>
- <ul>
- <li><a href="#contribute_documentation">8.1 Tradurre la documentazione</a></li>
- <li><a href="#contribute_i18n">8.2 i18n <code>calcurse</code></a>
- <ul>
- <li><a href="#contribute_i18n_overview">8.2.1 Panoramica</a></li>
- <li><a href="#contribute_i18n_translator">8.2.2 Compiti del traduttore</a></li>
- <li><a href="#contribute_i18n_po-files">8.2.3 File po</a></li>
- </ul></li>
- </ul></li>
- <li><a href="#links">9. Links</a>
- <ul>
- <li><a href="#links_homepage">9.1 Homepage di <code>calcurse</code></a></li>
- <li><a href="#links_list">9.2 Lista degli annunci di <code>calcurse</code></a></li>
- <li><a href="#links_rss">9.3 Feed RSS di <code>calcurse</code></a></li>
- <li><a href="#links_others"><div class="todo">9.4 Other links</div></a></li>
- </ul></li>
- <li><a href="#thanks">10. Ringraziamenti</a></li>
-</ul>
-</div>
-
-<h1>1. Introduzione<a name="intro"></a></h1>
-<p>
- <code>Calcurse</code> è un programma testuale per la gestione
- dell'agenda. Permette la gestione degli eventi, degli appuntamenti
- e dei compiti quotidiani: un sistema configurabile di avvisi ricorda
- all'utente l'avvicinarsi delle scadenze; l'interfaccia testuale può
- essere personalizzata secondo le necessità dell'utente. Tutti i
- comandi sono documentati da un sistema d'aiuto in linea.
-</p>
-
-<h1>2. Panoramica<a name="overview"></a></h1>
-<h2>2.1 Storia dello sviluppo<a name="overview_history"></a></h2>
-<p>
- Ho cominciato a pensare a questo progetto mentre stavo finendo il
- mio dottorato in astrofisica... Stava diventando piuttosto difficile
- organizzare la mia vita per cui avevo veramente necessità di un
- valido strumento per aiutarmi in questo compito difficile ;)
-</p>
-<p>
- Personalmente apprezzo i programmi con interfaccia utente testuale
- perché sono semplici, veloci, portabili ed efficienti perciò ho
- pensato di realizzare un semplice calendario testuale.
-
- Inoltre volevo imparare il linguaggio <code>C</code> che avevo usato
- solo durante i miei studi secondari; perciò ho pensato che questo
- sarebbe stato un buon progetto per organizzarmi e per imparare
- qualche nozione di <code>C</code>!
-</p>
-<p>
- Sfortunatamente ho finito il mio dottorato prima di aver
- terminato <code>calcurse</code>; in ogni modo ho continuato a
- lavorarci sperando che potesse risultare utile anche ad altre
- persone. Perciò eccolo qua....
-
-</p>
-<p>
- Perché il nome 'calcurse'? Perché è semplicemente l'unione di
- 'CALendar' e 'nCURSEs', dal nome delle librerie usate per realizzare
- l'interfaccia utente.
-</p>
-
-<h2>2.2 Principali
-caratteristiche<a name="overview_features"></a></h2>
-<p>
- <code>Calcurse</code> è multi-piattaforma e vuole essere leggero,
- veloce e affidabile; deve essere usato all'interno della console o
- in un terminale, localmente o su un computer remoto mediante una
- connessione di tipo ssh.
-</p>
-<p>
- <code>Calcurse</code> può essere usato in due diversi modi,
- interattivo e non-interattivo. Nel primo modo permette all'utente di
- controllare la propria agenda praticamente ovunque grazie
- all'interfaccia testuale.
- Il secondo modo permette di aggiungere appuntamenti semplicemente
- usando appropriati argomenti alla linea di comando all'interno di un
- compito di cron o di uno script di avvio della shell.
-</p>
-<p>
- Inoltre <code>calcurse</code> è stato realizzato pensando all'utente
- finale perciò cerca di essere quanto più semplice possibile. Questo
- comporta un completo aiuto in linea oltre ad una barra di stato in
- cui sono elencate tutte le azioni disponibili.
- Anche l'interfaccia utente è configurabile permettendo di poter
- scegliere fra diverse combinazioni di colori e layout.
-<span class="todo">Key bindings are also configurable, to fit everyone's needs.</span>
- Infine un sistema configurabile di allarmi ricorda all'utente
- l'avvicinarsi degli appuntamenti.
-<span class="todo">The reminders are sent even if the user's interface
-is not running, as calcurse is able to run in background.</span>
-</p>
-
-<h1>3. Installazione<a name="install"></a></h1>
-<h2>3.1 Requisiti<a name="install_requirements"></a></h2>
-<h3>3.1.1 Librerie <code>ncurses</code><a name="install_requirements_ncurses"></a></h3>
-<p>
- <code>Calcurse</code> richiede esclusivamente un
- compilatore <code>C</code> quale <code>cc</code>
- oppure <code>gcc</code> nonché le librerie <code>ncurses</code>.
- &Egrave; piuttosto difficile non avere le
- librerie <code>ncurses</code> già correttamente installate sul
- proprio computer ma nel caso è possibile trovarle all'indirizzo:
- <pre>http://ftp.gnu.org/pub/gnu/ncurses/</pre>
-</p>
-
-<div class="todo">
- <p class="rq"><span class="valorize">Note:</span>
- It is also possible to link <code>calcurse</code> against the
- <code>ncursesw</code> library (ncurses with support for unicode).
- However, UTF-8 is not yet supported by <code>calcurse</code>.</p>
-</div>
-
-<h3>3.1.2 Librerie <code>gettext</code><a name="install_requirements_gettext"></a></h3>
-<p>
- <code>Calcurse</code> ha il supporto per la localizzazione
- (<span class="emp">i18n</span> da qui in avanti) attraverso
- l'utilità <code>gettext</code> perciò può usare messaggi in molte
- lingue se compilato con il relativo supporto
- (detto <span class="emp">NLS</span>).
-
-</p>
-<p>
- Comunque <span class="emp">NLS</span> è opzionale e se non lo si
- desiderasse è possibile disabilitarlo dando
- l'opzione <code>--disable-nls</code> a <code>configure</code> (vedi
- la sezione <a href="#install_process">Procedura
- d'installazione</a>).
-
- Per verificare che le utilità <code>gettext</code> sono installate
- sul vostro computer cercate il file di header <code>libintl.h</code>
- ad esempio:
-</p>
- <pre>locate libintl.h</pre>
-<p>
- Nel caso non troviate il file potete ottenere i sorgenti
- di <code>gettext</code> al seguente indirizzo:
-</p>
- <pre>http://ftp.gnu.org/pub/gnu/gettext/</pre>
-<p>
- <p class="rq"><span class="valorize">Nota:</span>
-
- Se anche si fosse trovato il file <code>libintl.h</code>
- potrebbe essere necessario specificarne la posizione durante
- la <a href="#install_process">procedura d'installazione</a>
- usando l'opzione <code>--with-libintl-prefix</code>
- con <code>configure</code>.
-
- Questo perché <code>configure</code> potrebbe non essere in
- grado di localizzarlo se fosse stato installato in una
- posizione inusuale.
-</p>
-
-<h2>3.2 Procedura d'installazione<a name="install_process"></a></h2>
-<p>
- Innanzitutto è necessario scompattare l'archivio contenente i
- sorgenti:
-</p>
- <pre>tar zxvf calcurse-2.8.tar.gz</pre>
-<p>
- Una volta verificati i requisiti e scompattato l'archivio la
- procedura d'installazione è piuttosto semplice visto che segue i tre
- passi standard:
- <ol>
- <li><code>./configure</code></li>
- <li><code>make</code></li>
- <li><code>make install</code> (potrebbero essere necessari i
- diritti di root)</li>
- </ol>
-</p>
-<p>
- Usate <code>./configure --help</code> per l'elenco delle opzioni
- possibili.
-</p>
-
-<h1>4. Elementi di base di <code>calcurse</code><a name="basics"></a></h1>
-<h2>4.1 Avvio<a name="basics_invocation"></a></h2>
-<h3>4.1.1 Argomenti della linea di comando<a name="basics_invocation_commandline"></a></h3>
-<p>
- <code>Calcurse</code> accetta le seguenti opzioni della linea di
- comando (sia nel formato breve che in quello lungo):
-</p>
-<p>
-
- <dl>
- <dt><code>-a, --appointment</code></dt>
- <dd>
- Mostra gli appuntamenti e gli eventi per il giorno corrente e
- poi esce.
- <p class="rq"><span class="valorise">Nota:</span> il calendario
- dal quale leggere gli appuntamenti può essere specificato con
- l'opzione '-c'.
- </p>
- </dd>
- <dt><code>-c &lt;file&gt;, --calendar &lt;file&gt;</code></dt>
- <dd>
- Indica il file calendario da usare.
-
- Il calendario predefinito è <code>~/.calcurse/apts</code> (vedi
- la sezione <a href="#basics_files"><code>calcurse</code>
- files</a>).
- </dd>
- <dt><code>-d &lt;data|num&gt;, --day &lt;data|num&gt;</code></dt>
- <dd>
- Mostra gli appuntamenti per la data indicata o per il numero
- indicato per i giorni futuri a seconda del formato
- dell'argomento. Sono possibili due formati:
-
- <ul>
- <li>una data <span class="todo">(possible formats described below).</span></li>
- <li>un numero 'n'.</li>
- </ul>
- Nel primo caso viene mostrata la lista degli appuntamenti per la
- data indicata; nel secondo caso viene mostrata la lista per gli
- 'n' giorni futuri.
- Ad esempio digitando <code>calcurse -d 3</code> verrà mostrata
- la lista degli appuntamenti di oggi, domani e dopodomani.
-
- <div class="todo">
- Possible formats for specifying the date are defined inside the
- general configuration menu (see
- <a href="#options_general">General options</a>), using the
- <code>input_datefmt</code> variable.
- </div>
-
- <p class="rq"><span class="valorise">Nota:</span> così come con
- l'argomento '-a' il calendario dal quale leggere gli
- appuntamenti può essere specificato con l'argomento '-c'.</p>
- </dd>
-
- <dt><code>-D &lt;dir&gt;, --directory &lt;dir&gt;</code></dt>
- <dd>
- <div class="todo">
- Specify the data directory to use. This option is
- incompatible with -c. If not specified, the
- default directory is <code>'~/.calcurse/'</code>.
- </div>
- </dd>
-
- <dt><code>-h, --help</code></dt>
- <dd>
- Stampa la versione breve del testo che descrive le opzioni della
- riga di comando ed esce.</dd>
-
- <dt><code>-i &lt;file&gt;, --import &lt;file&gt;</code></dt>
- <dd>
- <div class="todo">
- Import the icalendar data contained in <code>file</code>.
- </div>
- </dd>
-
- <dt><code>-n, --next</code></dt>
- <dd>
- Stampa il prossimo appuntamento nelle successive 24 ore ed esce.
- Il tempo stampato indica le ore e i minuti mancanti
- all'appuntamento.
-
- <p class="rq"><span class="valorise">Nota:</span> il calendario
- dal quale leggere gli appuntamenti può essere specificato con
- l'opzione '-c'.</p>
- </dd>
-
- <dt><code>-N, --note</code></dt>
- <dd>
- <div class="todo">
- When used with the '-a' or '-t' flag, also print note content
- if one is associated with the displayed item.
- </div>
- </dd>
-
- <dt><code>-r[num], --range[=num]</code></dt>
- <dd>
- <div class="todo">
- Print events and appointments for the num number of
- days and exit. If no num is given, a range of 1 day
- is considered.
- </div>
- </dd>
- <dt><code>-s[date], --startday[=date]</code></dt>
- <dd>
- <div class="todo">
- Print events and appointments from date and exit.
- If no date is given, the current day is considered.
- </div>
- </dd>
- <dt><code>-S&lt;regex&gt;, --search=&lt;regex&gt;</code></dt>
- <dd>
- <div class="todo">
- When used with the '-a', '-d', '-r', '-s', or '-t' flag,
- print only the items having a description that matches the given
- regular expression.
- </div>
- </dd>
- <dt><code>--status</code></dt>
- <dd>
- <div class="todo">
- Display the status of running instances of calcurse. If
- calcurse is running, this will tell if the interactive
- mode was launched or if calcurse is running in background.
- The process pid will also be indicated.
- </div>
- </dd>
-
- <dt><code>-t[num], --todo[=num]</code></dt>
- <dd>
- Stampa la lista delle 'attività' ed esce. Se viene specificato
- anche il numero <code>num</code> opzionale vengono stampate
- esclusivamente le attività che hanno priorità pari al numero
- stesso.
- <div class="todo">
- The priority number must be between 1 (highest) and 9 (lowest). It is also possible
- to specify '0' for the priority, in which case only completed tasks will be shown.</p>
- </div>
- </dd>
- <dt><code>-v, --version</code></dt>
- <dd>
- Stampa la versione di <code>calcurse</code> ed esce.
- </dd>
- <dt><code>-x[format], --export[=format]</code></dt>
- <dd><div class="todo">
- Export user data to specified format. Events, appointments and
- todos are converted and echoed to stdout.
- Two possible formats are available: ical and pcal
- (see section <a href="#links_others">Links</a> below).
- If the optional argument <code>format</code> is not given,
- ical format is selected by default.
- </div>
- <p class="rq"><span class="valorise">Nota:</span> è possibile
- reindirizzare lo standard output per salvare i dati su un file
- con un comando del tipo
- <code>$ calcurse --export &gt; my_data.dat</code></p>
- </dd>
- </dl>
-
-<h3>4.1.2 Variabili d'ambiente per l'i18n<a name="basics_invocation_variable"></a></h3>
-<p>
- <code>Calcurse</code> può essere compilato con il supporto per la
- localizzazione
- (vedi <a href="#install_requirements_gettext">librerie
- <code>gettext</code></a>).
-
- Di conseguenza, se preferite che i messaggi del programma vengano
- mostrati nella vostra lingua, innanzitutto verificate che questa sia
- disponibile nel file <code>po/LINGUAS</code>: questo file indica
- quali lingue sono supportate mostrando il codice di due lettere
- corrispondente (ad esempio <span class="emp">fr</span> indica il
- francese). Nel caso in cui la vostra lingua non fosse presente
- sarebbe estremamente apprezzabile il vostro aiuto nella traduzione
- di <code>calcurse</code> (vedi la sezione <a href="#contribute">Come
- contribuire</a>).</p>
-
-<p>
- Se invece la vostra lingua è presente avviate <code>calcurse</code>
- con il seguente comando:</p>
-<pre>LC_ALL=fr_FR calcurse</pre>
-<p>
- dove <span class="emp">fr_FR</span> è il nome della localizzazione
- d'esempio che deve essere sostituita dal nome della localizzazione
- desiderata.
-</p>
-<p>
- &Egrave; anche necessario indicare il set di caratteri da usare
- perché in alcuni casi gli accenti e altri caratteri simili non
- vengono mostrati correttamente. Questo set di caratteri è indicato
- all'inizio del file po corrispondente alla localizzazione prescelta:
- ad esempio nel file fr.po viene indicato l'uso del set iso-8859-1 e
- di conseguenza dovete avviare <code>calcurse</code> con il seguente
- comando:</p>
-<pre>LC_ALL=fr_FR.ISO8859-1 calcurse</pre>
-
-<h3>4.1.3 Altre variabili
-d'ambiente<a name="basics_invocation_environment"></a></h3>
-<p>
- Le seguenti variabili d'ambiente modificano il funzionamento
- di <code>calcurse</code>:</p>
-
-<dl>
- <dt><code>VISUAL</code></dt>
- <dd>Indica l'editor usato per scrivere le note.
- </dd>
- <dt><code>EDITOR</code></dt>
- <dd>Se non viene impostata la variabile <code>VISUAL</code> viene
- usato l'editor indicato dalla variabile <code>EDITOR</code> come
- editor di default; se non viene definita nessuna variabile viene
- usato l'editor <code>/usr/bin/vi</code>.
- </dd>
- <dt><code>PAGER</code></dt>
- <dd>Specifica il visualizzatore di default usato per leggere le
- note. Se questa variabile non viene impostata viene
- usato <code>/usr/bin/less</code>.
- </dd>
-</dl>
-
-<h2>4.2 Interfaccia utente<a name="basics_interface"></a></h2>
-<h3>4.2.1 Modalità non-interattiva<a name="basics_interface_noninteractive"></a></h3>
-<p>
- Quando <code>calcurse</code> viene avviato con una delle opzioni
- <code>-a</code>, <code>-d</code>, <code>-h</code>, <code>-n</code>, <code>-t</code>, <code>-v</code>, <code>-x</code>
- funziona nella modalità non-interattiva; questo significa che dopo
- aver mostrato le informazioni richieste <code>calcurse</code> esce riportando al
- prompt della shell.</p>
-
-<p>
- In questo modo è possibile ad esempio aggiungere una linea
- siffatta <code>'calcurse --todo --appointment'</code> nel file di
- avvio della shell per mostrare al logon un elenco dei compiti e
- degli appuntamenti previsti per la data odierna.</p>
-
-<h3>4.2.2 Modalità interattiva<a name="basics_interface_interactive"></a></h3>
-<div class="todo">
- <p class="rq"><span class="valorise">Note:</span>
- Key bindings that are indicated in this manual correspond to
- the default ones, defined when <code>calcurse</code> is launched
- for the first time. If those key bindings do not suit user's needs,
- it is possible to change them within the keys configuration menu
- (see <a href="#options_keys">key bindings</a>).</p>
-</div>
-<p>
- Se viene avviato senza argomenti oppure solo con
- l'opzione <code>'-c'</code> <code>calcurse</code> si avvia nella modalità
- interattiva; in questa modalità viene mostrata un'interfaccia
- contenente tre differenti sezioni (fra le quali è possibile passare
- con il tasto 'TAB'), una barra di notifica ed una barra di stato
- (vedi la figura sotto).
-</p>
-<pre>
-
- Sezione appuntamenti ---. .--- Sezione calendario
- | |
- v v
- +------------------------------------++----------------------------+
- | Appointments || Calendar |
- |------------------------------------||----------------------------|
- | (|) April 6, 2006 || April 2006 |
- | ||Mon Tue Wed Thu Fri Sat Sun |
- | || 1 2 |
- | || 3 4 5 6 7 8 9 |
- | || 10 11 12 13 14 15 16 |
- | || 17 18 19 20 21 22 23 |
- | || 24 25 26 27 28 29 30 |
- | || |
- | |+----------------------------+
- | |+----------------------------+
- | || ToDo | Sezione
- | ||----------------------------| attività
- | || | |
- | || | |
- | || |&lt;--.
- | || |
- +------------------------------------++----------------------------+
- |---[ Mon 2006-11-22 | 10:11:43 ]---(apts)----&gt; 01:20 :: lunch &lt;---|&lt;--.
- +------------------------------------------------------------------+ barra di notifica
- | ? Help R Redraw H/L -/+1 Day G GoTo C Config |
- | Q Quit S Save J/K -/+1 Week Tab Chg View |&lt;-.
- +------------------------------------------------------------------+ |
- |
- barra di stato
-
-
-</pre>
-<p>
- La prima sezione rappresenta un calendario dove è possibile
- evidenziare una particolare data; la seconda sezione contiene la
- lista degli eventi e degli appuntamenti per la data evidenziata; ed
- infine la terza sezione contiene la lista delle attività non
- assegnate a nessun giorno particolare.</p>
-<div class="todo">
-<p>
- Depending on the selected view, the calendar could either display
- a monthly (default as shown in previous figure) or weekly view.
- The weekly view would look like the following:</p>
- <pre>
-
-+------------------------------------+
-| Calendar |
-|----------------------------(# 13)--|
-| Mon Tue Wed Thu Fri Sat Sun |
-| 29 30 31 01 02 03 04 |
-| <----+-- slice 1: 00:00 to 04:00 AM
-| -- -- -- -- -- -- |
-| <----+-- slice 2: 04:00 to 08:00 AM
-| -- -- -- -- -- -- |
-| <----+-- slice 3: 08:00 to 12:00 AM
-| - -- -- -- -- -- -- - <-+-- midday
-| <----+-- slice 4: 12:00 to 04:00 PM
-| -- -- -- -- -- -- |
-| <----+-- slice 5: 04:00 to 08:00 PM
-| -- -- -- -- -- -- |
-| <----+-- slice 6: 08:00 to 12:00 PM
-+------------------------------------+
-
- </pre>
-<p>
- The current week number is displayed on the top-right side of the panel
- (<span class="emp"># 13</span> meaning it is the 13th week of the year
- in the above example). The seven days of the current week are displayed
- in column. Each day is divided into slices of 4 hours each (6 slices in
- total, see figure above). A slice will appear in a different color if
- an appointment falls into the corresponding time-slot.
-</p>
-</div>
-
-<p>
- Nella sezione degli appuntamenti si può notare il
- segno <span class="emp">'(|)'</span> accanto alla data indicante la
- fase lunare secondo la seguente tabella:
-
- <dl class="compact">
- <dt>'<code> |) </code>':</dt>
- <dd>primo quarto</dd>
- <dt>'<code> (|) </code>':</dt>
- <dd>plenilunio</dd>
- <dt>'<code> (| </code>':</dt>
- <dd>terzo quarto</dd>
- <dt>'<code> | </code>':</dt>
- <dd>novilunio</dd>
- <dt>nessun segno:</dt>
- <dd>la fase della luna non corrisponde a nessuna di queste</dd>
- </dl>
-</p>
-<p>
- Nell'ultima riga dello schermo si trova la barra di stato che
- indica le azioni possibili e le relative scorciatoie di tastiera.
-</p>
-<p>
- Al di sopra della barra di notifica si trova la barra di notifica
- che indica (da destra a sinistra): la data e l'ora correnti, il file
- calendario attualmente in uso (apts nella figura precedente, che è
- il nome di default, vedi la prossima sezione) e il prossimo
- appuntamento nelle successive 24 ore; nella figura d'esempio viene
- indicato l'appuntamento per il pranzo fra un'ora e venti.
-</p>
-
-<p class="rq"><span class="valorise">Nota:</span> alcune azioni, quali
- modifica o aggiunta di una voce, richiedono l'inserimento del testo
- mediante l'editor a linea compreso nel programma.</p>
-
-<p>
- All'interno di questo editor se appare una linea maggiore
- dell'ampiezza dello schermo vengono mostrati i caratteri '&gt;',
- '*', o '&lt;' nell'ultima colonna nel caso ci siano altri caratteri
- successivamente, prima o dopo della posizione corrente; è inoltre
- possibile scorrere orizzontalmente.</p>
-
-<p>
- Inoltre alcuni comandi sono collegati ad alcune scorciatoie. Di
- seguito sono elencati alcuni comandi (dove '^' indica per il tasto
- Control):
- <dl class="compact">
- <dt><code>^a</code>:</dt>
- <dd>sposta il cursore all'inizio della riga di input</dd>
- <dt><code>^b</code>:</dt>
- <dd>sposta il cursore indietro</dd>
- <dt><code>^d</code>:</dt>
- <dd>cancella il carattere davanti</dd>
- <dt><code>^e</code>:</dt>
- <dd>sposta il cursore alla fine della riga di input</dd>
- <dt><code>^f</code>:</dt>
- <dd>sposta il cursore avanti</dd>
- <dt><code>^h</code>:</dt>
- <dd>cancella il carattere dietro</dd>
- <dt><code>^k</code>:</dt>
- <dd>cancella dal cursore fino alla fine della riga di input</dd>
- <dt><code>ESCAPE</code>:</dt>
- <dd>cancella la modifica</dd>
- </dl>
-</p>
-
-<div class="todo">
-<h2>4.3 Background mode<a name="basics_daemon"></a></h2>
-
-<p>When the daemon mode is enabled in the notification configuration menu
-(see <a href="#options_notify">Notify-bar settings</a>), <code>calcurse</code> will stay
-in background when the user interface is not running. In background mode,
-<code>calcurse</code> checks for upcoming appointments and runs the user-defined
-notification command when necessary. When the user interface is started again,
-the daemon automatically stops.</p>
-
-<p><code>calcurse</code> background activity can be logged (set the
-<code>notify-daemon_log</code> variable in the notification configuration
-<a href="#options_notify">menu</a>), and in that case, information about the daemon
-start and stop time, reminders' command launch time, signals received... will be written
-in the <code>daemon.log</code> file (see section <a href="#basics_files">files</a>).</p>
-
-<p>
-Using the <code>--status</code> command line option (see section
-<a href="#basics_invocation_commandline">Command line arguments</a>),
-one can know if <code>calcurse</code> is currently running in background or not.
-If the daemon is running, a message like the following one will be displayed (the pid of
-the daemon process will be shown):
-<pre>calcurse is running in background (pid 14536)</pre>
-
-<p class="rq"><span class="valorise">Note:</span>
-To stop the daemon, just send the <code>TERM</code> signal to it, using a command such as:
-<code>'kill daemon_pid'</code>, where <span class="emp">daemon_pid</span> is the process id
-of the daemon (14536 in the above example).
-</p>
-</div>
-
-<h2>4.4 File di <code>calcurse</code><a name="basics_files"></a></h2>
-<p>
- Al primo avvio di <code>calcurse</code> viene creata nella vostra
- directory <code>$HOME</code>
- <div class="todo">(or in the directory you specified with the -D option)</div>
- questa gerarchia di directory:
-</p>
-<pre>
- $HOME/.calcurse/
- |___notes/
- |___conf
- |___keys
- |___apts
- |___todo
-</pre>
-
-<dl class="compact">
- <dt><code>notes/</code>:</dt>
- <dd>questa sotto-directory contiene le descrizioni delle note
- allegate agli appuntamenti, eventi o attività. Per ogni nota viene
- creato un file di testo con un nome creato dalla funziona
- mkstemp(3) che dovrebbe essere unico ma senza alcuna correlazione
- evidente con la descrizione dell'oggetto al quale viene collegato.
- </dd>
-
- <dt><code>conf</code>:</dt>
- <dd>questo file contiene le configurazioni dell'utente</dd>
-
- <dt><code>keys</code>:</dt>
- <dd><span class="todo">this file contains the user-defined key bindings</span></dd>
-
- <dt><code>apts</code>:</dt>
- <dd>questo file contiene gli eventi e gli appuntamenti
- dell'utente</dd>
-
- <dt><code>todo</code>:</dt>
- <dd>questo file contiene l'elenco delle attività</dd>
-</dl>
-
-<div class="todo">
- <p class="rq"><span class="valorise">Note:</span>
- If the logging of calcurse daemon activity was set in the notification
- configuration menu, the extra file <code>daemon.log</code> will appear
- in calcurse data directory. This file contains logs about calcurse activity
- when running in background.
- </p>
-</div>
-
-<div class="todo">
-<h2>4.5 Import/Export capabilities<a name="basics_import_export"></a></h2>
-<p>
- The import and export capabilities offered by <code>calcurse</code>
- are described below.
-</p>
-
-<h3>4.5.1 Import<a name="basics_import"></a></h3>
-<p>
- Data in icalendar format as described in the rfc2445 specification
- (see <a href="#links_others">links</a> section below) can be imported
- into calcurse. Calcurse ical parser is based on version 2.0 of this
- specification, but for now on, only a subset of it is supported.
-</p>
-<p>
- The following icalendar properties are handled by calcurse:
- <ul>
- <li><code>VTODO</code> items:<br>
- "PRIORITY", "VALARM", "SUMMARY", "DESCRIPTION"</li>
- <li><code>VEVENT</code> items:<br>
- "DTSTART", "DTEND", "DURATION", "RRULE", "EXDATE", "VALARM", "SUMMARY",
- "DESCRIPTION"</li>
- </ul>
-</p>
-<p>
- The icalendar "DESCRIPTION" property will be converted into calcurse format
- by adding a note to the item. If a "VALARM" property is found, the item
- will be flagged as important and the user will get a notification (this is
- only applicable to appointments).
-</p>
-<p>
- Here are the properties that are not implemented:
- <ul>
- <li>negative time durations are not taken into account (item is skipped)</li>
- <li>some recurence frequences are not recognize:<br>
- "SECONDLY" / "MINUTELY" / "HOURLY"</li>
- <li>some recurrence keywords are not recognized
- (all those starting with 'BY'):<br>
- "BYSECOND" / "BYMINUTE" / "BYHOUR" / "BYDAY" / "BYMONTHDAY"<br>
- "BYYEARDAY" / "BYWEEKNO" / "BYMONTH" / "BYSETPOS"<br>
- plus "WKST"</li>
- <li>the recurrence exception keyword "EXRULE" is not recognized</li>
- <li>timezones are not taken into account</li>
- </ul>
-</p>
-
-<h3>4.5.2 Export<a name="basics_export"></a></h3>
-<p>
- Two possible export formats are available: <code>ical</code> and
- <code>pcal</code> (see section <a href="#links_others">Links</a> below
- to find out about those formats).
-</p>
-</div>
-
-<h2>4.6 Aiuto in linea<a name="basics_help"></a></h2>
-<p>
- In ogni momento è possibile richiedere il sistema dell'aiuto in
- linea premendo il tasto '?': una volta avviato si possono richiedere
- le informazioni su un certo comando premendo il tasto relativo.
-</p>
-
-<h1>5. Opzioni<a name="options"></a></h1>
-<p>
- Tutti i parametri di <code>calcurse</code> sono configurabili dal menù
- Configuration accessibile premendo il tasto 'C' che porta ad un
- sotto-menù con quattro possibili scelte: premendo ancora 'C' si
- raggiunge alla configurazione dello schema dei colori; premendo 'L'
- è possibile scegliere la configurazione dell'interfaccia dello
- schermo principale di <code>calcurse</code> (praticamente le posizioni relative
- dei tre pannelli); premendo 'G' è possibile modificare alcune
- opzioni generali;
- <span class="todo">pressing 'K' opens the key bindings configuration
- menu,</span>
- ed infine premendo 'N' è possibile modificare le
- impostazioni della barra di notifica.
-</p>
-
-<h2>5.1 Opzioni generali<a name="options_general"></a></h2>
-<p>
- Queste opzioni controllano il comportamento generale di <code>calcurse</code>:
-</p>
- <dl>
- <dt><code>auto_save</code>
- (default: <span class="emp">yes</span>)</dt>
- <dd>
- Questa opzione permette di salvare automaticamente i dati
- dell'utente all'uscita del programma.
- <p class="rq"><span class="valorise">attenzione:</span> i
- dati non verranno salvati automaticamente se impostato
- a <span class="emp">no</span>. Questo comporta che sarà
- necessario premere 'S' per salvare i dati eventualmente
- modificati.
- </dd>
-
- <dt><code><span class="todo">periodic_save</code>
- (default: <span class="emp">0</span>)</span></dt>
- <dd><span class="todo">If different from '0', user's data will be automatically
- saved every <span class="emp">periodic_save</span> minutes.
- When an automatic save is performed, two asterisks
- (i.e. '<code>**</code>') will appear on the top right-hand side
- of the screen).</span>
- </dd>
-
- <dt><code>confirm_quit</code>
- (default: <span class="emp">yes</span>)</dt>
- <dd>
- Se impostato a <span class="emp">yes</span> è necessario
- confermare l'uscita dal programma; altrimenti premendo 'Q'
- <code>calcurse</code> esce senza chiedere conferma.
- </dd>
-
- <dt><code>confirm_delete</code>
- (default: <span class="emp">yes</span>)
- </dt>
- <dd>
- Se viene impostata a <span class="emp">yes</span> premendo
- 'D' per cancellare una voce (che può essere
- un'<span class="emp">attività</span>,
- un <span class="emp">appuntamento</span>, o
- un <span class="emp">evento</span>) è necessario
- confermare. Altrimenti non è necessaria alcuna conferma.
- </dd>
-
- <dt><code>skip_system_dialogs</code>
- (default: <span class="emp">no</span>)
- </dt>
- <dd>
- Impostando questa opzione a <span class="emp">yes</span>
- non verranno più mostrati i messaggi di sistema
- riguardanti il salvataggio e la lettura dei dati, utile
- per velocizzare le operazioni di input e output.
- </dd>
- <dt><code>skip_progress_bar</code>
- (default: <span class="emp">no</span>)</dt>
- <dd>
- Se impostato a <span class="emp">yes</span> non verrà
- visualizzata la barra di avanzamento che indica il
- salvataggio in corso dei files insieme al file che viene
- salvato (vedi la
- sezione <a href="#basics_files"><code>calcurse</code> files</a>).
- </dd>
-
- <dt><code><span class="todo">calendar_default_view</span></code>
- (default: <span class="emp">0</span>)</dt>
- <dd><span class="todo">If set to <span class="emp">0</span>, the monthly calendar view will be
- displayed by default otherwise it is the weekly view that will be displayed.</span>
- </dd>
-
- <dt><code>week_begins_on_monday</code>
- (default: <span class="emp">yes</span>)</dt>
- <dd>
- Con questa opzione è possibile indicare con quale giorno,
- domenica o lunedì, far iniziare la settimana nella
- finestra del calendario.
- </dd>
-
- <dt><code><span class="todo">output_datefmt</code>
- (default: <span class="emp">%D</span>)</span></dt>
- <dd><span class="todo">This option indicates the format to be used when displaying dates
- in non-interactive mode. Using the default values, dates are displayed the
- following way: <span class="emp">mm/dd/aa</span>.
- You can see all of the possible formats by typing <code>man 3 strftime</code>
- inside a terminal.</span></dd>
-
- <dt><code><span class="todo">input_datefmt</code>
- (default: <span class="emp">1</span>)</span></dt>
- <dd><span class="todo">This option indicates the format that will be used to enter dates in
- <span class="emp">calcurse</span>. Four choices are available:</span>
- <ol>
- <li>mm/dd/yyyy</li>
- <li>dd/mm/yyyy</li>
- <li>yyyy/mm/dd</li>
- <li>yyyy-mm-dd</li>
- </ol>
- </dd>
-
- </dl>
-
-<div class="todo">
-<h2>5.2 Key bindings<a name="options_keys"></a></h2>
-<p>
- One can define it's own keybindings within the 'Keys' configuration
- menu. The default keys look like the one used by the <code>vim</code>
- editor, especially the displacement keys. Anyway, within this
- configuration menu, users can redefine all of the keys available from
- within calcurse's user interface.</p>
-<p>
- To define new keybindings, first highlight the action to which it will
- apply. Then, delete the actual key binding if necessary, and add a new
- one. You will then be asked to press the key corresponding to the new
- binding. It is possible to define more than one key binding for a single
- action.</p>
-<p>
- An automatic check is performed to see if the new key binding
- is not already set for another action. In that case, you will be asked
- to choose a different one. Another check is done when exiting from this
- menu, to make sure all possible actions have a key associated with it.</p>
-<p>
- The following keys can be used to define bindings:
- <ul>
- <li>lower-case, upper-case letters and numbers, such as 'a', 'Z', '0'</li>
- <li>CONTROL-key followed by one of the above letters</li>
- <li>escape, horizontal tab, and space keys</li>
- <li>arrow keys (up, down, left, and right)</li>
- <li>'HOME' and 'END' keys</li>
- </ul> </p>
-<p>
- While inside the key configuration menu, an online help is available for
- each one of the available actions. This help briefly describes what the
- highlighted action is used for.</p>
-</div>
-
- <h2>5.3 Color themes<a name="options_colors"></a></h2>
-<p>
- Il tema del colore di <code>calcurse</code> può essere personalizzato a seconda
- delle necessità dell'utente. Nella pagina di configurazione è
- possibile cambiare i colori dello sfondo e del primo piano del tema
- predefinito: usando i tasti cursore o i tasti di movimento definiti
- per lo spostamento in <code>calcurse</code>, il tasto 'X' o lo spazio per
- selezionare il colore l'utente può vedere l'anteprima del tema
- prescelto. &Egrave; anche possibile mantenere i colori predefiniti del
- terminale selezionando la relativa opzione nella lista.
-</p>
-
-<p>
- Il tema scelto viene applicato ai bordi del pannello, ai titoli,
- alle indicazioni delle scorciatoie da tastiera e in generale alle
- informazioni mostrate nella barra di stato. Fra gli altri è anche
- presente un tema in bianco e nero per usarlo sui terminali monocromatici.
-</p>
-
- <p class="rq">
- <span class="valorise">Nota:</span> i colori possono anche
- non essere supportati a seconda del tipo di terminale e dal
- valore della variabile d'ambiente <code>$TERM</code>; nel
- caso in cui il tipo di terminale non li supportasse apparirà
- un messaggio d'errore provando a cambiare i colori.
- Se sapete che il vostro terminale supporta i colori ma
- questi non appaiono provate ad impostare la variabile
- <code>$TERM</code> ad un altro valore (come ad
- esempio <span class="emp">xterm-xfree86</span>).
- </p>
-
-
-<h2>5.4 Configurazione del layout<a name="options_layout"></a></h2>
-<p>
- Il layout è la posizione dei pannelli all'interno dello schermo di
- <code>calcurse</code>. Il layout predefinito è così disposto: il pannello del
- calendario in alto a destra, il pannello delle attività in basso a
- destra e il pannello degli appuntamenti sul lato sinistro dello
- schermo (vedi la figura della
- sezione <a href="#basics_interface_interactive">Modo
- interattivo</a>).
- Scegliendo un altro layout è possibile personalizzare l'aspetto di
- <code>calcurse</code> a seconda delle necessità.
-</p>
-
-<div class="todo">
-<p>
- The following option is used to modify the layout configuration:</p>
- <dl>
- <dt><code>layout</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>Eight different layouts are to be chosen from (see layout
- configuration screen for the description of the available layouts).</dd>
- </dl>
-</div>
-
-
-<div class="todo">
-<h2>5.5 Sidebar configuration<a name="options_sidebar"></a></h2>
-<p>
- The sidebar is the part of the screen which contains two panels:
- the calendar and, depending on the chosen layout, either the todo
- list or the appointment list.</p>
-<p>
- The following option is used to change the width of the sidebar:</p>
- <dl>
- <dt><code>side-bar_width</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>Width (in percentage, 0 being the minimum width) of the side bar.</dd>
- </dl>
-</div>
-
-<h2>5.6 Impostazioni della barra delle notifiche<a name="options_notify"></a></h2>
-<p>
- Le seguenti opzioni modificano il comportamento della barra delle
- notifiche:
-</p>
-<dl>
- <dt><code>notify-bar_show</code>
- (default: <span class="emp">yes</span>)</dt>
- <dd>
- Questa opzione imposta la visibilità della barra delle notifiche.
- </dd>
-
- <dt><code>notify-bar_date</code>
- (default: <span class="emp">%a %F</span>)</dt>
- <dd>
- Questa opzione imposta il formato utilizzato per la data mostrata
- all'interno della barra delle notifiche. &Egrave; possibile vedere
- tutti i possibili formati digitando <code>man 3 strftime</code>
- all'interno di un terminale.
- </dd>
-
- <dt><code>notify-bar_time</code>
- (default: <span class="emp">%T</span>)</dt>
- <dd>
- Questa opzione imposta il formato utilizzato per mostrare l'orario
- all'interno della barra delle notifiche. &Egrave; possibile vedere
- tutti i possibili formati digitando <code>man 3 strftime</code>
- all'interno di un terminale.
- </dd>
-
- <dt><code>notify-bar_warning</code>
- (default: <span class="emp">300</span>)</dt>
- <dd>
- Nel caso sia presente un appuntamento marcato come 'important'
- nell'intervallo definito (in secondi) nella variabile
- 'notify-bar_warning' viene mostrata lampeggiante la descrizione
- dell'appuntamento stesso all'interno della barra delle notifiche.
- Inoltre viene eseguito il comando definito
- dall'opzione <code>notify-bar_command</code>.
- In questo modo è possibile essere avvisati dell'avvicinarsi
- di un appuntamento.
- </dd>
-
- <dt><code>notify-bar_command</code>
- (default: <span class="emp">printf '\a'</span>)</dt>
- <dd>
- Questa opzione imposta il comando che deve essere avviato
- all'avvicinarsi di un appuntamento marcato come 'important'. Il
- comando viene passato alla shell che lo deve interpretare. Per
- sapere quale tipo di shell è in uso verificare il valore della
- variabile d'ambiente <code>$SHELL</code>; nel caso questa
- variabile non sia impostata viene usata <code>/bin/sh</code>.
-
- <p class="rq"><span class="valorise">Esempio:</span>
- Ammesso che sul sistema in uso sia disponibile il
- comando <code>mail</code> il seguente comando permette di
- ricevere la notifica con un messaggio di posta elettronica di un
- appuntamento imminente (la descrizione dell'appuntamento viene
- inclusa anche nel corpo del messaggio):
- </p>
- <code>
- calcurse --next | mail -s "[calcurse] upcoming appointment!" user@host.com
- </code>
- </dd>
- <dt><code><span class="todo">notify-daemon_enable</code>
- (default: <span class="emp">no</span>)</span></dt>
- <dd><span class="todo">If set to yes, daemon mode will be enabled, meaning <code>calcurse</code>
- will run into background when the user's interface is exited. This will allow the
- notifications to be launched even when the interface is not running. More details
- can be found in section <a href="#basics_daemon">'Background mode'</a>.</span>
- </dd>
- <dt><code><span class="todo">notify-daemon_log</code>
- (default: <span class="emp">no</span>)</span></dt>
- <dd><span class="todo">If set to yes, <code>calcurse</code> daemon activity will be logged (see section
- <a href="#basics_files">files</a></span>).
- </dd>
-
-</dl>
-
-<h1>6. Bachi conosciuti<a name="known_bugs"></a></h1>
-<p>
- L'evidenziazione delle voci appare scorretta usando calcurse con un
- tema bianco e nero insieme alla variabile <code>$TERM</code>
- impostata a <span class="emp">xterm-color</span>.
-
- Per risolvere questo baco, così come affermato da Thomas E. Dickey
- (manutentore di <code>xterm</code>), si deve usare il
- valore <span class="emp">xterm-xfree86</span> per la
- variabile <code>$TERM</code>:
-</p>
-<blockquote class="rq">
- "The xterm-color value for $TERM is a bad choice for XFree86 xterm
- because it is commonly used for a terminfo entry which happens to
- not support bce. Use the xterm-xfree86 entry which is distributed
- with XFree86 xterm (or the similar one distributed with ncurses)."
-</blockquote>
-
-<h1>7. Segnalazione dei bachi e feedback<a name="bugs"></a></h1>
-<p>
- Siete invitati a segnalare i bachi e quant'altro a:
-</p>
-<pre>calcurse .at. culot .dot. org</pre>
-<p>
- oppure direttamente all'autore:
-</p>
-<pre>frederic .at. culot .dot. org</pre>
-
-<h1>8. Come contribuire<a name="contribute"></a></h1>
-<p>
- Se siete interessati a collaborare al progetto dovreste prima di
- tutto segnalare pregi e difetti oppure funzionalità mancanti in
- <code>calcurse</code>.
- Attualmente è possibile partecipare alle traduzioni dei messaggi e
- del manuale di <code>calcurse</code>
-</p>
-<p class="rq"><span class="valorise">Nota:</span> ogni aiuto ad
- aumentare il supporto all'internazionalizzazione di <code>calcurse</code> è
- benvenuto ma prima di cominciare scrivete a
- <code>calcurse-i18n .at. culot .dot. org</code>
- per evitare di duplicare gli sforzi.
-</p>
-
-<h2>8.1 Tradurre la documentazione<a name="contribute_documentation"></a></h2>
-<p>
- La directory <span class="emp">doc/</span> del pacchetto dei
- sorgenti contiene anche le versioni già tradotte del manuale di
- <code>calcurse</code>; se il manuale non è ancora stato tradotto nella vostra
- lingua ogni aiuto in tal senso sarà più che apprezzato.
-</p>
-<p>
- Per fare questo è sufficiente copiare il file contenente il manuale
- con il nome <code>manual_XX.html</code>
- dove <span class="emp">XX</span> identifica il vostro linguaggio:
- questo file deve essere tradotto ed inviato all'autore
- (vedi <a href="#bugs">Riportare i bachi e feedback</a>) così che
- possa essere incluso nel successivo rilascio
- di <code>calcurse</code>.
-</p>
-
-<h2>8.2 <code>calcurse</code> i18n<a name="contribute_i18n"></a></h2>
-<p>
-
- Le utilità di <code>calcurse</code> producono messaggi multi-lingua,
- così come ricordato in precedenza: questa sezione contiene
- informazioni sulla traduzione di questi messaggi nella vostra
- lingua; queste informazioni sono però incomplete in quanto sono
- concentrate sull'uso di <code>gettext</code>
- per <code>calcurse</code>. Per informazioni maggiormente
- approfondite e per comprendere il Grande Disegno che sottintende al
- Supporto delle Lingue fate riferimento al manuale di
- <code>GNU gettext</code>:
-
-</p>
-<pre>http://www.gnu.org/software/gettext/manual/</pre>
-<p>
- Fondamentalmente sono tre le figure coinvolte nel processo di
- traduzione: gli sviluppatori, i coordinatori per la lingua e i
- traduttori. Dopo una rapida scorsa al funzionamento del meccanismo
- verrà illustrato il compito dei traduttori.
-</p>
-
-
-<h3>8.2.1 Panoramica<a name="contribute_i18n_overview"></a></h3>
-<p>
- Per essere in grado di mostrare i messaggi nel linguaggio definito
- dall'utente sono necessari due passaggi:
- l'<span class="emp">internazionalizzazione</span> (i18n) e
- la <span class="emp">localizzazione</span> (l10n).
-</p>
-<p>
- i18n è la possibilità per <code>calcurse</code> di supportare svariati linguaggi
- che viene inserita dagli sviluppatori, i quali indicano come
- traducibili i messaggi e prevedono un sistema per mostrarli tradotti
- mentre il programma sta funzionando.
-</p>
-<p>
- l10n è invece il rendere <code>calcurse</code> così programmato adatto al
- linguaggio definito dall'utente traducendo le stringhe predefinite
- dagli sviluppatori e impostando le variabili d'ambiente così che
- <code>calcurse</code> sia in grado di mostrare le stringhe tradotte.
-</p>
-<p>
- Le stringhe traducibili vengono innanzitutto indicate come tali nei
- sorgenti <code>C</code>, poi raccolte in un file modello
- (<span class="emp">calcurse.pot</span> - la cui
- estensione <span class="emp">pot</span>
- significa <span class="emp">portable object template</span>). Il
- contenuto del file modello viene successivamente inserito nei file
- per la traduzione per ogni linguaggio (ad
- esempio <span class="emp">fr.po</span> per il francese, la cui
- estensione <span class="emp">po</span> sta
- per <span class="emp">portable object</span>, cioè leggibile e
- modificabile dagli umani).
- Ogni gruppo di traduzione prende questo file, ne traduce le stringhe
- e poi le invia indietro agli sviluppatori.
- Al momento della compilazione viene prodotta una versione binaria di
- questo file per ragioni d'efficienza (nel nostro
- esempio <span class="emp">fr.mo</span> -
- dove <span class="emp">mo</span> sta per <span class="emp">machine
- object</span>, cioè leggibile dai programmi) e successivamente
- installato.
- A questo punto <code>calcurse</code> sarà in grado di usare questo file
- traducendo le stringhe a seconda delle variabili d'ambiente
- impostate dall'utente.
-</p>
-
-
-<h3>8.2.2 Compiti dei traduttori<a name="contribute_i18n_translator"></a></h3>
-<p>
- Questi sono i passaggi da seguire qualora si volesse iniziare una
- nuova traduzione:
-</p>
-<ul>
- <li>
- Innanzitutto si deve trovare quale sia la sigla che individua il
- linguaggio prescelto: ad esempio 'fr_FR' o più semplicemente 'fr'
- indica il francese. Questo sarà il valore a cui impostare la e
- variabile d'ambiente <code>LC_ALL</code> perché il programma
- mostri correttamente le stringhe tradotte (vedi
- <a href="#basics_invocation_variable">Variabili d'ambiente per
- l'i18</a>).
- </li>
-
- <li>
- Poi si dovrà creare un nuovo file 'po' all'interno della
- directory <span class="emp">po/</span> usando un file modello con
- il seguente comando:
- <code>'msginit -i calcurse.pot -o fr.po -l fr --no-translator'</code>.
- Nel caso in cui il comando <code>msginit</code> non sia
- disponibile sul sistema in uso copiate semplicemente il
- file <span class="emp">calcurse.pot</span> con il nome (nel nostro
- esempio) <span class="emp">fr.po</span> e modificatene gli header
- a mano.
- </li>
-</ul>
-<p>
- A questo punto è possibile iniziare la traduzione del
- file <span class="emp">fr.po</span> appena creato.
-</p>
-
-
-<h3>8.2.3 I file po<a name="contribute_i18n_po-files"></a></h3>
-<p>
- Il formato dei file po è relativamente semplice essendo composti di
- quattro componenti:
-</p>
-<ol>
- <li>
- <span class="emp">Linee locations:</span> indicano la posizione in
- cui si trovano le stringhe (nome del file e numero di linea) nel
- caso sia necessario avere un po' di contesto.
- </li>
- <li>
- <span class="emp">Linee msgid:</span> le stringhe da tradurre.
- </li>
- <li>
- <span class="emp">Linee msgstr:</span> le stringhe tradotte.
- </li>
- <li>
- <span class="emp">Linee che iniziano con '#':</span> commenti (alcuni
- con significati speciali come spiegato più avanti).
- </li>
-</ol>
-<p>
- Praticamente è necessario tradurre le suddette linee marcate
- con <span class="emp">msgstr</span> con la traduzione delle linee
- marcate con <span class="emp">msgid</span>
-</p>
-<p>
- <span class="valorise">Alcune note:</span>
- <dl>
- <dt>
- <span class="emp">Stringhe fuzzy</span>
- </dt>
- <dd>
- Potrete trovare alcune stringhe marcate con un
- commento <code>"#, fuzzy"</code>, stringhe che <code>calcurse</code> non
- userà finché non verrà preso qualche provvedimento. Questo
- perché la stringa in questione è stata cambiata nei sorgenti del
- programma oppure perché <code>gettext</code> ha tentato di
- 'indovinarne' il significato basandosi su altre stringhe simili
- già presenti nel file. Questo comporta la necessità di
- controllare la traduzione.
- Alcune volte la stringa originale è stata modificata per
- correggere un errore ortografico; in questo caso non è
- necessaria alcuna azione. Altre volte però la traduzione non è
- più corretta per cui è necessario rivederla.
- Una volta che la traduzione può essere considerata corretta è
- sufficiente rimuovere la linea <code>"#, fuzzy"</code> e questa
- verrà usata normalmente.
- </dd>
- <dt>
- <span class="emp">Stringhe c-format e sequenze speciali</span>
- </dt>
- <dd>
- Alcune stringhe potranno avere il commento <code>"#, c-format"</code>.
- Questo indica che una componente della stringa ha un particolare
- significato per il programma e che quindi avrà lasciata
- inalterata. Ad esempio la sequenze come <code>"%s"</code>
- vengono sostituite dal programma con altre stringhe.
- Ci sono anche le sequenze del tipo <code>\n</code>
- e <code>\t</code> che non devono essere modificate perché la
- prima indica un ritorno a capo e la seconda una tabulazione.
- </dd>
- <dt>
- <span class="emp">Le traduzioni possono avere ritorno a
- capo</span>
- </dt>
- <dd>
- Se le linee sono troppo lunghe possono essere interrotte così:
- <pre>
- msgid ""
- "some very long line"
- "another line"
- </pre>
- </dd>
- <dt>
- <span class="emp">Header dei file po</span>
- </dt>
- <dd>
- Nelle prime righe del file po la prima stringa costituisce un
- header contenente alcune informazioni che devono essere
- completate. Questi header sono:
- <pre>
- "Content-Type: text/plain; charset=utf-8\n"
- </pre>
- &Egrave; anche necessario compilare il campo 'Last-Translator'
- di modo che altri potenziali collaboratori possano contattarvi
- per unire gli sforzi o per segnalare errori e
- correzioni. &Egrave; possibile usare anche un soprannome o
- aggiungere un indirizzo di posta elettronica come ad esempio:
- <pre>
- "Last-Translator: Frederic Culot &lt;frederic@culot.org&gt;\n"
- </pre></dd>
- <dt>
- <span class="emp">Commenti</span>
- </dt>
- <dd>
- Aggiungere commenti (indicati dalle linee che iniziano con il
- carattere '#') può essere un valido modo per indicare problemi o
- difficoltà trovate nella traduzione ad altri collaboratori o in
- generale ai partecipanti alla traduzione.
- </dd>
- <dt>
- <span class="emp">Dimensione delle stringhe</span>
- </dt>
- <dd>
- <code>Calcurse</code> è un programma per la console scritto
- usando le librerie 'curses' per cui può essere fortemente
- limitato dalle dimensioni (in particolare dal numero di colonne)
- del terminale, limitazioni che è necessario tenere a mente
- mentre si traduce. Spesso una stringa deve essere tutta compresa
- in una singola linea (la cui dimensione standard è di 80
- caratteri). Ponete attenzione e verificate che la vostra
- traduzione si adatti alla posizione prevista sullo schermo.
- </dd>
- <dt>
- <span class="emp">Alcuni utili strumenti</span>
- </dt>
- <dd>
- Il file po ha una struttura estremamente semplice per cui può
- essere modificato anche direttamente con un normale editor di
- testi; in ogni caso è possibile anche usare degli strumenti
- specializzati:
- <ul>
- <li>
- <code>poEdit</code> (<a href="http://www.poedit.org/" target="_blank">http://www.poedit.org/</a>)
- </li>
- <li>
- <code>KBabel</code>
- (<a href="http://i18n.kde.org/tools/kbabel/" target="_blank">http://i18n.kde.org/tools/kbabel/</a>)
- </li>
- <li>
- <code>GTranslator</code>
- (<a href="http://gtranslator.sourceforge.net/" target="_blank">http://gtranslator.sourceforge.net/</a>)
- </li>
- <li>
- <code>Emacs</code> po mode
- </li>
- <li>
- <code>Vim</code> po mode
- </li>
- </ul>
- </dd>
- <dt>
- <span class="emp">E per chiudere</span>
- </dt>
- <dd>
- Mi auguro che troviate soddisfazione nel contribuire ad un mondo
- maggiormente internazionalizzato. :) Se avete altre domande non
- esitate a contattarmi all'indirizzo
- <span class="emp">frederic .at. culot .dot. org</span>.
- </dd>
- </dl>
-
-
- <h1>9. Link<a name="links"></a></h1>
-<p>
- Questa sezione contiene link e riferimenti che possono risultare
- interessanti.
-</p>
-
-<h2>9.1 Homepage di <code>calcurse</code><a name="links_homepage"></a></h2>
-<p>
- L'homepage di <code>calcurse</code> è
-</p>
-<pre>http://culot.org/calcurse</pre>
-
-<h2>9.2 Mailing list degli annunci di <code>calcurse</code><a name="links_list"></a></h2>
-<p>
- Se siete interessati al progetto e volete ricevere gli annunci
- relativi ai rilasci delle nuove versioni (o all'inserimento di nuove
- funzionalità) potete iscrivervi alla mailing list degli annunci di
- <code>calcurse</code>.
-</p>
-<p>
- Per iscriversi alla lista inviate un messaggio
- all'indirizzo <span class="emp">calcurse-announce .at. culot
- .dot. org</span> con "subscribe" nel soggetto.
-</p>
-
-<h2>9.3 Feed rss di <code>calcurse</code><a name="links_rss"></a></h2>
-<p>
- Un'altra possibilità per ricevere questi annunci è l'iscrizione al
- feed RSS all'indirizzo:
-</p>
-<pre>http://culot.org/calcurse/news_rss.xml</pre>
-<p>
- Questo feed viene aggiornato ogni volta viene pubblicata una nuova
- versione con la descrizione delle funzionalità aggiunte.
-</p>
-
-<h2><div class="todo">9.4 Other links</div><a name="links_others"></a></h2>
-<div class="todo">
-<p>
- You may want to look at the ical format specification (rfc2445) at:
- <pre>http://tools.ietf.org/html/rfc2445</pre>
-<p>
- The pcal project page can be found at:
- <pre>http://pcal.sourceforge.net/</pre>
-</div>
-
-<h1>10. Ringraziamenti<a name="thanks"></a></h1>
-<p>
- &Egrave; giunto il momento per ringraziare le persone senza le quali
- questo programma non esisterebbe. Questa è la lista:
- <ul>
- <li>
- Alex per le sue patch, per il suo aiuto e consigli per la
- programmazione in <code>C</code>
- </li>
- <li>
- Gwen per il testing e per i consigli in generale sulle migliorie
- da apportare a <code>calcurse</code>
- </li>
- <li>
- Herbert per aver impacchettato <code>calcurse</code> per FreeBSD
- </li>
- <li>
- Zul per aver impacchettato <code>calcurse</code> per NetBSD
- </li>
- <li>
- Wain, Steffen e Ronald per aver
- impacchettato <code>calcurse</code> per Archlinux
- </li>
- <li>
- Kevin, Ryan, e fEnIo per aver
- impacchettato <code>calcurse</code> per Debian e Ubuntu
- </li>
- <li>
- Pascal per aver impacchettato <code>calcurse</code> per
- Slackware
- </li>
- <li>
- Alexandre e Markus per aver impacchettato <code>calcurse</code>
- per Mac OsX e Darwin
- </li>
- <li>
- Igor per aver impacchettato <code>calcurse</code> per ALT Linux
- </li>
- <li>
- Joel per il suo script calendar che ha inspirato la vista a
- calendario per <code>calcurse</code>
- </li>
- <li>
- Michael Schulz e Chris M. per la traduzione in tedesco
- di <code>calcurse</code> e del manuale
- </li>
- <li>
- Jose Lopez per la traduzione in spagnolo
- di <code>calcurse</code> e del manuale
- </li>
- <li>
- Neil Williams per la traduzione inglese
- </li>
- <li>
- Tony per la sua patch che ha contribuito a migliorare la
- funzione recur_item_inday()
- <span class="todo">, and for implementing the date format configuration options</span>
- </li>
- <li>
- Jeremy Roon per la traduzione olandese
- </li>
- <li>
- Leandro Noferini per la traduzione italiana
- </li>
- <li><div class="todo">Erik Saule for its patch implementing the '-N', '-s', '-S', '-r' and '-D' flags</div></li>
- <li>
- le persone che hanno scritto software che mi piace e che
- mi ha inspirato, e specialmente:
- <ul>
- <li>
- <code>vim</code> per i tasti di movimento
- </li>
- <li>
- <code>orpheus</code> e <code>abook</code> per la
- documentazione
- </li>
- <li>
- <code>pine</code> e <code>aptitude</code> per l'interfaccia
- utente testuale
- </li>
- <li><span class="todo"><code>tmux</code> for coding style</span></li>
- </ul>
- </li>
- </ul>
-</p>
-<p>
- Ed infine ancora molti ringraziamenti a tutti gli utenti
- di <code>calcurse</code> che mi hanno inviato i loro commenti.
-</p>
-
-<div class="footer">
- Copyright &copy; 2004-2010 Fr&eacute;d&eacute;ric Culot<br>
- Calcurse version 2.8 - Last change: March 29, 2010<br>
-</div>
-</div>
-
-</body>
-</html>
diff --git a/doc/manual_nl.html b/doc/manual_nl.html
deleted file mode 100644
index 87e8fa1..0000000
--- a/doc/manual_nl.html
+++ /dev/null
@@ -1,1350 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//NL">
-<!--
-/*
- * $calcurse: manual_nl.html,v 1.21 2010/03/29 18:18:04 culot Exp $
- *
- * Copyright (c) 2004-2010 Frederic Culot <frederic@culot.org>
- * All rights reserved.
- *
- * Redistribution and use in source and binary forms, with or without
- * modification, are permitted provided that the following conditions
- * are met:
- *
- * - Redistributions of source code must retain the above
- * copyright notice, this list of conditions and the
- * following disclaimer.
- *
- * - Redistributions in binary form must reproduce the above
- * copyright notice, this list of conditions and the
- * following disclaimer in the documentation and/or other
- * materials provided with the distribution.
- *
- * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
- * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- *
- */
--->
-
-<html>
-<head>
-<title>CALCURSE documentatie</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css" media="all">
- @import url(manual.css);
-</style>
-</head>
-<body>
-
-<div id="mainContent">
-
-<h1 id="title">
-<span class="main">CALCURSE - tekst-gebaseerde organizer</span></h1>
-
-<div class="warn">
-<h1>Abstract</h1> Deze handleiding beschrijft de functionaliteit van calcurse
-en hoe die te gebruiken. Als eerste wordt de installatie vanaf de broncode
-beschreven, samen met de commandoregel-argumenten. Daarna, wordt de interface
-met alle instellingen die de werking van <code>calcurse</code> wijzigen,
-besproken. Als laatste wordt zowel de procedure van het melden van fouten in
-<code>calcurse</code> uitgelegd, alsook de manier waarop men kan meehelpen om
-<code>calcurse</code> te verbeteren.
-</div>
-
-<div id="toc">
-<h1>Inhoudsopgave</h1>
-<ul>
- <li><a href="#intro">1. Introductie</a></li>
- <li><a href="#overview">2. Overzicht</a>
- <ul>
- <li><a href="#overview_history">2.1 Inleiding</a></li>
- <li><a href="#overview_features">2.2 Belangrijke kenmerken</a></li>
- </ul></li>
- <li><a href="#install">3. Installatie</a>
- <ul>
- <li><a href="#install_requirements">3.1 Afhankelijkheden</a>
- <ul>
- <li><a href="#install_requirements_ncurses">3.1.1 <code>ncurses</code> bibliotheek</a></li>
- <li><a href="#install_requirements_gettext">3.1.2 <code>gettext</code> bibliotheek</a></li>
- </ul></li>
- <li><a href="#install_process">3.2 Installatieprocedure</a></li>
- </ul></li>
- <li><a href="#basics">4. <code>calcurse</code> basis</a>
- <ul>
- <li><a href="#basics_invocation">4.1 Calcurse starten</a>
- <ul>
- <li><a href="#basics_invocation_commandline">4.1.1 Commandoregel-opties</a></li>
- <li><a href="#basics_invocation_variable">4.1.2 Omgevingsvariabele voor i18n</a></li>
- <li><a href="#basics_invocation_environment">4.1.3 Andere omgevingsvariabelen</a></li>
- </ul></li>
- <li><a href="#basics_interface">4.2 Gebruikers-interface</a>
- <ul>
- <li><a href="#basics_interface_noninteractive">4.2.1 Niet-interactieve modus</a></li>
- <li><a href="#basics_interface_interactive">4.2.2 Interactieve modus</a></li>
- </ul></li>
- <li><a href="#basics_daemon"><span class="todo">4.3 Background mode</span></a></li>
- <li><a href="#basics_files">4.4 <code>calcurse</code> bestanden</a></li>
- <li><a href="#basics_import_export">4.5 Import/Export mogelijkheden</a>
- <ul>
- <li><a href="#basics_import">4.5.1 Importeren</a></li>
- <li><a href="#basics_export">4.5.2 Exporteren</a></li>
- </ul></li>
- <li><a href="#basics_help">4.6 Online hulp</a></li>
- </ul></li>
- <li><a href="#options">5. Opties</a>
- <ul>
- <li><a href="#options_general">5.1 Algemene opties</a></li>
- <li><a href="#options_keys"><span class="todo">5.2 Key bindings</span></a>
- <li><a href="#options_colors">5.3 Kleurenschema's</a></li>
- <li><a href="#options_layout">5.4 Layout configuratie</a></li>
- <li><a href="#options_sidebar"><span class="todo">5.5 Sidebar configuration</span></a></li>
- <li><a href="#options_notify">5.6 Informatiebalk instellingen</a></li>
- </ul></li>
- <li><a href="#known_bugs">6. Bekende bugs</a></li>
- <li><a href="#bugs">7. Rapporteren bugs en aanmerkingen</a></li>
- <li><a href="#contribute">8. Hoe kan ik mee helpen?</a>
- <ul>
- <li><a href="#contribute_documentation">8.1 Vertalen van documentatie</a></li>
- <li><a href="#contribute_i18n">8.2 <code>calcurse</code> i18n</a>
- <ul>
- <li><a href="#contribute_i18n_overview">8.2.1 Overzicht</a></li>
- <li><a href="#contribute_i18n_translator">8.2.2 Vertaal stappen</a></li>
- <li><a href="#contribute_i18n_po-files">8.2.3 Po-bestanden</a></li>
- </ul></li>
- </ul></li>
- <li><a href="#links">9. Links</a>
- <ul>
- <li><a href="#links_homepage">9.1 <code>Calcurse</code> homepage</a></li>
- <li><a href="#links_list">9.2 <code>Calcurse</code> nieuws lijst</a></li>
- <li><a href="#links_rss">9.3 <code>Calcurse</code> RSS feed</a></li>
- <li><a href="#links_others">9.4 Links</a></li>
- </ul></li>
- <li><a href="#thanks">10. Dankwoord</a></li>
-</ul>
-</div>
-
-<h1>1. Introductie<a name="intro"></a></h1>
-<p>
- <code>calcurse</code> is een tekstgebaseerde kalender en planner. Het
- helpt om overzicht te houden over afspraken en alledaagse taken. Een
- aan te passen meldingssysteem herinnert de gebruiker aan komende
- deadlines, en de curses-gebaseerde interface kan aangepast worden aan
- de wensen van de gebruiker. Alle commando's zijn gedocumenteerd in een
- online hulpsysteem.
-</p>
-
-<h1>2. Overzicht<a name="overview"></a></h1>
-<h2>2.1 Inleiding<a name="overview_history"></a></h2>
-<p>
- Ik begon te denken aan dit project toen ik bijna afgestudeerd was in
- de astrofysica... Het werd moeilijk om alles georganiseerd te houden
- en ik had behoefte aan een goed hulpmiddel om me daar bij te helpen.
- ;)
-</p>
-<p>
- Ik hou van programma's die gebruik maken van de tekst-interface, omdat
- ze simpel, snel, overdraagbaar en efficient zijn, dus ik dacht eraan
- om een simpele tekst-interface kalender te programmeren. Ook wilde ik
- graag verder leren programmeren in de programmeertaal <code>C</code>,
- welke ik alleen in mijn vooropleiding had gebruikt. Zodoende zou ik
- dus leren programmeren in <code>C</code>, en mijn zaakjes voor elkaar
- krijgen.
-</p>
-<p>
- Helaas studeerde ik af voordat ik klaar was met <code>calcurse</code>,
- maar ik was nog steeds geboeid door het project, in de hoop dat het
- ook voor anderen een handig programma zou zijn. En hier is dan het
- resultaat...
-</p>
-<p>
- Waarom de naam 'calcurse', vraagt u zich af? Het is simpelweg een
- samentrekking van 'CALendar' en 'nCURSEs', de naam van de bibliotheek
- die gebruikt wordt om de gebruikers-interface aan te sturen.
-</p>
-
-<h2>2.2 Belangrijke kenmerken<a name="overview_features"></a></h2>
-<p>
- <code>Calcurse</code> is multi-platform, neemt weinig systeembronnen
- in beslag, en is snel en betrouwbaar. Het moet gebruikt worden binnen
- een console of terminal, lokaal of op een aparte computer door middel
- van een connectie met een programma zoals ssh.
-</p>
-<p>
- <code>Calcurse</code> kan op twee verschillende manieren gebruikt
- worden: interactieve of niet-interactieve modus. De eerste modus zorgt
- er voor dat men zijn eigen agenda bijna overal kan bekijken, dankzij
- de tekst-gebaseerde interface. Met de tweede modus, kan men makkelijk
- met geheugensteuntjes werken door <code>calcurse</code> met de juiste
- commandoregel-opties in een cron tab of shell init script te
- zetten.
-</p>
-<p>
- Bovendien, is <code>calcurse</code> geschreven met de
- eindgebruiker in gedachten, en is dus zo gebruikersvriendelijk
- mogelijk. Dit betekent dat er een volledige hulp-functie is, en de
- beschikbare acties altijd op het scherm staan in de statusbalk. De
- gebruikers-interface is ook aan te passen, en men kan tussen
- verschillende kleurenschema's en layout-combinaties kiezen.
-<span class="todo">Key bindings are also configurable, to fit everyone's needs.</span>
- En als laatste, is er het configurabele meldingssysteem, dat gebruikers
- verwittigt van op handen zijnde afspraken.
-<span class="todo">The reminders are sent even if the user's interface
-is not running, as calcurse is able to run in background.</span>
-</p>
-
-<h1>3. Installatie<a name="install"></a></h1>
-<h2>3.1 Benodigheden<a name="install_requirements"></a></h2>
-<h3>3.1.1 <code>ncurses</code> bibliotheek<a name="install_requirements_ncurses"></a></h3>
-<p>
- <code>Calcurse</code> maakt alleen gebruik van een <code>C</code>
- compiler, zoals <code>cc</code> of <code>gcc</code>, en de
- <code>ncurses</code> bibliotheek. Het is onwaarschijnlijk dat er nog
- geen juiste versie van <code>ncurses</code> op uw computer staat, maar
- indien het niet zo is, is het via de volgende url te vinden:</p>
- <pre>http://ftp.gnu.org/pub/gnu/ncurses/</pre>
-
-<div class="todo">
- <p class="rq"><span class="valorize">Note:</span>
- It is also possible to link <code>calcurse</code> against the
- <code>ncursesw</code> library (ncurses with support for unicode).
- However, UTF-8 is not yet supported by <code>calcurse</code>.</p>
-</div>
-
-<h3>3.1.2 <code>gettext</code> bibliotheek<a name="install_requirements_gettext"></a></h3>
-<p>
- <code>calcurse</code> ondersteunt internationalisatie
- (<span class="emp">i18n</span>
- genoemd hierna) door middel van <code>gettext</code>. Dit betekent
- dat <code>calcurse</code> berichten in verschillende talen kan
- weergeven, indien gecompileerd met native language support
- (<span class="emp">NLS</span>).
-</p>
-<p>
- <span class="emp">NLS</span> is optioneel en als het niet nodig is,
- kan het uitgeschakeld worden. Dit wordt gedaan door
- <code>--disable-nls</code> als optie mee te geven aan
- <code>configure</code> (zie sectie <a
- href="#install_process">Installatieprocedure</a>). Om te zien of
- gettext op het systeem aanwezig is, kan er gezocht worden naar het
- <code>libintl.h</code> header bestand b.v.:</p>
- <pre>locate libintl.h</pre>
-<p>
- Indien het header bestand niet gevonden wordt, kan het via de volgende
- url verkregen worden:</p>
- <pre>http://ftp.gnu.org/pub/gnu/gettext/</pre>
-<p>
- <p class="rq"><span class="valorize">Noot:</span>
- Zelfs als <code>libintl.h</code> gevonden wordt, is het
- misschien beter om de lokatie van het bestand tijdens de <a
- href="#install_process">Installatieprocedure</a>) mee te geven aan
- <code>configure</code> door middel van
- <code>--with-libintl-prefix</code>. Het zou kunnen, dat
- <code>configure</code> de bibliotheek niet kan vinden, als het op een
- niet-gangbare plaats ge&iuml;nstalleerd is.
-</p>
-
-<h2>3.2 Installatieprocedure<a name="install_process"></a></h2>
-<p>
- Als eerste moet het volgende archief uitgepakt worden met gunzip en
- untar:</p>
- <pre>tar zxvf calcurse-2.8.tar.gz</pre>
-<p>
- Zodra de benodigde pakketten ge&iuml;nstalleerd zijn en het archief
- uitgepakt is, is de installatieprocedure vrij simpel, via de
- standaard drie stappen:
- <ol>
- <li><code>./configure</code></li>
- <li><code>make</code></li>
- <li><code>make install</code> (mogelijk root privileges nodig)</li>
- </ol>
-</p>
-<p>
- Typ <code>./configure --help</code> om een lijst te zien van mogelijke
- opties.
-</p>
-
-<h1>4. <code>calcurse</code> basis<a name="basics"></a></h1>
-<h2>4.1 Het aanroepen van calcurse<a name="basics_invocation"></a></h2>
-<h3>4.1.1 Commandoregel-opties<a name="basics_invocation_commandline"></a></h3>
-<p>
- <code>calcurse</code> accepteert de volgende opties op de
- commandoregel (zowel korte en lange opties worden ondersteund):</p>
- <p>
-
- <dl>
- <dt><code>-a, --appointment</code></dt>
- <dd>
- Geeft de afspraken van vandaag weer en verlaat het programma.
- <p class="rq"><span class="valorise">Noot:</span>
- de te gebruiken kalender waaruit de afspraken gelezen
- moeten worden, kan gekozen worden met de '-c' vlag.</p>
- </dd>
- <dt><code>-c &lt;file&gt;, --calendar &lt;file&gt;</code></dt>
- <dd>
- Kies het te gebruiken kalenderbestand. De standaardkalender is
- <code>~/.calcurse/apts</code> (zie sectie <a
- href="#basics_files"><code>calcurse</code> bestanden</a>).
- </dd>
- <dt><code>-d &lt;date|num&gt;, --day &lt;date|num&gt;</code></dt>
- <dd>
- Geef de afspraken weer van de gegeven datum of van het gegeven aantal
- komende dagen, afhankelijk van de opties. Er zijn twee mogelijkheden:
- <ul>
- <li>een datum <span class="todo">(possible formats described below).</span></li>
- <li>een nummer 'n'.</li>
- </ul>
- In het eerste geval, wordt een lijst met afspraken voor de gegeven
- datum weergegeven, terwijl in het tweede geval, een lijst met
- afspraken voor de komende 'n' aantal dagen wordt weergegeven.
- Als je bijvoorbeeld <code>calcurse -d 3</code> intypt, zullen de
- afpraken voor vandaag, morgen en overmorgen worden weergegeven.
- <div class="todo">
- Possible formats for specifying the date are defined inside the
- general configuration menu (see
- <a href="#options_general">General options</a>), using the
- <code>input_datefmt</code> variable.
- </div>
- <p class="rq"><span class="valorise">Noot:</span>
- Net zoals bij de '-a' vlag, kan de te gebruiken kalender
- worden gekozen met de '-c' vlag.</p>
- </dd>
- <dt><code>-D &lt;dir&gt;, --directory &lt;dir&gt;</code></dt>
- <dd>
- Specificeer de te gebruiken directory. Deze optie kan niet samen
- met -c gebruikt worden. Als geen directory is gegeven, wordt
- standaard <code>'~/.calcurse/'</code> gebruikt.
- </dd>
- <dt><code>-h, --help</code></dt>
- <dd>
- Geeft een korte hulptekst weer, met de ondersteunde
- commandoregel-opties en verlaat het programma.
- </dd>
- <dt><code>-i &lt;file&gt;, --import &lt;file&gt;</code></dt>
- <dd>
- Importeer de icalender-data uit <code>file</code>.
- </dd>
- <dt><code>-n, --next</code></dt>
- <dd>
- Geeft de eerstvolgende afspraak weer die binnen 24 uur valt en verlaat
- het programma.
- De weergegeven tijd is het aantal uren en minuten tot de afspraak.
- <p class="rq"><span class="valorise">Noot:</span>
- de te gebruiken kalender met de afspraken, kan gekozen
- worden met de '-c' vlag.</p>
- </dd>
- <dt><code>-N, --note</code></dt>
- <dd>
- Indien gebruikt met de '-a' of 't' vlag, wordt ook de inhoud van de
- gerelateerde noot weergegeven.
- </dd>
- <dt><code>-r[num], --range[=num]</code></dt>
- <dd>
- Geeft de gebeurtenissen en afspraken voor num aantal dagen weer.
- Als num niet is gegeven wordt een dag gebruikt.
- </dd>
- <dt><code>-s[date], --startday[=date]</code></dt>
- <dd>
- Print gebeurtenissen en afspraken voor datum en stopt. Als er geen
- datum wordt gegeven, wordt de huidige datum gebruikt.
- </dd>
- <dt><code>-S&lt;regex&gt;, --search=&lt;regex&gt;</code></dt>
- <dd>
- <div class="todo">
- When used with the '-a', '-d', '-r', '-s', or '-t' flag,
- print only the items having a description that matches the given
- regular expression.
- </div>
- </dd>
- <dt><code>--status</code></dt>
- <dd>
- <div class="todo">
- Display the status of running instances of calcurse. If
- calcurse is running, this will tell if the interactive
- mode was launched or if calcurse is running in background.
- The process pid will also be indicated.
- </div>
- </dd>
- <dt><code>-t[num], --todo[=num]</code></dt>
- <dd>
- Geef de 'todo' lijst weer en verlaat het programma. Als het optionele
- nummer <code>num</code> wordt meegegeven, zullen alleen de todo's met
- de prioriteit gelijk aan <code>num</code> worden weergegeven.
- <div class="todo">
- The priority number must be between 1 (highest) and 9 (lowest). It is also possible
- to specify '0' for the priority, in which case only completed tasks will be shown.</p>
- </div>
- </dd>
- <dt><code>-v, --version</code></dt>
- <dd>
- Geeft het versienummer van <code>calcurse</code> weer en verlaat het
- programma.
- </dd>
- <dt><code>-x[format], --export[=format]</code></dt>
- Exporteer data van de gebruiker naar een bepaald formaat.
- Gebeurtenissen, afspraken en taken worden geconverteerd en naar
- stdout gezonden. Er is een keuze uit twee formaten: ical en pcal
- (zie sectie <a href="#links_others">Links</a> beneden). Als het
- optionele argument <code>formaat</code> niet is gegeven, zal het
- ical formaat worden gebruikt.
- <p class="rq"><span class="valorise">Noot:</span>
- Om de data te exporteren naar een bestand, kan men de
- standaard output omleiden met een commando zoals:
- <code>$ calcurse --export > my_data.dat</code></p>
- </dd>
- </dl>
-
-<h3>4.1.2 Omgevingsvariabele voor i18n<a name="basics_invocation_variable"></a></h3>
-<p>
- <code>calcurse</code> kan gecompileerd worden met native language
- support (zie <a
- href="#install_requirements_gettext"><code>gettext</code>
- bibliotheek</a>). Als je berichten wilt zien in je moedertaal, kijk
- dan eerst na of het beschikbaar is door naar het
- <code>po/LINGUAS</code> bestand te kijken. Dit bestand geeft de
- beschikbare talen weer door middel van twee letters. (Voorbeeld,
- <span class="emp">fr</span> duidt frans aan). Indien je je taal niet vindt, zouden we
- het op prijs stellen, als je meehelpt met het vertalen van
- <code>calcurse</code> (zie <a href="#contribute">Hoe kan ik
- helpen?</a>).</p>
-<p>
- Als je taal beschikbaar is, start <code>calcurse</code> met het
- volgende commando:</p>
- <pre>LC_ALL=fr_FR calcurse</pre>
-<p>
- waar <span class="emp">fr_FR</span> de locale naam van dit voorbeeld is, maar
- veranderd moet worden naar de locale van de gewenste taal.</p>
-<p>
- De te gebruiken karakterset zou ook gespecificeerd moeten worden,
- omdat anders in bepaalde gevallen de accenten en dergelijke niet
- correct weergegeven worden. De karakterset wordt gekozen in het begin
- van het po bestand, dat overeenkomt met de gewenste taal. Je kan
- bijvoorbeeld in het fr.po bestand zien dat het gebruik maakt van de
- iso-8859-1 karakterset, dus om <code>calcurse</code> te starten, kan
- het volgende commando worden gebruikt:</p>
- <pre>LC_ALL=fr_FR.ISO8859-1 calcurse</pre>
-
-<h3>4.1.3 Andere omgevingsvariabelen<a name="basics_invocation_environment"></a></h3>
-<p>
- De volgende omgevingsvariabelen bepalen hoe <code>calcurse</code> werkt:</p>
- <dl>
- <dt><code>VISUAL</code></dt>
- <dd>Specificeert welke externe editor wordt gebruikt voor het
- schrijven van een noot.
- </dd>
- <dt><code>EDITOR</code></dt>
- <dd>als de <code>VISUAL</code> omgevingsvariabele niet is ingesteld,
- zal de inhoud van <code>EDITOR</code> worden gebruikt voor het
- bepalen van de externe editor. Als beide variabelen niet zijn
- ingesteld zal <code>/usr/bin/vi</code> worden gebruikt.
- </dd>
- <dt><code>PAGER</code></dt>
- <dd>Specificeert met welk programma een noot wordt weergegeven.
- Als de variabele leeg is, zal <code>/usr/bin/less</code> gebruikt
- worden.
- </dd>
- </dl>
-
-<h2>4.2 Gebruikers-interface<a name="basics_interface"></a></h2>
-<h3>4.2.1 Niet-interactieve modus<a name="basics_interface_noninteractive"></a></h3>
-<p>
- <code>calcurse</code> wordt in niet-interactieve modus gestart, als
- ten minste een van de volgende opties wordt gebruikt:
- <code>-a</code>, <code>-d</code>, <code>-h</code>, <code>-n</code>,
- <code>-t</code>, <code>-v</code>, <code>-x</code>,
- Dit betekent dat de gewenste informatie wordt getoond, en dat daarna
- <code>calcurse</code> simpelweg wordt verlaten en men weer terug is
- bij de shell prompt.</p>
-<p>
- Op deze manier, kan men een regel zoals <code>'calcurse --todo
- --appointment'</code> in zijn init config bestand zetten, zodat
- bij het inloggen de takenlijst en afspraken van vandaag worden
- weergegeven.</p>
-
-<h3>4.2.2 Interactieve modus<a name="basics_interface_interactive"></a></h3>
-<div class="todo">
- <p class="rq"><span class="valorise">Note:</span>
- Key bindings that are indicated in this manual correspond to
- the default ones, defined when <code>calcurse</code> is launched
- for the first time. If those key bindings do not suit user's needs,
- it is possible to change them within the keys configuration menu
- (see <a href="#options_keys">key bindings</a>).</p>
-</div>
-<p>
- Als <code>calcurse</code> zonder opties of alleen met de
- <code>-c</code> optie wordt aangeroepen, wordt <code>calcurse</code>
- in interactieve modus gestart. In deze modus, wordt er een interface
- getoond, dat drie verschillende panels (panelen) bevat, waartussen je
- kan schakelen door middel van de 'TAB' toets, een notify-bar
- (informatiebalk), en een statusbar (statusbalk) (zie onderstaand
- figuur).</p>
- <pre>
-
- afspraken panel---. .---kalender panel
- | |
- v v
- +------------------------------------++----------------------------+
- | Afspraken || Kalender |
- |------------------------------------||----------------------------|
- | (|) April 6, 2006 || April 2006 |
- | || Ma Di Wo Do Vr Za Zo |
- | || 1 2 |
- | || 3 4 5 6 7 8 9 |
- | || 10 11 12 13 14 15 16 |
- | || 17 18 19 20 21 22 23 |
- | || 24 25 26 27 28 29 30 |
- | || |
- | |+----------------------------+
- | |+----------------------------+
- | || Taken | taken
- | ||----------------------------| panel
- | || | |
- | || | |
- | || |&lt;--.
- | || |
- +------------------------------------++----------------------------+
- |---[ Ma 2006-11-22 | 10:11:43 ]---(apts)----&gt; 01:20 :: lunch &lt;---|&lt;--.
- +------------------------------------------------------------------+ informatie
- | ? Help R Herteken H/L -/+1 Dag G Ga Naar C Config | balk
- | Q Einde S Opslaan J/K -/+1 Week Tab Schakelen |&lt;-.
- +------------------------------------------------------------------+ |
- |
- statusbalk
-
- </pre>
-<p>
- Het eerste panel geeft een kalender weer, die het mogelijk maakt om
- een bepaalde datum te kiezen. Het tweede panel bevat de afspraken en
- gebeurtenissen van die dag. Het laatste panel bevat een lijst met
- taken (todo's) die nog moeten gebeuren, maar niet aan een bepaalde dag
- zijn toegewezen.</p>
-<div class="todo">
-<p>
- Depending on the selected view, the calendar could either display
- a monthly (default as shown in previous figure) or weekly view.
- The weekly view would look like the following:</p>
- <pre>
-
-+------------------------------------+
-| Calendar |
-|----------------------------(# 13)--|
-| Mon Tue Wed Thu Fri Sat Sun |
-| 29 30 31 01 02 03 04 |
-| <----+-- slice 1: 00:00 to 04:00 AM
-| -- -- -- -- -- -- |
-| <----+-- slice 2: 04:00 to 08:00 AM
-| -- -- -- -- -- -- |
-| <----+-- slice 3: 08:00 to 12:00 AM
-| - -- -- -- -- -- -- - <-+-- midday
-| <----+-- slice 4: 12:00 to 04:00 PM
-| -- -- -- -- -- -- |
-| <----+-- slice 5: 04:00 to 08:00 PM
-| -- -- -- -- -- -- |
-| <----+-- slice 6: 08:00 to 12:00 PM
-+------------------------------------+
-
- </pre>
-<p>
- The current week number is displayed on the top-right side of the panel
- (<span class="emp"># 13</span> meaning it is the 13th week of the year
- in the above example). The seven days of the current week are displayed
- in column. Each day is divided into slices of 4 hours each (6 slices in
- total, see figure above). A slice will appear in a different color if
- an appointment falls into the corresponding time-slot.
-</p>
-</div>
-
-<p>
- In het afspraken panel, staat vlak voor de datum het <span class="emp">'(|)'</span>
- teken. Dit geeft de huidige fase van de maan aan. Afhankelijk van de
- fase, kunnen de volgende tekens worden gezien:
- <dl class="compact">
- <dt>'<code> |) </code>':</dt>
- <dd>eerste kwartier</dd>
- <dt>'<code> (|) </code>':</dt>
- <dd>volle maan</dd>
- <dt>'<code> (| </code>':</dt>
- <dd>laatste kwartier</dd>
- <dt>'<code> | </code>':</dt>
- <dd>nieuwe maan</dd>
- <dt>geen teken:</dt>
- <dd>huidige fase van de maan correspondeert met geen
- van bovenstaande fases</dd>
- </dl>
- </p>
- <p>
- Aan de onderkant van het scherm is de statusbalk, die de mogelijke
- acties en de daarbij horende toetscombinaties weergeeft.</p>
- <p>
- Net boven de statusbalk is de informatiebalk, die van links naar
- rechts het volgende toont: de huidige datum, de huidige tijd, het
- kalenderbestand dat in gebruik is (apts in het bovenstaand voorbeeld,
- dat het standaardkalender bestand is, zie de volgende sectie), en de
- volgende afspraak binnen 24 uur. In het voorbeeld staat dat het over
- een uur en twintig minuten tijd is voor de lunch.</p>
- <p>
- <p class="rq"><span class="valorise">Noot:</span>
- Voor sommige acties, zoals het bewerken of toevoegen van
- een item, is het nodig dat er tekst wordt ingevoerd. Dit wordt gedaan
- met de hulp van de ingebouwde editor.</p>
- <p>
- Als een regel met tekst langer is dan de breedte van het scherm, wordt
- er in de editor een '&gt;', '*', or '&lt;' karakter getoond in de
- laatste kolom, wat aanduid dat er respectievelijk meer karakters
- achter, voor en achter, of voor de huidige positie staan. De
- tekstregel schuift horizontaal mee als het nodig is.</p>
- <p>
- Sommige bewerkingscommando's zijn gebonden aan speciale controle
- karakters. Hierna zijn de beschikbare bewerkingscommando's weergegeven
- ('^' staat voor de control-toets):
- <dl class="compact">
- <dt><code>^a</code>:</dt>
- <dd>verplaats de cursor naar het begin van de invoerregel</dd>
- <dt><code>^b</code>:</dt>
- <dd>verplaats de cursor terug</dd>
- <dt><code>^d</code>:</dt>
- <dd>verwijder een karakter voorwaarts</dd>
- <dt><code>^e</code>:</dt>
- <dd>verplaats de cursor naar het einde van de invoerregel</dd>
- <dt><code>^f</code>:</dt>
- <dd>verplaats de cursor voorwaarts</dd>
- <dt><code>^h</code>:</dt>
- <dd>verwijder een karakter terug</dd>
- <dt><code>^k</code>:</dt>
- <dd>verwijder de invoer vanaf de cursor naar het einde van
- de regel</dd>
- <dt><code>ESCAPE</code>:</dt>
- <dd>annuleert het bewerken</dd>
- </dl>
-</p>
-
-<div class="todo">
-<h2>4.3 Background mode<a name="basics_daemon"></a></h2>
-
-<p>When the daemon mode is enabled in the notification configuration menu
-(see <a href="#options_notify">Notify-bar settings</a>), <code>calcurse</code> will stay
-in background when the user interface is not running. In background mode,
-<code>calcurse</code> checks for upcoming appointments and runs the user-defined
-notification command when necessary. When the user interface is started again,
-the daemon automatically stops.</p>
-
-<p><code>calcurse</code> background activity can be logged (set the
-<code>notify-daemon_log</code> variable in the notification configuration
-<a href="#options_notify">menu</a>), and in that case, information about the daemon
-start and stop time, reminders' command launch time, signals received... will be written
-in the <code>daemon.log</code> file (see section <a href="#basics_files">files</a>).</p>
-
-<p>
-Using the <code>--status</code> command line option (see section
-<a href="#basics_invocation_commandline">Command line arguments</a>),
-one can know if <code>calcurse</code> is currently running in background or not.
-If the daemon is running, a message like the following one will be displayed (the pid of
-the daemon process will be shown):
-<pre>calcurse is running in background (pid 14536)</pre>
-
-<p class="rq"><span class="valorise">Note:</span>
-To stop the daemon, just send the <code>TERM</code> signal to it, using a command such as:
-<code>'kill daemon_pid'</code>, where <span class="emp">daemon_pid</span> is the process id
-of the daemon (14536 in the above example).
-</p>
-</div>
-
-<h2>4.4 <code>calcurse</code> bestanden<a name="basics_files"></a></h2>
-<p>
- De volgende structuur wordt in je <code>$HOME</code> directory
- aangemaakt, of in de door -D aangeduide directory)
- als <code>calcurse</code> voor de eerste keer wordt gestart:</p>
- <pre>
-$HOME/.calcurse/
- |___notes/
- |___conf
- |___keys
- |___apts
- |___todo
- </pre>
- <dl class="compact">
- <dt><code>notes/</code>:</dt>
- <dd>deze subdirectory bevat de beschrijvingen van de noten die
- zijn bijgesloten bij afspraken, gebeurtenissen of taken. Voor
- elke noot wordt er een tekstbestand aangemaakt. Dit bestand
- heeft een unieke naam dat bepaald wordt door mkstemp(3). Deze
- naam heeft echter geen enkel verband met de beschrijving van
- het corresponderende item.</dd>
- <dt><code>conf</code>:</dt>
- <dd>bevat de configuratie van de gebruiker.</dd>
- <dt><code>keys</code>:</dt>
- <dd><span class="todo">this file contains the user-defined key bindings</span></dd>
- <dt><code>apts</code>:</dt
- <dd>bevat alle gebeurtenissen en afspraken van de gebruiker.</dd>
- <dt><code>todo</code>:</dt>
- <dd>bevat de takenlijst.</dd>
- </dl>
-
-<div class="todo">
- <p class="rq"><span class="valorise">Note:</span>
- If the logging of calcurse daemon activity was set in the notification
- configuration menu, the extra file <code>daemon.log</code> will appear
- in calcurse data directory. This file contains logs about calcurse activity
- when running in background.
- </p>
-</div>
-
-<h2>4.5 Import/Export mogelijkheden<a name="basics_import_export"></a></h2>
-<p>
- De import en export mogelijkheden van <code>calcurse</code> zijn als
- volgt:
-</p>
-
-<h3>4.5.1 Import<a name="basics_import"></a></h3>
-<p>
- Data in icalender formaat, zoals beschrevein in de rfc2445 specificatie
- (zie <a href="#links_others">links</a> sectie beneden), kan
- ge&iuml;mporteerd worden in calcurse. De Calcurse ical parser is op
- versie 2.0 van deze specificatie gebaseerd. Van nu af aan echter, zal
- alleen een subset worden ondersteund.
-</p>
-<p>
- Hier volgt het icalendar formaat zoals calcurse het gebruikt:
- <ul>
- <li><code>VTODO</code> items:<br>
- "PRIORITY", "VALARM", "SUMMARY", "DESCRIPTION"</li>
- <li><code>VEVENT</code> items:<br>
- "DTSTART", "DTEND", "DURATION", "RRULE", "EXDATE", "VALARM", "SUMMARY",
- "DESCRIPTION"</li>
- </ul>
-</p>
-<p>
- Het icalender "DESCRIPTION"-veld (omschrijving) zal worden geconverteerd naar
- het eigen formaat van calcurse, door het toevoegen van een noot. Als
- een "VALARM"-veld is gevonden, zal het worden gemarkeerd als belangrijk
- en zal de gebruiker een melding krijgen (alleen bij afspraken).
-</p>
-<p>
- Hier zijn de velden die niet worden gebruikt:
- <ul>
- <li>negatief tijdsduur zal niet herkend worden (item wordt
- overgeslagen)
- </li> <li>sommige herhalings frequenties worden niet
- herkend:<br>
- "SECONDLY" / "MINUTELY" / "HOURLY"</li>
- <li>Sommige herhalingssleutelwoorden worden niet herkend (degene
- die starten met 'BY'):<br>
- "BYSECOND" / "BYMINUTE" / "BYHOUR" / "BYDAY" / "BYMONTHDAY"<br>
- "BYYEARDAY" / "BYWEEKNO" / "BYMONTH" / "BYSETPOS"<br>
- plus "WKST"</li>
- <li>het exceptie herhalingssleutelwoord "EXRULE" wordt niet
- herkend</li>
- <li>er wordt geen rekening gehouden met timezones</li>
- </ul>
-</p>
-
-<h3>4.5.2 Export<a name="basics_export"></a></h3>
-<p>
- Twee export formaten zijn voorradig: <code>ical</code> en
- <code>pcal</code> (zie sectie <a href="#links_others">Links</a> beneden
- voor meer informatie over deze formaten).
-</p>
-
-<h2>4.6 Online hulp<a name="basics_help"></a></h2>
-<p>
- De ingebouwde hulp kan waar nodig aangeroepen worden door middel van
- de '?' toets. Tijdens het gebruik van de hulpschermen kan een
- specifiek commando opgevraagd worden door op de toetscombinatie te
- drukken van dat commando.
-</p>
-
-<h1>5. Opties<a name="options"></a></h1>
-<p>
- Alle opties van <code>calcurse</code> zijn aan te passen vanuit het
- Configuratie menu. Als je op 'C' drukt, kom je in een submenu met 5
- keuzes: Druk opnieuw 'C' om naar de configuratie van de
- kleurenschema's te gaan, druk op 'L' om naar de hoofdindeling van
- <code>calcurse</code> te gaan (in andere woorden, waar de 3 panels op
- het scherm komen), druk op 'G' om een aantal algemene opties in te
- stellen,
- <span class="todo">pressing 'K' opens the key bindings configuration
- menu,</span>
- en als laatste kan de informatiebalk worden aangepast worden
- met de toets 'N'.
-</p>
-
-<h2>5.1 Algemene opties<a name="options_general"></a></h2>
-<p>
- Met de volgende opties kan <code>calcurse</code> naar wens ingesteld
- worden:</p>
- <dl>
- <dt><code>automatisch_opslaan</code>
- (standaard: <span class="emp">ja</span>)</dt>
- <dd>Door deze optie wordt de data van de gebruiker automatisch opgeslagen
- (indien ingesteld op <span class="emp">ja</span>) bij het
- afsluiten.
- <p class="rq"><span class="valorise">Let op:</span>
- De data wordt niet automatisch opgeslagen als
- <code>automatisch_opslaan</code> ingesteld is op <span class="emp">nee</span>. Dit
- betekent dat de gebruiker op 'S' moet drukken om de gewijzigde data te
- bewaren.</p>
- </dd>
-
- <dt><code><span class="todo">periodic_save</code>
- (default: <span class="emp">0</span>)</span></dt>
- <dd><span class="todo">If different from '0', user's data will be automatically
- saved every <span class="emp">periodic_save</span> minutes.
- When an automatic save is performed, two asterisks
- (i.e. '<code>**</code>') will appear on the top right-hand side
- of the screen).</span>
- </dd>
-
- <dt><code>einde_bevestigen</code>
- (standaard: <span class="emp">ja</span>)</dt>
- <dd>Bij het be&euml;indigen van <code>calcurse</code>, zal er om een
- bevestiging worden gevraagd, als de optie op <span class="emp">ja</span> is ingesteld.
- Zoniet, dan zal <code>calcurse</code> zonder bevestigingsvraag
- eindigen, als er op 'Q' wordt gedrukt.
- </dd>
- <dt><code>bevestig_verwijderen</code>
- (standaard: <span class="emp">ja</span>)</dt>
- <dd>Als deze optie op <span class="emp">ja</span> is ingesteld, zal er om een bevestiging
- gevraagd worden voor het wissen van een item door middel van een
- toetsdruk op 'D' (dit kan een <span class="emp">todo</span>, <span class="emp">afspraak</span>, of
- <span class="emp">gebeurtenis</span> zijn. Anders zal er geen bevestiging nodig zijn
- voor het wissen van een item.
- </dd>
- <dt><code>overslaan_systeem_dialoog</code>
- (standaard: <span class="emp">nee</span>)</dt>
- <dd>Als deze optie ingesteld is op <span class="emp">ja</span> zullen de systeem dialogen
- gerelateerd aan het opslaan en laden van data worden overgeslagen. Dit
- zorgt ervoor dat <code>calcurse</code> sneller opstart en afsluit.
- </dd>
- <dt><code>overslaan_progressie_balk</code>
- (standaard: <span class="emp">nee</span>)</dt>
- <dd>Indien ingesteld op <span class="emp">ja</span>, zal deze optie er voor zorgen dat de
- progressie balk, die normaal gesproken getoond wordt bij het opslaan
- van data naar bestand, verdwijnt. Ingesteld op <span class="emp">ja></span>, wordt de
- progressie balk getoond samen met de bestandsnaam. (zie sectie <a
- href="#basics_files"><code>calcurse</code> bestanden</a>).
- </dd>
- <dt><code><span class="todo">calendar_default_view</span></code>
- (default: <span class="emp">0</span>)</dt>
- <dd><span class="todo">If set to <span class="emp">0</span>, the monthly calendar view will be
- displayed by default otherwise it is the weekly view that will be displayed.</span>
- </dd>
- <dt><code>week_begint_op_maandag</code>
- (standaard: <span class="emp">ja</span>)</dt>
- <dd>Er kan gekozen worden tussen maandag en zondag als de eerste dag van
- de week. Als <span class="emp">week_begint_op_maandag</span> ingesteld is op
- <span class="emp">ja</span>, dan zal maandag als eerste staan in het kalender
- overzicht. Anders staat zondag als eerste dag van de week.
- </dd>
-
- <dt><code>output_datefmt</code>
- (standaard: <span class="emp">%D</span>)</dt>
- <dd>Deze optie geeft het te gebruiken formaat aan bij datums in
- niet-interactieve modus. Standaard worden de datums als volgt
- weergegeven: <span class="emp">mm/dd/aa</span>. Het is
- mogelijk om alle mogelijke formaten te zien, door <code>man 3
- strftime</code> in een terminal in te typen.</dd>
- <dt><code>input_datefmt</code>
- (standaard: <span class="emp">1</span>)</dt>
- <dd>Met deze optie wordt het formaat aangeven dat zal worden
- gebruikt om datums in te voern in <span
- class="emp">calcurse</span>. Er zijn <span class="todo">four</span> keuzes: <ol>
- <li>mm/dd/yyyy</li>
- <li>dd/mm/yyyy</li>
- <li>yyyy/mm/dd</li>
- <li>yyyy-mm-dd</li>
- </ol>
- </dd>
- </dl>
-
-<div class="todo">
-<h2>5.2 Key bindings<a name="options_keys"></a></h2>
-<p>
- One can define it's own keybindings within the 'Keys' configuration
- menu. The default keys look like the one used by the <code>vim</code>
- editor, especially the displacement keys. Anyway, within this
- configuration menu, users can redefine all of the keys available from
- within calcurse's user interface.</p>
-<p>
- To define new keybindings, first highlight the action to which it will
- apply. Then, delete the actual key binding if necessary, and add a new
- one. You will then be asked to press the key corresponding to the new
- binding. It is possible to define more than one key binding for a single
- action.</p>
-<p>
- An automatic check is performed to see if the new key binding
- is not already set for another action. In that case, you will be asked
- to choose a different one. Another check is done when exiting from this
- menu, to make sure all possible actions have a key associated with it.</p>
-<p>
- The following keys can be used to define bindings:
- <ul>
- <li>lower-case, upper-case letters and numbers, such as 'a', 'Z', '0'</li>
- <li>CONTROL-key followed by one of the above letters</li>
- <li>escape, horizontal tab, and space keys</li>
- <li>arrow keys (up, down, left, and right)</li>
- <li>'HOME' and 'END' keys</li>
- </ul> </p>
-<p>
- While inside the key configuration menu, an online help is available for
- each one of the available actions. This help briefly describes what the
- highlighted action is used for.</p>
-</div>
-
-<h2>5.3 Kleurenschema's<a name="options_colors"></a></h2>
-<p>
- De kleurenschema's van <code>calcurse</code> zijn aan te passen aan de
- wensen van de gebruiker. Om het standaard schema te wijzigen, zijn er
- in het configuratiescherm de mogelijke opties weergegeven voor voor-
- en achtergrondkleuren. Door met de pijltjes-toetsen of de
- <code>calcurse</code>-toetsen de cursor te verplaatsen, en met 'X' of
- spatie een kleur te selecteren, kan de gebruiker de kleur toegepast
- zien. Het is ook mogelijk om de standaard kleuren van de terminal te
- gebruiken. Selecteer hiervoor de corresponderende optie.
-</p>
-<p>
- De kleuren van de randen, titels, toetshulp, en algemene informatie
- binnen de statusbalk zullen worden aangepast. Er is ook een zwart-wit
- schema, voor terminals die geen kleuren ondersteunen.</p>
- <p class="rq"><span class="valorise">Noot:</span>
- Afhankelijk van het type terminal en van de <code>$TERM</code>
- omgevingsvariabele, is het mogelijk dat kleur wel of niet wordt
- ondersteund. Indien gepoogd wordt de kleuren te veranderen, terwijl de
- terminal geen kleuren ondersteund, zal er een foutbericht
- verschijnen.
- Als bekend is dat de terminal kleuren ondersteund, maar niet
- getoond worden door <code>calcurse</code>, probeerd dan om de waarde
- van de <code>$TERM</code> variabele te veranderen in iets anders
- (zoals bijvoorbeeld <span class="emp">xterm-xfree86</span>)
- </p>
-
-<h2>5.4 Layout configuratie<a name="options_layout"></a></h2>
-<p>
- De layout stelt de positie van de panels van <code>calcurse</code> in.
- Bij de standaard layout is de positie van het kalender panel in de
- terminal rechtsboven, het todo-panel rechtsonder, en het afspraken
- panel wordt aan de linkerkant van het scherm getoond (zie het figuur
- in sectie <a href="#basics_interface_interactive">Interactieve
- modus</a> voor een voorbeeld van de standaard layout).
- Door een andere layout te kiezen in het configuratie scherm, kan de
- gebruiker <code>calcurse</code> zo het beste aan zijn behoeftes
- aanpassen.</p>
-
-<div class="todo">
-<p>
- The following option is used to modify the layout configuration:</p>
- <dl>
- <dt><code>layout</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>Eight different layouts are to be chosen from (see layout
- configuration screen for the description of the available layouts).</dd>
- </dl>
-</div>
-
-<div class="todo">
-<h2>5.5 Sidebar configuration<a name="options_sidebar"></a></h2>
-<p>
- The sidebar is the part of the screen which contains two panels:
- the calendar and, depending on the chosen layout, either the todo
- list or the appointment list.</p>
-<p>
- The following option is used to change the width of the sidebar:</p>
- <dl>
- <dt><code>side-bar_width</code>
- (default: <span class="emp">0</span>)</dt>
- <dd>Width (in percentage, 0 being the minimum width) of the side bar.</dd>
- </dl>
-</div>
-
-<h2>5.6 Informatiebalk instellingen<a name="options_notify"></a></h2>
-<p>
- De volgende opties stelt het gedrag van de informatiebalk in:</p>
- <dl>
- <dt><code>informatiebalk_toon</code>
- (standaard: <span class="emp">ja</span>)</dt>
- <dd>Deze optie stelt in of de informatiebalk getoond wordt op het scherm
- of niet.</dd>
- <dt><code>informatiebalk_datum</code>
- (standaard: <span class="emp">%a %F</span>)</dt>
- <dd>Door middel van deze optie, kan ingesteld worden hoe de datum wordt
- weergegeven in de informatiebalk. Alle mogelijkheden kunnen gezien
- worden door <code>man 3 strftime</code> in de terminal te typen.</dd>
- <dt><code>informatiebalk_tijd</code>
- (standaard: <span class="emp">%T</span>)</dt>
- <dd>Door middel van deze optie, kan insteld worden hoe de huidige tijd
- wordt weergegeven in de informatiebalk. weergegeven in de
- informatiebalk. Alle mogelijkheden kunnen gezien worden door
- <code>man 3 strftime</code> in de terminal te typen.</dd>
- <dt><code>informatiebalk_waarschuwing</code>
- (standaard: <span class="emp">300</span>)</dt>
- <dd>Indien een afspraak binnen de tijd valt die is ingesteld in
- 'informatiebalk_waarschuwing', begint de weergave van die boodschap te
- knipperen. Zo wordt de gebruiker gewaarschuwd, dat er een op handen
- zijnde afspraak is. Bovendien zal het commando uitgevoerd worden dat
- is gedefinieerd door informatiebalk_commando.</dd>
- <dt><code>informatiebalk_commando</code>
- (standaard: <span class="emp">printf '\a'</span>)</dt>
- <dd>Deze optie geeft het commando weer dat wordt uitgevoerd wanneer er een
- op handen zijnde afspraak is, die gemarkeerd is als 'belangrijk'. Het
- commando zal naar de shell van de gebruiker gestuurd worden, waar het
- door de shell uitgevoerd wordt. Om van de gewenste shell gebruik te
- maken, wordt gebruik gemaakt van de <code>$SHELL</code>
- omgevingsvariabele. Er wordt gebruik gemaakt van <code>/bin/sh</code>,
- indien de variabele leeg is.
- <p class="rq"><span class="valorise">Voorbeeld:</span>
- Stel dat het commando <code>mail</code> uit te
- voeren is op het systeem van de gebruiker. Men kan dan het volgende
- commando gebruiken om op de hoogte gesteld te worden van een op handen
- zijnde afspraak (de beschrijving van de afspraak zal ook te zien zijn
- in de body van de mail):</p>
- <code>
-calcurse --next | mail -s "[calcurse] upcoming appointment!" user@host.com
- </code>
- </dd>
-
- <dt><code><span class="todo">notify-daemon_enable</code>
- (default: <span class="emp">no</span>)</span></dt>
- <dd><span class="todo">If set to yes, daemon mode will be enabled, meaning <code>calcurse</code>
- will run into background when the user's interface is exited. This will allow the
- notifications to be launched even when the interface is not running. More details
- can be found in section <a href="#basics_daemon">'Background mode'</a>.</span>
- </dd>
- <dt><code><span class="todo">notify-daemon_log</code>
- (default: <span class="emp">no</span>)</span></dt>
- <dd><span class="todo">If set to yes, <code>calcurse</code> daemon activity will be logged (see section
- <a href="#basics_files">files</a></span>).
- </dd>
-
- </dl>
-
-<h1>6. bekende bugs<a name="bekende_bugs"></a></h1>
-<p>
- Wanneer <code>calcurse</code> gebruikt maakt van een zwart-wit schema
- terwijl de <code>$TERM</code> variabele is ingesteld op
- <span class="emp">xterm-color</span>, zullen er verkeerde items gemarkeerd worden.
- Gebruik om deze bug op te lossen, <span class="emp">xterm-xfree86</span> in plaats van
- <span class="emp">xterm-color</span> in de variabele <code>$TERM</code>,
- adviseert Thomas E. Dickey (<code>xterm</code> maintainer):</p>
- <blockquote class="rq">
- "De waarde van xterm-color voor $TERM is geen goede keuze voor XFree86
- xterm, omdat het vaak gebruikt wordt voor een optie in terminfo, dat
- bce niet ondersteunt. Maak gebruik van de xterm-xfree86 optie die met
- de xterm van XFree86 wordt gedistribueerd (of eenzelfde die wordt
- gedistribueerd met ncurses)."
- </blockquote>
-
-<h1>7. Het melden van bugs en aanmerkingen<a name="bugs"></a></h1>
-<p>
- Meldt bugs en aanmerkingen alstublieft aan:</p>
- <pre>calcurse @ culot . org</pre>
-<p>
- Of aan de auteur:</p>
- <pre>frederic @ culot . org</pre>
-
-<h1>8. Hoe kan ik helpen?<a name="contribute"></a></h1>
-<p>
- Mocht je mee willen helpen aan het project, dan kan je ten eerste
- laten weten wat je wel en niet goed vindt, en of er nog dingen zijn
- die je mist in <code>calcurse</code>.
- Ook wordt het vertalen van <code>calcurse</code> berichten en
- documentatie zeer gewaardeerd.</p>
- <p class="rq"><span class="valorise">Noot:</span>
- Alle hulp bij het 'internationaliseren' van
- <code>calcurse</code> wordt zeer op prijs gesteld, maar voordat je
- begint, mail dan eerst naar <code>calcurse-i18n @ culot . org</code>, om
- te weten te komen of iemand anders al met een vertaling naar jouw taal
- bezig is.</p>
-
-<h2>8.1 Vertalen van de documentatie<a name="contribute_documentation"></a></h2>
-<p>
- De <span class="emp">doc/</span> directory van het bronpakket bevat alle vertalingen
- van de handleidingen van <code>calcurse</code>. Als de handleiding van
- je moedertaal echter nog niet aanwezig is, wordt het zeer op prijs
- gesteld als je kunt helpen met de vertaling.</p>
-<p>
- Kopieer eenvoudig de bestaande handleiding naar
- <code>manual_XX.html</code>, waar <span class="emp">XX</span> de code is van je taal.
- Vertaal dan het zojuist aangemaakte bestand en zend het naar de
- auteur (zie <a href="#bugs">Het melden van bugs en aanmerkingen</a>),
- zodat het bij de volgende versie van <code>calcurse</code> gevoegd can
- worden.</p>
-
-<h2>8.2 <code>calcurse</code> i18n<a name="contribute_i18n"></a></h2>
-<p>
- Zoals eerder gezegd, maakt <code>calcurse</code> gebruikt van
- <code>gettext</code> om berichten weer te geven in meerdere talen.
- Deze sectie informeert hoe de berichten te vertalen in je moedertaal.
- Deze howto is echter met opzet incompleet, en verlegt de focus op het
- werken met <code>gettext</code> voor <code>calcurse</code>. Voor meer
- gespecificeerde informatie of om het grotere geheel te begrijpen, is
- er de <code>GNU gettext</code> handleiding:</p>
- <pre>http://www.gnu.org/software/gettext/manual/</pre>
-<p>
- In principe, zijn er drie verschillende mensen bezig in de
- vertaalketen: programmeurs, de vertaal co&ouml;rdinator, en de vertalers.
- Na in vogelvlucht uit te leggen hoe dingen werken, zal de taak van de
- vertaler beschreven worden.</p>
-
-<h3>8.2.1 Overzicht<a name="contribute_i18n_overview"></a></h3>
-<p>
- Om het mogelijk te maken om teksten weer te geven in de taal van de
- gebruiker, zijn er twee stappen vereist: <span class="emp">internationalisatie</span>
- (i18n) en <span class="emp">localisatie</span> (l10n).</p>
-<p>
- i18n zorgt ervoor dat
- <code>calcurse</code> meerdere talen ondersteund. De programmeurs
- markeren de te vertalen tekst (strings genaamd) en bieden een manier
- aan om deze direct te vertalen als <code>calcurse</code> gestart is.</p>
-<p>
- l10n zorgt ervoor dat de i18n-de <code>calcurse</code> zich instelt op
- de taal van de gebruiker, dus worden de door de programmeurs
- gemarkeerde strings vertaald, en wordt de omgeving correct ingesteld,
- zodat <code>calcurse</code> gebruik kan maken van de vertaling.</p>
-<p>
- Dus, de te vertalen strings worden eerst gemarkeerd door de
- programmeurs binnen in de <code>C</code> broncode, dan worden ze
- verzameld in een sjabloon bestand (<span class="emp">calcurse.pot</span> - de
- <span class="emp">pot</span> extensie staat voor <span class="emp">portable object template</span>,
- wat zoiets als overdraagbaar object sjabloon betekent). De inhoud van
- deze sjabloonbestanden worden dan samengevoegd met de vertaalbestanden
- van elke taal (<span class="emp">fr.po</span> voor frans, bijvoorbeeld - waar
- <span class="emp">po</span> voor <span class="emp">portable object</span> staat, dus bedoeld om
- gelezen en gewijzigd te worden door mensen). Dit bestand wordt door een
- vertaalteam vertaald, en verzonden naar de ontwikkelaars. Bij het
- compileren wordt voor efficientie een binaire versie van dit bestand
- gemaakt (<span class="emp">fr.mo</span> - <span class="emp">mo</span> staat voor <span class="emp">machine
- object</span>, dus met als doel gelezen te worden door programma's), en
- ge&iuml;nstalleerd. <code>calcurse</code> gebruikt dit bestand dan, om de
- strings te vertalen volgende de instellingen van de locale van de
- gebruiker.</p>
-
-<h3>8.2.2 Taken van de vertaler<a name="contribute_i18n_translator"></a></h3>
-<p>
- Stel dat iemand met het vertalen naar een nieuwe taal wil beginnen.
- Dan zijn dit de stappen die gevolgd moeten worden:</p>
- <ul>
- <li>Vindt eerst uit wat de naam van de locale is. Voor frans
- bijvoorbeeld is het 'fr_FR', of simpelweg 'fr'. Dit is de waarde die
- in de omgevingsvariabele <code>LC_ALL</code> moet staan om software te
- vertalen (zie <a href="#basics_invocation_variable">De i18n
- omgevingsvariabele</a>).</li>
- <li>Ga dan naar de <span class="emp">po/</span> directory, en maak nieuwe
- po-bestanden aan met het volgende commando:
- <code>'msginit -i calcurse.pot -o fr.po -l fr --no-translator'</code>
- Indien <code>msginit</code> niet aanwezig is op het systeem, kopieer
- dan simpelweg het <span class="emp">calcurse.pot</span> bestand en hernoem het naar
- bijvoorbeeld <span class="emp">fr.po</span> en wijzig de header
- handmatig.</li>
- </ul>
-<p>
- Nu <span class="emp">fr.po</span> aangemaakt is, kan de vertaler beginnen.</p>
-
-<h3>8.2.3 po-bestanden<a name="contribute_i18n_po-files"></a></h3>
-<p>
- De indeling van de po-bestanden is vrij simpel. Po-bestanden bestaan
- uit vier onderdelen:</p>
- <ol>
- <li><span class="emp">locatie regels:</span> informeert waar de strings gevonden
- kunnen worden (bestandsnaam en regelnummer), in het geval dat je het
- een beetje in context wilt zien.</li>
- <li><span class="emp">msgid regels:</span> de te vertalen strings.</li>
- <li><span class="emp">msgstr regels:</span> de vertaalde strings.</li>
- <li><span class="emp">regels met een '#' ervoor:</span> commentaar (sommige met een
- speciale betekenis, zoals we verderop zullen zien).</li>
- </ol>
-<p>
- Eigenlijk, hoef je alleen de <span class="emp">msgstr</span> regels te vullen met de
- vertaling van bovenstaande <span class="emp">msgid</span> regels.</p>
-<p>
- <span class="valorise">Een paar aanmerkingen:</span>
- <dl>
- <dt><span class="emp">Fuzzy strings</span></dt>
- <dd>Wanneer je een string tegenkomt die gemarkeerd is met <code>"#,
- fuzzy"</code>, zal <code>calcurse</code> de vertaling niet gebruiken
- totdat je iets verandert. 'Fuzzy' betekent dat de string al vertaald
- is, maar sindsdien is veranderd in de broncode van het programma, of
- dat het een nieuwe string is, waar <code>gettext</code> zelf een ruwe
- vertaling van heeft gemaakt, gebaseerd op andere strings in het
- bestand. Het komt erop neer dat je de vertaling moet nakijken. Soms is
- er een kleine verandering in de originele string, omdat er een typfout
- is verbeterd. In dit geval hoeft er niets te veranderen. Maar het kan
- ook zo zijn dat de vertaling niet juist meer is, en een verandering
- noodzakelijk is. Als de vertaling weer in orde is, wis dan de regel
- met <code>"#, fuzzy"</code>, en dan zal de vertaling weer gebruikt
- worden in <code>calcurse</code>.</dd>
- <dt><span class="emp">c-format strings en speciale tekens</span></dt>
- <dd>Sommige string hebben het volgende commentaar: <code>"#,
- c-format"</code>. Dit betekent dat een deel van de te vertalen string
- een speciale betekenis heeft voor het programma, en niet veranderd mag
- worden. Bijvoorbeeld, het teken %, gebruikt als <code>"%s"</code>. Dit
- betekent dat <code>calcurse</code> dit teken zal vervangen met een
- andere string. Het is dus belangrijk dat het niet verwijderd wordt. Er
- zijn ook andere tekens zoals \, gebruikt als <code>\n</code> of
- <code>\t</code>. Verander ook deze niet. Het zijn respectievelijk
- tekens voor einde-van-de-regel, en een tab.</dd>
- <dt><span class="emp">Vertalingen mogen afgebroken worden</span></dt>
- <dd>Zodra een regel te lang wordt, kan je hem splitsen als volgt:
- <pre>
-msgid ""
-"een hele lange regel"
-"de volgende regel"
- </pre></dd>
- <dt><span class="emp">het begin van het po-bestand</span></dt>
- <dd>Aan het begin van het po-bestand, vormt de eerste string de 'header',
- waar verschillende soorten informatie kan worden ingevuld. Het
- belangrijkste is de karakterset. Het zou er als volgt uit moeten zien:
- <pre>
-"Content-Type: text/plain; charset=utf-8\n"
- </pre>
- Het is ook belangrijk dat het Last-Translator veld wordt ingevuld,
- zodat nieuwe vertalers zich bij je kunnen aanmelden, of dat mensen
- contact kunnen opnemen als ze aanvullingen hebben of typfouten
- gevonden hebben. Je kan zowel een naam/bijnaam, of email adres
- invulllen, zoals bijvoorbeeld:
- <pre>
-"Last-Translator: Frederic Culot &lt;frederic@culot.org&gt;\n"
- </pre></dd>
- <dt><span class="emp">Commentaar</span></dt>
- <dd>Het toevoegen van commentaar (regels die beginnen met het karakter
- '#', is een juiste manier om problemen met vertalingen te markeren
- voor proeflezers of andere vertalers.</dd>
- <dt><span class="emp">De lengte van strings</span></dt>
- <dd><code>calcurse</code> is een curses/console programma, dus het is nauw
- verbonden met het aantal kolommen dat de terminal gebruikt. Dit is
- iets om in gedachten te houden bij het vertalen. Vaak moet een string
- op een enkele regel passen. Het beste is dus om niet zomaar de strings
- te vertalen, maar om eerst te kijken waar ze weergegeven worden in het
- programma, en pas dan te vertalen.</dd>
- <dt><span class="emp">Een paar nuttige hulpmiddelen</span></dt>
- <dd>Het po-bestandsformaat is vrij simpel, en het bestand kan gewijzigd
- worden met een standaard tekst-editor. Maar er zijn een paar
- gespecialiseerde hulpmiddelen, die je misschien handig vindt bij het
- vertalen:
- <ul>
- <li><code>poEdit</code> (<a
- href="http://www.poedit.org/" target="_blank">
- http://www.poedit.org/</a>)</li>
- <li><code>KBabel</code> (<a
- href="http://i18n.kde.org/tools/kbabel/" target="_blank">
- http://i18n.kde.org/tools/kbabel/</a>)</li>
- <li><code>GTranslator</code> (<a
- href="http://gtranslator.sourceforge.net/" target="_blank">
- http://gtranslator.sourceforge.net/</a>)</li>
- <li><code>Emacs</code> po mode</li>
- <li><code>Vim</code> po mode</li>
- </ul>
- </dd>
- <dt><span class="emp">En als laatste</span></dt>
- <dd>Ik hoop dat je het leuk vindt om bij te dragen aan een
- 'ge&iuml;nternationaliseerde' wereld. :) Mocht je nog vragen hebben,
- schroom dat niet om contact met me op te nemen via
- <span class="emp">frederic @ culot . org</span>. </dd>
- </dl>
-
-<h1>9. Links<a name="links"></a></h1>
-<p>
- Deze sectie bevat links en referenties welke je misschien interesseren.</p>
-
-<h2>9.1 <code>calcurse</code> homepage<a name="links_homepage"></a></h2>
-<p>
- De <code>calcurse</code> homepage is hier te vinden:</p>
- <pre>http://culot.org/calcurse</pre>
-
-<h2>9.2 <code>calcurse</code> mededelingenlijst<a name="links_list"></a></h2>
-<p>
- Mocht je interesse hebben in het project, en op de hoogte wilt worden
- gehouden als er een nieuwe versie uitkomt, kan je jezelf inschrijven
- op de <code>calcurse</code> mededelingenlijst. Je ontvangt dan een
- email zodra er iets nieuws is in <code>calcurse</code>.</p>
-<p>
- Om je in te schrijven, zend dan een email naar
- <code>calcurse-announce @ culot . org</code> met "subscribe"
- ingevuld bij 'onderwerp'.</p>
-
-<h2><code>9.3 calcurse</code> RSS feed<a name="links_rss"></a></h2>
-<p>
- Nog een mogelijkheid om op de hoogte te blijven over nieuwe versies
- is om de RSS feed te volgen:</p>
- <pre>http://culot.org/calcurse/news_rss.xml</pre>
-<p>
- Deze RSS feed wordt iedere keer vernieuwd als er een nieuwe versie van
- calcurse beschikbaar is, waarbij ook de nieuwe opties beschreven
- worden. </p>
-
-<h2>9.4 Links<a name="links_others"></a></h2>
-<p>
- Voor meer informatie over het ical-formaatspecificatie (rfc2445):
- <pre>http://tools.ietf.org/html/rfc2445</pre>
-<p>
- De pcal projectpagina kan hier gevonden worden:
- <pre>http://pcal.sourceforge.net/</pre>
-
-<h1>10. Dankwoord<a name="thanks"></a></h1>
-<p>
- Het is tijd om de mensen te bedanken, zonder wie dit programma niet
- zou bestaan! Hier is een lijst met mensen die ik graag wil bedanken:
- <ul>
- <li>Alex voor zijn patches, hulp en advies met het programmeren in
- <code>C</code> </li>
- <li>Gwen voor het testen en voor de discussies om
- <code>calcurse</code> te verbeteren</li>
- <li>Herbert voor het maken van een pakket voor <code>calcurse</code>
- voor FreeBSD </li>
- <li>Zul voor het maken van een pakket voor <code>calcurse</code> voor
- NetBSD</li>
- <li>Wain, Steffen and Ronald voor het maken van een pakket voor <code>calcurse</code> voor
- Archlinux</li>
- <li>Kevin, Ryan, en fEnIo voor het maken van een pakket voor
- <code>calcurse</code> voor Debian en Ubuntu</li>
- <li>Pascal voor het maken van een pakket voor <code>calcurse</code>
- voor Slackware</li>
- <li>Alexandre en Markus voor het maken van een pakket voor
- <code>calcurse</code> voor Mac OsX en Darwin</li>
- <li>Igor voor het maken van een pakket voor <code>calcurse</code> for
- ALT Linux</li>
- <li>Joel voor zijn kalender script waarop de kalenderview van
- <code>calcurse</code> ge&iuml;nspireerd is</li>
- <li>Michael Schulz en Chris M. voor de duitse vertaling van
- <code>calcurse</code> en handleiding</li>
- <li>Jose Lopez voor de spaanse vertaling van <code>calcurse</code> en
- handleiding</li>
- <li>Neil Williams voor de engelse vertaling</li>
- <li>Leandro Noferini voor de italian vertaling</li>
- <li>Tony voor zijn patch die de recur_item_inday functie verbeterde
- , en voor het implementeren van de datumformaat
- configuratie-opties</span></li>
- <li>Jeremy Roon voor de nederlandse vertaling van
- <code>calcurse</code> en handleiding</li>
- <li>Erik Saule voor zijn patch, waarmee de '-N', '-s', '-S', '-r' en '-D'
- vlaggen zijn ge&iuml;mplementeerd</li>
- <li>en de mensen die de software geschreven hebben die ik goed vind
- en mij ge&iuml;nspireerd hebben zoals:
- <ul>
- <li><code>vim</code> voor de toetsen die de cursor verplaatsen</li>
- <li><code>orpheus</code> en <code>abook</code> voor de
- documentatie</li>
- <li><code>pine</code> en <code>aptitude</code>
- voor de tekstinterface</li>
- <li><span class="todo"><code>tmux</code> for coding style</span></li>
- </ul></li>
- </ul>
-</p>
-<p>
- En als laatste wil ik graag de mensen bedanken die
- <code>calcurse</code> gebruiken, en mij aanvullingen en opbouwende
- kritiek stuurden.</p>
-
-<div class="footer">
- Copyright &copy; 2004-2010 Frédéric Culot<br>
- Calcurse version 2.8 - Last change: March 29th, 2010<br>
-</div>
-</div>
-
-</body>
-</html>