[cl-debian] Bug#492177: Announce of the upcoming NMU for the gclcvs package

[Christian Perrier]

Dear maintainer of gclcvs and Debian translators,

Some days ago, I sent a notice to the maintainer of the gclcvs 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 de es fi fr gl nl pt ru sv vi

Among these, the following translations are incomplete: es vi

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

The deadline for receiving updates and new translations is Saturday, November 01, 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):

 Tuesday, October 21, 2008   : send the first intent to NMU notice to
                 the package maintainer.
 Sunday, October 26, 2008       : send this notice
 Saturday, November 01, 2008       : (midnight) deadline for receiving translation updates
 Sunday, November 02, 2008       : build the package and upload it to DELAYED/2-day
                 send the NMU patch to the BTS
 Tuesday, November 04, 2008       : NMU uploaded to incoming

Thanks for your efforts and time.

-- 


-- 


-------------- next part --------------
#
#    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: 2007-01-21 08:47+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../in.gcl.templates:1001
msgid "Use the work-in-progress ANSI build by default?"
msgstr ""

#. Type: boolean
#. Description
#: ../in.gcl.templates:1001
msgid ""
"GCL is in the process of providing an ANSI compliant image in addition to "
"its traditional CLtL1 image still in production use.  Please see the README."
"Debian file for a brief description of these terms.  Setting this variable "
"will determine which image you will use by default on executing 'gcl at EXT@'.  "
"You can locally override this choice by setting the GCL_ANSI environment "
"variable to any non-empty string for the ANSI build, and to the empty string "
"for the CLtL1 build, e.g. GCL_ANSI=t gcl at EXT@.  The flavor of the build in "
"force will be reported in the initial startup banner."
msgstr ""

#. Type: boolean
#. Description
#: ../in.gcl.templates:2001
msgid "Use the profiling build by default?"
msgstr ""

#. Type: boolean
#. Description
#: ../in.gcl.templates:2001
msgid ""
"GCL now has optional support for profiling via gprof.  Please see the "
"documentation for si::gprof-start and si::gprof-quit for details. As this "
"build is slower than builds without gprof support, it is not recommended for "
"final production use. You can locally override the default choice made here "
"by setting the GCL_PROF environment variable to any non-empty string for "
"profiling support, and to the empty string for the more optimized builds, e."
"g. GCL_PROF=t gcl at EXT@.  If profiling is enabled, this will be reported in "
"the initial startup banner."
msgstr ""
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <https://mailman.common-lisp.net/pipermail/cl-debian/attachments/20081026/d803bfab/attachment.sig>