Dear maintainer of uptimed and Debian translators, Some days ago, I sent a notice to the maintainer of the uptimed 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:
ca cs da de es fr gl it ja nl pt pt_BR ru sv vi
Among these, the following translations are incomplete: 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 uptimed package so I can incorporate them in the build.
The deadline for receiving updates and new translations is Thursday, February
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):
Friday, February 12, 2010 : send the first intent to NMU notice to
the package maintainer.
Friday, February 12, 2010 : send this notice
Thursday, February 18, 2010 : (midnight) deadline for receiving
translation updates
Friday, February 19, 2010 : build the package and upload it to
DELAYED/7-day
send the NMU patch to the BTS
Friday, February 26, 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 <em...@address>, YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: upti...@packages.debian.org\n" "POT-Creation-Date: 2010-02-12 22:31+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <em...@address>\n" "Language-Team: LANGUAGE <l...@li.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: 8bit\n" #. Type: select #. Choices #: ../uprecords-cgi.templates:1001 msgid "pre, list, table" msgstr "" #. Type: select #. Description #: ../uprecords-cgi.templates:1002 msgid "Which format should uprecords.cgi use?" msgstr "" #. Type: select #. Description #: ../uprecords-cgi.templates:1002 msgid "" "The uprecords CGI script has different ways of doing a proper display " "layout. Which method you want to use depends mainly on your personal " "preference. Available options are:" msgstr "" #. Type: select #. Description #: ../uprecords-cgi.templates:1002 msgid "" " - pre: Encloses everything in <pre>...</pre>\n" " - list: Makes a list, using <ol>...</ol>\n" " - table: Creates an HTML table." msgstr "" #. Type: string #. Description #: ../uprecords-cgi.templates:2001 msgid "How many records should uprecords.cgi show?" msgstr "" #. Type: string #. Description #: ../uprecords-cgi.templates:2001 msgid "" "While uptimed may keep a large number of uptime records, not all of them are " "interesting to the outside world. Thus, you can limit the number of records " "that will be shown here." msgstr "" #. Type: note #. Description #: ../uprecords-cgi.templates:3001 msgid "uprecords.cgi has been installed into the webtree" msgstr "" #. Type: note #. Description #: ../uprecords-cgi.templates:3001 msgid "" "You have installed the uprecords-cgi package. That means that a new CGI " "script has been installed, which is now visible to the outside world as " "http://${hostname}/cgi-bin/uprecords.cgi (if you didn't modify your " "webserver configuration to have CGI scripts in a different place)." msgstr "" #. Type: note #. Description #: ../uprecords-cgi.templates:3001 msgid "" "In the default webserver configuration, CGI scripts are accessible from " "anywhere in the world. If you do not want this, you should set up access " "restrictions (but who doesn't want to show off with his/her uptimes?)." msgstr "" #. Type: note #. Description #: ../uprecords-cgi.templates:3001 msgid "" "You may also want to modify the HTML header and footer files in /etc/" "uprecords-cgi or tell your webmaster to do so (remember to give him the " "necessary permissions then)." msgstr "" #. Type: string #. Description #: ../uptimed.templates:1001 msgid "How many seconds should pass between database updates?" msgstr "" #. Type: string #. Description #: ../uptimed.templates:1001 msgid "" "Uptimed will update its database every n seconds so that the uptime doesn't " "get lost in case of a system crash. You can set how frequently this will " "happen (use higher values if you want to avoid disk activity, for example on " "a laptop). 60 seconds should be a reasonable default." msgstr "" #. Type: string #. Description #: ../uptimed.templates:2001 msgid "How many records should be kept?" msgstr "" #. Type: string #. Description #: ../uptimed.templates:2001 msgid "" "On systems that reboot frequently (such as desktop PCs), you will get a " "fairly large list of uptime records pretty soon. To avoid this, uptimed will " "only keep the n highest uptimes. You may want to limit this to a lower value " "if you want to get emails each time a record is broken or reboot your " "machine often. 10 is a nice value." msgstr "" #. Type: select #. Choices #: ../uptimed.templates:3001 msgid "Never, Record, Milestone, Both" msgstr "" #. Type: select #. Description #: ../uptimed.templates:3002 msgid "Send mails if a milestone or record is reached?" msgstr "" #. Type: select #. Description #: ../uptimed.templates:3002 msgid "" "Uptimed can be configured to send a mail each time a record is broken or a " "\"milestone\" is reached. You can choose whether you" msgstr "" #. Type: select #. Description #: ../uptimed.templates:3002 msgid "" " - never want to receive these mails\n" " - want to be notified only when a record is broken\n" " - would like to know about milestones\n" " - are interested in both" msgstr "" #. Type: string #. Description #: ../uptimed.templates:4001 msgid "Where should uptimed send its mails to?" msgstr "" #. Type: string #. Description #: ../uptimed.templates:4001 msgid "" "Since you have chosen to be sent emails, you should specify where to send " "these mails. The default \"r...@localhost\" makes sort of sense, but if you " "are one of many sysadmins and you are unsure whether the other admins want " "to get these mails, you should probably set this to your real address." msgstr "" #. Type: note #. Description #: ../uptimed.templates:5001 msgid "Milestone configuration should be done manually" msgstr "" #. Type: note #. Description #: ../uptimed.templates:5001 msgid "" "While all other configuration options can be set here, the milestones must " "be configured manually in /etc/uptimed.conf. Since you have chosen to " "receive emails for milestones you may probably want to edit that file." msgstr ""
signature.asc
Description: Digital signature
