2
# Translators, if you are not familiar with the PO format, gettext
3
# documentation is worth reading, especially sections dedicated to
4
# this format, e.g. by running:
5
# info -n '(gettext)PO Files'
6
# info -n '(gettext)Header Entry'
8
# Some information specific to po-debconf are available at
9
# /usr/share/doc/po-debconf/README-trans
10
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
12
# Developers do not need to manually edit POT or PO files.
17
"Project-Id-Version: PACKAGE VERSION\n"
18
"Report-Msgid-Bugs-To: \n"
19
"POT-Creation-Date: 2003-08-02 09:29+0200\n"
20
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
21
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
22
"Language-Team: LANGUAGE <LL@li.org>\n"
24
"Content-Type: text/plain; charset=CHARSET\n"
25
"Content-Transfer-Encoding: 8bit\n"
29
msgid "Should adjtimex be run at installation and at every startup?"
35
"adjtimex can run at system startup to set the kernel time parameters to the "
36
"values in /etc/default/adjtimex. Don't accept if you just want to use "
37
"adjtimex to inspect the current parameters."
42
msgid "Should adjtimexconfig be run at installation time?"
48
"The adjtimexconfig script will use adjtimex to find values for the kernel "
49
"variables tick and frequency that will make the system clock approximately "
50
"agree with the hardware clock (also known as the CMOS clock). It then saves "
51
"these values in the configuration file /etc/default/adjtimex so the settings "
52
"will be restored on every boot, when /etc/init.d/adjtimex runs."
58
"The script takes 70 sec to run. Alternatively, you can run adjtimexconfig "
59
"yourself at a later time, or determine the kernel variables one of several "
60
"other ways (see the adjtimex man page) and install them in /etc/default/"
added
removed
debian/po/templates.pot
