Dear maintainer of hotway and Debian translators,
An l10n NMU will soon happen for that package. This is the secodn such
NMU in a row, hence there was no initial "intent to NMU" mail.
The full planned schedule is available at the end of this mail.
The package is currently translated to:
cs de es eu fi fr gl it nl pt ru
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 hotway package so I can incorporate them in the build.
The deadline for receiving updates and new translations is Wednesday, July 16, 2008. If you
are not in time you can always send your translation to the BTS.
The POT file is attached to this mail.
If the maintainer objects to this process I will immediately abort my NMU
and send him/her all updates I receive.
Otherwise the following will happen (or already has):
Monday, July 07, 2008 : send this notice
Monday, July 14, 2008 : (midnight) deadline for receiving translation updates
Tuesday, July 15, 2008 : build the package and upload it to DELAYED/2-day
send the NMU patch to the BTS
Thursday, July 17, 2008 : NMU uploaded to incoming
Thanks for your efforts and time.
--
--
#
# 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.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: pik@debian.org\n"
"POT-Creation-Date: 2006-10-08 20:49-0600\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"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: note
#. Description
#: ../hotway.templates:1001
msgid "Port 110 is in use"
msgstr ""
#. Type: note
#. Description
#: ../hotway.templates:1001
msgid ""
"It looks like ${using110} is already using port 110, the standard port for "
"POP3 servers. Hotway will need to use something else. Unfortunately, there's "
"no simple way for this configuration script to set up your inetd to use a "
"different port, so you will need to do that yourself."
msgstr ""
#. Type: note
#. Description
#: ../hotway.templates:1001
msgid ""
"Alternatively, uninstall any other POP3 servers you may have installed, and "
"then reconfigure hotway."
msgstr ""
#. Type: boolean
#. Description
#: ../hotway.templates:2001
msgid "Manage inetd configuration automatically?"
msgstr ""
#. Type: boolean
#. Description
#: ../hotway.templates:2001
msgid ""
"Hotway can be configured to be run through inetd, and since it looks like "
"nothing is using the standard POP3 port (110), that configuration can be "
"done for you automatically."
msgstr ""
#. Type: boolean
#. Description
#: ../hotway.templates:2001
msgid ""
"However, since this package does not explicitly conflict with other pop3-"
"servers, if you install another one, it will probably deactivate hotway and "
"at that point you'll need to come up with your own inetd configuration so "
"that both can run."
msgstr ""
#. Type: boolean
#. Description
#: ../hotway.templates:2001
msgid ""
"If you decline automatic configuration, you will need to manage hotway's "
"inetd or other configuration on your own."
msgstr ""
#. Type: boolean
#. Description
#: ../hotway.templates:2001
msgid "If in doubt, it is suggested that you choose automatic configuration."
msgstr ""
Attachment:
signature.asc
Description: Digital signature