Dear maintainer of adjtimex and Debian translators, Some days ago, I sent a notice to the maintainer of the adjtimex 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 four days, 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 es eu fi fr gl it ja nl pl pt pt_BR ru sv vi Among these, the following translations are incomplete: nl pl pt_BR 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 adjtimex package so I can incorporate them in the build. The deadline for receiving updates and new translations is Monday, October 18, 2010. 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): Saturday, October 09, 2010 : send the first intent to NMU notice to the package maintainer. Thursday, October 14, 2010 : send this notice Monday, October 18, 2010 : (midnight) deadline for receiving translation updates Tuesday, October 19, 2010 : build the package and upload it to DELAYED/2-day send the NMU patch to the BTS Thursday, October 21, 2010 : NMU uploaded to incoming 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: email@example.com\n" "POT-Creation-Date: 2009-03-17 07:38+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 #: ../templates:2001 msgid "Should adjtimex be run at installation and at every startup?" msgstr "" #. Type: boolean #. Description #: ../templates:2001 msgid "" "Running adjtimex at system startup will set the kernel time parameters to " "the values in /etc/default/adjtimex." msgstr "" #. Type: boolean #. Description #: ../templates:2001 msgid "" "You should not choose this option if you just want to use adjtimex to " "inspect the current parameters." msgstr "" #. Type: boolean #. Description #: ../templates:3001 msgid "Run adjtimexconfig when adjtimex is installed or upgraded?" msgstr "" #. Type: boolean #. Description #. Translators: do not translate "tick" and "frequency" #: ../templates:3001 msgid "" "The adjtimexconfig script will use adjtimex to find values for the kernel " "variables \"tick\" and \"frequency\" that will make the system clock " "approximately agree with the hardware clock (also known as the CMOS clock). " "It then saves these values in the configuration file /etc/default/adjtimex " "so the settings will be restored on every boot, when /etc/init.d/adjtimex " "runs." msgstr "" #. Type: boolean #. Description #: ../templates:3001 msgid "" "The script takes 70 seconds to run, so running it for every upgrade may be a " "waste of time. Alternatively, you can run adjtimexconfig manually when " "needed, or determine the kernel variables by using other methods and set " "them manually in /etc/default/adjtimex." msgstr ""
Description: Digital signature