</para>
<para>
The short description should be kept short (50 characters or so) so that it may
-be accomodated by most debconf interfaces. Keeping it short also helps
+be accommodated by most debconf interfaces. Keeping it short also helps
translators, as usually translations tend to end up being longer than the
original.
</para>
The short description should be phrased in the form of a question which should
be kept short and should generally end with a question mark. Terse writing
style is permitted and even encouraged if the question is rather long (remember
-that translations are often longer than original versions)
+that translations are often longer than original versions).
</para>
</listitem>
<listitem>
If the default value may vary depending on language/country (for instance the
default value for a language choice), consider using the special _Default
type documented in <citerefentry> <refentrytitle>po-debconf</refentrytitle>
-<manvolnum>7</manvolnum> </citerefentry>).
+<manvolnum>7</manvolnum> </citerefentry>.
</para>
</section>
<para>
Make sure the bug is not already filed against a package. Each package has a
bug list easily reachable at
-<literal>http://&bugs-host;/<replaceable>packagename</replaceable></literal>
+<literal>http://&bugs-host;/<replaceable>packagename</replaceable></literal>.
Utilities like <citerefentry> <refentrytitle>querybts</refentrytitle>
<manvolnum>1</manvolnum> </citerefentry> can also provide you with this
information (and <command>reportbug</command> will usually invoke
* Update references to merkel (which is decommissionned) where
needed. Closes: #619990
Thanks to Charles Plessy for the patch.
+ * Many typos fixed by Chris Leick <c.leick@vollbio.de>. Closes: #623512
[ Chris Leick ]
* Initial German translation.
would be much less secure.<footnote><para> Version 4 keys are keys conforming
to the OpenPGP standard as defined in RFC 2440. Version 4 is the key type that
has always been created when using GnuPG. PGP versions since 5.x also could
-create v4 keys, the other choice having beein pgp 2.6.x compatible v3 keys
+create v4 keys, the other choice having been pgp 2.6.x compatible v3 keys
(also called legacy RSA by PGP). </para> <para> Version 4 (primary) keys can
either use the RSA or the DSA algorithms, so this has nothing to do with
GnuPG's question about which kind of key do you want: (1) DSA and Elgamal, (2)
</listitem>
<listitem>
<para>
-Unless the upstream source has been uploaded to <literal>security.debian.org
-</literal> before (by a previous security update), build the upload <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 -sd</literal>).
+Unless the upstream source has been uploaded to
+<literal>security.debian.org</literal> before (by a previous security update),
+build the upload <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
+-sd</literal>).
</para>
</listitem>
<listitem>
<replaceable>[architecture list]</replaceable> is optional and only needed
if the removal request only applies to some architectures, not all. Note
that the <command>reportbug</command> will create a title conforming
-to these rules when you use it to report a bug against the
+to these rules when you use it to report a bug against the
<literal>ftp.debian.org</literal> pseudo-package.
</para>
</para>
<para>
Sometimes, some packages never enter <literal>testing</literal> because the
-set of inter-relationship is too complicated and cannot be sorted out by the
+set of interrelationship is too complicated and cannot be sorted out by the
scripts. See below for details.
</para>
<para>
"Schablonenbeschreibungen haben zwei Teile: kurz und länger. Die "
"Kurzbeschreibung steht in der Zeile »Description:« der Schablone."
-# FIXME s/accomodated/accommodated/
#. type: Content of: <chapter><section><section><section><para>
#: best-pkging-practices.dbk:1119
msgid ""
"The short description should be kept short (50 characters or so) so that it "
-"may be accomodated by most debconf interfaces. Keeping it short also helps "
+"may be accommodated by most debconf interfaces. Keeping it short also helps "
"translators, as usually translations tend to end up being longer than the "
"original."
msgstr ""
msgid "Boolean templates"
msgstr "»boolean«-Schablonen"
-# FIXME missing full stop
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
#: best-pkging-practices.dbk:1224
msgid ""
"The short description should be phrased in the form of a question which "
"should be kept short and should generally end with a question mark. Terse "
"writing style is permitted and even encouraged if the question is rather "
-"long (remember that translations are often longer than original versions)"
+"long (remember that translations are often longer than original versions)."
msgstr ""
"Die Kurzbeschreibung sollte in der Frageform ausgedrückt werden, die kurz "
"gehalten und generell mit einem Fragezeichen beendet werden sollte. Knapper "
"Feld übersetzbar zu machen, wenn Sie der Meinung sind, es könnte übersetzt "
"werden."
-# FIXME superfluous second bracket
#. type: Content of: <chapter><section><section><section><para>
#: best-pkging-practices.dbk:1350
msgid ""
"If the default value may vary depending on language/country (for instance "
"the default value for a language choice), consider using the special "
"_Default type documented in <citerefentry> <refentrytitle>po-debconf</"
-"refentrytitle> <manvolnum>7</manvolnum> </citerefentry>)."
+"refentrytitle> <manvolnum>7</manvolnum> </citerefentry>."
msgstr ""
"Falls der Vorgabewert von Sprache oder Land abhängen könnte (zum Beispiel, "
"weil es sich bei der Auswahl um eine Sprachauswahl handelt), ziehen Sie in "
msgid ""
"Make sure the bug is not already filed against a package. Each package has "
"a bug list easily reachable at <literal>http://&bugs-host;/"
-"<replaceable>packagename</replaceable></literal> Utilities like "
+"<replaceable>packagename</replaceable></literal>. Utilities like "
"<citerefentry> <refentrytitle>querybts</refentrytitle> <manvolnum>1</"
"manvolnum> </citerefentry> can also provide you with this information (and "
"<command>reportbug</command> will usually invoke <command>querybts</command> "
"benutzen. Beachten Sie, dass OpenPGP ein offener Standard ist, der auf "
"<ulink url=\"&url-rfc2440;\">RFC 2440</ulink> basiert."
-# FIXME s/beein/been/
#. type: Content of: <chapter><section><para><footnote><para>
#: new-maintainer.dbk:159
msgid ""
"Version 4 keys are keys conforming to the OpenPGP standard as defined in RFC "
"2440. Version 4 is the key type that has always been created when using "
"GnuPG. PGP versions since 5.x also could create v4 keys, the other choice "
-"having beein pgp 2.6.x compatible v3 keys (also called legacy RSA by PGP)."
+"having been pgp 2.6.x compatible v3 keys (also called legacy RSA by PGP)."
msgstr ""
"Schlüssel der Version 4 folgen dem in RFC 2440 definierten OpenPGP-Standard. "
"Bei Verwendung von GnuPG wurden immer Version-4-Schlüssel erstellt. PGP-"
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
#: pkgs.dbk:1154
msgid ""
-"Unless the upstream source has been uploaded to <literal>security.debian.org "
+"Unless the upstream source has been uploaded to <literal>security.debian.org"
"</literal> before (by a previous security update), build the upload "
"<emphasis role=\"strong\">with full upstream source</emphasis> "
"(<literal>dpkg-buildpackage -sa</literal>). If there has been a previous "
"Distribution</ulink> stellt einige weitere Informationen über die üblichen "
"Probleme bereit, die derartigen Ärger verursachen."
-# FIXME s/inter-relationship/interrelationship/
#. type: Content of: <chapter><section><section><para>
#: pkgs.dbk:2394
msgid ""
"Sometimes, some packages never enter <literal>testing</literal> because the "
-"set of inter-relationship is too complicated and cannot be sorted out by the "
+"set of interrelationship is too complicated and cannot be sorted out by the "
"scripts. See below for details."
msgstr ""
"Manchmal errreichen einige Pakete <literal>testing</literal> niemals, da die "
msgid "The VCS servers"
msgstr "Die VCS-Server"
-# FIXME s/one the/one of the/
#. type: Content of: <chapter><section><section><para>
#: resources.dbk:333
msgid ""
"If you need to use a Version Control System for any of your Debian work, you "
-"can use one the existing repositories hosted on Alioth or you can request a "
-"new project and ask for the VCS repository of your choice. Alioth supports "
+"can use one of the existing repositories hosted on Alioth or you can request "
+"a new project and ask for the VCS repository of your choice. Alioth supports "
"CVS (cvs.alioth.debian.org/cvs.debian.org), Subversion (svn.debian.org), "
"Arch (tla/baz, both on arch.debian.org), Bazaar (bzr.debian.org), Darcs "
"(darcs.debian.org), Mercurial (hg.debian.org) and Git (git.debian.org). "
"sicherzustellen, dass alles in dieser Distribution funktioniert, ist sie "
"manchmal buchstäblich instabil."
-# FIXME s/testing /testing/
#. type: Content of: <chapter><section><section><section><para>
#: resources.dbk:636
msgid ""
"The <link linkend=\"testing\">testing</link> distribution is generated "
"automatically by taking packages from <literal>unstable</literal> if they "
"satisfy certain criteria. Those criteria should ensure a good quality for "
-"packages within <literal>testing</literal>. The update to <literal>testing "
+"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\"/>."
msgstr ""
"gleich nachdem die neuen Pakete installiert wurden. Siehe <xref linkend="
"\"testing\"/>."
-# FIXME s/)//
#. type: Content of: <chapter><section><section><section><para>
#: resources.dbk:644
msgid ""
"literal>, and a new copy is created for the new <literal>testing</literal>, "
"and the previous <literal>stable</literal> is renamed to <literal>oldstable</"
"literal> and stays there until it is finally archived. On archiving, the "
-"contents are moved to <literal>&archive-host;</literal>)."
+"contents are moved to <literal>&archive-host;</literal>."
msgstr ""
"Nach einer Entwicklungsperiode, sobald der Veröffentlichungsverwalter sie "
"als tauglich erachtet, wird die Distribution <literal>testing</literal> "
msgid "The <command>dak ls</command> utility"
msgstr "Das Hilfswerkzeug <command>dak ls</command>"
-# FIXME s/-host; /-host;/
#. type: Content of: <chapter><section><section><para>
#: resources.dbk:968
msgid ""
"<command>dak ls</command> is part of the dak suite of tools, listing "
"available package versions for all known distributions and architectures. "
-"The <command>dak</command> tool is available on <literal>&ftp-master-host; </"
+"The <command>dak</command> tool is available on <literal>&ftp-master-host;</"
"literal>, and on the mirror on <literal>&ftp-master-mirror;</literal>. It "
"uses a single argument corresponding to a package name. An example will "
"explain it better:"
#: best-pkging-practices.dbk:1119
msgid ""
"The short description should be kept short (50 characters or so) so that it "
-"may be accomodated by most debconf interfaces. Keeping it short also helps "
+"may be accommodated by most debconf interfaces. Keeping it short also helps "
"translators, as usually translations tend to end up being longer than the "
"original."
msgstr ""
"The short description should be phrased in the form of a question which "
"should be kept short and should generally end with a question mark. Terse "
"writing style is permitted and even encouraged if the question is rather "
-"long (remember that translations are often longer than original versions)"
+"long (remember that translations are often longer than original versions)."
msgstr ""
"La partie courte devrait utiliser la forme interrogative et se terminer par "
"un point d'interrogation. Un style abrégé est toléré et même encouragé si la "
"If the default value may vary depending on language/country (for instance "
"the default value for a language choice), consider using the special "
"_Default type documented in <citerefentry> <refentrytitle>po-debconf</"
-"refentrytitle> <manvolnum>7</manvolnum> </citerefentry>)."
+"refentrytitle> <manvolnum>7</manvolnum> </citerefentry>."
msgstr ""
"Si la valeur par défaut peut dépendre de la langue ou du pays (par exemple "
"une langue par défaut dans un programme), pensez à utiliser le type "
msgid ""
"Make sure the bug is not already filed against a package. Each package has "
"a bug list easily reachable at <literal>http://&bugs-host;/"
-"<replaceable>packagename</replaceable></literal> Utilities like "
+"<replaceable>packagename</replaceable></literal>. Utilities like "
"<citerefentry> <refentrytitle>querybts</refentrytitle> <manvolnum>1</"
"manvolnum> </citerefentry> can also provide you with this information (and "
"<command>reportbug</command> will usually invoke <command>querybts</command> "
"Version 4 keys are keys conforming to the OpenPGP standard as defined in RFC "
"2440. Version 4 is the key type that has always been created when using "
"GnuPG. PGP versions since 5.x also could create v4 keys, the other choice "
-"having beein pgp 2.6.x compatible v3 keys (also called legacy RSA by PGP)."
+"having been pgp 2.6.x compatible v3 keys (also called legacy RSA by PGP)."
msgstr ""
"Les clés en version 4 sont conformes au standard OpenPGP défini dans la "
"RFC 2440. La version 4 est le type de clé qui a toujours été créé avec "
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
#: pkgs.dbk:1154
msgid ""
-"Unless the upstream source has been uploaded to <literal>security.debian.org "
+"Unless the upstream source has been uploaded to <literal>security.debian.org"
"</literal> before (by a previous security update), build the upload "
"<emphasis role=\"strong\">with full upstream source</emphasis> "
"(<literal>dpkg-buildpackage -sa</literal>). If there has been a previous "
#: pkgs.dbk:2394
msgid ""
"Sometimes, some packages never enter <literal>testing</literal> because the "
-"set of inter-relationship is too complicated and cannot be sorted out by the "
+"set of interrelationship is too complicated and cannot be sorted out by the "
"scripts. See below for details."
msgstr ""
"Parfois, certains paquets n'entrent jamais dans <literal>testing</literal> "
#: resources.dbk:333
msgid ""
"If you need to use a Version Control System for any of your Debian work, you "
-"can use one the existing repositories hosted on Alioth or you can request a "
-"new project and ask for the VCS repository of your choice. Alioth supports "
+"can use one of the existing repositories hosted on Alioth or you can request "
+"a new project and ask for the VCS repository of your choice. Alioth supports "
"CVS (cvs.alioth.debian.org/cvs.debian.org), Subversion (svn.debian.org), "
"Arch (tla/baz, both on arch.debian.org), Bazaar (bzr.debian.org), Darcs "
"(darcs.debian.org), Mercurial (hg.debian.org) and Git (git.debian.org). "
"The <link linkend=\"testing\">testing</link> distribution is generated "
"automatically by taking packages from <literal>unstable</literal> if they "
"satisfy certain criteria. Those criteria should ensure a good quality for "
-"packages within <literal>testing</literal>. The update to <literal>testing "
+"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\"/>."
msgstr ""
"literal>, and a new copy is created for the new <literal>testing</literal>, "
"and the previous <literal>stable</literal> is renamed to <literal>oldstable</"
"literal> and stays there until it is finally archived. On archiving, the "
-"contents are moved to <literal>&archive-host;</literal>)."
+"contents are moved to <literal>&archive-host;</literal>."
msgstr ""
"Après une période de développement, quand l'équipe de publication "
"(« <literal>release team</literal> ») le juge opportun, la distribution "
msgid ""
"<command>dak ls</command> is part of the dak suite of tools, listing "
"available package versions for all known distributions and architectures. "
-"The <command>dak</command> tool is available on <literal>&ftp-master-host; </"
+"The <command>dak</command> tool is available on <literal>&ftp-master-host;</"
"literal>, and on the mirror on <literal>&ftp-master-mirror;</literal>. It "
"uses a single argument corresponding to a package name. An example will "
"explain it better:"
#: best-pkging-practices.dbk:1119
msgid ""
"The short description should be kept short (50 characters or so) so that it "
-"may be accomodated by most debconf interfaces. Keeping it short also helps "
+"may be accommodated by most debconf interfaces. Keeping it short also helps "
"translators, as usually translations tend to end up being longer than the "
"original."
msgstr ""
"The short description should be phrased in the form of a question which "
"should be kept short and should generally end with a question mark. Terse "
"writing style is permitted and even encouraged if the question is rather "
-"long (remember that translations are often longer than original versions)"
+"long (remember that translations are often longer than original versions)."
msgstr ""
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
"If the default value may vary depending on language/country (for instance "
"the default value for a language choice), consider using the special "
"_Default type documented in <citerefentry> <refentrytitle>po-debconf</"
-"refentrytitle> <manvolnum>7</manvolnum> </citerefentry>)."
+"refentrytitle> <manvolnum>7</manvolnum> </citerefentry>."
msgstr ""
# type: Content of: <chapter><section><title>
msgid ""
"Make sure the bug is not already filed against a package. Each package has "
"a bug list easily reachable at <literal>http://&bugs-host;/"
-"<replaceable>packagename</replaceable></literal> Utilities like "
+"<replaceable>packagename</replaceable></literal>. Utilities like "
"<citerefentry> <refentrytitle>querybts</refentrytitle> <manvolnum>1</"
"manvolnum> </citerefentry> can also provide you with this information (and "
"<command>reportbug</command> will usually invoke <command>querybts</command> "
"Version 4 keys are keys conforming to the OpenPGP standard as defined in RFC "
"2440. Version 4 is the key type that has always been created when using "
"GnuPG. PGP versions since 5.x also could create v4 keys, the other choice "
-"having beein pgp 2.6.x compatible v3 keys (also called legacy RSA by PGP)."
+"having been pgp 2.6.x compatible v3 keys (also called legacy RSA by PGP)."
msgstr ""
"バージョン 4 の鍵は、RFC 2440 で規定されているように OpenPGP 標準に適合しま"
"す。GnuPG を使って鍵を作ると、鍵のタイプは常にバージョン 4 になります。PGP は"
#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
#: pkgs.dbk:1154
msgid ""
-"Unless the upstream source has been uploaded to <literal>security.debian.org "
+"Unless the upstream source has been uploaded to <literal>security.debian.org"
"</literal> before (by a previous security update), build the upload "
"<emphasis role=\"strong\">with full upstream source</emphasis> "
"(<literal>dpkg-buildpackage -sa</literal>). If there has been a previous "
#: pkgs.dbk:2394
msgid ""
"Sometimes, some packages never enter <literal>testing</literal> because the "
-"set of inter-relationship is too complicated and cannot be sorted out by the "
+"set of interrelationship is too complicated and cannot be sorted out by the "
"scripts. See below for details."
msgstr ""
#: resources.dbk:333
msgid ""
"If you need to use a Version Control System for any of your Debian work, you "
-"can use one the existing repositories hosted on Alioth or you can request a "
-"new project and ask for the VCS repository of your choice. Alioth supports "
+"can use one of the existing repositories hosted on Alioth or you can request "
+"a new project and ask for the VCS repository of your choice. Alioth supports "
"CVS (cvs.alioth.debian.org/cvs.debian.org), Subversion (svn.debian.org), "
"Arch (tla/baz, both on arch.debian.org), Bazaar (bzr.debian.org), Darcs "
"(darcs.debian.org), Mercurial (hg.debian.org) and Git (git.debian.org). "
"The <link linkend=\"testing\">testing</link> distribution is generated "
"automatically by taking packages from <literal>unstable</literal> if they "
"satisfy certain criteria. Those criteria should ensure a good quality for "
-"packages within <literal>testing</literal>. The update to <literal>testing "
+"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\"/>."
msgstr ""
"literal>, and a new copy is created for the new <literal>testing</literal>, "
"and the previous <literal>stable</literal> is renamed to <literal>oldstable</"
"literal> and stays there until it is finally archived. On archiving, the "
-"contents are moved to <literal>&archive-host;</literal>)."
+"contents are moved to <literal>&archive-host;</literal>."
msgstr ""
"一定の開発期間後、リリースマネージャが適当であると決定すると、<literal>テスト"
"版 (testing)</literal> ディストリビューションはフリーズされます。これは、"
msgid ""
"<command>dak ls</command> is part of the dak suite of tools, listing "
"available package versions for all known distributions and architectures. "
-"The <command>dak</command> tool is available on <literal>&ftp-master-host; </"
+"The <command>dak</command> tool is available on <literal>&ftp-master-host;</"
"literal>, and on the mirror on <literal>&ftp-master-mirror;</literal>. It "
"uses a single argument corresponding to a package name. An example will "
"explain it better:"
<title>The VCS servers</title>
<para>
If you need to use a Version Control System for any of your Debian work,
-you can use one the existing repositories hosted on Alioth or you can
+you can use one of the existing repositories hosted on Alioth or you can
request a new project and ask for the VCS repository of your choice.
Alioth supports CVS (cvs.alioth.debian.org/cvs.debian.org), Subversion
(svn.debian.org), Arch (tla/baz, both on arch.debian.org), Bazaar
The <link linkend="testing">testing</link> distribution is generated
automatically by taking packages from <literal>unstable</literal> if they
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"/>.
+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"/>.
</para>
<para>
After a period of development, once the release manager deems fit, the
new copy is created for the new <literal>testing</literal>, and the previous
<literal>stable</literal> is renamed to <literal>oldstable</literal> and
stays there until it is finally archived. On archiving, the contents are moved
-to <literal>&archive-host;</literal>).
+to <literal>&archive-host;</literal>.
</para>
<para>
This development cycle is based on the assumption that the
<para>
<command>dak ls</command> is part of the dak suite of tools, listing
available package versions for all known distributions and architectures.
-The <command>dak</command> tool is available on <literal>&ftp-master-host;
-</literal>, and on the mirror on <literal>&ftp-master-mirror;</literal>.
-It uses a single argument corresponding to a package name. An example will
-explain it better:
+The <command>dak</command> tool is available on
+<literal>&ftp-master-host;</literal>, and on the mirror on
+<literal>&ftp-master-mirror;</literal>. It uses a single argument
+corresponding to a package name. An example will explain it better:
</para>
<screen>
$ dak ls evince
~ianmdlvl / developers-reference.git / commitdiff