diff -Nru developers-reference-3.4.20/best-pkging-practices.dbk developers-reference-3.4.21/best-pkging-practices.dbk
--- developers-reference-3.4.20/best-pkging-practices.dbk 2018-07-13 09:23:40.000000000 +0000
+++ developers-reference-3.4.21/best-pkging-practices.dbk 2018-09-21 14:20:13.000000000 +0000
@@ -675,7 +675,7 @@
If you need to check for the existence of a command, you should use something
like
-if which install-docs > /dev/null; then ...
+&if-which-install-docs;
You can use this function to search $PATH for a command
name, passed as an argument. It returns true (zero) if the command was found,
@@ -1618,7 +1618,7 @@
Also, it is recommended to adjust its section to
oldlibs
and its priority to
-extra
+optional
in order to ease deborphan's job.
diff -Nru developers-reference-3.4.20/common.ent developers-reference-3.4.21/common.ent
--- developers-reference-3.4.20/common.ent 2018-07-13 09:23:40.000000000 +0000
+++ developers-reference-3.4.21/common.ent 2018-09-23 15:09:13.000000000 +0000
@@ -110,6 +110,7 @@
+
@@ -140,6 +141,7 @@
+
@@ -188,6 +190,8 @@
address" | mail request@&bugs-host;'>
+ /dev/null; then ...">
+
diff -Nru developers-reference-3.4.20/debian/changelog developers-reference-3.4.21/debian/changelog
--- developers-reference-3.4.20/debian/changelog 2018-07-13 09:23:40.000000000 +0000
+++ developers-reference-3.4.21/debian/changelog 2018-09-25 21:21:04.000000000 +0000
@@ -1,3 +1,17 @@
+developers-reference (3.4.21) unstable; urgency=medium
+
+ [ Tobias Frost ]
+ * Team upload.
+ * Fix Alioth references in README-contrib (Closes: #907605)
+ * Add package-salvaging text (Closes: #681833, #907535).
+ * Move shell snippet in §6.4 to common.ent.
+ * Update German translation. (Closes: #908867)
+
+ [ Nicholas D Steeves ]
+ * Change priority extra to optional in §6.7.7 (Closes: #879863).
+
+ -- Tobias Frost Tue, 25 Sep 2018 23:21:04 +0200
+
developers-reference (3.4.20) unstable; urgency=medium
[ Raphaël Hertzog ]
diff -Nru developers-reference-3.4.20/developer-duties.dbk developers-reference-3.4.21/developer-duties.dbk
--- developers-reference-3.4.20/developer-duties.dbk 2018-07-13 09:23:40.000000000 +0000
+++ developers-reference-3.4.21/developer-duties.dbk 2018-09-23 15:09:13.000000000 +0000
@@ -140,6 +140,8 @@
Maintaining your public key
+
Be very careful with your private keys. Do not place them on any public
servers or multiuser machines, such as the Debian servers (see ). Back your keys up; keep a copy offline. Read
diff -Nru developers-reference-3.4.20/pkgs.dbk developers-reference-3.4.21/pkgs.dbk
--- developers-reference-3.4.20/pkgs.dbk 2018-07-13 09:23:40.000000000 +0000
+++ developers-reference-3.4.21/pkgs.dbk 2018-09-23 15:09:51.000000000 +0000
@@ -1471,15 +1471,20 @@
information and procedures.
-It is not OK to simply take over a package that you feel is neglected — that
-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 .
+It is not OK to simply take over a package without assent
+of the current maintainer — that would be package hijacking.
+You can, of course, contact the current maintainer and ask them for
+permission to take over the package.
-Generally, you may not take over the package without the assent of the current
-maintainer. Even if they ignore you, that is still not grounds to take over a
-package. Complaints about maintainers should be brought up on the developers'
+However, when a package has been neglected by the maintainer, you might
+be able to take over package maintainership by following the package
+salvaging process as described in .
+If you have reason to believe a maintainer is no longer active at all,
+see .
+
+
+Complaints about maintainers should be brought up on the developers'
mailing list. If the discussion doesn't end with a positive conclusion, and
the issue is of a technical nature, consider bringing it to the attention of
the technical committee (see the
+
+Package Salvaging
+
+
+Package salvaging is the process by which one attempts to save a
+package that, while not officially orphaned, appears poorly maintained or
+completely unmaintained. This is a weaker and faster procedure than
+orphaning a package officially through the powers of the MIA team.
+Salvaging a package is not meant to replace MIA handling, and differs
+in that it does not imply anything about the overall activity of a
+maintainer. Instead, it handles a package maintainership transition for
+a single package only, leaving any other package or Debian membership or
+upload rights (when applicable) untouched.
+
+ Note that the process is only intended for actively taking over
+maintainership. Do not start a package salvaging process when you do not intend
+to maintain the package for a prolonged time. If you only want to fix certain
+things, but not take over the package, you must use the NMU process,
+even if the package would be eligible for salvaging. The NMU process is
+explained in .
+
+ Another important thing to remember: It is not acceptable to
+hijack others' packages. If followed, this salvaging process will help
+you to ensure that your endeavour is not a hijack but a (legal)
+salvaging procedure, and you can counter any allegations of hijacking with a
+reference to this process. Thanks to this process, new contributors should no
+longer be afraid to take over packages that have been neglected or entirely
+forgotten.
+
+ The process is split into two phases: In the first phase you
+determine whether the package in question is
+eligible for the salvaging process. Only when the
+eligibility has been determined you may enter the second phase, the
+actual package salvaging.
+
+ For additional information, rationales and FAQs on package
+salvaging, please visit the Salvaging Packages page on the Debian
+wiki.
+
+
+When a package is eligible for package salvaging
+
+
+A package becomes eligible for salvaging when it has been neglected by the
+current maintainer. To determine that a package has really been
+neglected by the maintainer, the following indicators give
+a rough idea what to look for:
+
+
+ NMUs, especially if there has been more than one NMU
+ in a row.
+ Bugs filed against the package do not have answers
+ from the maintainer.
+ Upstream has released several versions, but despite
+ there being a bug entry asking for it, it has not been packaged.
+
+ There are QA issues with the package.
+
+
+
+
+You will have to use your judgement as to whether a given combination
+factors constitutes neglect; in case the maintainer disagrees they have
+only to say so (see below). If you're not sure about your judgement or
+simply want to be on the safe side, there is a more precise (and
+conservative) set of conditions in the Package Salvaging wiki
+page. These conditions represent a current Debian consensus on
+salvaging criteria. In any case you should explain your reasons for
+thinking the package is neglected when you file an Intent to Salvage bug
+later.
+
+
+
+
+
+How to salvage a package
+
+
+If and only if a package has been determined to be eligible
+for package salvaging, any prospective maintainer may start the following
+package salvaging procedure.
+
+
+ Open a bug with the severity "important" against the package
+ in question, expressing the intent to take over maintainership of the package.
+ For this, the title of the bug should start with ITS:
+ package-nameITS is shorthand for "Intend
+ to Salvage". You may alternatively offer to only
+ take co-maintenance of the package. When you file the bug, you must inform
+ all maintainers, uploaders and if applicable the packaging team explicitly by
+ adding them to X-Debbugs-CC. Additionally, if the
+ maintainer(s) seem(s) to be generally inactive, please inform the MIA team by
+ adding mia@qa.debian.org to X-Debbugs-CC
+ as well. As well as the explicit expression of the intent to salvage, please
+ also take the time to document your assessment of the eligibility in the bug
+ report, for example by listing the criteria you've applied and adding some
+ data to make it easier for others to assess the situation.
+
+
+
+ In this step you need to wait in case any objections to the salvaging are
+ raised; the maintainer, any current uploader or any member of the associated
+ packaging team of the package in question may object publicly in response to
+ the bug you've filed within 21 days, and this terminates
+ the salvaging process.
+ The current maintainers may also agree
+ to your intent to salvage by filing a (signed) public response to the the bug.
+ They might propose that you become a co-maintainer instead of the sole
+ maintainer. On team maintained packages, a member of the associated team can
+ accept your salvaging proposal by sending out a signed agreement notice to the
+ ITS bug, alternatively inviting you to become a new co-maintainer of the
+ package. The team may require you to keep the package under the team's
+ umbrella, but then may ask or invite you to join the team. In any of these
+ cases where you have received the OK to proceed, you can upload the new
+ package immediately as the new (co-)maintainer, without the need to utilise
+ the DELAYED queue as described in the next step.
+
+
+
+ After the 21 days delay, if no answer has been sent to the bug from the
+ maintainer, one of the uploaders or team, you may upload the new release of
+ the package into the DELAYED queue with a minimum delay of
+ seven days. You should close the salvage bug in the
+ changelog and you must also send an nmudiff to the bug ensuring that copies
+ are sent to the maintainer and any uploaders (including teams) of the package
+ by CC'ing them in the mail to the BTS.
+
+ During the waiting time of the DELAYED queue, the
+ maintainer can accept the salvaging, do an upload themselves or (ask to)
+ cancel the upload. The latter two of these will also stop the salvaging
+ process, but the maintainer must reply to the salvaging bug with more
+ information about their action.
+
+
+
+
+
Collaborative maintenance
diff -Nru developers-reference-3.4.20/po4a/po/de.po developers-reference-3.4.21/po4a/po/de.po
--- developers-reference-3.4.20/po4a/po/de.po 2018-07-13 09:23:40.000000000 +0000
+++ developers-reference-3.4.21/po4a/po/de.po 2018-09-24 19:32:23.000000000 +0000
@@ -7,14 +7,15 @@
msgstr ""
"Project-Id-Version: developers-reference 3.4.18\n"
"Report-Msgid-Bugs-To: developers-reference@packages.debian.org\n"
-"POT-Creation-Date: 2018-07-13 11:17+0200\n"
-"PO-Revision-Date: 2016-05-04 08:26+0100\n"
-"Last-Translator: Chris Leick \n"
+"POT-Creation-Date: 2018-09-24 21:32+0200\n"
+"PO-Revision-Date: 2018-09-21 16:55+0200\n"
+"Last-Translator: Tobias Frost \n"
"Language-Team: German \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: Poedit 2.1.1\n"
#. type: Content of:
#: best-pkging-practices.dbk:7
@@ -23,15 +24,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:9
-#, fuzzy
-#| msgid ""
-#| "Debian's quality is largely due to the Debian Policy, which defines explicit baseline requirements "
-#| "which all Debian packages must fulfill. Yet there is also a shared "
-#| "history of experience which goes beyond the Debian Policy, an "
-#| "accumulation of years of experience in packaging. Many very talented "
-#| "people have created great tools, tools which help you, the Debian "
-#| "maintainer, create and maintain excellent packages."
msgid ""
"Debian's quality is largely due to the Debian Policy, which defines explicit baseline requirements that "
@@ -70,12 +62,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:26
-#, fuzzy
-#| msgid ""
-#| "The following recommendations apply to the debian/rules"
-#| "filename> file. Since debian/rules controls the "
-#| "build process and selects the files which go into the package (directly "
-#| "or indirectly), it's usually the file maintainers spend the most time on."
msgid ""
"The following recommendations apply to the debian/rules "
"file. Since debian/rules controls the build process "
@@ -220,15 +206,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:92
-#, fuzzy
-#| msgid ""
-#| "Fortunately, with the source format “3.0 (quilt)” it is now possible to "
-#| "keep patches separate without having to modify debian/rules"
-#| "filename> to setup a patch system. Patches are stored in debian/"
-#| "patches/ and when the source package is unpacked patches "
-#| "listed in debian/patches/series are automatically "
-#| "applied. As the name implies, patches can be managed with "
-#| "quilt."
msgid ""
"Fortunately, with the source format “3.0 (quilt)” it is now possible to keep "
"patches separate without having to modify debian/rules "
@@ -271,12 +248,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:112
-#, fuzzy
-#| msgid ""
-#| "quilt is the recommended tool for this. It does all "
-#| "of the above, and also allows to manage patch series. See the "
-#| "quilt package for more "
-#| "information."
msgid ""
"quilt is the recommended tool for this. It does all of "
"the above, and also allows one to manage patch series. See the
#: best-pkging-practices.dbk:143
-#, fuzzy
-#| msgid ""
-#| "The first case is a bit more difficult since it involves multiple "
-#| "recompiles of the same software but with different configuration "
-#| "options. The vim source "
-#| "package is an example of how to manage this using an hand-crafted "
-#| "debian/rules file."
msgid ""
"The first case is a bit more difficult since it involves multiple recompiles "
"of the same software but with different configuration options. The "
@@ -359,7 +323,7 @@
"selben Software einschließt, aber mit unterschiedlichen "
"Konfigurationsoptionen. Das vim-"
"Quellpaket ist ein Beispiel dafür, wie dies mit einer handgemachten "
-"debian/rules-Datei verwaltet wird."
+"debian/rules-Datei gemacht wird."
#. type: Content of:
#: best-pkging-practices.dbk:155
@@ -640,14 +604,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:279
-#, fuzzy
-#| msgid ""
-#| "The following paragraphs should answer the following questions: Why do I "
-#| "as a user need this package? What other features does the package have? "
-#| "What outstanding features and deficiencies are there compared to other "
-#| "packages (e.g., if you need X, use Y instead)? Is this package related to "
-#| "other packages in some way that is not handled by the package manager (e."
-#| "g., this is the client for the foo server)?"
msgid ""
"The following paragraphs should answer the following questions: Why do I as "
"a user need this package? What other features does the package have? What "
@@ -740,11 +696,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:329
-#, fuzzy
-#| msgid ""
-#| "How is this package different from the competition? Is it a better "
-#| "implementation? more features? different features? Why should I choose "
-#| "this package."
msgid ""
"How is this package different from the competition? Is it a better "
"implementation? more features? different features? Why should I choose this "
@@ -822,18 +773,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:374
-#, fuzzy
-#| msgid ""
-#| "Value of this field should be a string identifying unequivocally the "
-#| "location of the Version Control System repository used to maintain the "
-#| "given package, if available. * identify the Version "
-#| "Control System; currently the following systems are supported by the "
-#| "package tracking system: arch, bzr "
-#| "(Bazaar), cvs, darcs, git"
-#| "literal>, hg (Mercurial), mtn "
-#| "(Monotone), svn (Subversion). It is allowed to "
-#| "specify different VCS fields for the same package: they will all be shown "
-#| "in the PTS web interface."
msgid ""
"Value of this field should be a string identifying unequivocally the "
"location of the Version Control System repository used to maintain the given "
@@ -1024,7 +963,7 @@
#. type: Content of:
#: best-pkging-practices.dbk:466
msgid "Selecting the upload urgency"
-msgstr ""
+msgstr "Die Dringlichkeit des Uploads wählen"
#. type: Content of:
#: best-pkging-practices.dbk:468
@@ -1038,6 +977,15 @@
"urgency=low if the changes since the "
"last upload are large and might be disruptive in unanticipated ways."
msgstr ""
+"Das Release-Team hat angegeben, dass sie erwarten, dass die meisten Uploads "
+"nach unstable die Dringlichkeit urgency=medium verwenden. Deshalb sollten Sie urgency=medium benutzen, es sei denn, es gibt "
+"spezielle Gründe, dass der Upload schneller oder langsamer nach "
+"testing migrieren soll (wie in beschrieben). Beispielsweise können Sie urgency=low nehmen, falls die Änderungen seit dem letzten "
+"Upload sehr umfangreiche oder disruptive, unerwartete Änderungen enthalten."
#. type: Content of:
#: best-pkging-practices.dbk:482
@@ -1204,14 +1152,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:559
-#, fuzzy
-#| msgid ""
-#| "If for some reason you didn't mention the bug number in a previous "
-#| "changelog entry, there's no problem, just close the bug normally in the "
-#| "BTS. There's no need to touch the changelog file, presuming the "
-#| "description of the fix is already in (this applies to the fixes by the "
-#| "upstream authors/maintainers as well, you don't have to track bugs that "
-#| "they fixed ages ago in your changelog)."
msgid ""
"If for some reason you didn't mention the bug number in a previous changelog "
"entry, there's no problem, just close the bug normally in the BTS. There's "
@@ -1223,7 +1163,7 @@
"Falls Sie aus irgend einem Grund die Fehlernummer in einem früheren "
"Änderungsprotokolleintrag nicht erwähnt haben, ist das kein Problem. "
"Schließen Sie den Fehler einfach im BTS. Es ist nicht nötig, die "
-"Änderungsprotokolldatei anzurühren, vorausgesetzt, die Beschreibung der "
+"Änderungsprotokolldatei anzufassen, vorausgesetzt, die Beschreibung der "
"Fehlerbehebung ist bereits darin enthalten (dies gilt auch für Korrekturen "
"durch die Originalautoren/-Betreuer. Sie müssen keine Fehler verfolgen, die "
"diese bereits vor Jahren in Ihrem Änderungsprotokoll behoben haben)."
@@ -1356,15 +1296,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:638
-#, fuzzy
-#| msgid ""
-#| "Maintainer scripts include the files debian/postinst"
-#| "filename>, debian/preinst, debian/prerm"
-#| "filename> and debian/postrm. These scripts take "
-#| "care of any package installation or deinstallation setup which isn't "
-#| "handled merely by the creation or removal of files and directories. The "
-#| "following instructions supplement the Debian Policy."
msgid ""
"Maintainer scripts include the files debian/postinst, "
"debian/preinst, debian/prerm and "
@@ -1373,13 +1304,13 @@
"creation or removal of files and directories. The following instructions "
"supplement the Debian Policy."
msgstr ""
-"Betreuerskripte beinhalten die Dateien debian/postinst, "
-"debian/preinst, debian/prerm und "
-"debian/postrm. Diese Skripte kümmern sich um jede "
-"Paketeinrichtung bei Installation oder Deinstallation des Pakets, bei der "
-"mehr als nur das Erstellen oder Entfernen von Dateien und Verzeichnissen "
-"erledigt werden muss. Die folgenden Anweisungen ergänzen die Debian Policy."
+"Zu den Betreuerskripten gehören die Dateien debian/postinst"
+"filename>, debian/preinst, debian/prerm"
+"filename> und debian/postrm. Diese Skripte kümmern sich "
+"um die Paketeinrichtung bei jeder Installation oder Deinstallation des "
+"Pakets, bei dem es nicht ausreicht, nur die Dateien und Verzeichnisse zu "
+"erstellen oder zu entfernen. Die folgenden Anweisungen ergänzen die Debian Policy."
#. type: Content of:
#: best-pkging-practices.dbk:646
@@ -1460,10 +1391,9 @@
#. type: Content of:
#: best-pkging-practices.dbk:678
-#, fuzzy, no-wrap
-#| msgid "if [ -x /usr/sbin/install-docs ]; then ..."
-msgid "if which install-docs > /dev/null; then ..."
-msgstr "if [ -x /usr/sbin/install-docs ]; then ..."
+#, no-wrap
+msgid "&if-which-install-docs;"
+msgstr "&if-which-install-docs;"
#. type: Content of:
#: best-pkging-practices.dbk:680
@@ -1510,15 +1440,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:699
-#, fuzzy
-#| msgid ""
-#| "Debconf is a configuration "
-#| "management system which can be used by all the various packaging scripts "
-#| "(postinst mainly) to request feedback from the user "
-#| "concerning how to configure the package. Direct user interactions must "
-#| "now be avoided in favor of debconf"
-#| "systemitem> interaction. This will enable non-interactive installations "
-#| "in the future."
msgid ""
"Debconf is a configuration "
"management system that can be used by all the various packaging scripts "
@@ -1532,8 +1453,8 @@
"(hauptsächlich postinst) benutzt werden kann, um "
"Rückmeldungen von Anwendern betreffend der Paketkonfiguration abzufragen. "
"Direkte Benutzer-Interaktion muss nun zugunsten der Interaktion mit "
-"debconf vermieden werden. Dies "
-"wird in Zukunft nicht interaktive Installationen ermöglichen."
+"debconf vermieden werden, damit in "
+"Zukunft unbeobachtete Installationen möglich sind."
#. type: Content of:
#: best-pkging-practices.dbk:707
@@ -1584,13 +1505,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:728
-#, fuzzy
-#| msgid ""
-#| "Keep usage notes to what they belong: the NEWS.Debian"
-#| "filename>, or README.Debian file. Only use notes "
-#| "for important notes which may directly affect the package usability. "
-#| "Remember that notes will always block the install until confirmed or "
-#| "bother the user by email."
msgid ""
"Keep usage notes to what they belong: the NEWS.Debian, "
"or README.Debian file. Only use notes for important "
@@ -1600,18 +1514,12 @@
"Lassen Sie Hinweise zur Benutzung der Software dort, wozu sie gehören: in "
"den Dateien NEWS.Debian oder README.Debian"
"filename>. Benutzen Sie Debconf-Meldungen nur für wichtige Anmerkungen, die "
-"direkt die Benutzbarkeit des Pakets beeinflussen. Bedenken Sie, dass diese "
-"die Installation immer blockieren, bis Sie bestätigt wurden, oder sie "
-"belästigen den Anwender per E-Mail."
+"direkt die Benutzbarkeit des Pakets betreffen. Bedenken Sie, dass diese die "
+"Installation immer blockieren, bis Sie bestätigt wurden, oder sie belästigen "
+"den Anwender per E-Mail."
#. type: Content of:
#: best-pkging-practices.dbk:734
-#, fuzzy
-#| msgid ""
-#| "Carefully choose the questions priorities in maintainer scripts. See "
-#| " debconf-devel 7"
-#| "manvolnum> for details about priorities. Most questions "
-#| "should use medium and low priorities."
msgid ""
"Carefully choose the questions' priorities in maintainer scripts. See "
" debconf-devel 7"
@@ -1683,18 +1591,13 @@
#. type: Content of:
#: best-pkging-practices.dbk:768
-#, fuzzy
-#| msgid ""
-#| "Debconf templates may be translated. Debconf, along with its sister "
-#| "package po-debconf offers a simple framework for "
-#| "getting templates translated by translation teams or even individuals."
msgid ""
"Debconf templates may be translated. Debconf, along with its sister package "
"po-debconf, offers a simple framework for getting "
"templates translated by translation teams or even individuals."
msgstr ""
"Debconf-Vorlagen können übersetzt werden. Debconf bietet zusammen mit seinem "
-"Schwesterpaket po-debconf ein einfaches Gerüst, um "
+"Schwesterpaket po-debconf ein einfaches Werkzeug, um "
"Vorlagen durch Übersetzer-Teams oder sogar einzelne Personen übersetzen zu "
"lassen."
@@ -1712,14 +1615,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:778
-#, fuzzy
-#| msgid ""
-#| "Avoid changing templates too often. Changing templates text induces more "
-#| "work to translators which will get their translation fuzzied. A fuzzy "
-#| "translation is a string for which the original changed since it was "
-#| "translated, therefore requiring some update by a translator to be "
-#| "usable. When changes are small enough, the original translation is kept "
-#| "in PO files but marked as fuzzy."
msgid ""
"Avoid changing templates too often. Changing template text induces more "
"work for translators, which will get their translation fuzzied. A fuzzy "
@@ -1771,16 +1666,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:802
-#, fuzzy
-#| msgid ""
-#| "This command will first synchronize the PO and POT files in "
-#| "debian/po with the templates files listed in "
-#| "debian/po/POTFILES.in. Then, it will send a call "
-#| "for new translations, in the &email-debian-i18n; mailing list. Finally, "
-#| "it will also send a call for translation updates to the language team "
-#| "(mentioned in the Language-Team field of each PO "
-#| "file) as well as the last translator (mentioned in Last-"
-#| "translator)."
msgid ""
"This command will first synchronize the PO and POT files in debian/"
"po with the template files listed in debian/po/POTFILES."
@@ -1795,7 +1680,7 @@
"Vorlagendateien synchronisieren. Dann wird er einen Aufruf für neue "
"Übersetzungen an die Mailingliste &email-debian-i18n; senden. Am Schluss "
"wird er außerdem einen Aufruf für neue Übersetzungen an das Sprach-Team (im "
-"Feld Language-Team jeder PO-Datei erwähnt) sowie den "
+"Feld Language-Team jeder PO-Datei erwähnt), sowie den "
"letzten Übersetzer (aus Last-Translator) senden."
#. type: Content of:
@@ -1967,12 +1852,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:900
-#, fuzzy
-#| msgid ""
-#| "Templates text should not make reference to widgets belonging to some "
-#| "debconf interfaces. Sentences like If you answer Yes..."
-#| "emphasis> have no meaning for users of graphical interfaces which use "
-#| "checkboxes for boolean questions."
msgid ""
"Templates text should not make reference to widgets belonging to some "
"debconf interfaces. Sentences like If you answer Yes..."
@@ -1980,10 +1859,9 @@
"checkboxes for boolean questions."
msgstr ""
"Vorlagentexte sollten keinen Bezug zu Steuerelementen herstellen, die zu "
-"irgendwelchen Debconf-Schnittstellen gehören. Sätze wie If you "
-"answer Yes... haben keinen Sinn für Benutzer grafischer "
-"Oberflächen, die für die Beantwortung logischer Fragen Kontrollkästchen "
-"verwenden."
+"irgendwelchen Debconf-Schnittstellen gehören. Sätze wie Wenn Sie "
+"mit Ja antworten... haben keinen Sinn für Benutzer grafischer "
+"Oberflächen, weil dort bei logischen Fragen Kontrollkästchen angehakt werden."
#. type: Content of:
#: best-pkging-practices.dbk:905
@@ -2015,16 +1893,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:919
-#, fuzzy
-#| msgid ""
-#| "You should avoid the use of first person (I will do this..."
-#| "emphasis> or We recommend...). The computer is not "
-#| "a person and the Debconf templates do not speak for the Debian "
-#| "developers. You should use neutral construction. Those of you who "
-#| "already wrote scientific publications, just write your templates like you "
-#| "would write a scientific paper. However, try using active voice if still "
-#| "possible, like Enable this if ... instead of "
-#| "This can be enabled if...."
msgid ""
"You should avoid the use of first person (I will do this..."
"emphasis> or We recommend...). The computer is not a "
@@ -2035,21 +1903,24 @@
"like Enable this if ... instead of This can "
"be enabled if...."
msgstr ""
-"Sie sollten vermeiden, in der ersten Person zu reden (I will do "
-"this... oder We recommend...). Der Rechner "
-"ist keine Person und die Debconf-Vorlagen sprechen nicht stellvertretend für "
-"Debian-Entwickler. Sie sollten neutrale Formulierungen benutzen. Diejenigen "
-"unter Ihnen, die bereits wissenschaftliche Publikationen verfasst haben, "
-"können ihre Vorlagen so schreiben, als würden Sie wissenschaftliche Papiere "
-"verfassen. Versuchen Sie jedoch, wenn möglich eine aktive Anrede zu "
-"verwenden, wie Enable this if ... anstelle von "
-"This can be enabled if...."
+"Sie sollten vermeiden, in der ersten Person zu reden (Ich werde "
+"das tun... oder Wir empfehlen...). Der "
+"Rechner ist keine Person und die Debconf-Vorlagen sprechen nicht "
+"stellvertretend für Debian-Entwickler. Sie sollten neutrale Formulierungen "
+"benutzen. Diejenigen unter Ihnen, die bereits wissenschaftliche "
+"Publikationen verfasst haben, können ihre Vorlagen so schreiben, als würden "
+"Sie wissenschaftliche Papiere verfassen. Versuchen Sie jedoch, wenn möglich "
+"eine aktive Anrede zu verwenden, wie Aktivieren Sie dies, wenn ..."
+" anstelle von Dies kann aktiviert werden, wenn..."
+"emphasis>."
#. type: Content of:
#: best-pkging-practices.dbk:929
msgid "Be gender neutral"
msgstr "Formulieren Sie geschlechtsneutral"
+# "singluar they" is not easy in German..
+# Maybe a link to https://geschicktgendern.de/ helpful? (site is licensed CC-BY-NC)
#. type: Content of:
#: best-pkging-practices.dbk:931
msgid ""
@@ -2060,6 +1931,12 @@
"you should use the plural form (singular they)."
msgstr ""
+"Um unser Bekenntnis zu unserem Diversity Statement zu zeigen, verwenden Sie bitte in "
+"Ihren Texten geschlechtergerechte Formulierungen, "
+"indem Sie Pronomen wie \"Er\" oder \"Sie\" vermeiden, wenn Sie auf eine "
+"Aufgabenrolle (wie zum Beispiel Betreuer) Bezug nehmen."
#. type: Content of:
#: best-pkging-practices.dbk:945
@@ -2260,20 +2137,14 @@
#. type: Content of:
#: best-pkging-practices.dbk:1044
-#, fuzzy
-#| msgid ""
-#| "This type is designed to handle error messages. It is mostly similar to "
-#| "the note type. Frontends may present it differently (for instance, the "
-#| "dialog frontend of cdebconf draws a red screen instead of the usual blue "
-#| "one)."
msgid ""
"This type is designed to handle error messages. It is mostly similar to the "
"note type. Front ends may present it differently (for instance, the dialog "
"front end of cdebconf draws a red screen instead of the usual blue one)."
msgstr ""
-"Dieser Typ wurde entworfen, um Fehlermeldungen zu handhaben. Er ist meist "
-"dem Typ »note« ähnlich. Oberflächen könnten ihn unterschiedlich anzeigen "
-"(die Oberfläche von Cdebconf zeichnet beispielsweise einen roten statt des "
+"Dieser Typ wurde für Fehlermeldungen entworfen. Er ist dem Typ »note« am "
+"ähnlichsten. Oberflächen könnten ihn unterschiedlich anzeigen (die "
+"Oberfläche von Cdebconf zeichnet beispielsweise einen roten statt des "
"üblichen blauen Bildschirms)."
#. type: Content of:
@@ -2315,12 +2186,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:1069
-#, fuzzy
-#| msgid ""
-#| "The short description should be able to stand on its own. Some "
-#| "interfaces do not show the long description by default, or only if the "
-#| "user explicitely asks for it or even do not show it at all. Avoid things "
-#| "like What do you want to do?"
msgid ""
"The short description should be able to stand on its own. Some interfaces "
"do not show the long description by default, or only if the user explicitly "
@@ -2330,7 +2195,7 @@
"Die Kurzbeschreibung sollte für sich allein stehen können. Einige "
"Schnittstellen zeigen die ausführliche Beschreibung standardmäßig nicht an, "
"oder nur, wenn der Benutzer explizit danach fragt, oder eventuell wird sie "
-"gar nicht angezeigt. Vermeiden Sie Dinge wie »Was möchten Sie tun?«"
+"gar nicht angezeigt. Vermeiden Sie sowas wie »Was möchten Sie tun?«"
#. type: Content of:
#: best-pkging-practices.dbk:1075
@@ -2409,18 +2274,13 @@
#. type: Content of:
#: best-pkging-practices.dbk:1109
-#, fuzzy
-#| msgid ""
-#| "This field should be used for select and multiselect types. It contains "
-#| "the possible choices which will be presented to users. These choices "
-#| "should be separated by commas."
msgid ""
"This field should be used for select and multiselect types. It contains the "
"possible choices that will be presented to users. These choices should be "
"separated by commas."
msgstr ""
"Dieses Feld sollte für »select«- und »multiselect«-Typen verwandt werden. Es "
-"enthält die Auswahlmöglichkeiten, die dem Benutzer angezeigt werden. Diese "
+"enthält die Auswahlmöglichkeiten, die dem Benutzer angezeigt werden. Die "
"Auswahlmöglichkeiten sollten durch Komma getrennt werden."
#. type: Content of:
@@ -2441,10 +2301,8 @@
#. type: Content of:
#: best-pkging-practices.dbk:1127
-#, fuzzy
-#| msgid "Templates fields specific style guide"
msgid "Template fields specific style guide"
-msgstr "Stilanleitung für Vorlagenfelder"
+msgstr "Gestaltungsrichtlinie für Vorlagenfelder"
#. type: Content of:
#: best-pkging-practices.dbk:1129
@@ -2511,24 +2369,16 @@
#. type: Content of:
#: best-pkging-practices.dbk:1168
-#, fuzzy
-#| 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)."
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)."
msgstr ""
-"Die Kurzbeschreibung sollte in der Frageform ausgedrückt werden, die kurz "
-"gehalten und generell mit einem Fragezeichen beendet werden sollte. Knapper "
-"Schreibstil ist erlaubt und sogar gewollt, falls die Frage eher lang ist. "
-"(Denken Sie daran, dass Übersetzungen oft länger als die Originalversionen "
-"sind.)"
+"Die Kurzbeschreibung sollte als Frage formuliert und kurz gehalten werden, "
+"und generell mit einem Fragezeichen enden. Kompakter Schreibstil ist erlaubt "
+"und sogar gewollt, falls die Frage eher lang ist. (Denken Sie daran, dass "
+"Übersetzungen oft länger als die Originalversionen sind.)"
#. type: Content of:
#: best-pkging-practices.dbk:1176
@@ -2547,12 +2397,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:1188
-#, fuzzy
-#| msgid ""
-#| "The short description is a prompt and not"
-#| "emphasis> a title. Do not use "
-#| "useless Please choose... constructions. Users are clever enough to "
-#| "figure out they have to choose something...:)"
msgid ""
"The short description is a prompt and not"
"emphasis> a title. Do not use useless "
@@ -2561,7 +2405,7 @@
msgstr ""
"Die Kurzbeschreibung ist eine Abfrage und kein"
"emphasis> Titel. Benutzen Sie keine "
-"nutzlosen »Please choose...«-Konstruktionen. Anwender sind klug genug "
+"nutzlosen »Bitte wählen Sie...«-Konstruktionen. Anwender sind klug genug, um "
"herauszufinden, dass sie etwas auswählen sollen ... :)"
#. type: Content of:
@@ -2603,16 +2447,6 @@
#. type: Content of:
#: best-pkging-practices.dbk:1221
-#, fuzzy
-#| msgid ""
-#| "Do not abuse debconf. Notes are the "
-#| "most common way to abuse debconf. As written in debconf-devel manual "
-#| "page: it's best to use them only for warning about very serious "
-#| "problems. The NEWS.Debian or README."
-#| "Debian files are the appropriate location for a lot of notes. "
-#| "If, by reading this, you consider converting your Note type templates to "
-#| "entries in NEWS.Debian or README.Debian"
-#| "filename>, plus consider keeping existing translations for the future."
msgid ""
"Do not abuse debconf. Notes are the "
"most common way to abuse debconf. As written in the debconf-devel manual "
@@ -2623,15 +2457,15 @@
"NEWS.Debian or README.Debian, "
"please consider keeping existing translations for the future."
msgstr ""
-"Missbrauchen Sie Debconf nicht. Notizen "
-"sind die häufigste Art, auf die Debconf missbraucht wird. Wie steht doch in "
-"der Handbuchseite von »debconf-devel« geschrieben: Es ist am Besten, dies "
-"nur für Warnungen über sehr ernsthafte Probleme zu benutzen. Die Dateien "
-"NEWS.Debian oder README.Debian "
-"sind für viele Notizen der passende Ort. Denken Sie, wenn Sie dies lesen, "
-"darüber nach, Ihre Vorlagen des Typs »notes« zu Einträgen in NEWS."
-"Debian oder README.Debian umzuwandeln und "
-"existierende Übersetzungen für die Zukunft aufzubewahren."
+"Missbrauchen Sie Debconf nicht. "
+"Anmerkungen sind die häufigste Art, auf die Debconf missbraucht wird. Wie "
+"steht doch in der Handbuchseite von »debconf-devel« geschrieben: Es ist am "
+"Besten, dies nur für Warnungen über sehr ernsthafte Probleme zu benutzen. "
+"Die Dateien NEWS.Debian oder README.Debian"
+"filename> sind für viele Notizen der passende Ort. Wenn Sie dies lesen, und "
+"darüber nachdenken, Ihre »notes« zu Einträgen in NEWS.Debian"
+"filename> oder README.Debian umzuwandeln, bewahren Sie "
+"bitte dennoch Ihre existierenden Übersetzungen für die Zukunft auf."
#. type: Content of:
#: best-pkging-practices.dbk:1236
@@ -2657,29 +2491,18 @@
#. type: Content of:
#: best-pkging-practices.dbk:1247
-#, fuzzy
-#| msgid ""
-#| "If the default value, for a select template, is likely to vary depending "
-#| "on the user language (for instance, if the choice is a language choice), "
-#| "please use the _Default trick."
msgid ""
"If the default value for a select template is likely to vary depending on "
"the user language (for instance, if the choice is a language choice), please "
"use the _Default trick."
msgstr ""
-"Falls der Vorgabewert für eine Auswahlvorlage sich möglicherweise abhängig "
-"von der Sprache des Anwenders unterscheidet (zum Beispiel, weil es sich bei "
-"der Auswahl um eine Sprachauswahl handelt), benutzen Sie bitte den _Default-"
+"Falls der Vorgabewert für eine Auswahlvorlage sich wahrscheinlich abhängig "
+"von der Sprache des Anwenders ändert (zum Beispiel, weil es sich bei der "
+"Auswahl um eine Sprachauswahl handelt), benutzen Sie bitte den _Default-"
"Trick."
#. type: Content of: