Dear maintainer of logtool and Debian translators,
Some days ago, I sent a notice to the maintainer of the logtool Debian
package, mentioning the status of at least one old po-debconf translation update in the BTS.
The package maintainer and I agreed for a translation update round. At
the end of this period, I will send him|her a full patch so that
an l10n upload can happen.
The full planned schedule is available at the end of this mail.
Please note that this upload is very likely to be THE ONLY ONE that
will happen for logtool until squeeze is released. As Wouter
explained, logtool is in low maintenance mode and he prefers having
only one upload. In short, if you're targeting 100% for debconf
templates translations, then this is your last chance...
The package is currently translated to:
cs de es eu fr gl it ja nl pt pt_BR ro ru sv tr vi
Among these, the following translations are incomplete: <none>
If you did any of the, currently incomplete, translations you will get
ANOTHER mail with the translation to update.
Other translators also have the opportunity to create new translations
for this package. Once completed, please send them as a bug report
against the logtool package so I can incorporate them in the build.
The deadline for receiving updates and new translations is Saturday, June 26, 2010. If you
are not in time you can always send your translation to the BTS.
The POT file is attached to this mail.
Schedule:
Friday, June 18, 2010 : send the first intent to NMU notice to
the package maintainer.
Sunday, June 20, 2010 : send this notice
Saturday, June 26, 2010 : (midnight) deadline for receiving translation updates
Sunday, June 27, 2010 : Send a summary to the maintainer. Maintainer uploads
when possible.
Thanks for your efforts and time.
--
--
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: logtool@packages.debian.org\n"
"POT-Creation-Date: 2010-06-20 12:35+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: boolean
#. Description
#: ../templates:1001
msgid "Manual configuration of logtool's database?"
msgstr ""
#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Logtool needs a database with regular expressions that describe logfile "
"entries that should be ignored, or considered less important. You can write "
"this database manually, or use the very flexible database in the package "
"logcheck-database for this purpose."
msgstr ""
#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"If you choose to use logcheck-database and already added values to the files "
"in /etc/logtool, these files will be replaced by symbolic links in the "
"logcheck database (although backups will be preserved). Make sure this is "
"not unwanted behaviour."
msgstr ""
#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Reply positively to manually write a database, or negatively to use the "
"database from the package \"logcheck-database\"."
msgstr ""
#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Note: since logtool does not depend on this database (but instead Recommends "
"it), the default answer to this question is to manually configure the "
"database."
msgstr ""
#. Type: boolean
#. Description
#. NOTE to translators: The terms 'paranoid', 'server', 'workstation',
#. 'violations', 'cracking', and 'violations-ignore' refer to file names in
#. /etc/logcheck. To avoid user confusion, these terms should either NOT be
#. translated, or the translated terms should be mentioned between brackets
#. after the untranslated version, like so:
#. violations (inbreuken).
#. Or, if you prefer, the other way around.
#: ../templates:3001
msgid "Do you want to use the '${level}' level regular expressions?"
msgstr ""
#. Type: boolean
#. Description
#. NOTE to translators: The terms 'paranoid', 'server', 'workstation',
#. 'violations', 'cracking', and 'violations-ignore' refer to file names in
#. /etc/logcheck. To avoid user confusion, these terms should either NOT be
#. translated, or the translated terms should be mentioned between brackets
#. after the untranslated version, like so:
#. violations (inbreuken).
#. Or, if you prefer, the other way around.
#: ../templates:3001
msgid ""
"The database in the logcheck-database package defines three levels: "
"paranoid, server, and workstation; and it also has a database for cracking, "
"violations, and ignored violations ('violations-ignore'). Logcheck allows "
"you to pick one of the levels, and ignores the rest."
msgstr ""
#. Type: boolean
#. Description
#. NOTE to translators: The terms 'paranoid', 'server', 'workstation',
#. 'violations', 'cracking', and 'violations-ignore' refer to file names in
#. /etc/logcheck. To avoid user confusion, these terms should either NOT be
#. translated, or the translated terms should be mentioned between brackets
#. after the untranslated version, like so:
#. violations (inbreuken).
#. Or, if you prefer, the other way around.
#: ../templates:3001
msgid ""
"Logtool, on the other hand, can use multiple databases, which either specify "
"lines that should be completely excluded from output (/etc/logtool/exclude) "
"or lines that should be given a specific color (green, yellow, blue, "
"magenta, cyan, brightcyan). There is also the possibility to not create an "
"exclude file, and use an 'include' style of file instead; its use is not "
"recommended. Last but not least, files that are not excluded from output but "
"that do not match any other regular expression are colored red."
msgstr ""
#. Type: boolean
#. Description
#. NOTE to translators: The terms 'paranoid', 'server', 'workstation',
#. 'violations', 'cracking', and 'violations-ignore' refer to file names in
#. /etc/logcheck. To avoid user confusion, these terms should either NOT be
#. translated, or the translated terms should be mentioned between brackets
#. after the untranslated version, like so:
#. violations (inbreuken).
#. Or, if you prefer, the other way around.
#: ../templates:3001
msgid ""
"If you want to map the '${level}' level database of regular expressions to "
"one of the above specified options, then answer positively to this question."
msgstr ""
#. Type: select
#. Choices
#: ../templates:4001
msgid "exclude, include, green, yellow, blue, magenta, cyan, brightcyan"
msgstr ""
#. Type: select
#. Description
#: ../templates:4002
msgid "What do you want the ${level} level of regular expressions to do?"
msgstr ""
#. Type: select
#. Description
#: ../templates:4002
msgid ""
"Please specify what you want to do with a line if it matches at least one of "
"the regular expressions in the ${level} level database. You have the "
"following options (note that regular expressions are matched on a line-per-"
"line basis):"
msgstr ""
#. Type: select
#. Description
#: ../templates:4002
msgid ""
" * exclude: discard matching lines\n"
" * include: discard all but matching lines. Not recommended. Note that\n"
" this is mutually exclusive with 'exclude'.\n"
" * green, yellow, blue, magenta, cyan, brightcyan: give matching lines\n"
" the specified color."
msgstr ""
#. Type: select
#. Description
#: ../templates:4002
msgid ""
"Note that each option can be specified for only one of paranoid, server, or "
"workstation."
msgstr ""
#. Type: error
#. Description
#: ../templates:5001
msgid "Please do not select an action more than once"
msgstr ""
#. Type: error
#. Description
#: ../templates:5001
msgid ""
"You have selected the action ${action} for at least ${level1} and ${level2}. "
"This is invalid; please either select a unique action for each level, or go "
"back and choose not to use a certain level."
msgstr ""
Attachment:
signature.asc
Description: Digital signature