msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2010-06-20 09:23-0400\n"
+"POT-Creation-Date: 2011-03-03 11:18-0400\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"
+"Language: \n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
-"Content-Transfer-Encoding: ENCODING"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
#. type: Content of: <chapter><title>
#: developer-duties.dbk:7
#. type: Content of: <chapter><section><para>
#: developer-duties.dbk:19
msgid ""
-"For more information about the database, please see <xref "
-"linkend=\"devel-db\"/>."
+"For more information about the database, please see <xref linkend=\"devel-db"
+"\"/>."
msgstr ""
#. type: Content of: <chapter><section><title>
#: developer-duties.dbk:26
msgid ""
"Be very careful with your private keys. Do not place them on any public "
-"servers or multiuser machines, such as the Debian servers (see <xref "
-"linkend=\"server-machines\"/>). Back your keys up; keep a copy offline. "
-"Read the documentation that comes with your software; read the <ulink "
-"url=\"&url-pgp-faq;\">PGP FAQ</ulink>."
+"servers or multiuser machines, such as the Debian servers (see <xref linkend="
+"\"server-machines\"/>). Back your keys up; keep a copy offline. Read the "
+"documentation that comes with your software; read the <ulink url=\"&url-pgp-"
+"faq;\">PGP FAQ</ulink>."
msgstr ""
#. type: Content of: <chapter><section><para>
"get the new key signed by another developer. If the old key is compromised "
"or invalid, you also have to add the revocation certificate. If there is no "
"real reason for a new key, the Keyring Maintainers might reject the new "
-"key. Details can be found at <ulink "
-"url=\"http://&keyserver-host;/replacing_keys.html\"></ulink>."
+"key. Details can be found at <ulink url=\"http://&keyserver-host;/"
+"replacing_keys.html\"></ulink>."
msgstr ""
#. type: Content of: <chapter><section><para>
#: developer-duties.dbk:52
msgid ""
-"The same key extraction routines discussed in <xref "
-"linkend=\"registering\"/> apply."
+"The same key extraction routines discussed in <xref linkend=\"registering\"/"
+"> apply."
msgstr ""
#. type: Content of: <chapter><section><para>
#: developer-duties.dbk:56
msgid ""
"You can find a more in-depth discussion of Debian key maintenance in the "
-"documentation of the <systemitem "
-"role=\"package\">debian-keyring</systemitem> package."
+"documentation of the <systemitem role=\"package\">debian-keyring</"
+"systemitem> package."
msgstr ""
#. type: Content of: <chapter><section><title>
msgid ""
"Even though Debian isn't really a democracy, we use a democratic process to "
"elect our leaders and to approve general resolutions. These procedures are "
-"defined by the <ulink url=\"&url-constitution;\">Debian "
-"Constitution</ulink>."
+"defined by the <ulink url=\"&url-constitution;\">Debian Constitution</ulink>."
msgstr ""
#. type: Content of: <chapter><section><para>
#. type: Content of: <chapter><section><para>
#: developer-duties.dbk:85
msgid ""
-"The list of all proposals (past and current) is available on the <ulink "
-"url=\"&url-vote;\">Debian Voting Information</ulink> page, along with "
+"The list of all proposals (past and current) is available on the <ulink url="
+"\"&url-vote;\">Debian Voting Information</ulink> page, along with "
"information on how to make, second and vote on proposals."
msgstr ""
msgid ""
"In order to inform the other developers, there are two things that you "
"should do. First send a mail to <email>debian-private@&lists-host;</email> "
-"with [VAC] prepended to the subject of your message<placeholder "
-"type=\"footnote\" id=\"0\"/> and state the period of time when you will be "
-"on vacation. You can also give some special instructions on what to do if a "
+"with [VAC] prepended to the subject of your message<placeholder type="
+"\"footnote\" id=\"0\"/> and state the period of time when you will be on "
+"vacation. You can also give some special instructions on what to do if a "
"problem occurs."
msgstr ""
"Assurance</ulink> group are following all such bugs, and trying to help "
"whenever possible. If, for any reason, you aren't able fix an RC bug in a "
"package of yours within 2 weeks, you should either ask for help by sending a "
-"mail to the Quality Assurance (QA) group "
-"<email>debian-qa@&lists-host;</email>, or explain your difficulties and "
-"present a plan to fix them by sending a mail to the bug report. Otherwise, "
-"people from the QA group may want to do a Non-Maintainer Upload (see <xref "
-"linkend=\"nmu\"/>) after trying to contact you (they might not wait as long "
-"as usual before they do their NMU if they have seen no recent activity from "
-"you in the BTS)."
+"mail to the Quality Assurance (QA) group <email>debian-qa@&lists-host;</"
+"email>, or explain your difficulties and present a plan to fix them by "
+"sending a mail to the bug report. Otherwise, people from the QA group may "
+"want to do a Non-Maintainer Upload (see <xref linkend=\"nmu\"/>) after "
+"trying to contact you (they might not wait as long as usual before they do "
+"their NMU if they have seen no recent activity from you in the BTS)."
msgstr ""
#. type: Content of: <chapter><section><title>
#. type: Content of: <chapter><section><orderedlist><listitem><para>
#: developer-duties.dbk:199
-msgid "Orphan all your packages, as described in <xref linkend=\"orphaning\"/>."
+msgid ""
+"Orphan all your packages, as described in <xref linkend=\"orphaning\"/>."
msgstr ""
#. type: Content of: <chapter><section><orderedlist><listitem><para>
~ianmdlvl / developers-reference.git / blobdiff