"Project-Id-Version: developers-reference 3.4.3\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2010-06-01 15:39-0400\n"
-"PO-Revision-Date: 2010-06-05 09:34-0400\n"
+"PO-Revision-Date: 2010-06-20 08:00-0400\n"
"Last-Translator: David Prévot <david@tilapin.org>\n"
"Language-Team: French <debian-l10n-french@lists.debian.org>\n"
"Language: fr\n"
#. type: Content of: <chapter><section><section><title>
#: best-pkging-practices.dbk:716
msgid "Do not abuse debconf"
-msgstr ""
-"Proscrire les abus de <systemitem role=\"package\">debconf</systemitem>"
+msgstr "Proscrire les abus de <systemitem role=\"package\">debconf</systemitem>"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
#: best-pkging-practices.dbk:884
msgid "Change the debconf template file to fix the typo."
-msgstr ""
-"modifier le ficher d'écrans <systemitem role=\"package\">debconf</"
-"systemitem> (<filename>templates</filename>) pour corriger la faute de "
-"frappe ;"
+msgstr "modifier le fichier d'écrans <systemitem role=\"package\">debconf</systemitem> (<filename>templates</filename>) pour corriger la faute de frappe ;"
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
# type: Content of: <chapter><section><section><section><section><para>
#. type: Content of: <chapter><section><section><section><section><para>
#: best-pkging-practices.dbk:1012
-msgid ""
-"Results in a free-form input field that the user can type any string into."
+msgid "Results in a free-form input field that the user can type any string into."
msgstr ""
"offre un champ de saisie où l'utilisateur peut entrer n'importe quelle "
"chaîne de caractères."
#. type: Content of: <chapter><section><section><title>
#: best-pkging-practices.dbk:1371
msgid "Handling debconf translations"
-msgstr ""
-"Gestion des traductions <systemitem role=\"package\">debconf</systemitem>"
+msgstr "Gestion des traductions <systemitem role=\"package\">debconf</systemitem>"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><title>
#: best-pkging-practices.dbk:1455
msgid "Packages using <command>autoconf</command>/<command>automake</command>"
-msgstr ""
-"Paquets utilisant <command>autoconf</command> ou <command>automake</command>"
+msgstr "Paquets utilisant <command>autoconf</command> ou <command>automake</command>"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
#, no-wrap
msgid "Depends: libfoo (= ${binary:Version})\n"
msgstr "Depends: libtruc (= ${binary:Version})\n"
+
#: developer-duties.dbk:19
msgid ""
"For more information about the database, please see <xref linkend=\"devel-db"
-"\"/> ."
+"\"/>."
msgstr ""
"Pour plus d'informations sur cette base de données, veuillez consulter <xref "
"linkend=\"devel-db\"/>."
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
#: pkgs.dbk:864
msgid ""
-"Any fixed packages that you have prepared yourself (send only the <literal>."
-"diff.gz</literal> and <literal>.dsc</literal> files and read <xref linkend="
+"Any fixed packages that you have prepared yourself (send only the <filename>."
+"diff.gz</filename> and <filename>.dsc</filename> files and read <xref linkend="
"\"bug-security-building\"/> first)"
msgstr ""
"tout paquet corrigé préparé par vous-même (envoyez seulement les fichiers "
-"<literal>.diff.gz</literal> et <literal>.dsc</literal> et lisez d'abord "
+"<filename>.diff.gz</filename> et <filename>.dsc</filename> et lisez d'abord "
"<xref linkend=\"bug-security-building\"/>) ;"
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
msgid ""
"The archive maintenance software will also send the OpenPGP/GnuPG signed "
"<filename>.changes</filename> file that you uploaded to the appropriate "
-"mailing lists. If a package is released with the <literal>Distribution:</"
+"mailing lists. If a package is released with the <literal>Distribution</"
"literal> set to <literal>stable</literal>, the announcement is sent to "
-"&email-debian-changes;. If a package is released with <literal>Distribution:"
+"&email-debian-changes;. If a package is released with <literal>Distribution"
"</literal> set to <literal>unstable</literal> or <literal>experimental</"
"literal>, the announcement will be posted to &email-debian-devel-changes; "
"instead."
msgstr ""
"Le logiciel de maintenance de l'archive enverra également le fichier "
"<filename>.changes</filename> signé avec OpenPGP/GnuPG à la liste de "
-"diffusion appropriée. Pour un paquet avec le champ <literal>Distribution:</"
+"diffusion appropriée. Pour un paquet avec le champ <literal>Distribution</"
"literal> à « <literal>stable</literal> », l'annonce sera envoyée à &email-"
-"debian-changes;. Pour un paquet avec le champ <literal>Distribution:</"
+"debian-changes;. Pour un paquet avec le champ <literal>Distribution</"
"literal> à « <literal>unstable</literal> » ou « <literal>experimental</"
"literal> », l'annonce sera envoyée à &email-debian-devel-changes;."
"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 <literal>package-name</literal></command>."
+"<command>apt-cache show <replaceable>package-name</replaceable></command>."
msgstr ""
"La plupart des descriptions de ces outils proviennent des descriptions de "
"leurs paquets. Vous trouverez plus d'informations dans les documentations de "
"From time to time you may want to check what has been going on with the bug "
"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>."
+"have to visit <literal>http://&bugs-host;/from:<replaceable>your-email-"
+"addr</replaceable></literal>."
msgstr ""
"時折、あなたが報告したバグ報告について何が起こっているのかをチェックしたくな"
"ることでしょう。これは、もう再現できないものをクローズするきっかけになりま"
"す。報告した全てのバグ報告を確認するには、<literal>http://&bugs-host;/from:"
-"<replaceable><your-email-addr></replaceable></literal> を参照すればいい"
+"<replaceable>your-email-addr</replaceable></literal> を参照すればいい"
"だけです。"
# 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 "
+"<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 ""
"<command>dd-list</command> プログラムを利用するのと、明確になっているのであれ"
-"ば影響を受けるパッケージのリストを (devscripts パッケージの) "
+"ば影響を受けるパッケージのリストを (<systemitem role=\"package"
+"\">devscripts</systemitem> パッケージの) "
"<command>whodepends</command> を使って出力して、&email-debian-devel; へのメー"
"ルに含めて下さい。"
#, 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 ""
"To: submit@bugs.debian.org\n"
-"Subject: <replaceable><バグタイトル></replaceable>\n"
+"Subject: <replaceable>バグタイトル</replaceable>\n"
"\n"
-"Package: <replaceable><パッケージ名></replaceable>\n"
+"Package: <replaceable>パッケージ名</replaceable>\n"
"<replaceable>[ ... ]</replaceable>\n"
-"User: <replaceable><メールアドレス></replaceable>\n"
-"Usertags: <replaceable><タグ名> [ <タグ名> ... ]</replaceable>\n"
+"User: <replaceable>メールアドレス</replaceable>\n"
+"Usertags: <replaceable>タグ名 [ タグ名 ... ]</replaceable>\n"
"\n"
-"<replaceable><バグの説明 ...></replaceable>\n"
+"<replaceable>バグの説明 ...</replaceable>\n"
#. 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 "
+"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 ""
#: 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>."
+"host;/cgi-bin/pkgreport.cgi?users=<replaceable>email-addr</"
+"replaceable>&tag=<replaceable>tag-name</replaceable></literal>."
msgstr ""
"特定の usertag でバグを参照する場合は <literal>http://&bugs-host;/cgi-bin/"
-"pkgreport.cgi?users=<replaceable><メールアドレス></replaceable>&"
-"tag=<replaceable><タグ名></replaceable></literal> を指定してください。"
+"pkgreport.cgi?users=<replaceable>メールアドレス</replaceable>&"
+"tag=<replaceable>タグ名</replaceable></literal> を指定してください。"
# type: Content of: <chapter><section><title>
#. 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 "
+"<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 "
+"<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\"/> )."
+"\"collaborative-maint\"/>)."
msgstr ""
"品質保証に割り当てられたグループの人々がいたとしても、QA 作業は彼らのみに課せ"
"られるものではありません。あなたもパッケージを可能な限りバグが無いように保"
#: beyond-pkging.dbk:198
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 "
+"distracting. Fortunately, there is a simple email alias, "
+"<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 ""
"パッケージメンテナのメールアドレスを探しだすのは骨が折れます。幸いな事に、"
-"<literal><package>@&packages-host;</literal> というシンプルなメールのエ"
+"<literal><replaceable>package</replaceable>@&packages-host;</literal> というシンプルなメールのエ"
"イリアスがあり、メンテナらの個人アドレスが何であれメンテナへメールを届ける手"
-"段となっています。<literal><package></literal> はパッケージのソース名か"
+"段となっています。<replaceable>package</replaceable> はパッケージのソース名か"
"バイナリパッケージ名に置き換えてください。"
# 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 ""
"<xref linkend=\"pkg-tracking-system\"/> 経由でソースパッケージの購読を行って"
-"いる人に連絡を取りたくなるかもしれません。その場合は <literal><package>"
+"いる人に連絡を取りたくなるかもしれません。その場合は <literal><replaceable>package</replaceable>"
"@&pts-host;</literal> メールアドレスが使えます。"
# type: Content of: <chapter><section><title>
"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 <command>mia-query</command> "
+"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 information, you should "
#: 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."
+"<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 ""
"MIA チームで働くのに興味を持った場合は、技術上の詳細と MIA の手順が記載されて"
"いる <literal>qa.debian.org</literal> 上の <filename>/org/qa.debian.org/mia</"
-"filename> 内の README ファイルを参照して、&email-mia; に連絡を取ってくださ"
+"filename> 内の <filename>README</filename> ファイルを参照して、&email-mia; に連絡を取ってくださ"
"い。"
# type: Content of: <chapter><section><title>
"location of the original source tarball, and then you should download the "
"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</"
+"that they haven't altered the upstream files in the <filename>.orig.tar.{gz,bz2,lzma}</"
"filename> file that they're providing."
msgstr ""
"あなたは、スポンサー対象者からの <filename>.deb</filename> バイナリを単にアッ"
"プロードすることはできません。通常、diff ファイルとオリジナルのソース tar "
"ファイルを要求して、それから自分でソースをダウンロードして diff を適用する必"
"要があります。実際には、スポンサー対象者が生成したソースパッケージを使うとい"
-"うことです。この場合、彼らが提供した <filename>.orig.tar.gz</filename> ファイ"
+"うことです。この場合、彼らが提供した <filename>.orig.tar.{gz,bz2,lzma}</filename> ファイ"
"ル中の開発元 (upstream) を改変していないことをチェックする必要があります。"
# 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 ""
"<xref linkend=\"pkg-tracking-system\"/> を使って、スポンサーしたパッケージの"
"状況を把握するのをお勧めします。"
#: developer-duties.dbk:19
msgid ""
"For more information about the database, please see <xref linkend=\"devel-db"
-"\"/> ."
+"\"/>."
msgstr ""
"データベースについての詳細は <xref linkend=\"devel-db\"/> を参照してくださ"
"い。"
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 "
+"\"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 "
+"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 ""
-"理想的には、休暇にあわせて <ulink url=\"&url-newmaint-db;gpg.php\">GPG "
-"coordination site</ulink> に登録して、誰かサインを希望している人がいるかどう"
+"理想的には、休暇にあわせて <ulink url=\"&url-gpg-coord;\">GPG "
+"coordination pages</ulink> に登録して、誰かサインを希望している人がいるかどう"
"かをチェックします。開発者がまだ誰もいないけれども応募に興味を持っている人が"
"いるようなエキゾチックな場所に行く場合、これは特に重要です。"
#: 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 "
"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 "
+"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><orderedlist><listitem><para>
#: developer-duties.dbk:200
msgid ""
-"Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ."
+"Orphan all your packages, as described in <xref linkend=\"orphaning\"/>."
msgstr ""
"<xref linkend=\"orphaning\"/> の記述にしたがって、全てのパッケージをみなしご"
"化 (orphan) してください。"
#: 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 "
+"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 ""
"'Debian RT' という単語 (大文字小文字は関係なし) が入ったメールを keyring@rt."
#. type: Content of: <chapter><para>
#: l10n.dbk:17
msgid ""
-"According to <ulink url=\"http://&www-debian-org;/doc/manuals/intro-i18n/"
+"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, "
"implementation of a specific language for an already internationalized "
"software."
msgstr ""
-"久保田智広さんによる <ulink url=\"http://&www-debian-org;/doc/manuals/intro-i18n/"
+"久保田智広さんによる <ulink url=\"&url-i18n-intro;"
"\">Introduction to i18n</ulink> によると、I18N (internationalization) は"
"ソフトウェアや関連する技術を調整し、ソフトウェアが複数の言語、習慣、その他世界の物事"
"などを扱えるようにすることで、対して L10N (localization) は既に国際化されている"
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 "
+"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 ""
"プログラムのメッセージについては、ほとんどが gettext という仕組みが使われて"
-"います。多くの場合、翻訳は <ulink url=\"http://www.iro.umontreal.ca/contrib/po/HTML/\">"
-"Free Translation Project</ulink> や <ulink url=\"http://developer.gnome.org/projects/gtp/\">"
-"Gnome translation Project</ulink>、<ulink url=\"http://i18n.kde.org/\">KDE one</ulink> "
+"います。多くの場合、翻訳は <ulink url=\"&url-l10n-tp;\">"
+"Free Translation Project</ulink> や <ulink url=\"&url-l10n-gnome;\">"
+"Gnome translation Project</ulink>、<ulink url=\"&url-l10n-kde;/\">KDE one</ulink> "
"などの開発元 (upstream) のプロジェクトで取り扱われています。Debian で唯一の集約化"
-"された情報は <ulink url=\"http://&www-debian-org;/intl/l10n/\">Debian の翻訳に関する統計</ulink>"
+"された情報は <ulink url=\"&url-l10n;\">Debian の翻訳に関する統計</ulink>"
"で、実際のパッケージ内での翻訳ファイルの状況について確認できますが、翻訳作業を実際に"
"容易にする仕組みではありません。"
"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;\">DDTP</ulink>."
msgstr ""
# type: Content of: <chapter><section><para>
#. type: Content of: <chapter><section><para>
#: l10n.dbk:74
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 ""
-"ウェブページについては、それぞれの l10n チームが対応する CVS にアクセスし、"
+"ウェブページについては、それぞれの l10n チームが対応する VCS にアクセスし、"
"Debian の翻訳に関する統計サイトから統計情報が取得できます。"
# type: Content of: <chapter><section><para>
#: l10n.dbk:78
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 ""
"Debian についての一般的なドキュメントは、作業は多少の差はあれウェブページと"
-"同じです (翻訳者は CVS にアクセスします)。ですが、統計情報のページはありません。"
+"同じです (翻訳者は VCS にアクセスします)。ですが、統計情報のページはありません。"
# type: Content of: <chapter><section><para>
#. type: Content of: <chapter><section><para>
#: l10n.dbk:91
msgid ""
"There is an effort to handle Debian-specific man pages within a <ulink url="
-"\"&url-cvsweb;manpages/?cvsroot=debian-doc\">specific CVS repository</ulink>."
+"\"&url-cvsweb;manpages/?cvsroot=debian-doc\">specific VCS repository</ulink>."
msgstr ""
"Debian 固有の man ページを <ulink url=\"&url-cvsweb;manpages/?cvsroot=debian-doc\">"
-"特定の CVS リポジトリ</ulink> で取り扱おうという動きもあります。"
+"特定の VCS リポジトリ</ulink> で取り扱おうという動きもあります。"
# type: Content of: <chapter><section><title>
#. type: Content of: <chapter><section><title>
"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\"/> . &email-debian-"
+"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 ""
msgid ""
"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\"/> ."
+"literal> can also be helpful; see <xref linkend=\"irc-channels\"/>."
msgstr ""
"もう一つ、購読すると良いのが &email-debian-mentors; です。詳細は <xref "
"linkend=\"mentors\"/> を参照してください。IRC チャンネル <literal>#debian</"
#: 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 ""
"メンターあるいはスポンサーになりたいという人は、<xref linkend=\"newmaint\"/> "
"でより詳細な情報が手に入ります。"
#. 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 "
"2440</ulink>."
msgstr ""
-"Debian では <command>GNU Privacy Guard</command> (<systemitem role=\"package"
+"Debian では <literal>GNU Privacy Guard</literal> (<systemitem role=\"package"
"\">gnupg</systemitem> パッケージ、バージョン 1 以降) を標準として利用していま"
"す。他の OpenPGP 実装も同様に利用できます。OpenPGP は <ulink url=\"&url-"
"rfc2440;\">RFC 2440</ulink> に準拠した公開標準です。"
msgid ""
"You need a version 4 key for use in Debian Development. Your key length "
"must be at least 1024 bits; there is no reason to use a smaller key, and "
-"doing so would be much less secure.
<placeholder type=\"footnote\" id=\"0\"/"
+"doing so would be much less secure.<placeholder type=\"footnote\" id=\"0\"/"
">"
msgstr ""
"Debian での開発においては、バージョン 4 の鍵の利用が求められます。鍵の長さは"
"少なくとも 1024 ビットが必要です。それより短い鍵を利用する理由は何もありませ"
-"んし、使った場合はあまり安全ではなくなります。
<placeholder type=\"footnote\" "
+"んし、使った場合はあまり安全ではなくなります。<placeholder type=\"footnote\" "
"id=\"0\"/>"
# type: Content of: <chapter><section><para>
#: pkgs.dbk:23
msgid ""
"Assuming no one else is already working on your prospective package, you "
-"must then submit a bug report (<xref linkend=\"submit-bug\"/> ) against the "
+"must then submit a bug report (<xref linkend=\"submit-bug\"/>) against the "
"pseudo-package <systemitem role=\"package\">wnpp</systemitem> describing "
"your plan to create a new package, including, but not limiting yourself to, "
"a description of the package, the license of the prospective package, and "
#. type: Content of: <chapter><section><para>
#: pkgs.dbk:45
msgid ""
-"Please include a <literal>Closes: bug#<replaceable>nnnnn</replaceable></"
+"Please include a <literal>Closes: #<replaceable>nnnnn</replaceable></"
"literal> entry in the changelog of the new package in order for the bug "
"report to be automatically closed once the new package is installed in the "
-"archive (see <xref linkend=\"upload-bugfix\"/> )."
+"archive (see <xref linkend=\"upload-bugfix\"/>)."
msgstr ""
"新規パッケージがアーカイブへインストールされる際にバグ報告を自動的に閉じるた"
-"め、<literal>Closes: bug#<replaceable>nnnnn</replaceable></literal> というエ"
+"め、<literal>Closes: #<replaceable>nnnnn</replaceable></literal> というエ"
"ントリを新規パッケージの changelog 内に含めてください (<xref linkend="
"\"upload-bugfix\"/> を参照)。"
msgid ""
"If you think your package needs some explanations for the administrators of "
"the NEW package queue, include them in your changelog, send to "
-"ftpmaster@debian.org a reply to the email you receive as a maintainer after "
+"&email-ftpmaster; a reply to the email you receive as a maintainer after "
"your upload, or reply to the rejection email in case you are already re-"
"uploading."
msgstr ""
"パッケージについて、NEW パッケージキューの管理者への説明が必要だろうと思う場"
"合は、アップロード後にメンテナとして受け取るメールへの返信、あるいは既に再"
"アップロードという場合は reject のメールに対しての返信として、説明を "
-"changelog に含めて ftpmaster@debian.org へ送ってください。"
+"changelog に含めて &email-ftpmaster; へ送ってください。"
# type: Content of: <chapter><section><para>
#. type: Content of: <chapter><section><para>
#: pkgs.dbk:57
msgid ""
-"When closing security bugs include CVE numbers as well as the Closes: "
-"#nnnnn. This is useful for the security team to track vulnerabilities. If "
+"When closing security bugs include CVE numbers as well as the <literal>Closes: "
+"#<replaceable>nnnnn</replaceable></literal>. This is useful for the security team to track vulnerabilities. If "
"an upload is made to fix the bug before the advisory ID is known, it is "
"encouraged to modify the historical changelog entry with the next upload. "
"Even in this case, please include all available pointers to background "
"information in the original changelog entry."
msgstr ""
-"セキュリティバグを閉じる場合は、CVE 番号を Closes: #nnnnnn と同じく含める"
+"セキュリティバグを閉じる場合は、CVE 番号を <literal>Closes: #<replaceable>nnnnn</replaceable></literal> と同じく含める"
"ようにしてください。これは、セキュリティチームが脆弱性を追跡するのに役立ちま"
"す。アドバイザリの ID が分かる前にバグ修正のためのアップロードが行われた場合"
"は、以前の changelog エントリを次のアップロード時に修正するのが推奨されていま"
"The <filename>debian/changelog</filename> file conforms to a certain "
"structure, with a number of different fields. One field of note, the "
"<literal>distribution</literal>, is described in <xref linkend=\"distribution"
-"\"/> . More information about the structure of this file can be found in "
+"\"/>. More information about the structure of this file can be found in "
"the Debian Policy section titled <filename>debian/changelog</filename>."
msgstr ""
"<filename>debian/changelog</filename> ファイルは、幾つもの異なった項目からなる"
msgid ""
"Changelog entries can be used to automatically close Debian bugs when the "
"package is installed into the archive. See <xref linkend=\"upload-bugfix\"/"
-"> ."
+">."
msgstr ""
"changelog への記載は、パッケージがアーカイブにインストールされる際、自動的に "
"Debian バグを閉じるのに利用できます。<xref linkend=\"upload-bugfix\"/> を参照"
#. type: Content of: <chapter><section><screen>
#: pkgs.dbk:137
#, no-wrap
-msgid " * new upstream version\n"
-msgstr " * new upstream version\n"
+msgid " * New upstream release.\n"
+msgstr " * New upstream release.\n"
# type: Content of: <chapter><section><para>
#. type: Content of: <chapter><section><para>
msgid ""
"There are tools to help you create entries and finalize the "
"<filename>changelog</filename> for release — see <xref linkend=\"devscripts"
-"\"/> and <xref linkend=\"dpkg-dev-el\"/> ."
+"\"/> and <xref linkend=\"dpkg-dev-el\"/>."
msgstr ""
"<filename>changelog</filename> エントリの作成と仕上げ処理に使えるツールがあります。"
"<xref linkend=\"devscripts\"/> と <xref linkend=\"dpkg-dev-el\"/> を参照してください。"
# type: Content of: <chapter><section><para>
#. type: Content of: <chapter><section><para>
#: pkgs.dbk:145
-msgid "See also <xref linkend=\"bpp-debian-changelog\"/> ."
+msgid "See also <xref linkend=\"bpp-debian-changelog\"/>."
msgstr "<xref linkend=\"bpp-debian-changelog\"/> も参照してください。"
# type: Content of: <chapter><section><title>
#: pkgs.dbk:179
msgid ""
"For more information on <command>lintian</command>, see <xref linkend="
-"\"lintian\"/> ."
+"\"lintian\"/>."
msgstr ""
"<command>lintian</command> についての詳細は、<xref linkend=\"lintian\"/> を参"
"照してください。"
"Copy the source package in a different directory and try unpacking it and "
"rebuilding it. This tests if the package relies on existing files outside "
"of it, or if it relies on permissions being preserved on the files shipped "
-"inside the .diff.gz file."
+"inside the <filename>.diff.gz</filename> file."
msgstr ""
"ソースパッケージを違うディレクトリにコピーして展開し、再構築する。これは、"
-"パッケージが外部の既存ファイルに依っているか、.diff.gz ファイル内に含"
+"パッケージが外部の既存ファイルに依っているか、<filename>.diff.gz</filename> ファイル内に含"
"まれているファイルで保存されている権限に依るかどうかをテストします。"
# type: Content of: <chapter><section><title>
#FIXME: control ファイル？コントロールファイル？
msgid ""
"For the native packages, the source package includes a Debian source control "
-"file (<literal>.dsc</literal>) and the source tarball (<literal>.tar.{gz,bz2,"
-"lzma}</literal>). A source package of a non-native package includes a Debian "
-"source control file, the original source tarball (<literal>.orig.tar.{gz,bz2,"
-"lzma}</literal>) and the Debian changes (<literal>.diff.gz</literal> for the "
-"source format “1.0” or <literal>.debian.tar.{gz,bz2,lzma}</literal> for the "
+"file (<filename>.dsc</filename>) and the source tarball (<filename>.tar.{gz,bz2,"
+"lzma}</filename>). A source package of a non-native package includes a Debian "
+"source control file, the original source tarball (<filename>.orig.tar.{gz,bz2,"
+"lzma}</filename>) and the Debian changes (<filename>.diff.gz</filename> for the "
+"source format “1.0” or <filename>.debian.tar.{gz,bz2,lzma}</filename> for the "
"source format “3.0 (quilt)”)."
msgstr ""
"native パッケージの場合、ソースパッケージは Debian のソース control ファイル "
-"(<literal>.dsc</literal>) とソースコードの tarball (<literal>.tar.{gz,bz2,lzma}"
-"</literal>) を含んでいます。native ではないパッケージのソースパッケージは Debian "
-"のソース control ファイルと、オリジナルのソースコードの tarball (<literal>.orig."
-"tar.{gz,bz2,lzma}</literal>)、そして Debian での変更点 (ソース形式“1.0”は "
-"<literal>.diff.gz</literal>、ソース形式“3.0 (quilt)”は <literal>.debian.tar"
-".{gz,bz2,lzma}</literal>) を含んでいます。"
+"(<filename>.dsc</filename>) とソースコードの tarball (<filename>.tar.{gz,bz2,lzma}"
+"</filename>) を含んでいます。native ではないパッケージのソースパッケージは Debian "
+"のソース control ファイルと、オリジナルのソースコードの tarball (<filename>.orig."
+"tar.{gz,bz2,lzma}</filename>)、そして Debian での変更点 (ソース形式“1.0”は "
+"<filename>.diff.gz</filename>、ソース形式“3.0 (quilt)”は <filename>.debian.tar"
+".{gz,bz2,lzma}</filename>) を含んでいます。"
#. type: Content of: <chapter><section><para>
#: pkgs.dbk:240
"Each upload needs to specify which distribution the package is intended "
"for. The package build process extracts this information from the first "
"line of the <filename>debian/changelog</filename> file and places it in the "
-"<literal>Distribution</literal> field of the <literal>.changes</literal> "
+"<literal>Distribution</literal> field of the <filename>.changes</filename> "
"file."
msgstr ""
"アップロードでは、パッケージがどのディストリビューション向けになっているかを"
"指定してあることが必要です。パッケージの構築プロセスでは、<filename>debian/"
-"changelog</filename> ファイルの最初の行からこの情報を展開し、<literal>."
-"changes</literal> ファイルの <literal>Distribution</literal> 欄に配置します。"
+"changelog</filename> ファイルの最初の行からこの情報を展開し、<filename>."
+"changes</filename> ファイルの <literal>Distribution</literal> 欄に配置します。"
# type: Content of: <chapter><section><para>
#. type: Content of: <chapter><section><para>
#: pkgs.dbk:292
msgid ""
"Actually, there are two other possible distributions: <literal>stable-"
-"security </literal> and <literal>testing-security</literal>, but read <xref "
+"security</literal> and <literal>testing-security</literal>, but read <xref "
"linkend=\"bug-security\"/> for more information on those."
msgstr ""
"実際には、他に二つ指定可能なディストリビューションがあります: "
-"<literal>stable-security </literal> と <literal>testing-security</literal> で"
+"<literal>stable-security</literal> と <literal>testing-security</literal> で"
"すが、これらについての詳細は <xref linkend=\"bug-security\"/> を読んでくださ"
"い。"
#: pkgs.dbk:407
msgid ""
"For removing packages, please see <ulink url=\"ftp://&ftp-upload-host;"
-"&upload-queue;/README\"/> and the Debian package <xref linkend=\"dcut\"/> ."
+"&upload-queue;/README\"/> and the Debian package <xref linkend=\"dcut\"/>."
msgstr ""
# type: Content of: <chapter><section><section><title>
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
"upload queue (<literal>oldstable-security</literal>, <literal>stable-"
-"security </literal>, etc.) without prior authorization from the security "
+"security</literal>, etc.) without prior authorization from the security "
"team. If the package does not exactly meet the team's requirements, it will "
"cause many problems and delays in dealing with the unwanted upload. For "
-"details, please see section <xref linkend=\"bug-security\"/> ."
+"details, please see section <xref linkend=\"bug-security\"/>."
msgstr ""
"セキュリティアップロードキュー (<literal>oldstable-security</literal>、"
-"<literal>stable-security </literal> 等) には、セキュリティチームからの事前許"
+"<literal>stable-security</literal> 等) には、セキュリティチームからの事前許"
"可無しにパッケージを<emphasis role=\"strong\">アップロードしないでください</"
"emphasis>。パッケージがチームの要求に完全に合致していない場合、望まれないアッ"
"プロードに対処するために多くの問題が引き起こされたり遅延が生じることになりま"
msgid ""
"Note that the <literal>Section</literal> field describes both the section as "
"well as the subsection, which are described in <xref linkend=\"archive-"
-"sections\"/> . If the section is main, it should be omitted. The list of "
+"sections\"/>. If the section is main, it should be omitted. The list of "
"allowable subsections can be found in <ulink url=\"&url-debian-policy;ch-"
"archive.html#s-subsections\"></ulink>."
msgstr ""
msgid ""
"Every developer has to be able to work with the Debian <ulink url=\"&url-bts;"
"\">bug tracking system</ulink>. This includes knowing how to file bug "
-"reports properly (see <xref linkend=\"submit-bug\"/> ), how to update them "
+"reports properly (see <xref linkend=\"submit-bug\"/>), how to update them "
"and reorder them, and how to process and close them."
msgstr ""
"すべての開発者は Debian <ulink url=\"&url-bts;\">バグ追跡システム</ulink>を取"
msgid ""
"When responding to bugs, make sure that any discussion you have about bugs "
"is sent both to the original submitter of the bug, and to the bug itself (e."
-"g., <email>123@&bugs-host;</email>). If you're writing a new mail and you "
-"don't remember the submitter email address, you can use the <email>123-"
+"g., <email><replaceable>123</replaceable>@&bugs-host;</email>). If you're writing a new mail and you "
+"don't remember the submitter email address, you can use the <email><replaceable>123</replaceable>-"
"submitter@&bugs-host;</email> email to contact the submitter <emphasis>and</"
"emphasis> to record your mail within the bug log (that means you don't need "
-"to send a copy of the mail to <email>123@&bugs-host;</email>)."
+"to send a copy of the mail to <email><replaceable>123</replaceable>@&bugs-host;</email>)."
msgstr ""
"バグに対応する際は、バグについて行った議論がバグの元々の報告者とバグ自身 (例"
-"えば <email>123@&bugs-host;</email>) の両方に送られているのを確認してくださ"
+"えば <email><replaceable>123</replaceable>@&bugs-host;</email>) の両方に送られているのを確認してくださ"
"い。新しくメールを書いていて元々の報告者のメールアドレスを思い出せない場合"
-"は、<email>123-submitter@&bugs-host;</email> というメールアドレスを報告者へ連"
+"は、<email><replaceable>123</replaceable>-submitter@&bugs-host;</email> というメールアドレスを報告者へ連"
"絡するのに使えます。<emphasis>さらに</emphasis>バグのログへあなたのメールを記"
-"録するのにも使えます (これは <email>123@&bugs-host;</email> へメールのコピー"
+"録するのにも使えます (これは <email><replaceable>123</replaceable>@&bugs-host;</email> へメールのコピー"
"を送らなくても済むことを意味しています)。"
# type: Content of: <chapter><section><section><para>
msgid ""
"Once you've dealt with a bug report (e.g. fixed it), mark it as "
"<literal>done</literal> (close it) by sending an explanation message to "
-"<email>123-done@&bugs-host;</email>. If you're fixing a bug by changing and "
+"<email><replaceable>123</replaceable>-done@&bugs-host;</email>. If you're fixing a bug by changing and "
"uploading the package, you can automate bug closing as described in <xref "
-"linkend=\"upload-bugfix\"/> ."
+"linkend=\"upload-bugfix\"/>."
msgstr ""
-"既にバグに対処していた場合 (例えば修正済み)、説明のメッセージを <email>123-"
+"既にバグに対処していた場合 (例えば修正済み)、説明のメッセージを <email><replaceable>123</replaceable>-"
"done@&bugs-host;</email> に送ることで <literal>done</literal> とマークしてお"
"いて (閉じて) ください。パッケージを変更してアップロードすることでバグを修正"
"する場合は、<xref linkend=\"upload-bugfix\"/> に記載されているように自動的に"
#: pkgs.dbk:827
msgid ""
"For general information on how to write your changelog entries, see <xref "
-"linkend=\"bpp-debian-changelog\"/> ."
+"linkend=\"bpp-debian-changelog\"/>."
msgstr ""
"どのように changelog のエントリを書くのか、一般的な情報については <xref "
"linkend=\"bpp-debian-changelog\"/> を参照してください。"
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
#: pkgs.dbk:864
msgid ""
-"Any fixed packages that you have prepared yourself (send only the <literal>."
-"diff.gz</literal> and <literal>.dsc</literal> files and read <xref linkend="
+"Any fixed packages that you have prepared yourself (send only the <filename>."
+"diff.gz</filename> and <filename>.dsc</filename> files and read <xref linkend="
"\"bug-security-building\"/> first)"
msgstr ""
"自身で準備した修正パッケージ (まずは <xref linkend=\"bug-security-building\"/"
-"> を読んで、<literal>.diff.gz</literal> と <literal>.dsc</literal> ファイルだ"
+"> を読んで、<filename>.diff.gz</filename> と <filename>.dsc</filename> ファイルだ"
"けを送ってください)"
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
#: pkgs.dbk:877
msgid ""
"Any information needed for the advisory (see <xref linkend=\"bug-security-"
-"advisories\"/> )"
+"advisories\"/>)"
msgstr ""
"勧告に必要になる情報 (<xref linkend=\"bug-security-advisories\"/> 参照)"
"ください。"
# type: Content of: <chapter><section><section><section><para>
-# FIXME: CVS repository ? VCS?
#. type: Content of: <chapter><section><section><section><para>
#: pkgs.dbk:963
msgid ""
"Please note that if secrecy is needed you may not upload a fix to "
-"<literal>unstable</literal> (or anywhere else, such as a public CVS "
+"<literal>unstable</literal> (or anywhere else, such as a public VCS "
"repository). It is not sufficient to obfuscate the details of the change, "
"as the code itself is public, and can (and will) be examined by the general "
"public."
msgstr ""
-"機密を要する場合は、修正を<literal>不安定版 (unstable)</literal> (や公開 CVS "
+"機密を要する場合は、修正を<literal>不安定版 (unstable)</literal> (や公開 VCS "
"リポジトリなどその他どこでも) へ修正をアップロードしないよう、注意してくださ"
"い。コードその物が公開されている場合、変更の詳細を難読化するだけでは十分では"
"なく、皆によって解析され得る (そしてされる) でしょう。"
"from the previous version repeatedly (<command>interdiff</command> from the "
"<systemitem role=\"package\">patchutils</systemitem> package and "
"<command>debdiff</command> from <systemitem role=\"package\">devscripts</"
-"systemitem> are useful tools for this, see <xref linkend=\"debdiff\"/> )."
+"systemitem> are useful tools for this, see <xref linkend=\"debdiff\"/>)."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
"you have already used for a previous upload, or one that conflicts with a "
"binNMU. The convention is to append <literal>+</"
"literal><replaceable>codename</replaceable><literal>1</literal>, e.g. "
-"<literal>1:2.4.3-4+etch1</literal>, of course increasing 1 for any "
+"<literal>1:2.4.3-4+lenny1</literal>, of course increasing 1 for any "
"subsequent uploads."
msgstr ""
"<emphasis role=\"strong\">バージョン番号</emphasis>が正しいことを確認する。現"
"バージョン番号を再利用しないように注意してください。そうしないと番号が "
"binNMU と衝突します。<literal>+</literal><replaceable>codename</"
"replaceable><literal>1</literal> を追加するのが通例です。例えば "
-"<literal>1:2.4.3-4+etch1</literal> とします。もちろん 1 はアップロードするご"
+"<literal>1:2.4.3-4+lenny1</literal> とします。もちろん 1 はアップロードするご"
"とに増やします。"
# FIXME: remove " "
"<emphasis role=\"strong\">with full upstream source</emphasis> "
"(<literal>dpkg-buildpackage -sa</literal>). If there has been a previous "
"upload to <literal>security.debian.org</literal> with the same upstream "
-"version, you may upload without upstream source (<literal> dpkg-buildpackage "
+"version, you may upload without upstream source (<literal>dpkg-buildpackage "
"-sd</literal>)."
msgstr ""
"これまでに (以前のセキュリティ更新によって) <literal>security.debian.org</"
"Build the package on a <emphasis role=\"strong\">clean system</emphasis> "
"which only has packages installed from the distribution you are building "
"for. If you do not have such a system yourself, you can use a debian.org "
-"machine (see <xref linkend=\"server-machines\"/> ) or setup a chroot (see "
-"<xref linkend=\"pbuilder\"/> and <xref linkend=\"debootstrap\"/> )."
+"machine (see <xref linkend=\"server-machines\"/>) or setup a chroot (see "
+"<xref linkend=\"pbuilder\"/> and <xref linkend=\"debootstrap\"/>)."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
msgid ""
"Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
"upload queue (<literal>oldstable-security</literal>, <literal>stable-"
-"security </literal>, etc.) without prior authorization from the security "
+"security</literal>, etc.) without prior authorization from the security "
"team. If the package does not exactly meet the team's requirements, it will "
"cause many problems and delays in dealing with the unwanted upload."
msgstr ""
"the security team, it needs to be uploaded so that it can be installed in "
"the archives. For security uploads, the place to upload to is "
"<literal>ftp://security-master.debian.org/pub/SecurityUploadQueue/</"
-"literal> ."
+"literal>."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
"of one of your packages (e.g., ``devel'', ``admin''), the procedure is "
"slightly different. Correct the subsection as found in the control file of "
"the package, and re-upload that. Also, you'll need to get the override file "
-"updated, as described in <xref linkend=\"override-file\"/> ."
+"updated, as described in <xref linkend=\"override-file\"/>."
msgstr ""
# type: Content of: <chapter><section><section><title>
"would be package hijacking. You can, of course, contact the current "
"maintainer and ask them if you may take over the package. If you have "
"reason to believe a maintainer has gone AWOL (absent without leave), see "
-"<xref linkend=\"mia-qa\"/> ."
+"<xref linkend=\"mia-qa\"/>."
msgstr ""
# type: Content of: <chapter><section><section><para>
"Depends-Indep</literal> settings in <filename>debian/control</filename> are "
"set properly. The best way to validate this is to use the <systemitem role="
"\"package\">debootstrap</systemitem> package to create an <literal>unstable</"
-"literal> chroot environment (see <xref linkend=\"debootstrap\"/> ). Within "
+"literal> chroot environment (see <xref linkend=\"debootstrap\"/>). Within "
"that chrooted environment, install the <systemitem role=\"package\">build-"
"essential</systemitem> package and any package dependencies mentioned in "
"<literal>Build-Depends</literal> and/or <literal>Build-Depends-Indep</"
"literal>. Finally, try building your package within that chrooted "
"environment. These steps can be automated by the use of the "
"<command>pbuilder</command> program which is provided by the package of the "
-"same name (see <xref linkend=\"pbuilder\"/> )."
+"same name (see <xref linkend=\"pbuilder\"/>)."
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
#: pkgs.dbk:1534
msgid ""
"If you can't set up a proper chroot, <command>dpkg-depcheck</command> may be "
-"of assistance (see <xref linkend=\"dpkg-depcheck\"/> )."
+"of assistance (see <xref linkend=\"dpkg-depcheck\"/>)."
msgstr ""
# type: Content of: <chapter><section><section><orderedlist><listitem><para>
#: pkgs.dbk:1762
msgid ""
"Descriptions of several porting tools can be found in <xref linkend=\"tools-"
-"porting\"/> ."
+"porting\"/>."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
"as a package; however, all Debian porting efforts are using it for automated "
"package building. The tool used to do the actual package builds, "
"<systemitem role=\"package\">sbuild</systemitem> is available as a package, "
-"see its description in <xref linkend=\"sbuild\"/> . Please note that the "
+"see its description in <xref linkend=\"sbuild\"/>. Please note that the "
"packaged version is not the same as the one used on build daemons, but it is "
"close enough to reproduce problems."
msgstr ""
#. type: Content of: <chapter><section><section><title>
#: pkgs.dbk:1998
-msgid "NMUs and debian/changelog"
-msgstr "NMU と debian/changelog"
+msgid "NMUs and <filename>debian/changelog</filename>"
+msgstr "NMU と <filename>debian/changelog</filename>"
#. type: Content of: <chapter><section><section><para>
#: pkgs.dbk:2000
msgid ""
"Just like any other (source) upload, NMUs must add an entry to "
-"<literal>debian/changelog</literal>, telling what has changed with this "
+"<filename>debian/changelog</filename>, telling what has changed with this "
"upload. The first line of this entry must explicitely mention that this "
"upload is an NMU, e.g.:"
msgstr ""
"Setup the co-maintainer with access to the sources you build the package "
"from. Generally this implies you are using a network-capable version "
"control system, such as <command>CVS</command> or <command>Subversion</"
-"command>. Alioth (see <xref linkend=\"alioth\"/> ) provides such tools, "
+"command>. Alioth (see <xref linkend=\"alioth\"/>) provides such tools, "
"amongst others."
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
#: pkgs.dbk:2242
msgid ""
-"Using the PTS (<xref linkend=\"pkg-tracking-system\"/> ), the co-maintainers "
+"Using the PTS (<xref linkend=\"pkg-tracking-system\"/>), the co-maintainers "
"should subscribe themselves to the appropriate source package."
msgstr ""
msgid ""
"In any case, it is a bad idea to automatically put all team members in the "
"Uploaders field. It clutters the Developer's Package Overview listing (see "
-"<xref linkend=\"ddpo\"/> ) with packages one doesn't really care for, and "
+"<xref linkend=\"ddpo\"/>) with packages one doesn't really care for, and "
"creates a false sense of good maintenance."
msgstr ""
"channels are dedicated to an architecture or a set of packages: "
"<literal>#debian-kde</literal>, <literal>#debian-dpkg</literal>, "
"<literal>#debian-jr</literal>, <literal>#debian-edu</literal>, "
-"<literal>#debian-oo</literal> (OpenOffice package) ..."
+"<literal>#debian-oo</literal> (OpenOffice.org package)..."
msgstr ""
"他にも、特定の話題について専用のチャンネルがあります。<literal>#debian-bugs</"
"literal> は、バグ潰しパーティ (BSP) を開催するために使われます。"
"ケージ群について話すため、他にも専用チャンネルがあります：<literal>#debian-"
"kde</literal>、<literal>#debian-dpkg</literal>、<literal>#debian-jr</"
"literal>、<literal>#debian-edu</literal>、<literal>#debian-oo</literal> "
-"(OpenOffice パッケージ) など…"
+"(OpenOffice.org パッケージ) など…"
# type: Content of: <chapter><section><para>
#. type: Content of: <chapter><section><para>
msgid ""
"Please take care to protect your Debian passwords and SSH keys installed on "
"Debian machines. Avoid login or upload methods which send passwords over "
-"the Internet in the clear, such as telnet, FTP, POP etc."
+"the Internet in the clear, such as Telnet, FTP, POP etc."
msgstr ""
"Debian で利用しているパスワードと Debian のマシンにインストールしてある SSH "
"鍵を保護することに注意してください。ログインやアップロードの際にパスワードを"
-"インターネット越しに平文で送るような telnet や FTP や POP などの利用方法は避"
+"インターネット越しに平文で送るような Telnet や FTP や POP などの利用方法は避"
"けてください。"
# type: Content of: <chapter><section><para>
"Problems with the Debian FTP archive generally need to be reported as bugs "
"against the <systemitem role=\"package\">&ftp-debian-org;</systemitem> "
"pseudo-package or an email to &email-ftpmaster;, but also see the procedures "
-"in <xref linkend=\"archive-manip\"/> ."
+"in <xref linkend=\"archive-manip\"/>."
msgstr ""
"Debian FTP アーカイブについて問題がある場合、通常 <systemitem role=\"package"
"\">&ftp-debian-org;</systemitem> 擬似パッケージに対するバグ報告を行うか、"
#: resources.dbk:359
msgid ""
"In all chroots, the normal user home directories are available. You can "
-"find out which chroots are available via <literal>&url-devel-machines;</"
-"literal>."
+"find out which chroots are available via <ulink url=\"&url-devel-machines;"
+"\"></ulink>."
msgstr ""
"全ての chroot 環境内で、一般ユーザの home ディレクトリが利用可能になっていま"
"す。どの chroot が利用可能かについては <ulink url=\"&url-devel-machines;"
msgid ""
"In each of the areas, there is a directory for the source packages "
"(<filename>source</filename>) and a directory for each supported "
-"architecture (<filename>binary-i386</filename>, <filename>binary-m68k</"
+"architecture (<filename>binary-i386</filename>, <filename>binary-amd64</"
"filename>, etc.)."
msgstr ""
"それぞれ、source パッケージ (<filename>source</filename>) のディレクトリとサ"
"ポートしている各アーキテクチャ (<filename>binary-i386</filename>、"
-"<filename>binary-m68k</filename> など) のディレクトリがあります。"
+"<filename>binary-amd64</filename> など) のディレクトリがあります。"
# type: Content of: <chapter><section><para>
#. type: Content of: <chapter><section><para>
"The <filename>main</filename> area contains additional directories which "
"hold the disk images and some essential pieces of documentation required for "
"installing the Debian distribution on a specific architecture "
-"(<filename>disks-i386</filename>, <filename>disks-m68k</filename>, etc.)."
+"(<filename>disks-i386</filename>, <filename>disks-amd64</filename>, etc.)."
msgstr ""
"<filename>main</filename> はディスクイメージと特定のアーキテクチャで Debian "
"をインストールする際に必要となるドキュメントの基本部分が入っている追加ディレ"
-"クトリを含んでいます (<filename>disks-i386</filename>、<filename>disks-m68k</"
+"クトリを含んでいます (<filename>disks-i386</filename>、<filename>disks-amd64</"
"filename> など)。"
# type: Content of: <chapter><section><section><title>
"satisfy certain criteria. Those criteria should ensure a good quality for "
"packages within <literal>testing</literal>. The update to <literal>testing "
"</literal> is launched twice each day, right after the new packages have "
-"been installed. See <xref linkend=\"testing\"/> ."
+"been installed. See <xref linkend=\"testing\"/>."
msgstr ""
"<link linkend=\"testing\">テスト版 (testing)</link> ディストリビューション"
"は、パッケージが特定の判定規準を満たした際に<literal>不安定版</literal>から自"
msgid ""
"Thus, the names of the distribution directories in the archive are "
"determined by their code names and not their release status (e.g., "
-"`slink'). These names stay the same during the development period and after "
+"`squeeze'). These names stay the same during the development period and after "
"the release; symbolic links, which can be changed easily, indicate the "
"currently released stable distribution. That's why the real distribution "
"directories use the <literal>code names</literal>, while symbolic links for "
"<literal>unstable</literal> point to the appropriate release directories."
msgstr ""
"従って、アーカイブ内のディストリビューションディレクトリの名前はリリースの状"
-"態ではなくコードネームで決定されます (例えば `slink' など)。これらの名称は開"
+"態ではなくコードネームで決定されます (例えば `squeeze' など)。これらの名称は開"
"発期間中とリリース後も同じものであり続けます。そして、簡単に変更可能なシンボ"
"リックリンクによって、現在の安定版リリースディストリビューションを示すことに"
"なります。これが、<literal>stable</literal>、<literal>testing</literal>、"
msgid ""
"The archive maintenance software will also send the OpenPGP/GnuPG signed "
"<filename>.changes</filename> file that you uploaded to the appropriate "
-"mailing lists. If a package is released with the <literal>Distribution:</"
+"mailing lists. If a package is released with the <literal>Distribution</"
"literal> set to <literal>stable</literal>, the announcement is sent to "
-"&email-debian-changes;. If a package is released with <literal>Distribution:"
+"&email-debian-changes;. If a package is released with <literal>Distribution"
"</literal> set to <literal>unstable</literal> or <literal>experimental</"
"literal>, the announcement will be posted to &email-debian-devel-changes; "
"instead."
msgstr ""
"アーカイブメンテナンスのソフトウェアは、あなたがアップロードした OpenPGP/"
"GnuPG で署名された <filename>.changes</filename> ファイルも適切なメーリングリ"
-"ストへと送信します。パッケージが <literal>Distribution:</literal> として "
+"ストへと送信します。パッケージが <literal>Distribution</literal> として "
"<literal>stable</literal> が設定されてリリースされた場合、案内は &email-"
-"debian-changes; に送られます。パッケージの <literal>Distribution:</literal> "
+"debian-changes; に送られます。パッケージの <literal>Distribution</literal> "
"として <literal>unstable</literal> や <literal>experimental</literal> が設定"
"されている場合、案内は代わりに &email-debian-devel-changes; へと投稿されま"
"す。"
#: resources.dbk:1475
msgid ""
"Here are a few examples of valid mails used to generate news items in the "
-"PTS. The first one adds a link to the cvsweb interface of debian-cd in the "
+"PTS. The first one adds a link to the viewsvn interface of debian-cd in the "
"Static information section:"
msgstr ""
"PTS 中のニュース項目の生成に使われる正しいメールの例を幾つか挙げます。最初の1"
-"つ目は Static information section 中の debian-cd の cvsweb インターフェイスへ"
+"つ目は Static information section 中の debian-cd の viewsvn インターフェイスへ"
"のリンクを付け加えるものです:"
# type: Content of: <chapter><section><section><screen>
"FusionForge software (which evolved from SourceForge and GForge). This "
"software offers developers access to easy-to-use tools such as bug trackers, "
"patch manager, project/task managers, file hosting services, mailing lists, "
-"CVS repositories etc. All these tools are managed via a web interface."
+"VCS repositories etc. All these tools are managed via a web interface."
msgstr ""
"Alioth は FusionForge (SourceForge と GForge から派生したソフトウェア) に多少"
"変更を加えたものを基にした Debian のサービスです。このソフトは開発者が容易に"
"使えるバグトラッキングシステム、パッチ管理、プロジェクト／タスク管理、ファイ"
-"ルのアップロード、メーリングリスト、CVS リポジトリなどのツールを提供します。"
+"ルのアップロード、メーリングリスト、VCS リポジトリなどのツールを提供します。"
"これらの機能全てはウェブインターフェイスから管理します。"
# type: Content of: <chapter><section><para>
#: scope.dbk:14
msgid ""
"The procedures discussed within include how to become a maintainer (<xref "
-"linkend=\"new-maintainer\"/> ); how to create new packages (<xref linkend="
-"\"newpackage\"/> ) and how to upload packages (<xref linkend=\"upload\"/> ); "
-"how to handle bug reports (<xref linkend=\"bug-handling\"/> ); how to move, "
-"remove, or orphan packages (<xref linkend=\"archive-manip\"/> ); how to port "
-"packages (<xref linkend=\"porting\"/> ); and how and when to do interim "
-"releases of other maintainers' packages (<xref linkend=\"nmu\"/> )."
+"linkend=\"new-maintainer\"/>); how to create new packages (<xref linkend="
+"\"newpackage\"/>) and how to upload packages (<xref linkend=\"upload\"/>); "
+"how to handle bug reports (<xref linkend=\"bug-handling\"/>); how to move, "
+"remove, or orphan packages (<xref linkend=\"archive-manip\"/>); how to port "
+"packages (<xref linkend=\"porting\"/>); and how and when to do interim "
+"releases of other maintainers' packages (<xref linkend=\"nmu\"/>)."
msgstr ""
"ここで取り上げる手続きには、開発者になる方法 (<xref linkend=\"new-maintainer"
-"\"/>) 、新しいパッケージの作り方 (<xref linkend=\"newpackage\"/> ) とパッケー"
+"\"/>) 、新しいパッケージの作り方 (<xref linkend=\"newpackage\"/>) とパッケー"
"ジをアップロードする方法 (<xref linkend=\"upload\"/>)、バグ報告の取扱い方 "
-"(<xref linkend=\"bug-handling\"/> )、パッケージを移動、削除、みなしご化 "
+"(<xref linkend=\"bug-handling\"/>)、パッケージを移動、削除、みなしご化 "
"(orphan) する方法 (<xref linkend=\"archive-manip\"/>)、パッケージ移植のやり"
-"方 (<xref linkend=\"porting\"/> )他のメンテナのパッケージを暫定的にリリースす"
+"方 (<xref linkend=\"porting\"/>)他のメンテナのパッケージを暫定的にリリースす"
"るのは、いつどの様にしたらよいのか (<xref linkend=\"nmu\"/>) が含まれます。"
# type: Content of: <chapter><para>
#: scope.dbk:23
msgid ""
"The resources discussed in this reference include the mailing lists (<xref "
-"linkend=\"mailing-lists\"/> ) and servers (<xref linkend=\"server-machines\"/"
-"> ); a discussion of the structure of the Debian archive (<xref linkend="
-"\"archive\"/> ); explanation of the different servers which accept package "
-"uploads (<xref linkend=\"upload-ftp-master\"/> ); and a discussion of "
+"linkend=\"mailing-lists\"/>) and servers (<xref linkend=\"server-machines\"/"
+">); a discussion of the structure of the Debian archive (<xref linkend="
+"\"archive\"/>); explanation of the different servers which accept package "
+"uploads (<xref linkend=\"upload-ftp-master\"/>); and a discussion of "
"resources which can help maintainers with the quality of their packages "
-"(<xref linkend=\"tools\"/> )."
+"(<xref linkend=\"tools\"/>)."
msgstr ""
"また、このリファレンスで触れるリソースには、メーリングリスト (<xref linkend="
-"\"mailing-lists\"/>) およびサーバ (<xref linkend=\"server-machines\"/> )、"
+"\"mailing-lists\"/>) およびサーバ (<xref linkend=\"server-machines\"/>)、"
"Debian アーカイブの構成に関する解説 (<xref linkend=\"archive\"/>)、パッケージ"
"のアップロードを受け付ける様々なサーバの説明 (<xref linkend=\"upload-ftp-"
"master\"/>)、パッケージの品質を高めるために開発者が利用できるリソースについて"
"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 <replaceable>package-name</replaceable></command>."
msgstr ""
"パッケージの説明文のほとんどは実際のパッケージの説明から取ったものです。より"
"詳細な情報はパッケージ内のドキュメントで確認できます。<command>apt-cache "
-"show <package-name></command> コマンドとしても情報を得られます。"
+"show <replaceable>package-name</replaceable></command> コマンドとしても情報を得られます。"
# type: Content of: <appendix><section><title>
#. 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>
#. type: Content of: <appendix><section><section><title>
#: tools.dbk:116
-msgid "<systemitem role=\"package\">debdiff</systemitem>"
-msgstr "<systemitem role=\"package\">debdiff</systemitem>"
+msgid "<command>debdiff</command>"
+msgstr "<command>debdiff</command>"
# type: Content of: <appendix><section><section><para>
#. type: Content of: <appendix><section><section><para>
#: tools.dbk:118
msgid ""
"<command>debdiff</command> (from the <systemitem role=\"package"
-"\">devscripts</systemitem> package, <xref linkend=\"devscripts\"/> ) "
+"\">devscripts</systemitem> package, <xref 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 "
"<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 "
+"\"package\">debmake</systemitem> and its template files use <command>dh_*</command> programs "
"from <systemitem role=\"package\">debhelper</systemitem>."
msgstr ""
"<systemitem role=\"package\">dh-make</systemitem> パッケージは、ソースツリー"
"<command>dh_make</command> を含んでいます。その名が示すように、"
"<command>dh_make</command> は <systemitem role=\"package\">debmake</"
"systemitem> の焼き直しで、そのテンプレートファイルは<systemitem role="
-"\"package\">debhelper</systemitem> の dh_* プログラムを使うようになっていま"
+"\"package\">debhelper</systemitem> の <command>dh_*</command> プログラムを使うようになっていま"
"す。"
# 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 ""
-"より詳細については <literal><ulink url=\"http://yada.alioth.debian.org/"
-"\">YADA のサイト</ulink></literal> を参照してください。"
+"より詳細については <ulink url=\"http://yada.alioth.debian.org/"
+"\"><literal>YADA</literal> のサイト</ulink> を参照してください。"
# type: Content of: <appendix><section><section><title>
#. type: Content of: <appendix><section><section><title>
# type: Content of: <appendix><section><section><title>
#. type: Content of: <appendix><section><section><title>
#: tools.dbk:324
-msgid "<systemitem role=\"package\">dcut</systemitem>"
-msgstr "<systemitem role=\"package\">dcut</systemitem>"
+msgid "<command>dcut</command>"
+msgstr "<command>dcut</command>"
# type: Content of: <appendix><section><section><para>
#. 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 "
+"The <command>dcut</command> script (part of the "
+"package <xref linkend=\"dput\"/>) helps in removing files from the ftp "
"upload directory."
msgstr ""
-"<systemitem role=\"package\">dcut</systemitem> スクリプト (<xref linkend="
+"<command>dcut</command> スクリプト (<xref linkend="
"\"dput\"/> パッケージの一部) は、ftp アップロードディレクトリからファイルを削"
"除するのに役立ちます。"
# type: Content of: <appendix><section><section><title>
#. type: Content of: <appendix><section><section><title>
#: tools.dbk:418
-msgid "<systemitem role=\"package\">dpkg-depcheck</systemitem>"
-msgstr "<systemitem role=\"package\">dpkg-depcheck</systemitem>"
+msgid "<command>dpkg-depcheck</command>"
+msgstr "<command>dpkg-depcheck</command>"
# type: Content of: <appendix><section><section><para>
#. type: Content of: <appendix><section><section><para>
#: tools.dbk:420
msgid ""
"<command>dpkg-depcheck</command> (from the <systemitem role=\"package"
-"\">devscripts</systemitem> package, <xref linkend=\"devscripts\"/> ) runs a "
+"\">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."
msgstr ""
#: 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 ""
"<command>dpkg-depcheck</command> は、特にパッケージが他のプログラムを実行する"
-"のに exec(2) を使っている場合に実行時の依存性を確認するのにも使えます。"
+"のに <citerefentry> "
+"<refentrytitle>exec</refentrytitle> <manvolnum>2</manvolnum> </citerefentry> を使っている場合に実行時の依存性を確認するのにも使えます。"
# type: Content of: <appendix><section><section><para>
#. type: Content of: <appendix><section><section><para>
~ianmdlvl / developers-reference.git / commitdiff