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

Announce of the upcoming NMU for the iterm package

Dear maintainer of iterm and Debian translators,

Some days ago, I sent a notice to the maintainer of the iterm Debian
package, mentioning the status of at least one old po-debconf translation update in the BTS.

I announced the intent to build and possibly upload a non-maintainer upload
for this package in order to fix this long-time pending localization
bug as well as all other pending translations.

The package maintainer agreed for the NMU or did not respond in two
weeks, so I will proceed with the NMU.

The full planned schedule is available at the end of this mail.

The package is currently translated to: 
cs da de dz fr ja nl pt ru sv vi zh_CN zh_TW

Among these, the following translations are incomplete: da ja nl zh_CN zh_TW

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 iterm package so I can incorporate them in the build.

The deadline for receiving updates and new translations is Tuesday, May 27, 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):

 Wednesday, May 07, 2008   : send the first intent to NMU notice to
                 the package maintainer.
 Sunday, May 18, 2008       : send this notice
 Sunday, May 25, 2008       : (midnight) deadline for receiving translation updates
 Tuesday, May 27, 2008       : build the package and upload it to DELAYED/2-day
                 send the NMU patch to the BTS
 Thursday, May 29, 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: \n"
"POT-Creation-Date: 2006-11-30 07:36+0100\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: boolean
#. Description
#: ../fbiterm.templates:1001
msgid "Do you want /usr/bin/fbiterm to be installed SUID root?"
msgstr ""

#. Type: boolean
#. Description
#: ../fbiterm.templates:1001
msgid ""
"You have the option of installing the /usr/bin/fbiterm binary with the SUID "
"bit set.  By setting 'SUID root', non-root users may run fbiterm directly."
msgstr ""

#. Type: boolean
#. Description
#: ../fbiterm.templates:1001
msgid ""
"This can open security concerns: fbiterm may contain undiscovered security "
"flaws which malicious users may exploit if fbiterm is set SUID root."
msgstr ""

#. Type: boolean
#. Description
#: ../fbiterm.templates:1001
msgid ""
"You should install fbiterm with SUID bit set unless you do not intend to use "
"it regularly.  You may change this setting by running \"dpkg-reconfigure "
msgstr ""

Attachment: signature.asc
Description: Digital signature

Reply to: