msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2010-05-31 19:21-0400\n"
+"POT-Creation-Date: 2010-06-03 21:58-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"
msgid ""
"Important news about changes in a package can also be put in "
"<filename>NEWS.Debian</filename> files. The news will be displayed by tools "
-"like apt-listchanges, before all the rest of the changelogs. This is the "
-"preferred means to let the user know about significant changes in a "
-"package. It is better than using debconf notes since it is less annoying "
-"and the user can go back and refer to the <filename>NEWS.Debian</filename> "
-"file after the install. And it's better than listing major changes in "
-"<filename>README.Debian</filename>, since the user can easily miss such "
-"notes."
+"like <systemitem role=\"package\">apt-listchanges</systemitem>, before all "
+"the rest of the changelogs. This is the preferred means to let the user "
+"know about significant changes in a package. It is better than using "
+"<systemitem role=\"package\">debconf</systemitem> notes since it is less "
+"annoying and the user can go back and refer to the "
+"<filename>NEWS.Debian</filename> file after the install. And it's better "
+"than listing major changes in <filename>README.Debian</filename>, since the "
+"user can easily miss such notes."
msgstr ""
#. type: Content of: <chapter><section><section><para>
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2010-05-06 17:34-0400\n"
+"POT-Creation-Date: 2010-06-03 21:58-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"
"reports that you submitted. Take this opportunity to close those that you "
"can't reproduce anymore. To find out all the bugs you submitted, you just "
"have to visit "
-"<literal>http://&bugs-host;/from:<replaceable><your-email-addr></replaceable></literal>."
+"<literal>http://&bugs-host;/from:<replaceable>your-email-addr</replaceable></literal>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
#: beyond-pkging.dbk:87
msgid ""
"Please use the programs <command>dd-list</command> and if appropriate "
-"<command>whodepends</command> (from the package devscripts) to generate a "
-"list of all affected packages, and include the output in your mail to "
-"&email-debian-devel;."
+"<command>whodepends</command> (from the package <systemitem "
+"role=\"package\">devscripts</systemitem>) to generate a list of all affected "
+"packages, and include the output in your mail to &email-debian-devel;."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#, no-wrap
msgid ""
"To: submit@bugs.debian.org\n"
-"Subject: <replaceable><title-of-bug></replaceable>\n"
+"Subject: <replaceable>title-of-bug</replaceable>\n"
"\n"
-"Package: <replaceable><pkgname></replaceable>\n"
+"Package: <replaceable>pkgname</replaceable>\n"
"<replaceable>[ ... ]</replaceable>\n"
-"User: <replaceable><email-addr></replaceable>\n"
-"Usertags: <replaceable><tag-name> [ <tag-name> "
-"... ]</replaceable>\n"
+"User: <replaceable>email-addr</replaceable>\n"
+"Usertags: <replaceable>tag-name [ tag-name ... ]</replaceable>\n"
"\n"
-"<replaceable><description-of-bug ...></replaceable>\n"
+"<replaceable>description-of-bug ...</replaceable>\n"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#: beyond-pkging.dbk:122
msgid ""
"Note that tags are seperated by spaces and cannot contain underscores. If "
-"you are filing bugs for for a particular group or team it is recommended "
-"that you set the <literal>User</literal> to an appropriate mailing list "
-"after describing your intention there."
+"you are filing bugs for a particular group or team it is recommended that "
+"you set the <literal>User</literal> to an appropriate mailing list after "
+"describing your intention there."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#: beyond-pkging.dbk:128
msgid ""
"To view bugs tagged with a specific usertag, visit "
-"<literal>http://&bugs-host;/cgi-bin/pkgreport.cgi?users=<replaceable><email-addr></replaceable>&tag=<replaceable><tag-name></replaceable></literal>."
+"<literal>http://&bugs-host;/cgi-bin/pkgreport.cgi?users=<replaceable>email-addr</replaceable>&tag=<replaceable>tag-name</replaceable></literal>."
msgstr ""
#. type: Content of: <chapter><section><title>
"Even though there is a dedicated group of people for Quality Assurance, QA "
"duties are not reserved solely for them. You can participate in this effort "
"by keeping your packages as bug-free as possible, and as lintian-clean (see "
-"<xref linkend=\"lintian\"/> ) as possible. If you do not find that "
-"possible, then you should consider orphaning some of your packages (see "
-"<xref linkend=\"orphaning\"/> ). Alternatively, you may ask the help of "
-"other people in order to catch up with the backlog of bugs that you have "
-"(you can ask for help on &email-debian-qa; or &email-debian-devel;). At the "
-"same time, you can look for co-maintainers (see <xref "
-"linkend=\"collaborative-maint\"/> )."
+"<xref linkend=\"lintian\"/>) as possible. If you do not find that possible, "
+"then you should consider orphaning some of your packages (see <xref "
+"linkend=\"orphaning\"/>). Alternatively, you may ask the help of other "
+"people in order to catch up with the backlog of bugs that you have (you can "
+"ask for help on &email-debian-qa; or &email-debian-devel;). At the same "
+"time, you can look for co-maintainers (see <xref "
+"linkend=\"collaborative-maint\"/>)."
msgstr ""
#. type: Content of: <chapter><section><section><title>
msgid ""
"Looking up the email address of the maintainer for the package can be "
"distracting. Fortunately, there is a simple email alias, "
-"<literal><package>@&packages-host;</literal>, which provides a way to "
-"email the maintainer, whatever their individual email address (or addresses) "
-"may be. Replace <literal><package></literal> with the name of a "
-"source or a binary package."
+"<literal><replaceable>package</replaceable>@&packages-host;</literal>, which "
+"provides a way to email the maintainer, whatever their individual email "
+"address (or addresses) may be. Replace <replaceable>package</replaceable> "
+"with the name of a source or a binary package."
msgstr ""
#. type: Content of: <chapter><section><para>
#: beyond-pkging.dbk:206
msgid ""
"You may also be interested in contacting the persons who are subscribed to a "
-"given source package via <xref linkend=\"pkg-tracking-system\"/> . You can "
-"do so by using the <literal><package>@&pts-host;</literal> email "
+"given source package via <xref linkend=\"pkg-tracking-system\"/>. You can "
+"do so by using the "
+"<literal><replaceable>package</replaceable>@&pts-host;</literal> email "
"address."
msgstr ""
"the QA group contacts an inactive maintainer or finds more information about "
"one, this is recorded in the MIA database. This system is available in "
"<filename>/org/qa.debian.org/mia</filename> on the host "
-"<literal>qa.debian.org </literal>, and can be queried with the "
+"<literal>qa.debian.org</literal>, and can be queried with the "
"<command>mia-query</command> tool. Use <command>mia-query --help</command> "
"to see how to query the database. If you find that no information has been "
"recorded about an inactive maintainer yet, or that you can add more "
#: beyond-pkging.dbk:310
msgid ""
"If you are interested in working in the MIA team, please have a look at the "
-"README file in <filename>/org/qa.debian.org/mia</filename> on <literal> "
-"qa.debian.org</literal> where the technical details and the MIA procedures "
-"are documented and contact &email-mia;."
+"<filename>README</filename> file in "
+"<filename>/org/qa.debian.org/mia</filename> on "
+"<literal>qa.debian.org</literal> where the technical details and the MIA "
+"procedures are documented and contact &email-mia;."
msgstr ""
#. type: Content of: <chapter><section><title>
"source and apply the diff yourself. In practice, you may want to use the "
"source package built by your sponsoree. In that case, you have to check "
"that they haven't altered the upstream files in the "
-"<filename>.orig.tar.gz</filename> file that they're providing."
+"<filename>.orig.tar.{gz,bz2,lzma}</filename> file that they're providing."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
#: beyond-pkging.dbk:392
msgid ""
-"The Maintainer field of the <filename>control</filename> file and the "
-"<filename>changelog</filename> should list the person who did the packaging, "
-"i.e., the sponsoree. The sponsoree will therefore get all the BTS mail "
-"about the package."
+"The <literal>Maintainer</literal> field of the <filename>control</filename> "
+"file and the <filename>changelog</filename> should list the person who did "
+"the packaging, i.e., the sponsoree. The sponsoree will therefore get all "
+"the BTS mail about the package."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: beyond-pkging.dbk:402
msgid ""
"You are encouraged to keep tabs on the package you sponsor using <xref "
-"linkend=\"pkg-tracking-system\"/> ."
+"linkend=\"pkg-tracking-system\"/>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2010-05-06 17:34-0400\n"
+"POT-Creation-Date: 2010-06-03 21:58-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"
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. "
+"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 ""
#: developer-duties.dbk:102
msgid ""
"Usually this means that other developers are allowed to NMU (see <xref "
-"linkend=\"nmu\"/> ) your package if a big problem (release critical bug, "
+"linkend=\"nmu\"/>) your package if a big problem (release critical bug, "
"security update, etc.) occurs while you're on vacation. Sometimes it's "
"nothing as critical as that, but it's still appropriate to let others know "
"that you're unavailable."
#. type: Content of: <chapter><section><para>
#: developer-duties.dbk:124
msgid ""
-"Ideally, you should sign up at the <ulink "
-"url=\"&url-newmaint-db;gpg.php\">GPG coordination site</ulink> when booking "
-"a holiday and check if anyone there is looking for signing. This is "
-"especially important when people go to exotic places where we don't have any "
-"developers yet but where there are people who are interested in applying."
+"Ideally, you should sign up at the <ulink url=\"&url-gpg-coord;\">GPG "
+"coordination pages</ulink> when booking a holiday and check if anyone there "
+"is looking for signing. This is especially important when people go to "
+"exotic places where we don't have any developers yet but where there are "
+"people who are interested in applying."
msgstr ""
#. type: Content of: <chapter><section><title>
#: developer-duties.dbk:166
msgid ""
"Generally you should deal with bug reports on your packages as described in "
-"<xref linkend=\"bug-handling\"/> . However, there's a special category of "
+"<xref linkend=\"bug-handling\"/>. However, there's a special category of "
"bugs that you need to take care of — the so-called release-critical bugs (RC "
"bugs). All bug reports that have severity <literal>critical</literal>, "
"<literal>grave</literal> or <literal>serious</literal> are considered to "
"<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 "
+"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><orderedlist><listitem><para>
#: developer-duties.dbk:200
-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>
#: developer-duties.dbk:211
msgid ""
"Notify the Debian key ring maintainers that you are leaving by opening a "
-"ticket in Debian RT by sending a mail to keyring@rt.debian.org with the "
-"words 'Debian RT' somewhere in the subject line (case doesn't matter)."
+"ticket in Debian RT by sending a mail to &email-keyring; with the words "
+"'Debian RT' somewhere in the subject line (case doesn't matter)."
msgstr ""
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2010-05-06 17:34-0400\n"
+"POT-Creation-Date: 2010-06-03 21:58-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"
#. type: Content of: <chapter><para>
#: l10n.dbk:17
msgid ""
-"According to <ulink "
-"url=\"http://&www-debian-org;/doc/manuals/intro-i18n/\">Introduction to "
-"i18n</ulink> from Tomohiro KUBOTA, I18N (internationalization) means "
-"modification of a software or related technologies so that a software can "
-"potentially handle multiple languages, customs, and so on in the world, "
-"while L10N (localization) means implementation of a specific language for an "
-"already internationalized software."
+"According to <ulink url=\"&url-i18n-intro;\">Introduction to i18n</ulink> "
+"from Tomohiro KUBOTA, I18N (internationalization) means modification of a "
+"software or related technologies so that a software can potentially handle "
+"multiple languages, customs, and so on in the world, while L10N "
+"(localization) means implementation of a specific language for an already "
+"internationalized software."
msgstr ""
#. type: Content of: <chapter><para>
msgid ""
"For program messages, the gettext infrastructure is used most of the time. "
"Most of the time, the translation is handled upstream within projects like "
-"the <ulink url=\"http://www.iro.umontreal.ca/contrib/po/HTML/\">Free "
-"Translation Project</ulink>, the <ulink "
-"url=\"http://developer.gnome.org/projects/gtp/\">Gnome translation "
-"Project</ulink> or the <ulink url=\"http://i18n.kde.org/\">KDE one</ulink>. "
-"The only centralized resource within Debian is the <ulink "
-"url=\"http://&www-debian-org;/intl/l10n/\">Central Debian translation "
-"statistics</ulink>, where you can find some statistics about the translation "
-"files found in the actual packages, but no real infrastructure to ease the "
-"translation process."
+"the <ulink url=\"&url-l10n-tp;\">Free Translation Project</ulink>, the "
+"<ulink url=\"&url-l10n-gnome;\">Gnome translation Project</ulink> or the "
+"<ulink url=\"&url-l10n-kde;\">KDE one</ulink>. The only centralized "
+"resource within Debian is the <ulink url=\"&url-l10n;\">Central Debian "
+"translation statistics</ulink>, where you can find some statistics about the "
+"translation files found in the actual packages, but no real infrastructure "
+"to ease the translation process."
msgstr ""
#. type: Content of: <chapter><section><para>
"very little support is offered by the tools to actually use them (i.e., only "
"APT can use them, when configured correctly). Maintainers don't need to do "
"anything special to support translated package descriptions; translators "
-"should use the <ulink url=\"http://ddtp.debian.org/\">DDTP</ulink>."
+"should use the <ulink url=\"&url-ddtp;\">Debian Description Translation "
+"Project (DDTP)</ulink>."
msgstr ""
#. type: Content of: <chapter><section><para>
#: l10n.dbk:66
msgid ""
-"For debconf templates, maintainers should use the po-debconf package to ease "
-"the work of translators, who could use the DDTP to do their work (but the "
-"French and Brazilian teams don't). Some statistics can be found both on the "
-"DDTP site (about what is actually translated), and on the <ulink "
-"url=\"http://&www-debian-org;/intl/l10n/\">Central Debian translation "
-"statistics</ulink> site (about what is integrated in the packages)."
+"For <systemitem role=\"package\">debconf</systemitem> templates, maintainers "
+"should use the <systemitem role=\"package\">po-debconf</systemitem> package "
+"to ease the work of translators, who could use the DDTP to do their work "
+"(but the French and Brazilian teams don't). Some statistics can be found "
+"both on the <ulink url=\"&url-ddtp;\">DDTP site</ulink> (about what is "
+"actually translated), and on the <ulink url=\"&url-l10n;\">Central Debian "
+"translation statistics</ulink> site (about what is integrated in the "
+"packages)."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: l10n.dbk:74
+#: l10n.dbk:75
msgid ""
-"For web pages, each l10n team has access to the relevant CVS, and the "
+"For web pages, each l10n team has access to the relevant VCS, and the "
"statistics are available from the Central Debian translation statistics "
"site."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: l10n.dbk:78
+#: l10n.dbk:79
msgid ""
"For general documentation about Debian, the process is more or less the same "
-"as for the web pages (the translators have access to the CVS), but there are "
+"as for the web pages (the translators have access to the VCS), but there are "
"no statistics pages."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: l10n.dbk:83
+#: l10n.dbk:84
msgid ""
"For package-specific documentation (man pages, info documents, other "
"formats), almost everything remains to be done."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: l10n.dbk:87
+#: l10n.dbk:88
msgid ""
"Most notably, the KDE project handles translation of its documentation in "
"the same way as its program messages."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: l10n.dbk:91
+#: l10n.dbk:92
msgid ""
"There is an effort to handle Debian-specific man pages within a <ulink "
-"url=\"&url-cvsweb;manpages/?cvsroot=debian-doc\">specific CVS "
+"url=\"&url-cvsweb;manpages/?cvsroot=debian-doc\">specific VCS "
"repository</ulink>."
msgstr ""
#. type: Content of: <chapter><section><title>
-#: l10n.dbk:98
+#: l10n.dbk:99
msgid "I18N & L10N FAQ for maintainers"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: l10n.dbk:100
+#: l10n.dbk:101
msgid ""
"This is a list of problems that maintainers may face concerning i18n and "
"l10n. While reading this, keep in mind that there is no real consensus on "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: l10n.dbk:107
+#: l10n.dbk:108
msgid "How to get a given text translated"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: l10n.dbk:109
+#: l10n.dbk:110
msgid ""
-"To translate package descriptions or debconf templates, you have nothing to "
-"do; the DDTP infrastructure will dispatch the material to translate to "
-"volunteers with no need for interaction from your part."
+"To translate package descriptions or <systemitem "
+"role=\"package\">debconf</systemitem> templates, you have nothing to do; the "
+"DDTP infrastructure will dispatch the material to translate to volunteers "
+"with no need for interaction from your part."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: l10n.dbk:114
+#: l10n.dbk:115
msgid ""
"For all other material (gettext files, man pages, or other documentation), "
"the best solution is to put your text somewhere on the Internet, and ask on "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: l10n.dbk:124
+#: l10n.dbk:125
msgid "How to get a given translation reviewed"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: l10n.dbk:126
+#: l10n.dbk:127
msgid ""
"From time to time, individuals translate some texts in your package and will "
"ask you for inclusion of the translation in the package. This can become "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: l10n.dbk:136
+#: l10n.dbk:137
msgid "How to get a given translation updated"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: l10n.dbk:138
+#: l10n.dbk:139
msgid ""
"If you have some translations of a given text lying around, each time you "
"update the original, you should ask the previous translator to update the "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: l10n.dbk:144
+#: l10n.dbk:145
msgid ""
"If the translator is unresponsive, you may ask for help on the corresponding "
"l10n mailing list. If everything fails, don't forget to put a warning in "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: l10n.dbk:150
+#: l10n.dbk:151
msgid ""
"Avoid removing a translation completely because it is outdated. Old "
"documentation is often better than no documentation at all for non-English "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: l10n.dbk:157
+#: l10n.dbk:158
msgid "How to handle a bug report concerning a translation"
msgstr ""
#. TODO: add the i18n tag to the bug?
#. type: Content of: <chapter><section><section><para>
-#: l10n.dbk:159
+#: l10n.dbk:160
msgid ""
"The best solution may be to mark the bug as forwarded to upstream, and "
"forward it to both the previous translator and his/her team (using the "
msgstr ""
#. type: Content of: <chapter><section><title>
-#: l10n.dbk:169
+#: l10n.dbk:170
msgid "I18N & L10N FAQ for translators"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: l10n.dbk:171
+#: l10n.dbk:172
msgid ""
"While reading this, please keep in mind that there is no general procedure "
"within Debian concerning these points, and that in any case, you should "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: l10n.dbk:176
+#: l10n.dbk:177
msgid "How to help the translation effort"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: l10n.dbk:178
+#: l10n.dbk:179
msgid ""
"Choose what you want to translate, make sure that nobody is already working "
"on it (using your debian-l10n-XXX mailing list), translate it, get it "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: l10n.dbk:186
+#: l10n.dbk:187
msgid "How to provide a translation for inclusion in a package"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: l10n.dbk:188
+#: l10n.dbk:189
msgid ""
"Make sure your translation is correct (asking for review on your l10n "
"mailing list) before providing it for inclusion. It will save time for "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: l10n.dbk:194
+#: l10n.dbk:195
msgid ""
"The best solution is to file a regular bug containing the translation "
"against the package. Make sure to use the 'PATCH' tag, and to not use a "
msgstr ""
#. type: Content of: <chapter><section><title>
-#: l10n.dbk:204
+#: l10n.dbk:205
msgid "Best current practice concerning l10n"
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: l10n.dbk:208
+#: l10n.dbk:209
msgid ""
"As a maintainer, never edit the translations in any way (even to reformat "
"the layout) without asking on the corresponding l10n mailing list. You risk "
-"for example breaksing the encoding of the file by doing so. Moreover, what "
+"for example breaking the encoding of the file by doing so. Moreover, what "
"you consider an error can be right (or even needed) in the given language."
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: l10n.dbk:216
+#: l10n.dbk:217
msgid ""
"As a translator, if you find an error in the original text, make sure to "
"report it. Translators are often the most attentive readers of a given "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: l10n.dbk:223
+#: l10n.dbk:224
msgid ""
"In any case, remember that the major issue with l10n is that it requires "
"several people to cooperate, and that it is very easy to start a flamewar "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: l10n.dbk:233
+#: l10n.dbk:234
msgid ""
"In any case, cooperation can only be achieved with <emphasis "
"role=\"strong\">mutual respect</emphasis>."
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2010-05-30 14:35-0400\n"
+"POT-Creation-Date: 2010-06-03 21:58-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"
"word <literal>subscribe</literal> in the <literal>Subject</literal> of an "
"email to &email-debian-devel-req;. In case of problems, contact the list "
"administrator at &email-listmaster;. More information on available mailing "
-"lists can be found in <xref linkend=\"mailing-lists\"/> . "
+"lists can be found in <xref linkend=\"mailing-lists\"/>. "
"&email-debian-devel-announce; is another list which is mandatory for anyone "
"who wishes to follow Debian's development."
msgstr ""
"Another good list to subscribe to is &email-debian-mentors;. See <xref "
"linkend=\"mentors\"/> for details. The IRC channel "
"<literal>#debian</literal> can also be helpful; see <xref "
-"linkend=\"irc-channels\"/> ."
+"linkend=\"irc-channels\"/>."
msgstr ""
#. type: Content of: <chapter><section><para>
#: new-maintainer.dbk:89
msgid ""
"If you wish to be a mentor and/or sponsor, more information is available in "
-"<xref linkend=\"newmaint\"/> ."
+"<xref linkend=\"newmaint\"/>."
msgstr ""
#. type: Content of: <chapter><section><title>
#. type: Content of: <chapter><section><para>
#: new-maintainer.dbk:150
msgid ""
-"Debian uses the <command>GNU Privacy Guard</command> (package <systemitem "
+"Debian uses the <literal>GNU Privacy Guard</literal> (package <systemitem "
"role=\"package\">gnupg</systemitem> version 1 or better) as its baseline "
"standard. You can use some other implementation of OpenPGP as well. Note "
"that OpenPGP is an open standard based on <ulink url=\"&url-rfc2440;\">RFC "
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2010-05-06 17:34-0400\n"
+"POT-Creation-Date: 2010-06-03 21:58-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"
"Most of the descriptions of these packages come from the actual package "
"descriptions themselves. Further information can be found in the package "
"documentation itself. You can also see more info with the command "
-"<command>apt-cache show <package-name></command>."
+"<command>apt-cache show <literal>package-name</literal></command>."
msgstr ""
#. type: Content of: <appendix><section><title>
#: tools.dbk:60
msgid ""
"Many feel that this system should be used for all packages which require "
-"interactive configuration; see <xref linkend=\"bpp-config-mgmt\"/> . "
+"interactive configuration; see <xref linkend=\"bpp-config-mgmt\"/>. "
"<systemitem role=\"package\">debconf</systemitem> is not currently required "
"by Debian Policy, but that may change in the future."
msgstr ""
#. type: Content of: <appendix><section><section><title>
#: tools.dbk:116
-msgid "<systemitem role=\"package\">debdiff</systemitem>"
+msgid "<command>debdiff</command>"
msgstr ""
#. type: Content of: <appendix><section><section><para>
msgid ""
"<command>debdiff</command> (from the <systemitem "
"role=\"package\">devscripts</systemitem> package, <xref "
-"linkend=\"devscripts\"/> ) compares file lists and control files of two "
+"linkend=\"devscripts\"/>) compares file lists and control files of two "
"packages. It is a simple regression test, as it will help you notice if the "
"number of binary packages has changed since the last upload, or if something "
"has changed in the control file. Of course, some of the changes it reports "
"<command>dh_make</command>, a program that creates a skeleton of files "
"necessary to build a Debian package out of a source tree. As the name "
"suggests, <command>dh_make</command> is a rewrite of <systemitem "
-"role=\"package\">debmake</systemitem> and its template files use dh_* "
-"programs from <systemitem role=\"package\">debhelper</systemitem>."
+"role=\"package\">debmake</systemitem> and its template files use "
+"<command>dh_*</command> programs from <systemitem "
+"role=\"package\">debhelper</systemitem>."
msgstr ""
#. type: Content of: <appendix><section><section><para>
#. type: Content of: <appendix><section><section><para>
#: tools.dbk:209
msgid ""
-"For more informations see <literal><ulink "
-"url=\"http://yada.alioth.debian.org/\">YADA site</ulink></literal>."
+"For more informations see <ulink "
+"url=\"http://yada.alioth.debian.org/\"><literal>YADA</literal> site</ulink>."
msgstr ""
#. type: Content of: <appendix><section><section><title>
#. type: Content of: <appendix><section><section><title>
#: tools.dbk:324
-msgid "<systemitem role=\"package\">dcut</systemitem>"
+msgid "<command>dcut</command>"
msgstr ""
#. type: Content of: <appendix><section><section><para>
#: tools.dbk:326
msgid ""
-"The <systemitem role=\"package\">dcut</systemitem> script (part of the "
-"package <xref linkend=\"dput\"/> ) helps in removing files from the ftp "
-"upload directory."
+"The <command>dcut</command> script (part of the package <systemitem "
+"role=\"package\">dput</systemitem>, <xref linkend=\"dput\"/>) helps in "
+"removing files from the ftp upload directory."
msgstr ""
#. type: Content of: <appendix><section><title>
#. type: Content of: <appendix><section><section><title>
#: tools.dbk:418
-msgid "<systemitem role=\"package\">dpkg-depcheck</systemitem>"
+msgid "<command>dpkg-depcheck</command>"
msgstr ""
#. type: Content of: <appendix><section><section><para>
msgid ""
"<command>dpkg-depcheck</command> (from the <systemitem "
"role=\"package\">devscripts</systemitem> package, <xref "
-"linkend=\"devscripts\"/> ) runs a command under <command>strace</command> "
-"to determine all the packages that were used by the said command."
+"linkend=\"devscripts\"/>) runs a command under <command>strace</command> to "
+"determine all the packages that were used by the said command."
msgstr ""
#. type: Content of: <appendix><section><section><para>
#: tools.dbk:435
msgid ""
"<command>dpkg-depcheck</command> can also be used to check for run-time "
-"dependencies, especially if your package uses exec(2) to run other programs."
+"dependencies, especially if your package uses <citerefentry> "
+"<refentrytitle>exec</refentrytitle> <manvolnum>2</manvolnum> </citerefentry> "
+"to run other programs."
msgstr ""
#. type: Content of: <appendix><section><section><para>
-#: tools.dbk:439
+#: tools.dbk:441
msgid ""
"For more information please see <citerefentry> "
"<refentrytitle>dpkg-depcheck</refentrytitle> <manvolnum>1</manvolnum> "
msgstr ""
#. type: Content of: <appendix><section><title>
-#: tools.dbk:448
+#: tools.dbk:450
msgid "Porting tools"
msgstr ""
#. type: Content of: <appendix><section><para>
-#: tools.dbk:450
+#: tools.dbk:452
msgid "The following tools are helpful for porters and for cross-compilation."
msgstr ""
#. type: Content of: <appendix><section><section><title>
-#: tools.dbk:453
+#: tools.dbk:455
msgid "<systemitem role=\"package\">quinn-diff</systemitem>"
msgstr ""
#. type: Content of: <appendix><section><section><para>
-#: tools.dbk:455
+#: tools.dbk:457
msgid ""
"<systemitem role=\"package\">quinn-diff</systemitem> is used to locate the "
"differences from one architecture to another. For instance, it could tell "
msgstr ""
#. type: Content of: <appendix><section><section><title>
-#: tools.dbk:463
+#: tools.dbk:465
msgid "<systemitem role=\"package\">dpkg-cross</systemitem>"
msgstr ""
#. type: Content of: <appendix><section><section><para>
-#: tools.dbk:465
+#: tools.dbk:467
msgid ""
"<systemitem role=\"package\">dpkg-cross</systemitem> is a tool for "
"installing libraries and headers for cross-compiling in a way similar to "
msgstr ""
#. type: Content of: <appendix><section><title>
-#: tools.dbk:476
+#: tools.dbk:478
msgid "Documentation and information"
msgstr ""
#. type: Content of: <appendix><section><para>
-#: tools.dbk:478
+#: tools.dbk:480
msgid ""
"The following packages provide information for maintainers or help with "
"building documentation."
msgstr ""
#. type: Content of: <appendix><section><section><title>
-#: tools.dbk:483
+#: tools.dbk:485
msgid "<systemitem role=\"package\">docbook-xml</systemitem>"
msgstr ""
#. type: Content of: <appendix><section><section><para>
-#: tools.dbk:485
+#: tools.dbk:487
msgid ""
"<systemitem role=\"package\">docbook-xml</systemitem> provides the DocBook "
"XML DTDs, which are commonly used for Debian documentation (as is the older "
msgstr ""
#. type: Content of: <appendix><section><section><para>
-#: tools.dbk:491
+#: tools.dbk:493
msgid ""
"The <systemitem role=\"package\">docbook-xsl</systemitem> package provides "
"the XSL files for building and styling the source to various output "
msgstr ""
#. type: Content of: <appendix><section><section><para>
-#: tools.dbk:499
+#: tools.dbk:501
msgid ""
"To produce PDF from FO, you need an FO processor, such as <systemitem "
"role=\"package\">xmlroff</systemitem> or <systemitem "
msgstr ""
#. type: Content of: <appendix><section><section><title>
-#: tools.dbk:507
+#: tools.dbk:509
msgid "<systemitem role=\"package\">debiandoc-sgml</systemitem>"
msgstr ""
#. type: Content of: <appendix><section><section><para>
-#: tools.dbk:509
+#: tools.dbk:511
msgid ""
"<systemitem role=\"package\">debiandoc-sgml</systemitem> provides the "
"DebianDoc SGML DTD, which is commonly used for Debian documentation, but is "
msgstr ""
#. type: Content of: <appendix><section><section><para>
-#: tools.dbk:518
+#: tools.dbk:520
msgid ""
"Documentation for the DTD can be found in the <systemitem "
"role=\"package\">debiandoc-sgml-doc</systemitem> package."
msgstr ""
#. type: Content of: <appendix><section><section><title>
-#: tools.dbk:524
+#: tools.dbk:526
msgid "<systemitem role=\"package\">debian-keyring</systemitem>"
msgstr ""
#. type: Content of: <appendix><section><section><para>
-#: tools.dbk:526
+#: tools.dbk:528
msgid ""
"Contains the public GPG and PGP keys of Debian developers. See <xref "
"linkend=\"key-maint\"/> and the package documentation for more information."
msgstr ""
#. type: Content of: <appendix><section><section><title>
-#: tools.dbk:532
+#: tools.dbk:534
msgid "<systemitem role=\"package\">debian-maintainers</systemitem>"
msgstr ""
#. type: Content of: <appendix><section><section><para>
-#: tools.dbk:534
+#: tools.dbk:536
msgid ""
"Contains the public GPG keys of Debian Maintainers. See <ulink "
"url=\"&url-wiki-dm;\"></ulink> for more information."
msgstr ""
#. type: Content of: <appendix><section><section><title>
-#: tools.dbk:540
+#: tools.dbk:542
msgid "<systemitem role=\"package\">debview</systemitem>"
msgstr ""
#. type: Content of: <appendix><section><section><para>
-#: tools.dbk:542
+#: tools.dbk:544
msgid ""
"<systemitem role=\"package\">debview</systemitem> provides an Emacs mode for "
"viewing Debian binary packages. This lets you examine a package without "
~ianmdlvl / developers-reference.git / commitdiff