[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

cgiemail 1.6-35.1: Please update debconf PO translation for the package cgiemail


A l10n NMU will happen on cgiemail pretty soon.

A round of translation updates is being launched to give all translators
a chance to get their translations in for that package.

Please send the updated file as a wishlist bug against the package.

The deadline for receiving the updated translation is
Friday, May 28, 2010.


#    Translators, if you are not familiar with the PO format, gettext
#    documentation is worth reading, especially sections dedicated to
#    this format, e.g. by running:
#         info -n '(gettext)PO Files'
#         info -n '(gettext)Header Entry'
#    Some information specific to po-debconf are available at
#            /usr/share/doc/po-debconf/README-trans
#         or http://www.debian.org/intl/l10n/po-debconf/README-trans
#    Developers do not need to manually edit POT or PO files.
msgid ""
msgstr ""
"Project-Id-Version: cgiemail 1.6-17\n"
"Report-Msgid-Bugs-To: cgiemail@packages.debian.org\n"
"POT-Creation-Date: 2008-05-08 10:39+0200\n"
"PO-Revision-Date: 2003-09-16 09:35+0200\n"
"Last-Translator: Philippe Faes <Philippe.Faes@UGent.be>\n"
"Language-Team: Dutch <debian-i10n-dutch@lists.debian.org>\n"
"Language: nl\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: string
#. Description
#: ../templates:1001
#, fuzzy
msgid "Directory where you want to put the cgiemail's mail templates:"
msgstr "Waar wilt u de mail sjablonen van cgiemail plaatsen?"

#. Type: string
#. Description
#: ../templates:1001
msgid ""
"In old versions of cgiemail, templates that were used for creating e-mails "
"to be sent could be placed anywhere that would be served up by the web "
"server.  This behaviour is a security vulnerability: an attacker can read "
"files that he shouldn't be able to, such as scripts in cgi-bin, if they "
"contain certain pieces of text."
msgstr ""
"In oude versies van cgiemail konden de sjablonen voor emails op eender welke "
"plaats gezet worden die door de webserver bediend kan worden. Dit houdt een "
"veiligheidsrisico in: een cracker kan bestanden lezen die hij niet mag "
"lezen, zoals scripts in cgi-bin. "

#. Type: string
#. Description
#: ../templates:1001
msgid ""
"If you enter nothing (that is, erase the default directory, leaving this "
"empty), cgiemail will still work. This may be needed if you are, for "
"instance, hosting web services, and cannot move all of your clients cgiemail "
"templates to one directory.  Remember that this will LEAVE THE SECURITY HOLE "
"OPEN, and is only a choice for backwards compatibility."
msgstr ""
"Als u niets invult (dus: de standaarddirectory uitwist en een leeg invulvak "
"achterlaat), zal cgiemail nog steeds werken. Dit kan nodig zijn als u bv. "
"een webserver uitbaat en de cgiemail sjablonen van uw klanten niet allemaal "
"kan verplaatsen naar dezelfde directory. Dit zal het VEILIGHEIDSRISICO LATEN "
"BESTAAN, en moet enkel gebruikt worden voor compatibiliteit met het verleden."

#. Type: string
#. Description
#: ../templates:1001
msgid ""
"To close the hole, enter a directory, which MUST be accessible by your web "
"server.  Template files that you want to use should go there. For further "
"instructions, please read the README.Debian and README files in /usr/share/"
msgstr ""
"Om het veiligheidsrisico te herstellen, vult u een directory in die MOET "
"toegankelijk zijn via de webserver. Sjablonen die u wilt gebruiken, plaatst "
"u in die directory. Voor verdere instructies kunt u README.Debian en de "
"andere README bestanden lezen in /usr/share/doc/cgiemail/."

Reply to: