[gnome-devel-docs] Update German translation
- From: Translations User D-L <translations src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-devel-docs] Update German translation
- Date: Sun, 12 Aug 2018 10:40:00 +0000 (UTC)
commit 7ab96b437117432363172e8a025a4760a1eb34f3
Author: Mario Blättermann <mario blaettermann gmail com>
Date: Sun Aug 12 10:39:32 2018 +0000
Update German translation
programming-guidelines/de/de.po | 4703 +++++++++++++++++++--------------------
1 file changed, 2245 insertions(+), 2458 deletions(-)
---
diff --git a/programming-guidelines/de/de.po b/programming-guidelines/de/de.po
index 2c441207..d7f83b47 100644
--- a/programming-guidelines/de/de.po
+++ b/programming-guidelines/de/de.po
@@ -7,33 +7,33 @@
msgid ""
msgstr ""
"Project-Id-Version: gnome-devel-docs master\n"
-"POT-Creation-Date: 2016-02-09 08:56+0000\n"
-"PO-Revision-Date: 2016-02-09 21:35+0100\n"
-"Last-Translator: Christian Kirbach <christian kirbach gmail com>\n"
+"POT-Creation-Date: 2018-06-09 14:29+0000\n"
+"PO-Revision-Date: 2018-08-12 12:38+0200\n"
+"Last-Translator: Mario Blättermann <mario blaettermann gmail com>\n"
"Language-Team: German <gnome-de gnome org>\n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
-"X-Generator: Poedit 1.8.6\n"
+"X-Generator: Poedit 2.1\n"
#. Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
msgctxt "_"
msgid "translator-credits"
msgstr ""
-"Mario Blättermann <mario blaettermann gmail com>, 2016\n"
+"Mario Blättermann <mario blaettermann gmail com>, 2016, 2018\n"
"Christian Kirbach <christian kirbach gmail com>, 2016"
#. (itstool) path: credit/name
-#: C/additional-materials.page:10 C/c-coding-style.page:10
-#: C/documentation.page:11 C/index.page:8 C/writing-good-code.page:10
+#: C/additional-materials.page:10 C/c-coding-style.page:10 C/documentation.page:11
+#: C/index.page:8 C/writing-good-code.page:10
msgid "Federico Mena-Quintero"
msgstr "Federico Mena-Quintero"
#. (itstool) path: credit/years
-#: C/additional-materials.page:12 C/c-coding-style.page:12
-#: C/documentation.page:13 C/index.page:10 C/writing-good-code.page:12
+#: C/additional-materials.page:12 C/c-coding-style.page:12 C/documentation.page:13
+#: C/index.page:10 C/writing-good-code.page:12
msgid "2013"
msgstr "2013"
@@ -41,8 +41,7 @@ msgstr "2013"
#: C/additional-materials.page:17
msgid "Other style guides and books about organizing free software projects"
msgstr ""
-"Andere Richtlinien und Bücher über die Organisation von Projekten der Freien "
-"Software"
+"Andere Richtlinien und Bücher über die Organisation von Projekten der Freien Software"
#. (itstool) path: page/title
#: C/additional-materials.page:21
@@ -52,53 +51,49 @@ msgstr "Zusätzliche Materialien"
#. (itstool) path: page/p
#: C/additional-materials.page:23
msgid ""
-"Here we give you links to other materials that you may want to read. These "
-"will teach you a lot about how to work on large distributed teams of free "
-"software developers, and about good programming style in general."
+"Here we give you links to other materials that you may want to read. These will "
+"teach you a lot about how to work on large distributed teams of free software "
+"developers, and about good programming style in general."
msgstr ""
-"Hier sind einige Links zu anderen Materialien, die Sie vielleicht lesen "
-"wollen. Sie vermitteln Ihnen einen Einblick in die Arbeitsweise weit "
-"verstreuter Teams von Entwicklern freier Software sowie über guten "
-"Programmierstil im Allgemeinen."
+"Hier sind einige Links zu anderen Materialien, die Sie vielleicht lesen wollen. Sie "
+"vermitteln Ihnen einen Einblick in die Arbeitsweise weit verstreuter Teams von "
+"Entwicklern freier Software sowie über guten Programmierstil im Allgemeinen."
#. (itstool) path: item/p
#: C/additional-materials.page:32
msgid ""
-"<link href=\"http://producingoss.com/\";>Produducing Open Source Software</"
-"link>, by Karl Fogel. This is a truly excellent book of good practices that "
-"free software projects should follow. This is about <em>social aspects</em> "
-"of the project: how to treat contributors, how to organize and moderate "
-"communication, how to deal with non-profit foundations. If you ask yourself "
-"at any time, \"how should I deal with $human_situation in the project?\", "
-"this book may provide the answer."
+"<link href=\"http://producingoss.com/\";>Producing Open Source Software</link>, by "
+"Karl Fogel. This is a truly excellent book of good practices that free software "
+"projects should follow. This is about <em>social aspects</em> of the project: how to "
+"treat contributors, how to organize and moderate communication, how to deal with non-"
+"profit foundations. If you ask yourself at any time, \"how should I deal with "
+"$human_situation in the project?\", this book may provide the answer."
msgstr ""
#. (itstool) path: item/p
#: C/additional-materials.page:46
msgid ""
-"<link href=\"http://www.gnu.org/prep/standards/\";>GNU Coding Standards</"
-"link>. This is an old document, but it still has lots of excellent advice. "
-"It talks about C coding style, issues when dealing with plug-in systems, "
-"common option names for command-line programs, conventions for Makefiles, "
-"and some very GNU-ish details like using Texinfo for documentation."
+"<link href=\"http://www.gnu.org/prep/standards/\";>GNU Coding Standards</link>. This "
+"is an old document, but it still has lots of excellent advice. It talks about C "
+"coding style, issues when dealing with plug-in systems, common option names for "
+"command-line programs, conventions for Makefiles, and some very GNU-ish details like "
+"using Texinfo for documentation."
msgstr ""
#. (itstool) path: item/p
#: C/additional-materials.page:57
msgid ""
-"<link href=\"https://www.kernel.org/doc/Documentation/CodingStyle\";>Linux "
-"Kernel Coding Style</link>. Explains the rationale for \"big indentation\", "
-"brace placement, concise but unambiguous naming, and centralized exit of "
-"functions."
+"<link href=\"https://www.kernel.org/doc/Documentation/process/coding-style.rst\";> "
+"Linux Kernel Coding Style</link>. Explains the rationale for \"big indentation\", "
+"brace placement, concise but unambiguous naming, and centralized exit of functions."
msgstr ""
#. (itstool) path: credit/name
#: C/api-stability.page:10 C/databases.page:11 C/documentation.page:16
#: C/file-system.page:11 C/gerror.page:11 C/glist.page:11 C/index.page:21
#: C/introspection.page:10 C/logging.page:11 C/main-contexts.page:11
-#: C/memory-management.page:10 C/namespacing.page:10
-#: C/parallel-installability.page:18 C/preconditions.page:11
-#: C/threading.page:11 C/tooling.page:10 C/unit-testing.page:10
+#: C/memory-management.page:10 C/namespacing.page:10 C/parallel-installability.page:18
+#: C/preconditions.page:11 C/threading.page:11 C/tooling.page:10 C/unit-testing.page:10
#: C/version-control.page:10 C/versioning.page:10
msgid "Philip Withnall"
msgstr "Philip Withnall"
@@ -107,9 +102,9 @@ msgstr "Philip Withnall"
#: C/api-stability.page:12 C/databases.page:13 C/documentation.page:18
#: C/file-system.page:13 C/gerror.page:13 C/glist.page:13 C/index.page:23
#: C/introspection.page:12 C/logging.page:13 C/memory-management.page:12
-#: C/parallel-installability.page:20 C/preconditions.page:13
-#: C/threading.page:13 C/tooling.page:12 C/unit-testing.page:12
-#: C/version-control.page:12 C/versioning.page:12
+#: C/parallel-installability.page:20 C/preconditions.page:13 C/threading.page:13
+#: C/tooling.page:12 C/unit-testing.page:12 C/version-control.page:12
+#: C/versioning.page:12
msgid "2015"
msgstr "2015"
@@ -134,21 +129,19 @@ msgstr "Zusammenfassung"
#. (itstool) path: item/p
#: C/api-stability.page:26
-msgid ""
-"Define API stability guarantees for your project. (<link xref=\"#stability\"/"
-">)"
+msgid "Define API stability guarantees for your project. (<link xref=\"#stability\"/>)"
msgstr ""
-"Definieren Sie API-Stabilitätsgarantien für Ihr Projekt. (<link xref="
-"\"#stability\"/>)"
+"Definieren Sie API-Stabilitätsgarantien für Ihr Projekt. (<link xref=\"#stability\"/"
+">)"
#. (itstool) path: item/p
#: C/api-stability.page:30
msgid ""
-"Ensure version numbers are changed as appropriate when API changes. (<link "
-"xref=\"#versioning\"/>)"
+"Ensure version numbers are changed as appropriate when API changes. (<link xref="
+"\"#versioning\"/>)"
msgstr ""
-"Stellen Sie sicher, dass Versionsnummern entsprechend den API-Änderungen "
-"Ihres Projekts ebenfalls geändert werden. (<link xref=\"#versioning\"/>)"
+"Stellen Sie sicher, dass Versionsnummern entsprechend den API-Änderungen Ihres "
+"Projekts ebenfalls geändert werden. (<link xref=\"#versioning\"/>)"
#. (itstool) path: section/title
#: C/api-stability.page:38
@@ -158,16 +151,15 @@ msgstr "API und ABI"
#. (itstool) path: section/p
#: C/api-stability.page:40
msgid ""
-"At a high level, an API – <em>Application Programming Interface</em> – is "
-"the boundary between two components when developing against them. It is "
-"closely related to an ABI – <em>Application Binary Interface</em> – which is "
-"the boundary at runtime. It defines the possible ways in which other "
-"components can interact with a component. More concretely, this normally "
-"means the C headers of a library form its API, and compiled library symbols "
-"its ABI. The difference between an API and ABI is given by compilation of "
-"the code: there are certain things in a C header, such as <code>#define</"
-"code>s, which can cause a library’s API to change without changing its ABI. "
-"But these differences are mostly academic, and for all practical purposes, "
+"At a high level, an API – <em>Application Programming Interface</em> – is the "
+"boundary between two components when developing against them. It is closely related "
+"to an ABI – <em>Application Binary Interface</em> – which is the boundary at "
+"runtime. It defines the possible ways in which other components can interact with a "
+"component. More concretely, this normally means the C headers of a library form its "
+"API, and compiled library symbols its ABI. The difference between an API and ABI is "
+"given by compilation of the code: there are certain things in a C header, such as "
+"<code>#define</code>s, which can cause a library’s API to change without changing "
+"its ABI. But these differences are mostly academic, and for all practical purposes, "
"API and ABI can be treated interchangeably."
msgstr ""
@@ -177,25 +169,25 @@ msgid ""
"Examples of API-incompatible changes to a C function would be to add a new "
"parameter, change the function’s return type, or remove a parameter."
msgstr ""
-"Beispiele für API-kompatiblen Änderungen einer C-Funktion wären das "
-"Hinzufügen eines neuen Parameters, Ändern des Rückgabetyps einer Funktion "
-"oder die Entfernung eines Parameters."
+"Beispiele für API-kompatiblen Änderungen einer C-Funktion wären das Hinzufügen eines "
+"neuen Parameters, Ändern des Rückgabetyps einer Funktion oder die Entfernung eines "
+"Parameters."
#. (itstool) path: section/p
#: C/api-stability.page:59
msgid ""
-"However, many other parts of a project can form an API. If a daemon exposes "
-"itself on D-Bus, the interfaces exported there form an API. Similarly, if a "
-"C API is exposed in higher level languages by use of GIR, the GIR file forms "
-"another API — if it changes, any higher level code using it must also change."
+"However, many other parts of a project can form an API. If a daemon exposes itself "
+"on D-Bus, the interfaces exported there form an API. Similarly, if a C API is "
+"exposed in higher level languages by use of GIR, the GIR file forms another API — if "
+"it changes, any higher level code using it must also change."
msgstr ""
#. (itstool) path: section/p
#: C/api-stability.page:67
msgid ""
-"Other examples of more unusual APIs are configuration file locations and "
-"formats, and GSettings schemas. Any changes to these could require code "
-"using your library to change."
+"Other examples of more unusual APIs are configuration file locations and formats, "
+"and GSettings schemas. Any changes to these could require code using your library to "
+"change."
msgstr ""
#. (itstool) path: section/title
@@ -206,28 +198,27 @@ msgstr "Stabilität"
#. (itstool) path: section/p
#: C/api-stability.page:77
msgid ""
-"API stability refers to some level of guarantee from a project that its API "
-"will only change in defined ways in the future, or will not change at all. "
-"Generally, an API is considered ‘stable’ if it commits to backwards-"
-"compatibility (defined below); but APIs could also commit to being unstable "
-"or even forwards-compatible. The purpose of API stability guarantees is to "
-"allow people to use your project from their own code without worrying about "
-"constantly updating their code to keep up with API changes. Typical API "
-"stability guarantees mean that code which is compiled against one version of "
-"a library will run without problems against all future versions of that "
-"library with the same major version number — or similarly that code which "
-"runs against a daemon will continue to run against all future versions of "
-"that daemon with the same major version number."
+"API stability refers to some level of guarantee from a project that its API will "
+"only change in defined ways in the future, or will not change at all. Generally, an "
+"API is considered ‘stable’ if it commits to backwards-compatibility (defined below); "
+"but APIs could also commit to being unstable or even forwards-compatible. The "
+"purpose of API stability guarantees is to allow people to use your project from "
+"their own code without worrying about constantly updating their code to keep up with "
+"API changes. Typical API stability guarantees mean that code which is compiled "
+"against one version of a library will run without problems against all future "
+"versions of that library with the same major version number — or similarly that code "
+"which runs against a daemon will continue to run against all future versions of that "
+"daemon with the same major version number."
msgstr ""
#. (itstool) path: section/p
#: C/api-stability.page:93
msgid ""
-"It is possible to apply different levels of API stability to components "
-"within a project. For example, the core functions in a library could be "
-"stable, and hence their API left unchanged in future; while the newer, less "
-"core functions could be left unstable and allowed to change wildly until the "
-"right design is found, at which point they could be marked as stable."
+"It is possible to apply different levels of API stability to components within a "
+"project. For example, the core functions in a library could be stable, and hence "
+"their API left unchanged in future; while the newer, less core functions could be "
+"left unstable and allowed to change wildly until the right design is found, at which "
+"point they could be marked as stable."
msgstr ""
#. (itstool) path: section/p
@@ -253,9 +244,9 @@ msgstr "Backwards compatible (Abwärtskompatibilität)"
#. (itstool) path: item/p
#: C/api-stability.page:112
msgid ""
-"Only changes which permit code compiled against the unmodified API to "
-"continue running against the modified API are allowed (for example, "
-"functions cannot be removed)."
+"Only changes which permit code compiled against the unmodified API to continue "
+"running against the modified API are allowed (for example, functions cannot be "
+"removed)."
msgstr ""
#. (itstool) path: item/title
@@ -266,9 +257,8 @@ msgstr "Forwards compatible (Aufwärtskompatibilität)"
#. (itstool) path: item/p
#: C/api-stability.page:120
msgid ""
-"Only changes which permit code compiled against the modified API to run "
-"against the unmodified API are allowed (for example, functions cannot be "
-"added)."
+"Only changes which permit code compiled against the modified API to run against the "
+"unmodified API are allowed (for example, functions cannot be added)."
msgstr ""
#. (itstool) path: item/title
@@ -279,15 +269,14 @@ msgstr "Forwards compatible (vollständig stabil)"
#. (itstool) path: item/p
#: C/api-stability.page:128
msgid "No changes are allowed to the API, only to the implementation."
-msgstr ""
-"Es sind keine Änderungen an der API erlaubt, nur an deren Implementation."
+msgstr "Es sind keine Änderungen an der API erlaubt, nur an deren Implementation."
#. (itstool) path: section/p
#: C/api-stability.page:132
msgid ""
-"Typically, projects commit to backwards-compatibility when they say an API "
-"is ‘stable’. Very few projects commit to total stability because it would "
-"prevent almost all further development of the project."
+"Typically, projects commit to backwards-compatibility when they say an API is "
+"‘stable’. Very few projects commit to total stability because it would prevent "
+"almost all further development of the project."
msgstr ""
#. (itstool) path: section/title
@@ -299,49 +288,46 @@ msgstr "Versionierung"
#. (itstool) path: section/p
#: C/api-stability.page:142
msgid ""
-"API stability guarantees are strongly linked to project versioning; both "
-"package versioning and libtool versioning. Libtool versioning exists "
-"entirely for the purpose of tracking ABI stability, and is explained in "
-"detail on the <link href=\"https://autotools.io/libtool/version.html";
-"\">Autotools Mythbuster</link> or <link xref=\"versioning\"/>."
+"API stability guarantees are strongly linked to project versioning; both package "
+"versioning and libtool versioning. Libtool versioning exists entirely for the "
+"purpose of tracking ABI stability, and is explained in detail on the <link href="
+"\"https://autotools.io/libtool/version.html\";>Autotools Mythbuster</link> or <link "
+"xref=\"versioning\"/>."
msgstr ""
-"API-Stabilitätsgarantien sind eng mit der Versionierung des Projekts "
-"verknüpft, das betrifft sowohl die Paket- als auch die Libtool-"
-"Versionierung. Letztere dient ausschließlich dem Zweck, die API-Stabilität "
-"zu überwachen, sie wird detailliert in <link href=\"https://autotools.io/";
-"libtool/version.html\">Autotools Mythbuster</link> oder <link xref="
-"\"versioning\"/> erklärt."
+"API-Stabilitätsgarantien sind eng mit der Versionierung des Projekts verknüpft, das "
+"betrifft sowohl die Paket- als auch die Libtool-Versionierung. Letztere dient "
+"ausschließlich dem Zweck, die API-Stabilität zu überwachen, sie wird detailliert in "
+"<link href=\"https://autotools.io/libtool/version.html\";>Autotools Mythbuster</link> "
+"oder <link xref=\"versioning\"/> erklärt."
#. (itstool) path: section/p
#: C/api-stability.page:151
msgid ""
-"Package versioning (<em>major.minor.micro</em>) is strongly linked to API "
-"stability: typically, the major version number is incremented when backwards-"
-"incompatible changes are made (for example, when functions are renamed, "
-"parameters are changed, or functions are removed). The minor version number "
-"is incremented when forwards-incompatible changes are made (for example, "
-"when new public API is added). The micro version number is incremented when "
-"code changes are made without modifying API. See <link xref=\"versioning\"/> "
-"for more information."
+"Package versioning (<em>major.minor.micro</em>) is strongly linked to API stability: "
+"typically, the major version number is incremented when backwards-incompatible "
+"changes are made (for example, when functions are renamed, parameters are changed, "
+"or functions are removed). The minor version number is incremented when forwards-"
+"incompatible changes are made (for example, when new public API is added). The micro "
+"version number is incremented when code changes are made without modifying API. See "
+"<link xref=\"versioning\"/> for more information."
msgstr ""
#. (itstool) path: section/p
#: C/api-stability.page:162
msgid ""
-"API versioning is just as important for D-Bus APIs and GSettings schemas (if "
-"they are likely to change) as for C APIs. See the <link href=\"http://dbus.";
-"freedesktop.org/doc/dbus-api-design.html#api-versioning\">documentation on D-"
-"Bus API versioning</link> for details."
+"API versioning is just as important for D-Bus APIs and GSettings schemas (if they "
+"are likely to change) as for C APIs. See the <link href=\"http://dbus.freedesktop.";
+"org/doc/dbus-api-design.html#api-versioning\">documentation on D-Bus API versioning</"
+"link> for details."
msgstr ""
#. (itstool) path: section/p
#: C/api-stability.page:169
msgid ""
-"For GIR APIs, their stability typically follows the C API stability, as they "
-"are generated from the C API. One complexity is that their stability "
-"additionally depends on the version of gobject-introspection used in "
-"generating the GIR, but recent versions have not changed much so this is not "
-"a major concern."
+"For GIR APIs, their stability typically follows the C API stability, as they are "
+"generated from the C API. One complexity is that their stability additionally "
+"depends on the version of gobject-introspection used in generating the GIR, but "
+"recent versions have not changed much so this is not a major concern."
msgstr ""
#. (itstool) path: section/title
@@ -360,26 +346,26 @@ msgid ""
"<link href=\"http://en.wikipedia.org/wiki/Application_programming_interface";
"\">Wikipedia page on APIs</link>"
msgstr ""
-"<link href=\"https://de.wikipedia.org/wiki/Programmierschnittstelle";
-"\">Wikipedia-Seite zu Programmierschnittstellen</link>"
+"<link href=\"https://de.wikipedia.org/wiki/Programmierschnittstelle\";>Wikipedia-"
+"Seite zu Programmierschnittstellen</link>"
#. (itstool) path: item/p
#: C/api-stability.page:189
msgid ""
-"<link href=\"http://en.wikipedia.org/wiki/Application_binary_interface";
-"\">Wikipedia page on ABIs</link>"
+"<link href=\"http://en.wikipedia.org/wiki/Application_binary_interface\";>Wikipedia "
+"page on ABIs</link>"
msgstr ""
-"<link href=\"https://de.wikipedia.org/wiki/Bin%C3%A4rschnittstelle";
-"\">Wikipedia-Seite zu Binärschnittstellen</link>"
+"<link href=\"https://de.wikipedia.org/wiki/Bin%C3%A4rschnittstelle\";>Wikipedia-Seite "
+"zu Binärschnittstellen</link>"
#. (itstool) path: item/p
#: C/api-stability.page:193
msgid ""
-"<link href=\"http://dbus.freedesktop.org/doc/dbus-api-design.html#api-";
-"versioning\">D-Bus API versioning documentation</link>"
+"<link href=\"http://dbus.freedesktop.org/doc/dbus-api-design.html#api-versioning\";>D-"
+"Bus API versioning documentation</link>"
msgstr ""
-"<link href=\"http://dbus.freedesktop.org/doc/dbus-api-design.html#api-";
-"versioning\">Dokumentation zur Versionierung der D-Bus-API-</link>"
+"<link href=\"http://dbus.freedesktop.org/doc/dbus-api-design.html#api-versioning";
+"\">Dokumentation zur Versionierung der D-Bus-API-</link>"
#. (itstool) path: credit/name
#: C/c-coding-style.page:15 C/documentation.page:21
@@ -399,38 +385,38 @@ msgstr "C-Programmierstil"
#. (itstool) path: page/p
#: C/c-coding-style.page:25
msgid ""
-"This document presents the preferred coding style for C programs in GNOME. "
-"While coding style is very much a matter of taste, in GNOME we favor a "
-"coding style that promotes consistency, readability, and maintainability."
+"This document presents the preferred coding style for C programs in GNOME. While "
+"coding style is very much a matter of taste, in GNOME we favor a coding style that "
+"promotes consistency, readability, and maintainability."
msgstr ""
#. (itstool) path: page/p
#: C/c-coding-style.page:32
msgid ""
-"We present examples of good coding style as well as examples of bad style "
-"that is not acceptable in GNOME. Please try to submit patches that conform "
-"to GNOME’s coding style; this indicates that you have done your homework to "
-"respect the project’s goal of long-term maintainability. Patches with "
-"GNOME’s coding style will also be easier to review!"
+"We present examples of good coding style as well as examples of bad style that is "
+"not acceptable in GNOME. Please try to submit patches that conform to GNOME’s coding "
+"style; this indicates that you have done your homework to respect the project’s goal "
+"of long-term maintainability. Patches with GNOME’s coding style will also be easier "
+"to review!"
msgstr ""
#. (itstool) path: note/p
#: C/c-coding-style.page:42
msgid ""
-"This document is for C code. For other languages, check the <link xref="
-"\"index\">main page</link> of the GNOME Programming Guidelines."
+"This document is for C code. For other languages, check the <link xref=\"index"
+"\">main page</link> of the GNOME Programming Guidelines."
msgstr ""
-"Dieses Dokument bezieht sich auf C-Programmcode. Informationen zu anderen "
-"Sprachen finden Sie auf der <link xref=\"index\">Hauptseite</link> der GNOME-"
+"Dieses Dokument bezieht sich auf C-Programmcode. Informationen zu anderen Sprachen "
+"finden Sie auf der <link xref=\"index\">Hauptseite</link> der GNOME-"
"Programmierrichtlinien."
#. (itstool) path: page/p
#: C/c-coding-style.page:49
msgid ""
-"These guidelines are heavily inspired by GTK’s CODING-STYLE document, the "
-"Linux Kernel’s CodingStyle, and the GNU Coding Standards. These are slight "
-"variations of each other, with particular modifications for each project’s "
-"particular needs and culture, and GNOME’s version is no different."
+"These guidelines are heavily inspired by GTK’s CODING-STYLE document, the Linux "
+"Kernel’s CodingStyle, and the GNU Coding Standards. These are slight variations of "
+"each other, with particular modifications for each project’s particular needs and "
+"culture, and GNOME’s version is no different."
msgstr ""
#. (itstool) path: section/title
@@ -441,33 +427,32 @@ msgstr "Die allerwichtigste Regel"
#. (itstool) path: section/p
#: C/c-coding-style.page:60
msgid ""
-"The single most important rule when writing code is this: <em>check the "
-"surrounding code and try to imitate it</em>."
+"The single most important rule when writing code is this: <em>check the surrounding "
+"code and try to imitate it</em>."
msgstr ""
-"Die allerwichtigste Regel für das Schreiben von Code ist: <em>Schauen Sie "
-"sich den umgebenden Code an und versuchen Sie, dessen Stil zu imitieren</em>."
+"Die allerwichtigste Regel für das Schreiben von Code ist: <em>Schauen Sie sich den "
+"umgebenden Code an und versuchen Sie, dessen Stil zu imitieren</em>."
#. (itstool) path: section/p
#: C/c-coding-style.page:65
msgid ""
-"As a maintainer it is dismaying to receive a patch that is obviously in a "
-"different coding style to the surrounding code. This is disrespectful, like "
-"someone tromping into a spotlessly-clean house with muddy shoes."
+"As a maintainer it is dismaying to receive a patch that is obviously in a different "
+"coding style to the surrounding code. This is disrespectful, like someone tromping "
+"into a spotlessly-clean house with muddy shoes."
msgstr ""
"Für einen Maintainer ist es erschreckend, einen Patch zu bekommen, der vom "
-"umgebenden Code stilistisch stark abweicht. Das ist respektlos, so als "
-"jemand mit schlammigen Schuhen in ein blitzsauberes Haus hineintrampelt."
+"umgebenden Code stilistisch stark abweicht. Das ist respektlos, so als jemand mit "
+"schlammigen Schuhen in ein blitzsauberes Haus hineintrampelt."
#. (itstool) path: section/p
#: C/c-coding-style.page:72
msgid ""
-"So, whatever this document recommends, if there is already written code and "
-"you are patching it, keep its current style consistent even if it is not "
-"your favorite style."
+"So, whatever this document recommends, if there is already written code and you are "
+"patching it, keep its current style consistent even if it is not your favorite style."
msgstr ""
-"Was auch immer dieses Dokument empfiehlt, so sollte sich Ihr Stil stets am "
-"Stil des bereits vorhandenen Codes orientieren, auch wenn es nicht <em>Ihr "
-"bevorzugter Stil</em> ist."
+"Was auch immer dieses Dokument empfiehlt, so sollte sich Ihr Stil stets am Stil des "
+"bereits vorhandenen Codes orientieren, auch wenn es nicht <em>Ihr bevorzugter Stil</"
+"em> ist."
#. (itstool) path: section/title
#: C/c-coding-style.page:80
@@ -477,18 +462,16 @@ msgstr "Zeilenbreite"
#. (itstool) path: section/p
#: C/c-coding-style.page:82
msgid ""
-"Try to use lines of code between 80 and 120 characters long. This amount of "
-"text is easy to fit in most monitors with a decent font size. Lines longer "
-"than that become hard to read, and they mean that you should probably "
-"restructure your code. If you have too many levels of indentation, it means "
-"that you should fix your code anyway."
+"Try to use lines of code between 80 and 120 characters long. This amount of text is "
+"easy to fit in most monitors with a decent font size. Lines longer than that become "
+"hard to read, and they mean that you should probably restructure your code. If you "
+"have too many levels of indentation, it means that you should fix your code anyway."
msgstr ""
-"Versuchen Sie, Ihre Zeilen zwischen 80 und 120 Zeichen breit zu halten. "
-"Diese Breite passt am besten in die meisten Bildschirme mit einer "
-"vernünftigen Schriftgröße. Längere Zeilen sind schwerer zu lesen, außerdem "
-"sollten Sie sich in diesem Fall überlegen, ob Sie Ihren Code nicht anders "
-"beziehungsweise besser strukturieren sollten. Bei zu vielen "
-"Einrückungsebenen sollte Ihr Code ohnehin überarbeitet werden."
+"Versuchen Sie, Ihre Zeilen zwischen 80 und 120 Zeichen breit zu halten. Diese Breite "
+"passt am besten in die meisten Bildschirme mit einer vernünftigen Schriftgröße. "
+"Längere Zeilen sind schwerer zu lesen, außerdem sollten Sie sich in diesem Fall "
+"überlegen, ob Sie Ihren Code nicht anders beziehungsweise besser strukturieren "
+"sollten. Bei zu vielen Einrückungsebenen sollte Ihr Code ohnehin überarbeitet werden."
#. (itstool) path: section/title
#: C/c-coding-style.page:93
@@ -497,18 +480,17 @@ msgstr "Einzüge"
#. (itstool) path: section/p
#: C/c-coding-style.page:95
-msgid ""
-"In general there are two preferred indentation styles for code in GNOME."
+msgid "In general there are two preferred indentation styles for code in GNOME."
msgstr "Allgemein gibt es zwei zu bevorzugende Einzugsstile für Code in GNOME."
#. (itstool) path: item/p
#: C/c-coding-style.page:102
msgid ""
-"Linux Kernel style. Tabs with a length of 8 characters are used for the "
-"indentation, with K&R brace placement:"
+"Linux Kernel style. Tabs with a length of 8 characters are used for the indentation, "
+"with K&R brace placement:"
msgstr ""
-"Linux-Kernel-Stil. Tabulatoren für Einrückungen sind 8 Zeichen breit, mit "
-"einer K&R-Klammernplatzierung:"
+"Linux-Kernel-Stil. Tabulatoren für Einrückungen sind 8 Zeichen breit, mit einer "
+"K&R-Klammernplatzierung:"
#. (itstool) path: item/code
#: C/c-coding-style.page:107
@@ -546,8 +528,8 @@ msgid ""
"GNU style. Each new level is indented by 2 spaces, braces go on a line by "
"themselves, and they are indented as well."
msgstr ""
-"GNU-Stil. Jede neue Ebene wird um zwei Leerzeichen eingerückt, Klammern "
-"werden in eine eigene Zeile gesetzt und ebenfalls eingerückt."
+"GNU-Stil. Jede neue Ebene wird um zwei Leerzeichen eingerückt, Klammern werden in "
+"eine eigene Zeile gesetzt und ebenfalls eingerückt."
#. (itstool) path: item/code
#: C/c-coding-style.page:128
@@ -591,35 +573,33 @@ msgstr ""
#: C/c-coding-style.page:148
msgid ""
"Both styles have their pros and cons. The most important things is to <em>be "
-"consistent</em> with the surrounding code. For example, the GTK+ library, "
-"which is GNOME’s widget toolkit, is written with the GNU style. Nautilus, "
-"GNOME’s file manager, is written in Linux kernel style. Both styles are "
-"perfectly readable and consistent when you get used to them."
+"consistent</em> with the surrounding code. For example, the GTK+ library, which is "
+"GNOME’s widget toolkit, is written with the GNU style. Nautilus, GNOME’s file "
+"manager, is written in Linux kernel style. Both styles are perfectly readable and "
+"consistent when you get used to them."
msgstr ""
"Beide Stile haben ihre Befürworter und Gegner. Der wichtigste Punkt ist die "
-"<em>Konsistenz</em> zum umgebenden Code. Zum Beispiel ist die GTK+-"
-"Bibliothek als Widget-Toolkit für GNOME im GNU-Stil geschrieben. Nautilus "
-"dagegen, der Dateimanager von GNOME, folgt dem Linux-Kernel-Stil. Beide "
-"Stile sind bestens lesbar und konsistent, wenn Sie sie verwenden."
+"<em>Konsistenz</em> zum umgebenden Code. Zum Beispiel ist die GTK+-Bibliothek als "
+"Widget-Toolkit für GNOME im GNU-Stil geschrieben. Nautilus dagegen, der Dateimanager "
+"von GNOME, folgt dem Linux-Kernel-Stil. Beide Stile sind bestens lesbar und "
+"konsistent, wenn Sie sie verwenden."
#. (itstool) path: section/p
#: C/c-coding-style.page:157
msgid ""
-"Your first feeling when having to study or work on a piece of code that "
-"doesn’t have your preferred indentation style may be, how shall we put it, "
-"gut-wrenching. You should resist your inclination to reindent everything, or "
-"to use an inconsistent style for your patch. Remember the first rule: <em>be "
-"consistent</em> and respectful of that code’s customs, and your patches will "
-"have a much higher chance of being accepted without a lot of arguing about "
-"the right indentation style."
-msgstr ""
-"Ihr erstes Gefühl bei der Arbeit an Programmcode, der nicht Ihrem "
-"bevorzugten Einrückungsstil folgt, könnte, sagen wir, ablehnend sein. "
-"Widerstehen Sie dem Drang, alles neu einrücken zu wollen, oder für Ihren "
-"Patch einen inkonsistenten Stil zu verwenden. Erinnern Sie sich an die "
-"oberste Regel: <em>Konsistenz</em> und Respekt vor den Eigenheiten des "
-"fremden Codes, und Ihre Patches haben eine ungleich größere Chance, ohne "
-"langatmige Diskussionen über den <em>richtigen</em> Einrückungsstil "
+"Your first feeling when having to study or work on a piece of code that doesn’t have "
+"your preferred indentation style may be, how shall we put it, gut-wrenching. You "
+"should resist your inclination to reindent everything, or to use an inconsistent "
+"style for your patch. Remember the first rule: <em>be consistent</em> and respectful "
+"of that code’s customs, and your patches will have a much higher chance of being "
+"accepted without a lot of arguing about the right indentation style."
+msgstr ""
+"Ihr erstes Gefühl bei der Arbeit an Programmcode, der nicht Ihrem bevorzugten "
+"Einrückungsstil folgt, könnte, sagen wir, ablehnend sein. Widerstehen Sie dem Drang, "
+"alles neu einrücken zu wollen, oder für Ihren Patch einen inkonsistenten Stil zu "
+"verwenden. Erinnern Sie sich an die oberste Regel: <em>Konsistenz</em> und Respekt "
+"vor den Eigenheiten des fremden Codes, und Ihre Patches haben eine ungleich größere "
+"Chance, ohne langatmige Diskussionen über den <em>richtigen</em> Einrückungsstil "
"angenommen zu werden."
#. (itstool) path: section/title
@@ -630,21 +610,21 @@ msgstr "Tabulatorzeichen"
#. (itstool) path: section/p
#: C/c-coding-style.page:172
msgid ""
-"<em>Do not ever change the size of tabs in your editor</em>; leave them as 8 "
-"spaces. Changing the size of tabs means that code that you didn’t write "
-"yourself will be perpetually misaligned."
+"<em>Do not ever change the size of tabs in your editor</em>; leave them as 8 spaces. "
+"Changing the size of tabs means that code that you didn’t write yourself will be "
+"perpetually misaligned."
msgstr ""
-"<em>Ändern Sie niemals die Tabulatorbreite in Ihrem Editor</em>. Behalten "
-"Sie 8 Zeichen bei. Durch Änderungen der Tabulatorbreite wird Code, den Sie "
-"nicht selbst geschrieben haben, immer falsch ausgerichtet."
+"<em>Ändern Sie niemals die Tabulatorbreite in Ihrem Editor</em>. Behalten Sie 8 "
+"Zeichen bei. Durch Änderungen der Tabulatorbreite wird Code, den Sie nicht selbst "
+"geschrieben haben, immer falsch ausgerichtet."
#. (itstool) path: section/p
#: C/c-coding-style.page:178
msgid ""
-"Instead, set the <em>indentation size</em> as appropriate for the code you "
-"are editing. When writing in something other than Linux kernel style, you "
-"may even want to tell your editor to automatically convert all tabs to 8 "
-"spaces, so that there is no ambiguity about the intended amount of space."
+"Instead, set the <em>indentation size</em> as appropriate for the code you are "
+"editing. When writing in something other than Linux kernel style, you may even want "
+"to tell your editor to automatically convert all tabs to 8 spaces, so that there is "
+"no ambiguity about the intended amount of space."
msgstr ""
#. (itstool) path: section/title
@@ -656,8 +636,7 @@ msgstr "Klammern"
#: C/c-coding-style.page:190
msgid "Curly braces should not be used for single statement blocks:"
msgstr ""
-"Geschweifte Klammern sollten nicht für einzelne Anweisungsblöcke verwendet "
-"werden:"
+"Geschweifte Klammern sollten nicht für einzelne Anweisungsblöcke verwendet werden:"
#. (itstool) path: section/code
#: C/c-coding-style.page:194
@@ -680,14 +659,13 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:201
msgid "The “no block for single statements” rule has only four exceptions:"
-msgstr ""
-"Für die Regel »kein Block für einzelne Anweisungen« gibt es vier Ausnahmen:"
+msgstr "Für die Regel »kein Block für einzelne Anweisungen« gibt es vier Ausnahmen:"
#. (itstool) path: item/p
#: C/c-coding-style.page:208
msgid ""
-"In GNU style, if either side of an if-else statement has braces, both sides "
-"should, to match up indentation:"
+"In GNU style, if either side of an if-else statement has braces, both sides should, "
+"to match up indentation:"
msgstr ""
#. (itstool) path: item/code
@@ -748,9 +726,9 @@ msgid ""
"If the single statement covers multiple lines, e.g. for functions with many "
"arguments, and it is followed by <code>else</code> or <code>else if</code>:"
msgstr ""
-"Wenn sich die einzelne Anweisung über mehrere Zeilen erstreckt, zum Beispiel "
-"für Funktionen mit vielen Argumenten, und wenn darauf <code>else</code> oder "
-"<code>else if</code> folgt:"
+"Wenn sich die einzelne Anweisung über mehrere Zeilen erstreckt, zum Beispiel für "
+"Funktionen mit vielen Argumenten, und wenn darauf <code>else</code> oder <code>else "
+"if</code> folgt:"
#. (itstool) path: item/code
#: C/c-coding-style.page:243
@@ -850,23 +828,23 @@ msgstr ""
#. (itstool) path: item/p
#: C/c-coding-style.page:290
msgid ""
-"Note that such long conditions are usually hard to understand. A good "
-"practice is to set the condition to a boolean variable, with a good name for "
-"that variable. Another way is to move the long condition to a function."
+"Note that such long conditions are usually hard to understand. A good practice is to "
+"set the condition to a boolean variable, with a good name for that variable. Another "
+"way is to move the long condition to a function."
msgstr ""
-"Bedenken Sie, dass solche überlangen Bedingungen oft schwer verständlich "
-"sind. Eine gute Alternative wäre, die Bedingung in eine boolesche Variable "
-"zu setzen und einen passenden Namen dafür zu wählen. Eine weitere "
-"Möglichkeit ist die Auslagerung der langen Bedingung in eine Funktion."
+"Bedenken Sie, dass solche überlangen Bedingungen oft schwer verständlich sind. Eine "
+"gute Alternative wäre, die Bedingung in eine boolesche Variable zu setzen und einen "
+"passenden Namen dafür zu wählen. Eine weitere Möglichkeit ist die Auslagerung der "
+"langen Bedingung in eine Funktion."
#. (itstool) path: item/p
#: C/c-coding-style.page:299
msgid ""
-"Nested <code>if</code>s, in which case the block should be placed on the "
-"outermost <code>if</code>:"
+"Nested <code>if</code>s, in which case the block should be placed on the outermost "
+"<code>if</code>:"
msgstr ""
-"Verschachtelte <code>if</code>s, wobei der Block im äußersten <code>if</"
-"code> platziert werden sollte:"
+"Verschachtelte <code>if</code>s, wobei der Block im äußersten <code>if</code> "
+"platziert werden sollte:"
#. (itstool) path: item/code
#: C/c-coding-style.page:304
@@ -930,12 +908,9 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:332
-msgid ""
-"In general, new blocks should be placed on a new indentation level, like "
-"this:"
+msgid "In general, new blocks should be placed on a new indentation level, like this:"
msgstr ""
-"Generell sollten neue Blöcke in eine neue Einrückungsebene gesetzt werden, "
-"wie hier:"
+"Generell sollten neue Blöcke in eine neue Einrückungsebene gesetzt werden, wie hier:"
#. (itstool) path: section/code
#: C/c-coding-style.page:337
@@ -974,11 +949,11 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:352
msgid ""
-"While curly braces for function definitions should rest on a new line they "
-"should not add an indentation level:"
+"While curly braces for function definitions should rest on a new line they should "
+"not add an indentation level:"
msgstr ""
-"Während geschweifte Klammern für Funktionsdefinitionen in eine neue Zeile "
-"gehören, sollten sie nicht weiter eingerückt werden:"
+"Während geschweifte Klammern für Funktionsdefinitionen in eine neue Zeile gehören, "
+"sollten sie nicht weiter eingerückt werden:"
#. (itstool) path: section/code
#: C/c-coding-style.page:357
@@ -1055,9 +1030,9 @@ msgstr "Bedingungen"
#: C/c-coding-style.page:390
msgid ""
"Do not check boolean values for equality. By using implicit comparisons, the "
-"resulting code can be read more like conversational English. Another "
-"rationale is that a ‘true’ value may not be necessarily equal to whatever "
-"the <code>TRUE</code> macro uses. For example:"
+"resulting code can be read more like conversational English. Another rationale is "
+"that a ‘true’ value may not be necessarily equal to whatever the <code>TRUE</code> "
+"macro uses. For example:"
msgstr ""
#. (itstool) path: section/code
@@ -1107,22 +1082,21 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:415
msgid ""
-"The C language uses the value 0 for many purposes. As a numeric value, the "
-"end of a string, a null pointer and the <code>FALSE</code> boolean. To make "
-"the code clearer, you should write code that highlights the specific way 0 "
-"is used. So when reading a comparison, it is possible to know the variable "
-"type. For boolean variables, an implicit comparison is appropriate because "
-"it’s already a logical expression. Other variable types are not logical "
-"expressions by themselves, so an explicit comparison is better:"
-msgstr ""
-"Die Programmiersprache C verwendet den Wert 0 für zahlreiche Zwecke, als "
-"numerischen Wert, als Ende einer Zeichenkette, als Null-Zeiger oder für den "
-"booleschen Wert <code>FALSE</code>. Um hier etwas mehr Klarheit zu schaffen, "
-"sollte in Ihrem Code der Zwecke entsprechend gekennzeichnet werden. So kann "
-"bei Vergleichen der Variablentyp erkannt werden. Für boolesche Variablen ist "
-"ein impliziter Vergleich angemessen, da es bereits ein logischer Ausdruck "
-"ist. Andere Variablentypen sind nicht direkt logische Ausdrücke, so dass ein "
-"expliziter Vergleich besser erscheint:"
+"The C language uses the value 0 for many purposes. As a numeric value, the end of a "
+"string, a null pointer and the <code>FALSE</code> boolean. To make the code clearer, "
+"you should write code that highlights the specific way 0 is used. So when reading a "
+"comparison, it is possible to know the variable type. For boolean variables, an "
+"implicit comparison is appropriate because it’s already a logical expression. Other "
+"variable types are not logical expressions by themselves, so an explicit comparison "
+"is better:"
+msgstr ""
+"Die Programmiersprache C verwendet den Wert 0 für zahlreiche Zwecke, als numerischen "
+"Wert, als Ende einer Zeichenkette, als Null-Zeiger oder für den booleschen Wert "
+"<code>FALSE</code>. Um hier etwas mehr Klarheit zu schaffen, sollte in Ihrem Code "
+"der Zwecke entsprechend gekennzeichnet werden. So kann bei Vergleichen der "
+"Variablentyp erkannt werden. Für boolesche Variablen ist ein impliziter Vergleich "
+"angemessen, da es bereits ein logischer Ausdruck ist. Andere Variablentypen sind "
+"nicht direkt logische Ausdrücke, so dass ein expliziter Vergleich besser erscheint:"
#. (itstool) path: section/code
#: C/c-coding-style.page:426
@@ -1192,11 +1166,11 @@ msgstr "Funktionen"
#. (itstool) path: section/p
#: C/c-coding-style.page:456
msgid ""
-"Functions should be declared by placing the returned value on a separate "
-"line from the function name:"
+"Functions should be declared by placing the returned value on a separate line from "
+"the function name:"
msgstr ""
-"Funktionen sollten so deklariert werden, dass der Rückgabewert in einer "
-"separaten Zeile vom Funktionsnamen abgesetzt wird:"
+"Funktionen sollten so deklariert werden, dass der Rückgabewert in einer separaten "
+"Zeile vom Funktionsnamen abgesetzt wird:"
#. (itstool) path: section/code
#: C/c-coding-style.page:461
@@ -1251,18 +1225,18 @@ msgstr ""
#: C/c-coding-style.page:484
#, fuzzy
msgid ""
-"If you use Emacs, you can use <code>M-x align</code> to do this kind of "
-"alignment automatically. Just put the point and mark around the function’s "
-"prototype, and invoke that command."
+"If you use Emacs, you can use <code>M-x align</code> to do this kind of alignment "
+"automatically. Just put the point and mark around the function’s prototype, and "
+"invoke that command."
msgstr ""
-"Wenn Sie Emacs verwenden, können Sie mit <code>M-x align</code> diese Art "
-"der Ausrichtung automatisch erledigen lassen."
+"Wenn Sie Emacs verwenden, können Sie mit <code>M-x align</code> diese Art der "
+"Ausrichtung automatisch erledigen lassen."
#. (itstool) path: section/p
#: C/c-coding-style.page:490
msgid ""
-"The alignment also holds when invoking a function without breaking the line "
-"length limit:"
+"The alignment also holds when invoking a function without breaking the line length "
+"limit:"
msgstr ""
#. (itstool) path: section/code
@@ -1288,8 +1262,7 @@ msgstr "Leerzeichen"
#: C/c-coding-style.page:504
msgid "Always put a space before an opening parenthesis but never after:"
msgstr ""
-"Setzen Sie stets vor einer öffnenden Klammer ein Leerzeichen, aber niemals "
-"dahinter:"
+"Setzen Sie stets vor einer öffnenden Klammer ein Leerzeichen, aber niemals dahinter:"
#. (itstool) path: section/code
#: C/c-coding-style.page:508
@@ -1338,8 +1311,8 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:526
msgid ""
-"When declaring a structure type use newlines to separate logical sections of "
-"the structure:"
+"When declaring a structure type use newlines to separate logical sections of the "
+"structure:"
msgstr ""
"Bei der Deklaration eines Strukturtyps verwenden Sie einen Zeilenumbruch, um "
"logische Abschnitte der Struktur zu trennen:"
@@ -1387,11 +1360,11 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:549
msgid ""
-"Do not eliminate whitespace and newlines just because something would fit on "
-"a single line:"
+"Do not eliminate whitespace and newlines just because something would fit on a "
+"single line:"
msgstr ""
-"Entfernen Sie keine Leerzeichen und Zeilenumbrücke, nur weil etwas auch in "
-"eine einzelne Zeile passen würde:"
+"Entfernen Sie keine Leerzeichen und Zeilenumbrücke, nur weil etwas auch in eine "
+"einzelne Zeile passen würde:"
#. (itstool) path: section/code
#: C/c-coding-style.page:554
@@ -1408,21 +1381,21 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:558
msgid ""
-"Do eliminate trailing whitespace on any line, preferably as a separate patch "
-"or commit. Never use empty lines at the beginning or at the end of a file."
+"Do eliminate trailing whitespace on any line, preferably as a separate patch or "
+"commit. Never use empty lines at the beginning or at the end of a file."
msgstr ""
-"Entfernen Sie stets angehängte Leerzeichen in jeder Zeile, vorzugsweise "
-"mittels separatem Patch oder Commit. Setzen Sie niemals leere Zeilen an den "
-"Anfang oder das Ende einer Datei."
+"Entfernen Sie stets angehängte Leerzeichen in jeder Zeile, vorzugsweise mittels "
+"separatem Patch oder Commit. Setzen Sie niemals leere Zeilen an den Anfang oder das "
+"Ende einer Datei."
#. (itstool) path: section/p
#: C/c-coding-style.page:564
msgid ""
-"This is a little Emacs function that you can use to clean up lines with "
-"trailing whitespace:"
+"This is a little Emacs function that you can use to clean up lines with trailing "
+"whitespace:"
msgstr ""
-"Hier ist eine kleine Emacs-Funktion, mit der Sie Zeilen mit angehängten "
-"Leerzeichen bereinigen können:"
+"Hier ist eine kleine Emacs-Funktion, mit der Sie Zeilen mit angehängten Leerzeichen "
+"bereinigen können:"
#. (itstool) path: section/code
#: C/c-coding-style.page:569
@@ -1460,14 +1433,14 @@ msgstr "Die <code>switch</code>-Anweisung"
#. (itstool) path: section/p
#: C/c-coding-style.page:585
msgid ""
-"A <code>switch</code> should open a block on a new indentation level, and "
-"each <code>case</code> should start on the same indentation level as the "
-"curly braces, with the case block on a new indentation level:"
+"A <code>switch</code> should open a block on a new indentation level, and each "
+"<code>case</code> should start on the same indentation level as the curly braces, "
+"with the case block on a new indentation level:"
msgstr ""
-"Ein <code>switch</code> sollte einen Block in einer neuen Einrückungsebene "
-"öffnen, und jedes <code>case</code> sollte in der gleichen Einrückungsebene "
-"beginnen wie die geschweiften Klammern, mit dem <code>case</code>-Block in "
-"einer neuen Einrückungsebene:"
+"Ein <code>switch</code> sollte einen Block in einer neuen Einrückungsebene öffnen, "
+"und jedes <code>case</code> sollte in der gleichen Einrückungsebene beginnen wie die "
+"geschweiften Klammern, mit dem <code>case</code>-Block in einer neuen "
+"Einrückungsebene:"
#. (itstool) path: section/code
#: C/c-coding-style.page:592
@@ -1582,11 +1555,10 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:643
msgid ""
-"It is preferable, though not mandatory, to separate the various cases with a "
-"newline:"
+"It is preferable, though not mandatory, to separate the various cases with a newline:"
msgstr ""
-"Es ist zu bevorzugen, jedoch nicht obligatorisch, die verschiedenen "
-"<code>case</code> durch Zeilenumbrüche voneinander zu trennen:"
+"Es ist zu bevorzugen, jedoch nicht obligatorisch, die verschiedenen <code>case</"
+"code> durch Zeilenumbrüche voneinander zu trennen:"
#. (itstool) path: section/code
#: C/c-coding-style.page:648
@@ -1623,16 +1595,15 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:662
msgid ""
-"The <code>break</code> statement for the <code>default</code> case is not "
-"mandatory."
+"The <code>break</code> statement for the <code>default</code> case is not mandatory."
msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:667
msgid ""
-"If switching over an enumerated type, a <code>case</code> statement must "
-"exist for every member of the enumerated type. For members you do not want "
-"to handle, alias their <code>case</code> statements to <code>default</code>:"
+"If switching over an enumerated type, a <code>case</code> statement must exist for "
+"every member of the enumerated type. For members you do not want to handle, alias "
+"their <code>case</code> statements to <code>default</code>:"
msgstr ""
#. (itstool) path: section/code
@@ -1674,16 +1645,16 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:690
msgid ""
-"If most members of the enumerated type should not be handled, consider using "
-"an <code>if</code> statement instead of a <code>switch</code>."
+"If most members of the enumerated type should not be handled, consider using an "
+"<code>if</code> statement instead of a <code>switch</code>."
msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:695
msgid ""
-"If a <code>case</code> block needs to declare new variables, the same rules "
-"as the inner blocks apply (see above); the <code>break</code> statement "
-"should be placed outside of the inner block:"
+"If a <code>case</code> block needs to declare new variables, the same rules as the "
+"inner blocks apply (see above); the <code>break</code> statement should be placed "
+"outside of the inner block:"
msgstr ""
#. (itstool) path: section/code
@@ -1748,12 +1719,10 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:730
-msgid ""
-"The maximum width of each column is given by the longest element in the "
-"column:"
+msgid "The maximum width of each column is given by the longest element in the column:"
msgstr ""
-"Die maximale Breite jeder Spalte wird durch das längste Element in der "
-"Spalte bestimmt:"
+"Die maximale Breite jeder Spalte wird durch das längste Element in der Spalte "
+"bestimmt:"
#. (itstool) path: section/code
#: C/c-coding-style.page:735
@@ -1795,20 +1764,17 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:751
msgid ""
-"As before, you can use <code>M-x align</code> in Emacs to do this "
-"automatically."
-msgstr ""
-"Wie schon erwähnt, erledigt Emacs dies mit <code>M-x align</code> "
-"automatisch."
+"As before, you can use <code>M-x align</code> in Emacs to do this automatically."
+msgstr "Wie schon erwähnt, erledigt Emacs dies mit <code>M-x align</code> automatisch."
#. (itstool) path: section/p
#: C/c-coding-style.page:756
msgid ""
-"If you are creating a public library, try to export a single public header "
-"file that in turn includes all the smaller header files into it. This is so "
-"that public headers are never included directly; rather a single include is "
-"used in applications. For example, GTK+ uses the following in its header "
-"files that should not be included directly by applications:"
+"If you are creating a public library, try to export a single public header file that "
+"in turn includes all the smaller header files into it. This is so that public "
+"headers are never included directly; rather a single include is used in "
+"applications. For example, GTK+ uses the following in its header files that should "
+"not be included directly by applications:"
msgstr ""
#. (itstool) path: section/code
@@ -1828,9 +1794,9 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:771
msgid ""
-"For libraries, all headers should have inclusion guards (for internal usage) "
-"and C++ guards. These provide the <code>extern \"C\"</code> magic that C++ "
-"requires to include plain C headers:"
+"For libraries, all headers should have inclusion guards (for internal usage) and C++ "
+"guards. These provide the <code>extern \"C\"</code> magic that C++ requires to "
+"include plain C headers:"
msgstr ""
#. (itstool) path: section/code
@@ -1873,9 +1839,9 @@ msgstr "GObject-Klassen"
#. (itstool) path: section/p
#: C/c-coding-style.page:795
msgid ""
-"GObject class definitions and implementations require some additional coding "
-"style notices, and should always be <link xref=\"namespacing#gobject"
-"\">correctly namespaced</link>."
+"GObject class definitions and implementations require some additional coding style "
+"notices, and should always be <link xref=\"namespacing#gobject\">correctly "
+"namespaced</link>."
msgstr ""
#. (itstool) path: section/p
@@ -1938,8 +1904,8 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:828
msgid ""
-"Instance structures should be declared using <code>G_DECLARE_FINAL_TYPE</"
-"code> or <code>G_DECLARE_DERIVABLE_TYPE</code>:"
+"Instance structures should be declared using <code>G_DECLARE_FINAL_TYPE</code> or "
+"<code>G_DECLARE_DERIVABLE_TYPE</code>:"
msgstr ""
#. (itstool) path: section/code
@@ -1957,8 +1923,8 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:838
msgid ""
-"For final types, private data can be stored in the object struct, which "
-"should be defined in the C file:"
+"For final types, private data can be stored in the object struct, which should be "
+"defined in the C file:"
msgstr ""
#. (itstool) path: section/code
@@ -1986,9 +1952,9 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:852
msgid ""
-"For derivable types, private data must be stored in a private struct in the "
-"C file, configured using <code>G_DEFINE_TYPE_WITH_PRIVATE()</code> and "
-"accessed using a <code>_get_instance_private()</code> function:"
+"For derivable types, private data must be stored in a private struct in the C file, "
+"configured using <code>G_DEFINE_TYPE_WITH_PRIVATE()</code> and accessed using a "
+"<code>_get_instance_private()</code> function:"
msgstr ""
#. (itstool) path: section/code
@@ -2026,12 +1992,10 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:872
msgid ""
-"Always use the <code>G_DEFINE_TYPE()</code>, "
-"<code>G_DEFINE_TYPE_WITH_PRIVATE()</code>, and "
-"<code>G_DEFINE_TYPE_WITH_CODE()</code> macros, or their abstract variants "
-"<code>G_DEFINE_ABSTRACT_TYPE()</code>, "
-"<code>G_DEFINE_ABSTRACT_TYPE_WITH_PRIVATE()</code>, and "
-"<code>G_DEFINE_ABSTRACT_TYPE_WITH_CODE()</code>; also, use the similar "
+"Always use the <code>G_DEFINE_TYPE()</code>, <code>G_DEFINE_TYPE_WITH_PRIVATE()</"
+"code>, and <code>G_DEFINE_TYPE_WITH_CODE()</code> macros, or their abstract variants "
+"<code>G_DEFINE_ABSTRACT_TYPE()</code>, <code>G_DEFINE_ABSTRACT_TYPE_WITH_PRIVATE()</"
+"code>, and <code>G_DEFINE_ABSTRACT_TYPE_WITH_CODE()</code>; also, use the similar "
"macros for defining interfaces and boxed types."
msgstr ""
@@ -2052,9 +2016,7 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:890
-msgid ""
-"The interface structure should have ‘Interface’ postfixed to the dummy "
-"typedef:"
+msgid "The interface structure should have ‘Interface’ postfixed to the dummy typedef:"
msgstr ""
#. (itstool) path: section/code
@@ -2152,9 +2114,8 @@ msgstr "Makros"
#. (itstool) path: section/p
#: C/c-coding-style.page:952
msgid ""
-"Try to avoid private macros unless strictly necessary. Remember to "
-"<code>#undef</code> them at the end of a block or a series of functions "
-"needing them."
+"Try to avoid private macros unless strictly necessary. Remember to <code>#undef</"
+"code> them at the end of a block or a series of functions needing them."
msgstr ""
#. (itstool) path: section/p
@@ -2175,9 +2136,9 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:971
msgid ""
-"Avoid exporting variables as public API, since this is cumbersome on some "
-"platforms. It is always preferable to add getters and setters instead. Also, "
-"beware global variables in general."
+"Avoid exporting variables as public API, since this is cumbersome on some platforms. "
+"It is always preferable to add getters and setters instead. Also, beware global "
+"variables in general."
msgstr ""
#. (itstool) path: section/title
@@ -2188,9 +2149,9 @@ msgstr ""
#. (itstool) path: section/p
#: C/c-coding-style.page:982
msgid ""
-"Non-exported functions that are needed in more than one source file should "
-"be prefixed with an underscore (‘_’), and declared in a private header file. "
-"For example, <code>_mylib_internal_foo()</code>."
+"Non-exported functions that are needed in more than one source file should be "
+"prefixed with an underscore (‘_’), and declared in a private header file. For "
+"example, <code>_mylib_internal_foo()</code>."
msgstr ""
#. (itstool) path: section/p
@@ -2201,11 +2162,29 @@ msgstr "Funktionen mit vorangestelltem Unterstrich werden niemals exportiert."
#. (itstool) path: section/p
#: C/c-coding-style.page:992
msgid ""
-"Non-exported functions that are only needed in one source file should be "
-"declared static."
+"Non-exported functions that are only needed in one source file should be declared "
+"static."
+msgstr ""
+"Nicht-exportierte Funktionen, die nur in einer Quelldatei benötigt werden, sollten "
+"als statisch deklariert werden."
+
+#. (itstool) path: p/link
+#: C/cc-by-sa-3-0.xml:4
+msgid "Creative Commons Attribution-Share Alike 3.0 United States License"
+msgstr ""
+
+#. (itstool) path: license/p
+#: C/cc-by-sa-3-0.xml:3
+msgid "This work is licensed under a <_:link-1/>."
+msgstr ""
+
+#. (itstool) path: license/p
+#: C/cc-by-sa-3-0.xml:6
+msgid ""
+"As a special exception, the copyright holders give you permission to copy, modify, "
+"and distribute the example code contained in this document under the terms of your "
+"choosing, without restriction."
msgstr ""
-"Nicht-exportierte Funktionen, die nur in einer Quelldatei benötigt werden, "
-"sollten als statisch deklariert werden."
#. (itstool) path: info/desc
#: C/databases.page:18
@@ -2220,29 +2199,29 @@ msgstr "Datenbanken"
#. (itstool) path: item/p
#: C/databases.page:27
msgid ""
-"Use databases for appropriate use cases: not configuration data (use "
-"GSettings). (<link xref=\"#when-to-use-databases\"/>)"
+"Use databases for appropriate use cases: not configuration data (use GSettings). "
+"(<link xref=\"#when-to-use-databases\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/databases.page:31
msgid ""
-"Choose between GOM and GVDB based on whether indexing is required. (<link "
-"xref=\"#when-to-use-databases\"/>)"
+"Choose between GOM and GVDB based on whether indexing is required. (<link xref="
+"\"#when-to-use-databases\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/databases.page:35
msgid ""
-"Consider your vacuuming policy before committing to using GOM. (<link xref="
-"\"#when-to-use-databases\"/>)"
+"Consider your vacuuming policy before committing to using GOM. (<link xref=\"#when-"
+"to-use-databases\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/databases.page:39
msgid ""
-"Avoid SQL injection vulnerabilities by using prepared statements. (<link "
-"xref=\"#sql-injection\"/>)"
+"Avoid SQL injection vulnerabilities by using prepared statements. (<link xref=\"#sql-"
+"injection\"/>)"
msgstr ""
#. (itstool) path: section/title
@@ -2253,93 +2232,98 @@ msgstr "Anwendungsfälle für Datenbanken"
#. (itstool) path: section/p
#: C/databases.page:49
msgid ""
-"Configuration data should be stored in <link href=\"https://developer.gnome.";
-"org/gio/stable/GSettings.html\">GSettings</link>. As a rule of thumb, if "
-"some data needs to be persistent and affects how an application behaves, it "
-"is configuration data. If it could potentially be subject to policies "
-"imposed by the system administrator (such as proxy or lockdown settings), it "
-"is configuration data. If it contains user created content, it is not "
-"configuration data, and should not be stored in GSettings."
+"Configuration data should be stored in <link href=\"https://developer.gnome.org/gio/";
+"stable/GSettings.html\">GSettings</link>. As a rule of thumb, if some data needs to "
+"be persistent and affects how an application behaves, it is configuration data. If "
+"it could potentially be subject to policies imposed by the system administrator "
+"(such as proxy or lockdown settings), it is configuration data. If it contains user "
+"created content, it is not configuration data, and should not be stored in GSettings."
msgstr ""
#. (itstool) path: section/p
#: C/databases.page:60
msgid ""
-"For such situations where user data is highly structured, storing it in a "
-"database is sensible. There are two main databases suggested for use within "
-"GNOME: GOM and GVDB. GOM is a wrapper around SQLite, and hence implements "
-"indexing of fields and SQL-style queries. GVDB is a much simpler object "
-"store, supporting fast serialization of a dictionary of objects to disk."
+"For such situations where user data is highly structured, storing it in a database "
+"is sensible. There are two main databases suggested for use within GNOME: GOM and "
+"GVDB. GOM is a wrapper around SQLite, and hence implements indexing of fields and "
+"SQL-style queries. GVDB is a much simpler object store, supporting fast "
+"serialization of a dictionary of objects to disk."
msgstr ""
#. (itstool) path: section/p
#: C/databases.page:69
msgid ""
-"GOM should be used if you need advanced features, especially indexing. GVDB "
-"should be used otherwise."
+"GOM should be used if you need advanced features, especially indexing. GVDB should "
+"be used otherwise."
msgstr ""
#. (itstool) path: section/p
#: C/databases.page:74
msgid ""
-"Before deciding to use GOM (and hence SQLite), you must consider a vacuuming "
-"policy for the database, and whether your use case will interact well with "
-"SQLite’s vacuuming system. Vacuuming is effectively SQLite’s term for "
-"defragmenting the database — if a database is not vacuumed appropriately, "
-"performance will degrade and the database size will increase indefinitely. "
-"Read <link href=\"http://blogs.gnome.org/jnelson/2015/01/06/sqlite-vacuum-";
-"and-auto_vacuum/\">this article</link> on vacuuming for more information; "
-"please consider it before choosing to use GOM."
+"Before deciding to use GOM (and hence SQLite), you must consider a vacuuming policy "
+"for the database, and whether your use case will interact well with SQLite’s "
+"vacuuming system. Vacuuming is effectively SQLite’s term for defragmenting the "
+"database — if a database is not vacuumed appropriately, performance will degrade and "
+"the database size will increase indefinitely. Read <link href=\"http://blogs.gnome.";
+"org/jnelson/2015/01/06/sqlite-vacuum-and-auto_vacuum/\">this article</link> on "
+"vacuuming for more information; please consider it before choosing to use GOM."
+msgstr ""
+
+#. (itstool) path: section/p
+#: C/databases.page:86
+msgid ""
+"GNOME has another database library: GNOME Data Access (GDA). This is targeted at "
+"abstracting access to various types of relational database, for use in a database "
+"utility program or office program, for example. It is not suitable for storing <link "
+"href=\"https://developer.gnome.org/gio/stable/GSettings.html\";>user settings</link>."
msgstr ""
#. (itstool) path: section/title
-#: C/databases.page:88
+#: C/databases.page:97
msgid "Using GOM"
msgstr "Verwendung von GOM"
#. (itstool) path: section/p
-#: C/databases.page:90
+#: C/databases.page:99
msgid ""
-"Providing a GOM tutorial is beyond the scope of this document, but a <link "
-"href=\"https://developer.gnome.org/gom/\";>reference manual is available</"
-"link>."
+"Providing a GOM tutorial is beyond the scope of this document, but a <link href="
+"\"https://developer.gnome.org/gom/\";>reference manual is available</link>."
msgstr ""
#. (itstool) path: section/title
-#: C/databases.page:104
+#: C/databases.page:113
msgid "SQL Injection"
msgstr ""
#. (itstool) path: section/p
-#: C/databases.page:106
+#: C/databases.page:115
msgid ""
-"GOM does allow access to the lower level SQLite query APIs. When using them, "
-"queries <em style=\"strong\">must</em> be constructed using SQLite’s <link "
-"href=\"https://www.sqlite.org/c3ref/stmt.html\";>prepared statement</link> "
-"and <link href=\"https://www.sqlite.org/c3ref/bind_blob.html\";>value "
-"binding</link> API, rather than by constructing SQL strings then passing "
-"them to SQLite to parse. Constructing strings makes <link href=\"http://en.";
-"wikipedia.org/wiki/SQL_injection\">SQL injection</link> vulnerabilities very "
-"likely, which can give attackers access to arbitrary user data from the "
-"database."
+"GOM does allow access to the lower level SQLite query APIs. When using them, queries "
+"<em style=\"strong\">must</em> be constructed using SQLite’s <link href=\"https://";
+"www.sqlite.org/c3ref/stmt.html\">prepared statement</link> and <link href=\"https://";
+"www.sqlite.org/c3ref/bind_blob.html\">value binding</link> API, rather than by "
+"constructing SQL strings then passing them to SQLite to parse. Constructing strings "
+"makes <link href=\"http://en.wikipedia.org/wiki/SQL_injection\";>SQL injection</link> "
+"vulnerabilities very likely, which can give attackers access to arbitrary user data "
+"from the database."
msgstr ""
#. (itstool) path: section/title
-#: C/databases.page:122
+#: C/databases.page:131
msgid "Using GVDB"
msgstr "GVDB verwenden"
#. (itstool) path: section/p
-#: C/databases.page:124
+#: C/databases.page:133
msgid ""
-"GVDB has a simple API which mirrors a conventional hash table. Presently, "
-"GVDB is only available as a copy-and-paste library; fetch the most recent "
-"copy of the code from <link href=\"https://git.gnome.org/browse/gvdb\";>GVDB "
-"git</link> and copy it into your project. It is licenced under LGPLv2.1+."
+"GVDB has a simple API which mirrors a conventional hash table. Presently, GVDB is "
+"only available as a copy-and-paste library; fetch the most recent copy of the code "
+"from <link href=\"https://git.gnome.org/browse/gvdb\";>GVDB git</link> and copy it "
+"into your project. It is licenced under LGPLv2.1+."
msgstr ""
#. (itstool) path: section/p
-#: C/databases.page:132
+#: C/databases.page:141
msgid "A full GVDB tutorial is beyond the scope of this document."
msgstr ""
@@ -2357,36 +2341,36 @@ msgstr "Dokumentation"
#. (itstool) path: item/p
#: C/documentation.page:35
msgid ""
-"Use gtk-doc with up-to-date settings for API documentation. (<link xref="
-"\"#gtk-doc\"/>)"
+"Use gtk-doc with up-to-date settings for API documentation. (<link xref=\"#gtk-doc\"/"
+">)"
msgstr ""
#. (itstool) path: item/p
#: C/documentation.page:39
msgid ""
-"Use XML entities for including external symbols into the documentation. "
-"(<link xref=\"#build-system\"/>)"
+"Use XML entities for including external symbols into the documentation. (<link xref="
+"\"#build-system\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/documentation.page:43
msgid ""
-"Use a consistent, standard, table of contents for all API documentation to "
-"maintain familiarity. (<link xref=\"#standard-layout\"/>)"
+"Use a consistent, standard, table of contents for all API documentation to maintain "
+"familiarity. (<link xref=\"#standard-layout\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/documentation.page:47
msgid ""
-"Use <cmd>gdbus-codegen</cmd> to generate D-Bus API documentation to include "
-"in the gtk-doc build. (<link xref=\"#dbus-api\"/>)"
+"Use <cmd>gdbus-codegen</cmd> to generate D-Bus API documentation to include in the "
+"gtk-doc build. (<link xref=\"#dbus-api\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/documentation.page:51
msgid ""
-"Add introspection annotations to all API documentation. (<link xref="
-"\"#introspection-annotations\"/>)"
+"Add introspection annotations to all API documentation. (<link xref=\"#introspection-"
+"annotations\"/>)"
msgstr ""
#. (itstool) path: item/p
@@ -2409,21 +2393,20 @@ msgstr "gtk-doc"
#. (itstool) path: section/p
#: C/documentation.page:68
msgid ""
-"The preferred documentation system for GNOME libraries is <link href="
-"\"http://www.gtk.org/gtk-doc/\";>gtk-doc</link>, which extracts inline "
-"comments from the code to let you build a <link href=\"http://docbook.org/";
-"\">DocBook</link> document and collection of HTML pages. These can then be "
-"read in <link href=\"https://wiki.gnome.org/Apps/Devhelp\";>Devhelp</link>. A "
-"lot of GNOME’s infrastructure is built to handle with documentation written "
-"using gtk-doc."
-msgstr ""
-"Das bevorzugte Dokumentationssystem für GNOME-Bibliotheken ist <link href="
-"\"http://www.gtk.org/gtk-doc/\";>gtk-doc</link>, welches eingebettete "
-"Kommentare aus dem Code entpackt und daraus ein <link href=\"http://docbook.";
-"org/\">DocBook</link>-Dokument und HTML-Seiten erstellen kann. Diese können "
-"in <link href=\"https://wiki.gnome.org/Apps/Devhelp\";>Devhelp</link> gelesen "
-"werden. Ein großer Teil der Infrastruktur von GNOME ist darauf ausgelegt, "
-"mit Dokumentation umzugehen, die mit gtk-doc erstellt wurde."
+"The preferred documentation system for GNOME libraries is <link href=\"http://www.";
+"gtk.org/gtk-doc/\">gtk-doc</link>, which extracts inline comments from the code to "
+"let you build a <link href=\"http://docbook.org/\";>DocBook</link> document and "
+"collection of HTML pages. These can then be read in <link href=\"https://wiki.gnome.";
+"org/Apps/Devhelp\">Devhelp</link>. A lot of GNOME’s infrastructure is built to "
+"handle with documentation written using gtk-doc."
+msgstr ""
+"Das bevorzugte Dokumentationssystem für GNOME-Bibliotheken ist <link href=\"http://";
+"www.gtk.org/gtk-doc/\">gtk-doc</link>, welches eingebettete Kommentare aus dem Code "
+"entpackt und daraus ein <link href=\"http://docbook.org/\";>DocBook</link>-Dokument "
+"und HTML-Seiten erstellen kann. Diese können in <link href=\"https://wiki.gnome.org/";
+"Apps/Devhelp\">Devhelp</link> gelesen werden. Ein großer Teil der Infrastruktur von "
+"GNOME ist darauf ausgelegt, mit Dokumentation umzugehen, die mit gtk-doc erstellt "
+"wurde."
#. (itstool) path: section/title
#: C/documentation.page:81
@@ -2433,32 +2416,30 @@ msgstr "Build-System"
#. (itstool) path: section/p
#: C/documentation.page:83
msgid ""
-"To integrate gtk-doc into a project’s build system, follow the <link href="
-"\"https://developer.gnome.org/gtk-doc-manual/stable/settingup.html.en\";> "
-"instructions in the gtk-doc manual</link>. Note that while the "
-"<file>sections.txt</file> file is automatically generated the first time gtk-"
-"doc is run, it is not generated subsequently, and should be kept up to date "
-"manually. It should also be <link href=\"https://developer.gnome.org/gtk-doc-";
-"manual/stable/settingup_vcs.html.en\"> in version control</link>."
+"To integrate gtk-doc into a project’s build system, follow the <link href=\"https://";
+"developer.gnome.org/gtk-doc-manual/stable/settingup.html.en\"> instructions in the "
+"gtk-doc manual</link>. Note that while the <file>sections.txt</file> file is "
+"automatically generated the first time gtk-doc is run, it is not generated "
+"subsequently, and should be kept up to date manually. It should also be <link href="
+"\"https://developer.gnome.org/gtk-doc-manual/stable/settingup_vcs.html.en\";> in "
+"version control</link>."
msgstr ""
#. (itstool) path: section/p
#: C/documentation.page:94
msgid ""
-"gtk-doc’s <code>no-tmpl</code> flavour should be used, and XML mode should "
-"be used instead of SGML. (tmpl mode and SGML are both outdated and slower "
-"than XML.)"
+"gtk-doc’s <code>no-tmpl</code> flavour should be used, and XML mode should be used "
+"instead of SGML. (tmpl mode and SGML are both outdated and slower than XML.)"
msgstr ""
#. (itstool) path: section/p
#: C/documentation.page:106
msgid ""
-"If the package version is needed to be substituted into the documentation, "
-"create a file named <file>docs/version.xml.in</file>, containing:"
+"If the package version is needed to be substituted into the documentation, create a "
+"file named <file>docs/version.xml.in</file>, containing:"
msgstr ""
-"Falls es nötig ist, die Paketversion in der Dokumentation anzupassen, "
-"erstellen Sie eine Datei namens <file>docs/version.xml.in</file>, die "
-"Folgendes enthält:"
+"Falls es nötig ist, die Paketversion in der Dokumentation anzupassen, erstellen Sie "
+"eine Datei namens <file>docs/version.xml.in</file>, die Folgendes enthält:"
#. (itstool) path: section/code
#: C/documentation.page:110
@@ -2469,18 +2450,17 @@ msgstr "@PACKAGE_VERSION@"
#. (itstool) path: section/p
#: C/documentation.page:111
msgid ""
-"Add it to <code>AC_CONFIG_FILES</code> in <file>configure.ac</file>, then "
-"include it into the main documentation file (<file>*-docs.xml</file>) using: "
-"<code><!ENTITY version SYSTEM \"version.xml\"></code> in the "
-"<code>DOCTYPE</code> at the top of the document. The package version can "
-"then be used inline as <code>&version;</code>."
+"Add it to <code>AC_CONFIG_FILES</code> in <file>configure.ac</file>, then include it "
+"into the main documentation file (<file>*-docs.xml</file>) using: <code><!ENTITY "
+"version SYSTEM \"version.xml\"></code> in the <code>DOCTYPE</code> at the top of "
+"the document. The package version can then be used inline as <code>&version;</"
+"code>."
msgstr ""
-"Fügen Sie sie zu <code>AC_CONFIG_FILES</code> in <file>configure.ac</file> "
-"hinzu und schließen Sie sie folgendermaßen in die Haupt-Dokumentationsdatei "
-"(<file>*-docs.xml</file>) ein: <code><!ENTITY version SYSTEM \"version.xml"
-"\"></code> in the <code>DOCTYPE</code> am Anfang des Dokuments. Die "
-"Paketversion kann dann als <code>&version;</code> in den Text "
-"eingebettet werden."
+"Fügen Sie sie zu <code>AC_CONFIG_FILES</code> in <file>configure.ac</file> hinzu und "
+"schließen Sie sie folgendermaßen in die Haupt-Dokumentationsdatei (<file>*-docs.xml</"
+"file>) ein: <code><!ENTITY version SYSTEM \"version.xml\"></code> in the "
+"<code>DOCTYPE</code> am Anfang des Dokuments. Die Paketversion kann dann als "
+"<code>&version;</code> in den Text eingebettet werden."
#. (itstool) path: section/title
#: C/documentation.page:121
@@ -2490,18 +2470,16 @@ msgstr "Standard-Layout"
#. (itstool) path: section/p
#: C/documentation.page:123
msgid ""
-"Using a standard layout for the table of contents, sections, appendices, "
-"etc. means the same <file><var>project-name</var>-docs.xml</file> template "
-"can be reused with few changes between projects. It also means the "
-"documentation layout is similar across all projects, making it more familiar "
-"to developers."
+"Using a standard layout for the table of contents, sections, appendices, etc. means "
+"the same <file><var>project-name</var>-docs.xml</file> template can be reused with "
+"few changes between projects. It also means the documentation layout is similar "
+"across all projects, making it more familiar to developers."
msgstr ""
-"Wenn Sie ein Standard-Layout für das Inhaltsverzeichnis, die Abschnitte, "
-"Anhänge usw. verwenden, können Sie die gleiche <file><var>Projektname</var>-"
-"docs.xml</file>-Vorlage mit wenigen Änderungen für andere Projekte "
-"verwenden. Es hat auch den Effekt, dass das Dokumentationslayout über "
-"Projektgrenzen hinweg gleich ist und dadurch den Entwicklern mehr vertraut "
-"ist."
+"Wenn Sie ein Standard-Layout für das Inhaltsverzeichnis, die Abschnitte, Anhänge "
+"usw. verwenden, können Sie die gleiche <file><var>Projektname</var>-docs.xml</file>-"
+"Vorlage mit wenigen Änderungen für andere Projekte verwenden. Es hat auch den "
+"Effekt, dass das Dokumentationslayout über Projektgrenzen hinweg gleich ist und "
+"dadurch den Entwicklern mehr vertraut ist."
#. (itstool) path: section/p
#: C/documentation.page:131
@@ -2526,31 +2504,29 @@ msgstr "Lizenzierung"
#. (itstool) path: section/p
#: C/documentation.page:150
msgid ""
-"It is important to make the license used for API references clear, "
-"especially if they contain code examples which could be copied around."
+"It is important to make the license used for API references clear, especially if "
+"they contain code examples which could be copied around."
msgstr ""
-"Es ist wichtig, die für die API-Referenzen verwendete Lizenz klar zu "
-"stellen, insbesondere dann, wenn der Code Beispiele enthält, die frei "
-"kopiert werden dürfen."
+"Es ist wichtig, die für die API-Referenzen verwendete Lizenz klar zu stellen, "
+"insbesondere dann, wenn der Code Beispiele enthält, die frei kopiert werden dürfen."
#. (itstool) path: section/p
#: C/documentation.page:155
msgid ""
"Typically, projects use the same license for their API reference as for the "
-"project’s code itself, to avoid confusion. Some other projects use CC-BY-SA "
-"3.0 for all their reference documentation. The choice is yours."
+"project’s code itself, to avoid confusion. Some other projects use CC-BY-SA 3.0 for "
+"all their reference documentation. The choice is yours."
msgstr ""
-"Typischerweise verwenden Projekte meist die gleiche Lizenz für ihre API-"
-"Referenzen wie für den Projektcode selbst, um Verwirrung zu vermeiden. "
-"Andere Projekte verwenden CC-BY-SA 3.0 für sämtliche Referenzdokumentation. "
-"Die Wahl liegt bei Ihnen."
+"Typischerweise verwenden Projekte meist die gleiche Lizenz für ihre API-Referenzen "
+"wie für den Projektcode selbst, um Verwirrung zu vermeiden. Andere Projekte "
+"verwenden CC-BY-SA 3.0 für sämtliche Referenzdokumentation. Die Wahl liegt bei Ihnen."
#. (itstool) path: section/p
#: C/documentation.page:161
msgid ""
-"As shown in the <link xref=\"#standard-layout\">Standard Layout</link> you "
-"should include a <file>license.xml</file> in the top-level gtk-doc DocBook "
-"file which gives the full text of your documentation license."
+"As shown in the <link xref=\"#standard-layout\">Standard Layout</link> you should "
+"include a <file>license.xml</file> in the top-level gtk-doc DocBook file which gives "
+"the full text of your documentation license."
msgstr ""
#. (itstool) path: section/title
@@ -2561,8 +2537,8 @@ msgstr ""
#. (itstool) path: section/p
#: C/documentation.page:171
msgid ""
-"All public APIs must have gtk-doc comments. For functions, these should be "
-"placed in the source file, directly above the function."
+"All public APIs must have gtk-doc comments. For functions, these should be placed in "
+"the source file, directly above the function."
msgstr ""
#. (itstool) path: section/code
@@ -2608,15 +2584,15 @@ msgstr ""
#. (itstool) path: section/p
#: C/documentation.page:194
msgid ""
-"Documentation comments for macros, function types, class structs, etc. "
-"should be placed next to the definitions, typically in header files."
+"Documentation comments for macros, function types, class structs, etc. should be "
+"placed next to the definitions, typically in header files."
msgstr ""
#. (itstool) path: section/p
#: C/documentation.page:200
msgid ""
-"Section introductions should be placed in the source file they describe, "
-"after the license header:"
+"Section introductions should be placed in the source file they describe, after the "
+"license header:"
msgstr ""
#. (itstool) path: section/code
@@ -2646,9 +2622,9 @@ msgstr ""
#. (itstool) path: section/p
#: C/documentation.page:215
msgid ""
-"Keep in mind that in order to include a function, macro, function type, or "
-"struct type, it needs to be listed in your documentation’s <file>modulename-"
-"sections.txt</file> file."
+"Keep in mind that in order to include a function, macro, function type, or struct "
+"type, it needs to be listed in your documentation’s <file>modulename-sections.txt</"
+"file> file."
msgstr ""
#. (itstool) path: section/p
@@ -2656,8 +2632,8 @@ msgstr ""
msgid ""
"To properly document a new class, it needs to be given its own section in "
"<file>modulename-sections.txt</file>, needs to be included in your toplevel "
-"<file>modulename-docs.sgml</file>, and the <code>get_type()</code> function "
-"for your class needs to be listed in your <file>modulename.types</file>."
+"<file>modulename-docs.sgml</file>, and the <code>get_type()</code> function for your "
+"class needs to be listed in your <file>modulename.types</file>."
msgstr ""
#. (itstool) path: section/title
@@ -2668,9 +2644,9 @@ msgstr ""
#. (itstool) path: section/p
#: C/documentation.page:233
msgid ""
-"Each gtk-doc comment should have appropriate <link href=\"https://wiki.gnome.";
-"org/Projects/GObjectIntrospection/Annotations\"> GObject introspection "
-"annotations</link>. These are useful for two reasons:"
+"Each gtk-doc comment should have appropriate <link href=\"https://wiki.gnome.org/";
+"Projects/GObjectIntrospection/Annotations\"> GObject introspection annotations</"
+"link>. These are useful for two reasons:"
msgstr ""
#. (itstool) path: item/p
@@ -2683,18 +2659,17 @@ msgstr ""
#. (itstool) path: item/p
#: C/documentation.page:244
msgid ""
-"They allow public APIs to be automatically bound in other languages, such as "
-"Python or JavaScript."
+"They allow public APIs to be automatically bound in other languages, such as Python "
+"or JavaScript."
msgstr ""
#. (itstool) path: section/p
#: C/documentation.page:250
msgid ""
-"Introspection annotations add information to APIs (functions, function "
-"parameters, function return values, structures, GObject properties, GObject "
-"signals) which is otherwise not present in the machine readable C API and "
-"only exists in the form of human readable documentation or convention. They "
-"are very important."
+"Introspection annotations add information to APIs (functions, function parameters, "
+"function return values, structures, GObject properties, GObject signals) which is "
+"otherwise not present in the machine readable C API and only exists in the form of "
+"human readable documentation or convention. They are very important."
msgstr ""
#. (itstool) path: section/p
@@ -2702,8 +2677,7 @@ msgstr ""
msgid ""
"In gtk-doc comments, annotations should be preferred over human-readable "
"equivalents. For example, when documenting a function parameter which may be "
-"<code>NULL</code>, use the <code>(nullable)</code> annotation rather than "
-"some text:"
+"<code>NULL</code>, use the <code>(nullable)</code> annotation rather than some text:"
msgstr ""
#. (itstool) path: section/code
@@ -2762,12 +2736,11 @@ msgstr ""
#. (itstool) path: section/p
#: C/documentation.page:290
msgid ""
-"Whenever a symbol is added to the public API, it should have a documentation "
-"comment added. This comment should always contain a <code>Since</code> line "
-"with the package version number of the release which will first contain the "
-"new API. This should be the number currently in <file>configure.ac</file> if "
-"<link xref=\"versioning#release-process\">post-release version incrementing</"
-"link> is being used."
+"Whenever a symbol is added to the public API, it should have a documentation comment "
+"added. This comment should always contain a <code>Since</code> line with the package "
+"version number of the release which will first contain the new API. This should be "
+"the number currently in <file>configure.ac</file> if <link xref=\"versioning#release-"
+"process\">post-release version incrementing</link> is being used."
msgstr ""
#. (itstool) path: section/p
@@ -2801,9 +2774,8 @@ msgstr ""
#. (itstool) path: section/p
#: C/documentation.page:312
msgid ""
-"gtk-doc uses this information to generate indexes of the APIs added in each "
-"release. These should be added to the main <file>*-docs.xml</file> as an "
-"appendix:"
+"gtk-doc uses this information to generate indexes of the APIs added in each release. "
+"These should be added to the main <file>*-docs.xml</file> as an appendix:"
msgstr ""
#. (itstool) path: section/code
@@ -2854,19 +2826,18 @@ msgstr "D-Bus-APIs"
#. (itstool) path: section/p
#: C/documentation.page:339
msgid ""
-"D-Bus interface descriptions contain documentation comments, and these can "
-"be extracted from the XML using <cmd>gdbus-codegen</cmd>, and turned into "
-"DocBook files to be included by gtk-doc."
+"D-Bus interface descriptions contain documentation comments, and these can be "
+"extracted from the XML using <cmd>gdbus-codegen</cmd>, and turned into DocBook files "
+"to be included by gtk-doc."
msgstr ""
#. (itstool) path: section/p
#: C/documentation.page:352
msgid ""
-"The DocBook files can be included in the main <file>*-docs.xml</file> file "
-"using:"
+"The DocBook files can be included in the main <file>*-docs.xml</file> file using:"
msgstr ""
-"Die DocBook-Dateien können folgendermaßen in die Datei <file>*-docs.xml</"
-"file> eingeschlossen werden:"
+"Die DocBook-Dateien können folgendermaßen in die Datei <file>*-docs.xml</file> "
+"eingeschlossen werden:"
#. (itstool) path: section/code
#: C/documentation.page:356
@@ -2895,10 +2866,10 @@ msgstr ""
#. (itstool) path: section/p
#: C/documentation.page:366
msgid ""
-"The generated XML files must be included in the <code>content_files</code> "
-"variable in your gtk-doc <file>Makefile.am</file>, otherwise the build will "
-"fail. (This is to fix situations where the <code>builddir</code> does not "
-"equal the <code>srcdir</code>.)"
+"The generated XML files must be included in the <code>content_files</code> variable "
+"in your gtk-doc <file>Makefile.am</file>, otherwise the build will fail. (This is to "
+"fix situations where the <code>builddir</code> does not equal the <code>srcdir</"
+"code>.)"
msgstr ""
#. (itstool) path: section/title
@@ -2909,20 +2880,19 @@ msgstr "Dekumentation aktuell halten"
#. (itstool) path: section/p
#: C/documentation.page:377
msgid ""
-"gtk-doc comes with support for checking the documentation with some basic "
-"tests. These check that all version indexes are included in the main <file>*-"
-"docs.xml</file> file and that all symbols are documented, amongst other "
-"things."
+"gtk-doc comes with support for checking the documentation with some basic tests. "
+"These check that all version indexes are included in the main <file>*-docs.xml</"
+"file> file and that all symbols are documented, among other things."
msgstr ""
#. (itstool) path: section/p
#: C/documentation.page:384
msgid ""
-"These tests should always be enabled, by adding the following to your gtk-"
-"doc <file>Makefile.am</file>:"
+"These tests should always be enabled, by adding the following to your gtk-doc "
+"<file>Makefile.am</file>:"
msgstr ""
-"Diese Tests sollten immer aktiviert werden. Fügen Sie Folgendes zu "
-"<file>Makefile.am</file> für gtk-doc hinzu:"
+"Diese Tests sollten immer aktiviert werden. Fügen Sie Folgendes zu <file>Makefile."
+"am</file> für gtk-doc hinzu:"
#. (itstool) path: section/code
#: C/documentation.page:388
@@ -2948,18 +2918,17 @@ msgstr "Dateisystemzugriff"
#. (itstool) path: synopsis/p
#: C/file-system.page:26
msgid ""
-"There are a few anti-patterns to consider when accessing the file system. "
-"This article assumes knowledge of the standard <link href=\"https://";
-"developer.gnome.org/gio/stable/GFile.html\"><code>GFile</code></link>, <link "
-"href=\"https://developer.gnome.org/gio/stable/GInputStream.html";
-"\"><code>GInputStream</code></link> and <link href=\"https://developer.gnome.";
-"org/gio/stable/GOutputStream.html\"><code>GOutputStream</code></link> APIs."
+"There are a few anti-patterns to consider when accessing the file system. This "
+"article assumes knowledge of the standard <link href=\"https://developer.gnome.org/";
+"gio/stable/GFile.html\"><code>GFile</code></link>, <link href=\"https://developer.";
+"gnome.org/gio/stable/GInputStream.html\"><code>GInputStream</code></link> and <link "
+"href=\"https://developer.gnome.org/gio/stable/GOutputStream.html";
+"\"><code>GOutputStream</code></link> APIs."
msgstr ""
#. (itstool) path: item/p
#: C/file-system.page:37
-msgid ""
-"Use asynchronous I/O for file access. (<link xref=\"#asynchronous-io\"/>)"
+msgid "Use asynchronous I/O for file access. (<link xref=\"#asynchronous-io\"/>)"
msgstr ""
"Verwenden Sie asynchrone Ein-/Ausgaben für den Dateizugriff. (<link xref="
"\"#asynchronous-io\"/>)"
@@ -2967,8 +2936,8 @@ msgstr ""
#. (itstool) path: item/p
#: C/file-system.page:41
msgid ""
-"Always use appropriate functions to construct file names and paths. (<link "
-"xref=\"#file-path-construction\"/>)"
+"Always use appropriate functions to construct file names and paths. (<link xref="
+"\"#file-path-construction\"/>)"
msgstr ""
"Verwenden Sie stets entsprechende Funktionen, um Dateinamen und Pfade zu "
"konstruieren. (<link xref=\"#file-path-construction\"/>)"
@@ -2976,21 +2945,20 @@ msgstr ""
#. (itstool) path: item/p
#: C/file-system.page:45
msgid ""
-"Validate file paths are in the expected directories before using them. "
-"(<link xref=\"#path-validation-and-sandboxing\"/>)"
+"Validate file paths are in the expected directories before using them. (<link xref="
+"\"#path-validation-and-sandboxing\"/>)"
msgstr ""
-"Überprüfen Sie Dateipfade in den erwarteten Ordnern, bevor Sie sie "
-"verwenden. (<link xref=\"#path-validation-and-sandboxing\"/>)"
+"Überprüfen Sie Dateipfade in den erwarteten Ordnern, bevor Sie sie verwenden. (<link "
+"xref=\"#path-validation-and-sandboxing\"/>)"
#. (itstool) path: item/p
#: C/file-system.page:49
msgid ""
-"Use mandatory access control profiles to enforce constraints on file access. "
-"(<link xref=\"#path-validation-and-sandboxing\"/>)"
+"Use mandatory access control profiles to enforce constraints on file access. (<link "
+"xref=\"#path-validation-and-sandboxing\"/>)"
msgstr ""
-"Verwenden Sie obligatorische Zugriffskontrollprofile, um Beschränkungen für "
-"den Dateizugriff zu erzwingen. (<link xref=\"#path-validation-and-sandboxing"
-"\"/>)"
+"Verwenden Sie obligatorische Zugriffskontrollprofile, um Beschränkungen für den "
+"Dateizugriff zu erzwingen. (<link xref=\"#path-validation-and-sandboxing\"/>)"
#. (itstool) path: section/title
#: C/file-system.page:58
@@ -3000,57 +2968,55 @@ msgstr "Asynchrone Ein-/Ausgaben"
#. (itstool) path: section/p
#: C/file-system.page:60
msgid ""
-"Almost all I/O should be performed asynchronously. That is, without blocking "
-"the <link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-";
-"Loop.html\">GLib main context</link>. This can be achieved by always using "
-"the <code>*_async()</code> and <code>*_finish()</code> variants of each I/O "
-"function."
+"Almost all I/O should be performed asynchronously. That is, without blocking the "
+"<link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html";
+"\">GLib main context</link>. This can be achieved by always using the "
+"<code>*_async()</code> and <code>*_finish()</code> variants of each I/O function."
msgstr ""
#. (itstool) path: example/p
#: C/file-system.page:70
msgid ""
-"For example, <link href=\"https://developer.gnome.org/gio/stable/";
-"GInputStream.html#g-input-stream-read-async"
-"\"><code>g_input_stream_read_async()</code></link> rather than <link href="
-"\"https://developer.gnome.org/gio/stable/GInputStream.html#g-input-stream-";
-"read\"><code>g_input_stream_read()</code></link>."
+"For example, <link href=\"https://developer.gnome.org/gio/stable/GInputStream.html#g-";
+"input-stream-read-async\"><code>g_input_stream_read_async()</code></link> rather "
+"than <link href=\"https://developer.gnome.org/gio/stable/GInputStream.html#g-input-";
+"stream-read\"><code>g_input_stream_read()</code></link>."
msgstr ""
#. (itstool) path: section/p
#: C/file-system.page:78
msgid ""
-"Synchronous I/O blocks the main loop, which means that other events, such as "
-"user input, incoming networking packets, timeouts and idle callbacks, are "
-"not handled until the blocking function returns."
+"Synchronous I/O blocks the main loop, which means that other events, such as user "
+"input, incoming networking packets, timeouts and idle callbacks, are not handled "
+"until the blocking function returns."
msgstr ""
#. (itstool) path: section/p
#: C/file-system.page:84
msgid ""
-"Synchronous I/O is acceptable in certain circumstances where the overheads "
-"of scheduling an asynchronous operation exceed the costs of local "
-"synchronous I/O on Linux. For example, making a small read from a local "
-"file, or from a virtual file system such as <file>/proc</file>. For such "
-"reads, the low level functions <code>g_open()</code>, <code>read()</code> "
-"and <code>g_close()</code> should be used rather than GIO."
+"Synchronous I/O is acceptable in certain circumstances where the overheads of "
+"scheduling an asynchronous operation exceed the costs of local synchronous I/O on "
+"Linux. For example, making a small read from a local file, or from a virtual file "
+"system such as <file>/proc</file>. For such reads, the low level functions "
+"<code>g_open()</code>, <code>read()</code> and <code>g_close()</code> should be used "
+"rather than GIO."
msgstr ""
#. (itstool) path: section/p
#: C/file-system.page:93
msgid ""
-"Files in the user’s home directory do <em>not</em> count as local, as they "
-"could be on a networked file system."
+"Files in the user’s home directory do <em>not</em> count as local, as they could be "
+"on a networked file system."
msgstr ""
-"Dateien im persönlichen Ordner des Benutzers gelten <em>nicht</em> als "
-"lokal, da sie sich auf einem Netzwerk-Dateisystem befinden könnten."
+"Dateien im persönlichen Ordner des Benutzers gelten <em>nicht</em> als lokal, da sie "
+"sich auf einem Netzwerk-Dateisystem befinden könnten."
#. (itstool) path: section/p
#: C/file-system.page:98
msgid ""
-"Note that the alternative – running synchronous I/O in a separate thread – "
-"is highly discouraged; see the <link xref=\"threading#when-to-use-threading"
-"\">threading guidelines</link> for more information."
+"Note that the alternative – running synchronous I/O in a separate thread – is highly "
+"discouraged; see the <link xref=\"threading#when-to-use-threading\">threading "
+"guidelines</link> for more information."
msgstr ""
#. (itstool) path: section/title
@@ -3062,43 +3028,42 @@ msgstr "Konstruktion von Dateipfaden"
#: C/file-system.page:109
msgid ""
"File names and paths are not normal strings: on some systems, they can use a "
-"character encoding other than UTF-8, while normal strings in GLib are "
-"guaranteed to always use UTF-8. For this reason, special functions should be "
-"used to build and handle file names and paths. (Modern Linux systems almost "
-"universally use UTF-8 for filename encoding, so this is not an issue in "
-"practice, but the file path functions should still be used for compatibility "
-"with systems such as Windows, which use UTF-16 filenames.)"
+"character encoding other than UTF-8, while normal strings in GLib are guaranteed to "
+"always use UTF-8. For this reason, special functions should be used to build and "
+"handle file names and paths. (Modern Linux systems almost universally use UTF-8 for "
+"filename encoding, so this is not an issue in practice, but the file path functions "
+"should still be used for compatibility with systems such as Windows, which use "
+"UTF-16 filenames.)"
msgstr ""
#. (itstool) path: example/p
#: C/file-system.page:120
msgid ""
-"For example, file paths should be built using <link href=\"https://developer.";
-"gnome.org/glib/stable/glib-Miscellaneous-Utility-Functions.html#g-build-"
-"filename\"><code>g_build_filename()</code></link> rather than <link href="
-"\"https://developer.gnome.org/glib/stable/glib-String-Utility-Functions.";
-"html#g-strconcat\"><code>g_strconcat()</code></link>."
+"For example, file paths should be built using <link href=\"https://developer.gnome.";
+"org/glib/stable/glib-Miscellaneous-Utility-Functions.html#g-build-filename"
+"\"><code>g_build_filename()</code></link> rather than <link href=\"https://developer.";
+"gnome.org/glib/stable/glib-String-Utility-Functions.html#g-strconcat"
+"\"><code>g_strconcat()</code></link>."
msgstr ""
#. (itstool) path: section/p
#: C/file-system.page:128
msgid ""
"Doing so makes it clearer what the code is meant to do, and also eliminates "
-"duplicate directory separators, so the returned path is canonical (though "
-"not necessarily absolute)."
+"duplicate directory separators, so the returned path is canonical (though not "
+"necessarily absolute)."
msgstr ""
#. (itstool) path: example/p
#: C/file-system.page:135
msgid ""
"As another example, paths should be disassembled using <link href=\"https://";
-"developer.gnome.org/glib/stable/glib-Miscellaneous-Utility-Functions.html#g-"
-"path-get-basename\"><code>g_path_get_basename()</code></link> and <link href="
-"\"https://developer.gnome.org/glib/stable/glib-Miscellaneous-Utility-";
-"Functions.html#g-path-get-dirname\"><code>g_path_get_dirname()</code></link> "
-"rather than <link href=\"https://developer.gnome.org/glib/stable/glib-String-";
-"Utility-Functions.html#g-strrstr\"><code>g_strrstr()</code></link> and other "
-"manual searching functions."
+"developer.gnome.org/glib/stable/glib-Miscellaneous-Utility-Functions.html#g-path-get-"
+"basename\"><code>g_path_get_basename()</code></link> and <link href=\"https://";
+"developer.gnome.org/glib/stable/glib-Miscellaneous-Utility-Functions.html#g-path-get-"
+"dirname\"><code>g_path_get_dirname()</code></link> rather than <link href=\"https://";
+"developer.gnome.org/glib/stable/glib-String-Utility-Functions.html#g-strrstr"
+"\"><code>g_strrstr()</code></link> and other manual searching functions."
msgstr ""
#. (itstool) path: section/title
@@ -3109,37 +3074,36 @@ msgstr "Pfad-Validierung und Sandboxing"
#. (itstool) path: section/p
#: C/file-system.page:150
msgid ""
-"If a filename or path comes from external input, such as a web page or user "
-"input, it should be validated to ensure that putting it into a file path "
-"will not produce an arbitrary path. For example if a filename is constructed "
-"from the constant string <file>~/</file> plus some user input, if the user "
-"inputs <file>../../etc/passwd</file>, they can (potentially) gain access to "
-"sensitive account information, depending on which user the program is "
-"running as, and what it does with data loaded from the constructed path."
+"If a filename or path comes from external input, such as a web page or user input, "
+"it should be validated to ensure that putting it into a file path will not produce "
+"an arbitrary path. For example if a filename is constructed from the constant string "
+"<file>~/</file> plus some user input, if the user inputs <file>../../etc/passwd</"
+"file>, they can (potentially) gain access to sensitive account information, "
+"depending on which user the program is running as, and what it does with data loaded "
+"from the constructed path."
msgstr ""
#. (itstool) path: section/p
#: C/file-system.page:161
msgid ""
-"This can be avoided by validating constructed paths before using them, using "
-"<link href=\"https://developer.gnome.org/gio/stable/GFile.html#g-file-";
-"resolve-relative-path\"><code>g_file_resolve_relative_path()</code></link> "
-"to convert any relative paths to absolute ones, and then validating that the "
-"path is beneath a given root sandboxing directory appropriate for the "
-"operation. For example, if code downloads a file, it could validate that all "
-"paths are beneath <file>~/Downloads</file>, using <link href=\"https://";
-"developer.gnome.org/gio/stable/GFile.html#g-file-has-parent"
+"This can be avoided by validating constructed paths before using them, using <link "
+"href=\"https://developer.gnome.org/gio/stable/GFile.html#g-file-resolve-relative-path";
+"\"><code>g_file_resolve_relative_path()</code></link> to convert any relative paths "
+"to absolute ones, and then validating that the path is beneath a given root "
+"sandboxing directory appropriate for the operation. For example, if code downloads a "
+"file, it could validate that all paths are beneath <file>~/Downloads</file>, using "
+"<link href=\"https://developer.gnome.org/gio/stable/GFile.html#g-file-has-parent";
"\"><code>g_file_has_parent()</code></link>."
msgstr ""
#. (itstool) path: section/p
#: C/file-system.page:172
msgid ""
-"As a second line of defence, all projects which access the file system "
-"should consider providing a mandatory access control profile, using a system "
-"such as <link href=\"http://apparmor.net/\";>AppArmor</link> or <link href="
-"\"http://selinuxproject.org/\";>SELinux</link>, which limits the directories "
-"and files they can read from and write to."
+"As a second line of defence, all projects which access the file system should "
+"consider providing a mandatory access control profile, using a system such as <link "
+"href=\"http://apparmor.net/\";>AppArmor</link> or <link href=\"http://selinuxproject.";
+"org/\">SELinux</link>, which limits the directories and files they can read from and "
+"write to."
msgstr ""
#. (itstool) path: info/desc
@@ -3160,59 +3124,55 @@ msgstr "Verwendung von GError"
#. (itstool) path: section/p
#: C/gerror.page:26
msgid ""
-"<link href=\"https://developer.gnome.org/glib/stable/glib-Error-Reporting.";
-"html\"><code>GError</code></link> is the standard error reporting mechanism "
-"for GLib-using code, and can be thought of as a C implementation of an <link "
-"href=\"http://en.wikipedia.org/wiki/Exception_handling\";>exception</link>."
+"<link href=\"https://developer.gnome.org/glib/stable/glib-Error-Reporting.html";
+"\"><code>GError</code></link> is the standard error reporting mechanism for GLib-"
+"using code, and can be thought of as a C implementation of an <link href=\"http://en.";
+"wikipedia.org/wiki/Exception_handling\">exception</link>."
msgstr ""
#. (itstool) path: section/p
#: C/gerror.page:33
msgid ""
-"Any kind of runtime failure (anything which is not a <link xref="
-"\"preconditions\">programmer error</link>) must be handled by including a "
-"<code>GError**</code> parameter in the function, and setting a useful and "
-"relevant GError describing the failure, before returning from the function. "
-"Programmer errors must not be handled using GError: use assertions, pre-"
-"conditions or post-conditions instead."
+"Any kind of runtime failure (anything which is not a <link xref=\"preconditions"
+"\">programmer error</link>) must be handled by including a <code>GError**</code> "
+"parameter in the function, and setting a useful and relevant GError describing the "
+"failure, before returning from the function. Programmer errors must not be handled "
+"using GError: use assertions, pre-conditions or post-conditions instead."
msgstr ""
#. (itstool) path: section/p
#: C/gerror.page:42
msgid ""
-"GError should be used in preference to a simple return code, as it can "
-"convey more information, and is also supported by all GLib tools. For "
-"example, <link xref=\"introspection\">introspecting an API</link> will "
-"automatically detect all GError parameters so that they can be converted to "
-"exceptions in other languages."
+"GError should be used in preference to a simple return code, as it can convey more "
+"information, and is also supported by all GLib tools. For example, <link xref="
+"\"introspection\">introspecting an API</link> will automatically detect all GError "
+"parameters so that they can be converted to exceptions in other languages."
msgstr ""
#. (itstool) path: section/p
#: C/gerror.page:50
msgid ""
-"Printing warnings to the console must not be done in library code: use a "
-"GError, and the calling code can propagate it further upwards, decide to "
-"handle it, or decide to print it to the console. Ideally, the only code "
-"which prints to the console will be top-level application code, and not "
-"library code."
+"Printing warnings to the console must not be done in library code: use a GError, and "
+"the calling code can propagate it further upwards, decide to handle it, or decide to "
+"print it to the console. Ideally, the only code which prints to the console will be "
+"top-level application code, and not library code."
msgstr ""
#. (itstool) path: section/p
#: C/gerror.page:58
msgid ""
-"Any function call which can take a <code>GError**</code>, <em>should</em> "
-"take such a parameter, and the returned GError should be handled "
-"appropriately. There are very few situations where ignoring a potential "
-"error by passing <code>NULL</code> to a <code>GError**</code> parameter is "
-"acceptable."
+"Any function call which can take a <code>GError**</code>, <em>should</em> take such "
+"a parameter, and the returned GError should be handled appropriately. There are very "
+"few situations where ignoring a potential error by passing <code>NULL</code> to a "
+"<code>GError**</code> parameter is acceptable."
msgstr ""
#. (itstool) path: section/p
#: C/gerror.page:66
msgid ""
-"The GLib API documentation contains a <link href=\"https://developer.gnome.";
-"org/glib/stable/glib-Error-Reporting.html#glib-Error-Reporting.description"
-"\">full tutorial for using GError</link>."
+"The GLib API documentation contains a <link href=\"https://developer.gnome.org/glib/";
+"stable/glib-Error-Reporting.html#glib-Error-Reporting.description\">full tutorial "
+"for using GError</link>."
msgstr ""
#. (itstool) path: info/desc
@@ -3234,38 +3194,36 @@ msgstr "Verwendung von GList"
#: C/glist.page:26
msgid ""
"GLib provides several container types for sets of data: <link href=\"https://";
-"developer.gnome.org/glib/stable/glib-Doubly-Linked-Lists.html\"><code>GList</"
-"code></link>, <link href=\"https://developer.gnome.org/glib/stable/glib-";
-"Singly-Linked-Lists.html\"><code>GSList</code></link>, <link href=\"https://";
-"developer.gnome.org/glib/stable/glib-Pointer-Arrays.html\"><code>GPtrArray</"
-"code></link> and <link href=\"https://developer.gnome.org/glib/stable/glib-";
-"Arrays.html\"><code>GArray</code></link>."
+"developer.gnome.org/glib/stable/glib-Doubly-Linked-Lists.html\"><code>GList</code></"
+"link>, <link href=\"https://developer.gnome.org/glib/stable/glib-Singly-Linked-Lists.";
+"html\"><code>GSList</code></link>, <link href=\"https://developer.gnome.org/glib/";
+"stable/glib-Pointer-Arrays.html\"><code>GPtrArray</code></link> and <link href="
+"\"https://developer.gnome.org/glib/stable/glib-Arrays.html\";><code>GArray</code></"
+"link>."
msgstr ""
#. (itstool) path: section/p
#: C/glist.page:34
msgid ""
-"It has been common practice in the past to use GList in all situations where "
-"a sequence or set of data needs to be stored. This is inadvisable — in most "
-"situations, a GPtrArray should be used instead. It has lower memory overhead "
-"(a third to a half of an equivalent list), better cache locality, and the "
-"same or lower algorithmic complexity for all common operations. The only "
-"typical situation where a GList may be more appropriate is when dealing with "
-"ordered data, which requires expensive insertions at arbitrary indexes in "
-"the array."
+"It has been common practice in the past to use GList in all situations where a "
+"sequence or set of data needs to be stored. This is inadvisable — in most "
+"situations, a GPtrArray should be used instead. It has lower memory overhead (a "
+"third to a half of an equivalent list), better cache locality, and the same or lower "
+"algorithmic complexity for all common operations. The only typical situation where a "
+"GList may be more appropriate is when dealing with ordered data, which requires "
+"expensive insertions at arbitrary indexes in the array."
msgstr ""
#. (itstool) path: section/p
#: C/glist.page:45
msgid ""
-"If linked lists are used, be careful to keep the complexity of operations on "
-"them low, using standard CS complexity analysis. Any operation which uses "
-"<link href=\"https://developer.gnome.org/glib/2.30/glib-Doubly-Linked-Lists.";
-"html#g-list-nth\"><code>g_list_nth()</code></link> or <link href=\"https://";
-"developer.gnome.org/glib/2.30/glib-Doubly-Linked-Lists.html#g-list-nth-data"
-"\"><code>g_list_nth_data()</code></link> is almost certainly wrong. For "
-"example, iteration over a GList should be implemented using the linking "
-"pointers, rather than a incrementing index:"
+"If linked lists are used, be careful to keep the complexity of operations on them "
+"low, using standard CS complexity analysis. Any operation which uses <link href="
+"\"https://developer.gnome.org/glib/2.30/glib-Doubly-Linked-Lists.html#g-list-nth";
+"\"><code>g_list_nth()</code></link> or <link href=\"https://developer.gnome.org/";
+"glib/2.30/glib-Doubly-Linked-Lists.html#g-list-nth-data\"><code>g_list_nth_data()</"
+"code></link> is almost certainly wrong. For example, iteration over a GList should "
+"be implemented using the linking pointers, rather than a incrementing index:"
msgstr ""
#. (itstool) path: section/code
@@ -3293,8 +3251,8 @@ msgstr ""
#. (itstool) path: section/p
#: C/glist.page:63
msgid ""
-"Using an incrementing index instead results in a quadratic decrease in "
-"performance (<em>O(N^2)</em> rather than <em>O(N)</em>):"
+"Using an incrementing index instead results in a quadratic decrease in performance "
+"(<em>O(N^2)</em> rather than <em>O(N)</em>):"
msgstr ""
#. (itstool) path: section/code
@@ -3327,8 +3285,8 @@ msgstr ""
#: C/glist.page:78
msgid ""
"The performance penalty comes from <code>g_list_length()</code> and "
-"<code>g_list_nth_data()</code> which both traverse the list (<em>O(N)</em>) "
-"to perform their operations."
+"<code>g_list_nth_data()</code> which both traverse the list (<em>O(N)</em>) to "
+"perform their operations."
msgstr ""
#. (itstool) path: section/p
@@ -3398,14 +3356,14 @@ msgstr "Programmierungsrichtlinien"
#. (itstool) path: page/p
#: C/index.page:39
msgid ""
-"This article contains several guidelines and suggestions for programmers "
-"working in and with the GNOME stack. This is intended for programmers to "
-"know about the development processes, conventions and philosophies behind "
-"GNOME applications and the stack of libraries supporting them. By knowing "
-"“the way things are done” in the GNOME ecosystem, it is hoped that "
-"programmers will find use of GNOME APIs and development of new applications "
-"easier and more natural, and will produce code which is legible and "
-"maintainable over a long period of time by a diverse team of programmers."
+"This article contains several guidelines and suggestions for programmers working in "
+"and with the GNOME stack. This is intended for programmers to know about the "
+"development processes, conventions and philosophies behind GNOME applications and "
+"the stack of libraries supporting them. By knowing “the way things are done” in the "
+"GNOME ecosystem, it is hoped that programmers will find use of GNOME APIs and "
+"development of new applications easier and more natural, and will produce code which "
+"is legible and maintainable over a long period of time by a diverse team of "
+"programmers."
msgstr ""
#. (itstool) path: page/p
@@ -3417,25 +3375,23 @@ msgstr "Diese Richtlinie verfolgt zweierlei Zweck:"
#: C/index.page:56
msgid ""
"To give you good suggestions on how to write code for GNOME or using GNOME "
-"technologies. This will help you write code that is consistent with best "
-"practices, and that will be accepted by the community. This will also lead "
-"to code that is a pleasure to work on."
+"technologies. This will help you write code that is consistent with best practices, "
+"and that will be accepted by the community. This will also lead to code that is a "
+"pleasure to work on."
msgstr ""
-"Wir wollen Ihnen praxisgerechte Empfehlungen für die Programmierung für "
-"GNOME oder mittels GNOME-Technologien geben. Dies wird Ihnen helfen, "
-"konsistenten Code zu schreiben, der von der Gemeinschaft akzeptiert wird. "
-"Als Nebeneffekt wird Ihnen die Programmierung so auch mehr Spaß machen."
+"Wir wollen Ihnen praxisgerechte Empfehlungen für die Programmierung für GNOME oder "
+"mittels GNOME-Technologien geben. Dies wird Ihnen helfen, konsistenten Code zu "
+"schreiben, der von der Gemeinschaft akzeptiert wird. Als Nebeneffekt wird Ihnen die "
+"Programmierung so auch mehr Spaß machen."
#. (itstool) path: item/p
#: C/index.page:65
msgid ""
-"To transmit the knowledge we have gotten over the years on how to keep the "
-"GNOME project sustainable, even when people’s contributions increase or "
-"decrease."
+"To transmit the knowledge we have gotten over the years on how to keep the GNOME "
+"project sustainable, even when people’s contributions increase or decrease."
msgstr ""
-"Wir wollen unser über die Jahre gewonnenes Wissen weitervermitteln, wie das "
-"GNOME-Projekt nachhaltig geführt wird, auch wenn die Beiträge der "
-"Mitwirkenden schwanken."
+"Wir wollen unser über die Jahre gewonnenes Wissen weitervermitteln, wie das GNOME-"
+"Projekt nachhaltig geführt wird, auch wenn die Beiträge der Mitwirkenden schwanken."
#. (itstool) path: info/title
#: C/index.page:75
@@ -3495,53 +3451,46 @@ msgstr ""
#: C/introspection.page:25
msgid ""
"<link href=\"https://wiki.gnome.org/Projects/GObjectIntrospection\";> GObject "
-"introspection</link> (abbreviated ‘GIR’) is a system which extracts APIs "
-"from C code and produces binary type libraries which can be used by non-C "
-"language bindings, and other tools, to <link href=\"http://en.wikipedia.org/";
-"wiki/Type_introspection\">introspect</link> or <link href=\"http://en.";
-"wikipedia.org/wiki/Language_binding\">wrap</link> the original C libraries. "
-"It uses a system of annotations in documentation comments in the C code to "
-"expose extra information about the APIs which is not machine readable from "
-"the code itself."
+"introspection</link> (abbreviated ‘GIR’) is a system which extracts APIs from C code "
+"and produces binary type libraries which can be used by non-C language bindings, and "
+"other tools, to <link href=\"http://en.wikipedia.org/wiki/Type_introspection";
+"\">introspect</link> or <link href=\"http://en.wikipedia.org/wiki/Language_binding";
+"\">wrap</link> the original C libraries. It uses a system of annotations in "
+"documentation comments in the C code to expose extra information about the APIs "
+"which is not machine readable from the code itself."
msgstr ""
#. (itstool) path: synopsis/p
#: C/introspection.page:37
msgid ""
-"It should be enabled for all public APIs: so all libraries. It cannot be "
-"enabled for programs, since they expose no APIs. However, it is still "
-"recommended to <link xref=\"documentation#introspection-annotations\">add "
-"introspection annotations to documentation comments</link> in program code, "
-"as they clarify the documentation."
+"It should be enabled for all public APIs: so all libraries. It cannot be enabled for "
+"programs, since they expose no APIs. However, it is still recommended to <link xref="
+"\"documentation#introspection-annotations\">add introspection annotations to "
+"documentation comments</link> in program code, as they clarify the documentation."
msgstr ""
#. (itstool) path: item/p
#: C/introspection.page:46
-msgid ""
-"Enable introspection for all libraries. (<link xref=\"#using-introspection\"/"
-">)"
+msgid "Enable introspection for all libraries. (<link xref=\"#using-introspection\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/introspection.page:50
msgid ""
-"Pay attention to warnings from <cmd>g-ir-scanner</cmd> and "
-"<code>introspectable=\"0\"</code> attributes in GIR files. (<link xref="
-"\"#using-introspection\"/>)"
+"Pay attention to warnings from <cmd>g-ir-scanner</cmd> and <code>introspectable="
+"\"0\"</code> attributes in GIR files. (<link xref=\"#using-introspection\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/introspection.page:55
msgid ""
-"Add introspection annotations to all documentation comments. (<link xref="
-"\"#using-introspection\"/>)"
+"Add introspection annotations to all documentation comments. (<link xref=\"#using-"
+"introspection\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/introspection.page:59
-msgid ""
-"Design APIs to be introspectable from the start. (<link xref=\"#api-design\"/"
-">)"
+msgid "Design APIs to be introspectable from the start. (<link xref=\"#api-design\"/>)"
msgstr ""
#. (itstool) path: section/title
@@ -3552,59 +3501,56 @@ msgstr ""
#. (itstool) path: section/p
#: C/introspection.page:69
msgid ""
-"The first step for using introspection is to add it to the build system, "
-"following the instructions <link href=\"https://wiki.gnome.org/Projects/";
-"GObjectIntrospection/AutotoolsIntegration#Method_1_-_Recommended_-"
-"_most_portable\">here</link>, following method 1. This should be done early "
-"in the life of a project, as introspectability affects <link xref=\"#api-"
-"design\">API design</link>."
+"The first step for using introspection is to add it to the build system, following "
+"the instructions <link href=\"https://wiki.gnome.org/Projects/GObjectIntrospection/";
+"AutotoolsIntegration#Method_1_-_Recommended_-_most_portable\">here</link>, following "
+"method 1. This should be done early in the life of a project, as introspectability "
+"affects <link xref=\"#api-design\">API design</link>."
msgstr ""
#. (itstool) path: section/p
#: C/introspection.page:77
msgid ""
-"This should result in a <file>.gir</file> and <file>.typelib</file> file "
-"being generated for the project. The <file>.gir</file> file is human "
-"readable, and can be inspected manually to see if the API has been "
-"introspected correctly (although the GIR compilation process will print "
-"error messages and warnings for any missing annotations or other problems). "
-"APIs with <code>introspectable=\"0\"</code> will not be exposed to language "
-"bindings as they are missing annotations or are otherwise not representable "
-"in the GIR file."
+"This should result in a <file>.gir</file> and <file>.typelib</file> file being "
+"generated for the project. The <file>.gir</file> file is human readable, and can be "
+"inspected manually to see if the API has been introspected correctly (although the "
+"GIR compilation process will print error messages and warnings for any missing "
+"annotations or other problems). APIs with <code>introspectable=\"0\"</code> will not "
+"be exposed to language bindings as they are missing annotations or are otherwise not "
+"representable in the GIR file."
msgstr ""
#. (itstool) path: section/p
#: C/introspection.page:88
msgid ""
-"The next step is to <link xref=\"documentation#introspection-annotations"
-"\">add annotations to the documentation comments for every piece of public "
-"API</link>. If a particular piece of API should not be exposed in the GIR "
-"file, use the <code>(skip)</code> annotation. Documentation on the available "
-"annotations is <link href=\"https://wiki.gnome.org/Projects/";
-"GObjectIntrospection/Annotations\">here</link>."
+"The next step is to <link xref=\"documentation#introspection-annotations\">add "
+"annotations to the documentation comments for every piece of public API</link>. If a "
+"particular piece of API should not be exposed in the GIR file, use the <code>(skip)</"
+"code> annotation. Documentation on the available annotations is <link href=\"https://";
+"wiki.gnome.org/Projects/GObjectIntrospection/Annotations\">here</link>."
msgstr ""
#. (itstool) path: section/p
#: C/introspection.page:98
msgid ""
-"If annotating the code for a program, a good approach is to split the bulk "
-"of the code out into an internal, private convenience library. An internal "
-"API reference manual can be built from its documentation comments (see <link "
-"xref=\"documentation\"/>). The library is then not installed, but is linked "
-"in to the program which is itself installed. This approach for generating "
-"internal API documentation is especially useful for large projects where the "
-"internal code may be large and hard to navigate."
+"If annotating the code for a program, a good approach is to split the bulk of the "
+"code out into an internal, private convenience library. An internal API reference "
+"manual can be built from its documentation comments (see <link xref=\"documentation"
+"\"/>). The library is then not installed, but is linked in to the program which is "
+"itself installed. This approach for generating internal API documentation is "
+"especially useful for large projects where the internal code may be large and hard "
+"to navigate."
msgstr ""
#. (itstool) path: section/p
#: C/introspection.page:108
msgid ""
"Annotations do not have to be added exhaustively: GIR has a set of default "
-"annotations which it applies based on various conventions (see <link xref="
-"\"#api-design\"/>). For example, a <code>const gchar*</code> parameter does "
-"not need an explicit <code>(transfer none)</code> annotation, because the "
-"<code>const</code> modifier implies this already. Learning the defaults for "
-"annotations is a matter of practice."
+"annotations which it applies based on various conventions (see <link xref=\"#api-"
+"design\"/>). For example, a <code>const gchar*</code> parameter does not need an "
+"explicit <code>(transfer none)</code> annotation, because the <code>const</code> "
+"modifier implies this already. Learning the defaults for annotations is a matter of "
+"practice."
msgstr ""
#. (itstool) path: section/title
@@ -3615,48 +3561,45 @@ msgstr "API-Design"
#. (itstool) path: section/p
#: C/introspection.page:121
msgid ""
-"In order to be introspectable without too many annotations, APIs must follow "
-"certain conventions, such as the <link href=\"https://developer.gnome.org/";
-"gobject/stable/gtype-conventions.html\">standard GObject naming conventions</"
-"link>, and the <link href=\"https://wiki.gnome.org/Projects/";
-"GObjectIntrospection/WritingBindingableAPIs\">conventions for bindable APIs</"
-"link>. This is necessary because of the flexibility of C: code can be "
-"written to behave in any way imaginable, but higher level languages don’t "
-"allow this kind of freedom. So in order for a C API to be representable in a "
-"higher level language, it has to conform to the behaviors supported by that "
-"language."
+"In order to be introspectable without too many annotations, APIs must follow certain "
+"conventions, such as the <link href=\"https://developer.gnome.org/gobject/stable/";
+"gtype-conventions.html\">standard GObject naming conventions</link>, and the <link "
+"href=\"https://wiki.gnome.org/Projects/GObjectIntrospection/WritingBindingableAPIs";
+"\">conventions for bindable APIs</link>. This is necessary because of the "
+"flexibility of C: code can be written to behave in any way imaginable, but higher "
+"level languages don’t allow this kind of freedom. So in order for a C API to be "
+"representable in a higher level language, it has to conform to the behaviors "
+"supported by that language."
msgstr ""
#. (itstool) path: section/p
#: C/introspection.page:134
msgid ""
-"For example, GIR expects that if a function can fail, it will have a "
-"<code>GError**</code> parameter, which will always be its final parameter. "
-"The GIR scanner detects this and automatically converts that parameter to an "
-"exception attribute on the method in the GIR file. It cannot do this if the "
-"<code>GError*</code> is returned directly, or is not the final function "
-"parameter, for example."
+"For example, GIR expects that if a function can fail, it will have a <code>GError**</"
+"code> parameter, which will always be its final parameter. The GIR scanner detects "
+"this and automatically converts that parameter to an exception attribute on the "
+"method in the GIR file. It cannot do this if the <code>GError*</code> is returned "
+"directly, or is not the final function parameter, for example."
msgstr ""
#. (itstool) path: section/p
#: C/introspection.page:143
msgid ""
-"Therefore, APIs must be designed to be introspectable, and the GIR file "
-"should be checked as the APIs are being written. If the GIR doesn’t match "
-"what you expect for a new API, the API may need extra annotations, or even "
-"for its C declaration to be changed (as in the case of <link href=\"https://";
-"wiki.gnome.org/Projects/GObjectIntrospection/WritingBindingableAPIs#va_list"
-"\"><code>va_list</code></link>)."
+"Therefore, APIs must be designed to be introspectable, and the GIR file should be "
+"checked as the APIs are being written. If the GIR doesn’t match what you expect for "
+"a new API, the API may need extra annotations, or even for its C declaration to be "
+"changed (as in the case of <link href=\"https://wiki.gnome.org/Projects/";
+"GObjectIntrospection/WritingBindingableAPIs#va_list\"><code>va_list</code></link>)."
msgstr ""
#. (itstool) path: section/p
#: C/introspection.page:151
msgid ""
"<cmd>g-ir-scanner</cmd> emits warnings when it encounters code it does not "
-"understand. By passing <cmd>--warn-error</cmd> as well as <cmd>--warn-all</"
-"cmd> in <code>INTROSPECTION_SCANNER_ARGS</code> in <file>Makefile.am</file>, "
-"compilation will fail when unintrospectable APIs are encountered. This will "
-"ensure all new APIs are introspectable, and is highly recommended."
+"understand. By passing <cmd>--warn-error</cmd> as well as <cmd>--warn-all</cmd> in "
+"<code>INTROSPECTION_SCANNER_ARGS</code> in <file>Makefile.am</file>, compilation "
+"will fail when unintrospectable APIs are encountered. This will ensure all new APIs "
+"are introspectable, and is highly recommended."
msgstr ""
#. (itstool) path: info/desc
@@ -3672,35 +3615,34 @@ msgstr "Protokollierung"
#. (itstool) path: synopsis/p
#: C/logging.page:28
msgid ""
-"Logging debug and informational output from libraries and programs is an "
-"open problem, and there are various methods for converting multiple streams "
-"of log output into the customary stdout and stderr streams. Below are some "
-"suggestions for how to implement logging. However, the most important thing "
-"is to ensure that logging is consistent, so that log data can be accessed "
-"and searched with a minimum of effort, since that’s what it’s used for. "
-"Using different logging mechanisms and formats in different projects is not "
-"the right approach."
+"Logging debug and informational output from libraries and programs is an open "
+"problem, and there are various methods for converting multiple streams of log output "
+"into the customary stdout and stderr streams. Below are some suggestions for how to "
+"implement logging. However, the most important thing is to ensure that logging is "
+"consistent, so that log data can be accessed and searched with a minimum of effort, "
+"since that’s what it’s used for. Using different logging mechanisms and formats in "
+"different projects is not the right approach."
msgstr ""
#. (itstool) path: item/p
#: C/logging.page:40
msgid ""
-"Use the GLib logging framework instead of logging directly to stderr and "
-"stdout. (<link xref=\"#glib-logging-framework\"/>)"
+"Use the GLib logging framework instead of logging directly to stderr and stdout. "
+"(<link xref=\"#glib-logging-framework\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/logging.page:44
msgid ""
-"If systemd can be a dependency of the project, consider logging directly to "
-"the journal. (<link xref=\"#journald-integration\"/>)"
+"If systemd can be a dependency of the project, consider logging directly to the "
+"journal. (<link xref=\"#journald-integration\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/logging.page:48
msgid ""
-"Do not implement log rotation and deletion; leave that to system services. "
-"(<link xref=\"#log-rotation\"/>)"
+"Do not implement log rotation and deletion; leave that to system services. (<link "
+"xref=\"#log-rotation\"/>)"
msgstr ""
#. (itstool) path: section/title
@@ -3711,25 +3653,24 @@ msgstr ""
#. (itstool) path: section/p
#: C/logging.page:58
msgid ""
-"GLib provides <link href=\"https://developer.gnome.org/glib/stable/glib-";
-"Message-Logging.html\">a logging framework</link> based around the <link "
-"href=\"https://developer.gnome.org/glib/stable/glib-Message-Logging.html#g-";
-"log\"><code>g_log()</code></link> function, with convenience wrappers <link "
-"href=\"https://developer.gnome.org/glib/stable/glib-Message-Logging.html#g-";
-"debug\"><code>g_debug()</code></link>, <link href=\"https://developer.gnome.";
-"org/glib/stable/glib-Message-Logging.html#g-message\"><code>g_message()</"
-"code></link>, <link href=\"https://developer.gnome.org/glib/stable/glib-";
-"Message-Logging.html#g-warning\"><code>g_warning()</code></link> and <link "
-"href=\"https://developer.gnome.org/glib/stable/glib-Message-Logging.html#g-";
-"error\"><code>g_error()</code></link>. The GLib logging framework has a few "
-"useful features:"
+"GLib provides <link href=\"https://developer.gnome.org/glib/stable/glib-Message-";
+"Logging.html\">a logging framework</link> based around the <link href=\"https://";
+"developer.gnome.org/glib/stable/glib-Message-Logging.html#g-log\"><code>g_log()</"
+"code></link> function, with convenience wrappers <link href=\"https://developer.";
+"gnome.org/glib/stable/glib-Message-Logging.html#g-debug\"><code>g_debug()</code></"
+"link>, <link href=\"https://developer.gnome.org/glib/stable/glib-Message-Logging.";
+"html#g-message\"><code>g_message()</code></link>, <link href=\"https://developer.";
+"gnome.org/glib/stable/glib-Message-Logging.html#g-warning\"><code>g_warning()</"
+"code></link> and <link href=\"https://developer.gnome.org/glib/stable/glib-Message-";
+"Logging.html#g-error\"><code>g_error()</code></link>. The GLib logging framework has "
+"a few useful features:"
msgstr ""
#. (itstool) path: item/p
#: C/logging.page:72
msgid ""
-"Programmatic redirection of log messages using <link href=\"https://";
-"developer.gnome.org/glib/stable/glib-Message-Logging.html#g-log-set-handler"
+"Programmatic redirection of log messages using <link href=\"https://developer.gnome.";
+"org/glib/stable/glib-Message-Logging.html#g-log-set-handler"
"\"><code>g_log_set_handler()</code></link>."
msgstr ""
@@ -3741,8 +3682,8 @@ msgstr ""
#. (itstool) path: item/p
#: C/logging.page:79
msgid ""
-"Multiple log levels, which can be processed separately. For example, this "
-"allows debug messages to be turned on and off at runtime."
+"Multiple log levels, which can be processed separately. For example, this allows "
+"debug messages to be turned on and off at runtime."
msgstr ""
#. (itstool) path: item/p
@@ -3753,40 +3694,38 @@ msgstr ""
#. (itstool) path: section/p
#: C/logging.page:88
msgid ""
-"These should be used in preference to functions like <code>printf()</code>, "
-"<link href=\"https://developer.gnome.org/glib/stable/glib-Warnings-and-";
-"Assertions.html#g-print\"><code>g_print()</code></link> and <link href="
-"\"https://developer.gnome.org/glib/stable/glib-Warnings-and-Assertions.";
-"html#g-printerr\"><code>g_printerr()</code></link>, due to their enhanced "
-"flexibility. The logging functions allow log processing to be done in code, "
-"rather than by external shell scripting, which simplifies everything."
+"These should be used in preference to functions like <code>printf()</code>, <link "
+"href=\"https://developer.gnome.org/glib/stable/glib-Warnings-and-Assertions.html#g-";
+"print\"><code>g_print()</code></link> and <link href=\"https://developer.gnome.org/";
+"glib/stable/glib-Warnings-and-Assertions.html#g-printerr\"><code>g_printerr()</"
+"code></link>, due to their enhanced flexibility. The logging functions allow log "
+"processing to be done in code, rather than by external shell scripting, which "
+"simplifies everything."
msgstr ""
#. (itstool) path: section/p
#: C/logging.page:99
msgid ""
-"A key reason to use the logging framework is that it is used in GLib and "
-"other related libraries already; by using it, all log messages are then "
-"going through the same system and can be processed similarly."
+"A key reason to use the logging framework is that it is used in GLib and other "
+"related libraries already; by using it, all log messages are then going through the "
+"same system and can be processed similarly."
msgstr ""
#. (itstool) path: section/p
#: C/logging.page:105
msgid ""
-"To use the GLib logging framework, define <link href=\"https://developer.";
-"gnome.org/glib/stable/glib-Message-Logging.html#G-LOG-DOMAIN:CAPS"
-"\"><code>G_LOG_DOMAIN</code></link> for the project so it’s unique from all "
-"other projects. Call <code>g_debug(\"Message\")</code> to log a debug "
-"message."
+"To use the GLib logging framework, define <link href=\"https://developer.gnome.org/";
+"glib/stable/glib-Message-Logging.html#G-LOG-DOMAIN:CAPS\"><code>G_LOG_DOMAIN</code></"
+"link> for the project so it’s unique from all other projects. Call "
+"<code>g_debug(\"Message\")</code> to log a debug message."
msgstr ""
#. (itstool) path: section/p
#: C/logging.page:112
msgid ""
-"If the default GLib log handlers are not sufficient, for example if log "
-"messages need to be in a custom format or <link xref=\"#journald-integration"
-"\">journald integration</link> is needed, set up a log handler with the "
-"following code:"
+"If the default GLib log handlers are not sufficient, for example if log messages "
+"need to be in a custom format or <link xref=\"#journald-integration\">journald "
+"integration</link> is needed, set up a log handler with the following code:"
msgstr ""
#. (itstool) path: section/code
@@ -3895,10 +3834,9 @@ msgstr "Ausnahmen"
#. (itstool) path: item/p
#: C/logging.page:169
msgid ""
-"Do not use <code>g_message()</code> in normal code to print output. Printing "
-"output should be done at the top level of an application, using "
-"<code>g_print()</code>, and should be quite rare; i.e. only done in command "
-"line applications."
+"Do not use <code>g_message()</code> in normal code to print output. Printing output "
+"should be done at the top level of an application, using <code>g_print()</code>, and "
+"should be quite rare; i.e. only done in command line applications."
msgstr ""
#. (itstool) path: item/p
@@ -3911,9 +3849,9 @@ msgstr ""
#. (itstool) path: item/p
#: C/logging.page:179
msgid ""
-"Similarly, do not set up log handlers in library code. Log messages should "
-"propagate through library code and be handled in a log handler at the top "
-"level of an application."
+"Similarly, do not set up log handlers in library code. Log messages should propagate "
+"through library code and be handled in a log handler at the top level of an "
+"application."
msgstr ""
#. (itstool) path: section/title
@@ -3924,20 +3862,20 @@ msgstr "journald-Integration"
#. (itstool) path: section/p
#: C/logging.page:191
msgid ""
-"Compared to conventional syslog-style logs, journald supports storage of "
-"structured logging data, which can make post-hoc analysis of logs much "
-"easier. If it’s possible to add <code>systemd-journal</code> as a dependency "
-"to a project, the project’s log handling function could be extended to use "
-"<link href=\"http://0pointer.de/public/systemd-man/sd_journal_send.html";
-"\"><code>sd_journal_print()</code> and <code>sd_journal_send()</code></link> "
-"instead of <code>g_print()</code> and <code>g_printerr()</code>."
+"Compared to conventional syslog-style logs, journald supports storage of structured "
+"logging data, which can make post-hoc analysis of logs much easier. If it’s possible "
+"to add <code>systemd-journal</code> as a dependency to a project, the project’s log "
+"handling function could be extended to use <link href=\"http://0pointer.de/public/";
+"systemd-man/sd_journal_send.html\"><code>sd_journal_print()</code> and "
+"<code>sd_journal_send()</code></link> instead of <code>g_print()</code> and "
+"<code>g_printerr()</code>."
msgstr ""
#. (itstool) path: section/p
#: C/logging.page:202
msgid ""
-"For more information, see this <link href=\"http://0pointer.de/blog/projects/";
-"journal-submit.html\">article on logging to the journal</link>."
+"For more information, see this <link href=\"http://0pointer.de/blog/projects/journal-";
+"submit.html\">article on logging to the journal</link>."
msgstr ""
#. (itstool) path: section/title
@@ -3948,9 +3886,9 @@ msgstr ""
#. (itstool) path: section/p
#: C/logging.page:212
msgid ""
-"Log file rotation is one feature which is out of scope of the GLib logging "
-"system. It should be handled by the normal system logging mechanisms, such "
-"as <cmd>logrotate</cmd> or <cmd>systemd-journald</cmd>."
+"Log file rotation is one feature which is out of scope of the GLib logging system. "
+"It should be handled by the normal system logging mechanisms, such as "
+"<cmd>logrotate</cmd> or <cmd>systemd-journald</cmd>."
msgstr ""
#. (itstool) path: credit/years
@@ -3960,8 +3898,7 @@ msgstr "2014–2015"
#. (itstool) path: info/desc
#: C/main-contexts.page:18
-msgid ""
-"GLib main contexts, invoking functions in other threads, and the event loop"
+msgid "GLib main contexts, invoking functions in other threads, and the event loop"
msgstr ""
#. (itstool) path: page/title
@@ -3972,43 +3909,42 @@ msgstr ""
#. (itstool) path: item/p
#: C/main-contexts.page:30
msgid ""
-"Use <link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-";
-"Loop.html#g-main-context-invoke-full\"><code>g_main_context_invoke_full()</"
-"code></link> to invoke functions in other threads, assuming every thread has "
-"a thread default main context which runs throughout the lifetime of that "
-"thread (<link xref=\"#g-main-context-invoke-full\"/>)"
+"Use <link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.";
+"html#g-main-context-invoke-full\"><code>g_main_context_invoke_full()</code></link> "
+"to invoke functions in other threads, assuming every thread has a thread default "
+"main context which runs throughout the lifetime of that thread (<link xref=\"#g-main-"
+"context-invoke-full\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/main-contexts.page:37
msgid ""
-"Use <link href=\"https://developer.gnome.org/gio/stable/GTask.html";
-"\"><code>GTask</code></link> to run a function in the background without "
-"caring about the specific thread used (<link xref=\"#gtask\"/>)"
+"Use <link href=\"https://developer.gnome.org/gio/stable/GTask.html\";><code>GTask</"
+"code></link> to run a function in the background without caring about the specific "
+"thread used (<link xref=\"#gtask\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/main-contexts.page:43
msgid ""
-"Liberally use assertions to check which context executes each function, and "
-"add these assertions when first writing the code (<link xref=\"#checking-"
-"threading\"/>)"
+"Liberally use assertions to check which context executes each function, and add "
+"these assertions when first writing the code (<link xref=\"#checking-threading\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/main-contexts.page:48
msgid ""
-"Explicitly document contexts a function is expected to be called in, a "
-"callback will be invoked in, or a signal will be emitted in (<link xref="
-"\"#using-gmaincontext-in-a-library\"/>)"
+"Explicitly document contexts a function is expected to be called in, a callback will "
+"be invoked in, or a signal will be emitted in (<link xref=\"#using-gmaincontext-in-a-"
+"library\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/main-contexts.page:53
msgid ""
-"Beware of <code>g_idle_add()</code> and similar functions which implicitly "
-"use the global-default main context (<link xref=\"#implicit-use-of-the-"
-"global-default-main-context\"/>)"
+"Beware of <code>g_idle_add()</code> and similar functions which implicitly use the "
+"global-default main context (<link xref=\"#implicit-use-of-the-global-default-main-"
+"context\"/>)"
msgstr ""
#. (itstool) path: section/title
@@ -4019,39 +3955,37 @@ msgstr "Was ist <code>GMainContext</code>?"
#. (itstool) path: section/p
#: C/main-contexts.page:64
msgid ""
-"<link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-";
-"Loop.html#GMainContext\"><code>GMainContext</code></link> is a generalized "
-"implementation of an <link href=\"http://en.wikipedia.org/wiki/Event_loop";
-"\">event loop</link>, useful for implementing polled file I/O or event-based "
-"widget systems (such as GTK+). It is at the core of almost every GLib "
-"application. To understand <code>GMainContext</code> requires understanding "
-"<link href=\"man:poll(2)\">poll()</link> and polled I/O."
+"<link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.";
+"html#GMainContext\"><code>GMainContext</code></link> is a generalized implementation "
+"of an <link href=\"http://en.wikipedia.org/wiki/Event_loop\";>event loop</link>, "
+"useful for implementing polled file I/O or event-based widget systems (such as GTK"
+"+). It is at the core of almost every GLib application. To understand "
+"<code>GMainContext</code> requires understanding <link href=\"man:poll(2)\">poll()</"
+"link> and polled I/O."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:74
msgid ""
-"A <code>GMainContext</code> has a set of <link href=\"https://developer.";
-"gnome.org/glib/stable/glib-The-Main-Event-Loop.html#GSource\"><code>GSource</"
-"code></link>s which are ‘attached’ to it, each of which can be thought of as "
-"an expected event with an associated callback function which will be invoked "
-"when that event is received; or equivalently as a set of file descriptors "
-"(FDs) to check. An event could be a timeout or data being received on a "
-"socket, for example. One iteration of the event loop will:"
+"A <code>GMainContext</code> has a set of <link href=\"https://developer.gnome.org/";
+"glib/stable/glib-The-Main-Event-Loop.html#GSource\"><code>GSource</code></link>s "
+"which are ‘attached’ to it, each of which can be thought of as an expected event "
+"with an associated callback function which will be invoked when that event is "
+"received; or equivalently as a set of file descriptors (FDs) to check. An event "
+"could be a timeout or data being received on a socket, for example. One iteration of "
+"the event loop will:"
msgstr ""
#. (itstool) path: item/p
#: C/main-contexts.page:84
-msgid ""
-"Prepare sources, determining if any of them are ready to dispatch "
-"immediately."
+msgid "Prepare sources, determining if any of them are ready to dispatch immediately."
msgstr ""
#. (itstool) path: item/p
#: C/main-contexts.page:88
msgid ""
-"Poll the sources, blocking the current thread until an event is received for "
-"one of the sources."
+"Poll the sources, blocking the current thread until an event is received for one of "
+"the sources."
msgstr ""
#. (itstool) path: item/p
@@ -4067,52 +4001,50 @@ msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:100
msgid ""
-"This is <link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-";
-"Event-Loop.html#mainloop-states\">explained very well</link> in the <link "
-"href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.";
-"html#GSourceFuncs\">GLib documentation</link>."
+"This is <link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-";
+"Loop.html#mainloop-states\">explained very well</link> in the <link href=\"https://";
+"developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html#GSourceFuncs\">GLib "
+"documentation</link>."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:108
msgid ""
-"At its core, <code>GMainContext</code> is just a <code>poll()</code> loop, "
-"with the preparation, check and dispatch stages of the loop corresponding to "
-"the normal preamble and postamble in a typical <code>poll()</code> loop "
-"implementation, such as listing 1 from <link href=\"http://www.linux-mag.com/";
-"id/357/\">this article</link>. Typically, some complexity is needed in non-"
-"trivial <code>poll()</code>-using applications to track the lists of FDs "
-"which are being polled. Additionally, <code>GMainContext</code> adds a lot "
-"of useful functionality which vanilla <code>poll()</code> doesn’t support. "
-"Most importantly, it adds thread safety."
+"At its core, <code>GMainContext</code> is just a <code>poll()</code> loop, with the "
+"preparation, check and dispatch stages of the loop corresponding to the normal "
+"preamble and postamble in a typical <code>poll()</code> loop implementation, such as "
+"listing 1 from <link href=\"http://www.linux-mag.com/id/357/\";>this article</link>. "
+"Typically, some complexity is needed in non-trivial <code>poll()</code>-using "
+"applications to track the lists of FDs which are being polled. Additionally, "
+"<code>GMainContext</code> adds a lot of useful functionality which vanilla "
+"<code>poll()</code> doesn’t support. Most importantly, it adds thread safety."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:121
msgid ""
-"<code>GMainContext</code> is completely thread safe, meaning that a "
-"<code>GSource</code> can be created in one thread and attached to a "
-"<code>GMainContext</code> running in another thread. (See also: <link xref="
-"\"threading\"/>.) A typical use for this might be to allow worker threads to "
-"control which sockets are being listened to by a <code>GMainContext</code> "
-"in a central I/O thread. Each <code>GMainContext</code> is ‘acquired’ by a "
-"thread for each iteration it’s put through. Other threads cannot iterate a "
-"<code>GMainContext</code> without acquiring it, which guarantees that a "
-"<code>GSource</code> and its FDs will only be polled by one thread at once "
-"(since each <code>GSource</code> is attached to at most one "
-"<code>GMainContext</code>). A <code>GMainContext</code> can be swapped "
-"between threads across iterations, but this is expensive."
+"<code>GMainContext</code> is completely thread safe, meaning that a <code>GSource</"
+"code> can be created in one thread and attached to a <code>GMainContext</code> "
+"running in another thread. (See also: <link xref=\"threading\"/>.) A typical use for "
+"this might be to allow worker threads to control which sockets are being listened to "
+"by a <code>GMainContext</code> in a central I/O thread. Each <code>GMainContext</"
+"code> is ‘acquired’ by a thread for each iteration it’s put through. Other threads "
+"cannot iterate a <code>GMainContext</code> without acquiring it, which guarantees "
+"that a <code>GSource</code> and its FDs will only be polled by one thread at once "
+"(since each <code>GSource</code> is attached to at most one <code>GMainContext</"
+"code>). A <code>GMainContext</code> can be swapped between threads across "
+"iterations, but this is expensive."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:137
msgid ""
"<code>GMainContext</code> is used instead of <code>poll()</code> mostly for "
-"convenience, as it transparently handles dynamically managing the array of "
-"FDs to pass to <code>poll()</code>, especially when operating over multiple "
-"threads. This is done by encapsulating FDs in <code>GSource</code>s, which "
-"decide whether those FDs should be passed to the <code>poll()</code> call on "
-"each ‘prepare’ stage of the main context iteration."
+"convenience, as it transparently handles dynamically managing the array of FDs to "
+"pass to <code>poll()</code>, especially when operating over multiple threads. This "
+"is done by encapsulating FDs in <code>GSource</code>s, which decide whether those "
+"FDs should be passed to the <code>poll()</code> call on each ‘prepare’ stage of the "
+"main context iteration."
msgstr ""
#. (itstool) path: section/title
@@ -4123,12 +4055,11 @@ msgstr "Was ist <code>GMainLoop</code>?"
#. (itstool) path: section/p
#: C/main-contexts.page:151
msgid ""
-"<link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-";
-"Loop.html#GMainLoop\"><code>GMainLoop</code></link> is essentially the "
-"following few lines of code, once reference counting and locking have been "
-"removed (from <link href=\"https://developer.gnome.org/glib/stable/glib-The-";
-"Main-Event-Loop.html#g-main-loop-run\"><code>g_main_loop_run()</code></"
-"link>):"
+"<link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.";
+"html#GMainLoop\"><code>GMainLoop</code></link> is essentially the following few "
+"lines of code, once reference counting and locking have been removed (from <link "
+"href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html#g-main-";
+"loop-run\"><code>g_main_loop_run()</code></link>):"
msgstr ""
#. (itstool) path: section/code
@@ -4150,29 +4081,28 @@ msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:163
msgid ""
-"Plus a fourth line in <link href=\"https://developer.gnome.org/glib/stable/";
-"glib-The-Main-Event-Loop.html#g-main-loop-quit\"><code>g_main_loop_quit()</"
-"code></link> which sets <code>loop->is_running = FALSE</code> and which "
-"will cause the loop to terminate once the current main context iteration "
-"ends."
+"Plus a fourth line in <link href=\"https://developer.gnome.org/glib/stable/glib-The-";
+"Main-Event-Loop.html#g-main-loop-quit\"><code>g_main_loop_quit()</code></link> which "
+"sets <code>loop->is_running = FALSE</code> and which will cause the loop to "
+"terminate once the current main context iteration ends."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:170
msgid ""
"Hence, <code>GMainLoop</code> is a convenient, thread-safe way of running a "
-"<code>GMainContext</code> to process events until a desired exit condition "
-"is met, at which point <code>g_main_loop_quit()</code> should be called. "
-"Typically, in a UI program, this will be the user clicking ‘exit’. In a "
-"socket handling program, this might be the final socket closing."
+"<code>GMainContext</code> to process events until a desired exit condition is met, "
+"at which point <code>g_main_loop_quit()</code> should be called. Typically, in a UI "
+"program, this will be the user clicking ‘exit’. In a socket handling program, this "
+"might be the final socket closing."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:178
msgid ""
-"It is important not to confuse main contexts with main loops. Main contexts "
-"do the bulk of the work: preparing source lists, waiting for events, and "
-"dispatching callbacks. A main loop simply iterates a context."
+"It is important not to confuse main contexts with main loops. Main contexts do the "
+"bulk of the work: preparing source lists, waiting for events, and dispatching "
+"callbacks. A main loop simply iterates a context."
msgstr ""
#. (itstool) path: section/title
@@ -4183,54 +4113,51 @@ msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:188
msgid ""
-"One of the important features of <code>GMainContext</code> is its support "
-"for ‘default’ contexts. There are two levels of default context: the thread-"
-"default, and the global-default. The global-default (accessed using "
-"<code>g_main_context_default()</code>) is run by GTK+ when <code>gtk_main()</"
-"code> is called. It’s also used for timeouts (<code>g_timeout_add()</code>) "
-"and idle callbacks (<code>g_idle_add()</code>) — these won’t be dispatched "
-"unless the default context is running! (See: <link xref=\"#implicit-use-of-"
-"the-global-default-main-context\"/>.)"
+"One of the important features of <code>GMainContext</code> is its support for "
+"‘default’ contexts. There are two levels of default context: the thread-default, and "
+"the global-default. The global-default (accessed using "
+"<code>g_main_context_default()</code>) is run by GTK+ when <code>gtk_main()</code> "
+"is called. It’s also used for timeouts (<code>g_timeout_add()</code>) and idle "
+"callbacks (<code>g_idle_add()</code>) — these won’t be dispatched unless the default "
+"context is running! (See: <link xref=\"#implicit-use-of-the-global-default-main-"
+"context\"/>.)"
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:200
msgid ""
-"Thread-default contexts are a later addition to GLib (since version 2.22), "
-"and are generally used for I/O operations which need to run and dispatch "
-"callbacks in a thread. By calling "
-"<code>g_main_context_push_thread_default()</code> before starting an I/O "
-"operation, the thread-default context is set and the I/O operation can add "
-"its sources to that context. The context can then be run in a new main loop "
-"in an I/O thread, causing the callbacks to be dispatched on that thread’s "
-"stack rather than on the stack of the thread running the global-default main "
-"context. This allows I/O operations to be run entirely in a separate thread "
-"without explicitly passing a specific <code>GMainContext</code> pointer "
-"around everywhere."
+"Thread-default contexts are a later addition to GLib (since version 2.22), and are "
+"generally used for I/O operations which need to run and dispatch callbacks in a "
+"thread. By calling <code>g_main_context_push_thread_default()</code> before starting "
+"an I/O operation, the thread-default context is set and the I/O operation can add "
+"its sources to that context. The context can then be run in a new main loop in an I/"
+"O thread, causing the callbacks to be dispatched on that thread’s stack rather than "
+"on the stack of the thread running the global-default main context. This allows I/O "
+"operations to be run entirely in a separate thread without explicitly passing a "
+"specific <code>GMainContext</code> pointer around everywhere."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:214
msgid ""
-"Conversely, by starting a long-running operation with a specific thread-"
-"default context set, the calling code can guarantee that the operation’s "
-"callbacks will be emitted in that context, even if the operation itself runs "
-"in a worker thread. This is the principle behind <link href=\"https://";
-"developer.gnome.org/gio/stable/GTask.html\"><code>GTask</code></link>: when "
-"a new <code>GTask</code> is created, it stores a reference to the current "
-"thread-default context, and dispatches its completion callback in that "
-"context, even if the task itself is run using <link href=\"https://developer.";
-"gnome.org/gio/stable/GTask.html#g-task-run-in-thread"
+"Conversely, by starting a long-running operation with a specific thread-default "
+"context set, the calling code can guarantee that the operation’s callbacks will be "
+"emitted in that context, even if the operation itself runs in a worker thread. This "
+"is the principle behind <link href=\"https://developer.gnome.org/gio/stable/GTask.";
+"html\"><code>GTask</code></link>: when a new <code>GTask</code> is created, it "
+"stores a reference to the current thread-default context, and dispatches its "
+"completion callback in that context, even if the task itself is run using <link href="
+"\"https://developer.gnome.org/gio/stable/GTask.html#g-task-run-in-thread";
"\"><code>g_task_run_in_thread()</code></link>."
msgstr ""
#. (itstool) path: example/p
#: C/main-contexts.page:227
msgid ""
-"For example, the code below will run a <code>GTask</code> which performs two "
-"writes in parallel from a thread. The callbacks for the writes will be "
-"dispatched in the worker thread, whereas the callback from the task as a "
-"whole will be dispatched in the <code>interesting_context</code>."
+"For example, the code below will run a <code>GTask</code> which performs two writes "
+"in parallel from a thread. The callbacks for the writes will be dispatched in the "
+"worker thread, whereas the callback from the task as a whole will be dispatched in "
+"the <code>interesting_context</code>."
msgstr ""
#. (itstool) path: example/code
@@ -4346,18 +4273,18 @@ msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:338
msgid ""
-"Several functions implicitly add sources to the global-default main context. "
-"They should <em>not</em> be used in threaded code. Instead, use "
-"<code>g_source_attach()</code> with the <code>GSource</code> created by the "
-"replacement function from the table below."
+"Several functions implicitly add sources to the global-default main context. They "
+"should <em>not</em> be used in threaded code. Instead, use <code>g_source_attach()</"
+"code> with the <code>GSource</code> created by the replacement function from the "
+"table below."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:345
msgid ""
-"Implicit use of the global-default main context means the callback functions "
-"are invoked in the main thread, typically resulting in work being brought "
-"back from a worker thread into the main thread."
+"Implicit use of the global-default main context means the callback functions are "
+"invoked in the main thread, typically resulting in work being brought back from a "
+"worker thread into the main thread."
msgstr ""
#. (itstool) path: td/p
@@ -4402,8 +4329,7 @@ msgstr "<code>g_child_watch_source_new()</code>"
#. (itstool) path: example/p
#: C/main-contexts.page:377
-msgid ""
-"So to delay some computation in a worker thread, use the following code:"
+msgid "So to delay some computation in a worker thread, use the following code:"
msgstr ""
#. (itstool) path: example/code
@@ -4446,75 +4372,73 @@ msgstr "Verwendung von <code>GMainContext</code> in einer Bibliothek"
#. (itstool) path: section/p
#: C/main-contexts.page:414
msgid ""
-"At a high level, library code must not make changes to main contexts which "
-"could affect the execution of an application using the library, for example "
-"by changing when the application’s <code>GSource</code>s are dispatched. "
-"There are various best practices which can be followed to aid this."
+"At a high level, library code must not make changes to main contexts which could "
+"affect the execution of an application using the library, for example by changing "
+"when the application’s <code>GSource</code>s are dispatched. There are various best "
+"practices which can be followed to aid this."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:422
msgid ""
-"Never iterate a context created outside the library, including the global-"
-"default or thread-default contexts. Otherwise, <code>GSource</code>s created "
-"in the application may be dispatched when the application is not expecting "
-"it, causing <link href=\"http://en.wikipedia.org/wiki/Reentrancy_%28computing";
-"%29\">re-entrancy problems</link> for the application code."
+"Never iterate a context created outside the library, including the global-default or "
+"thread-default contexts. Otherwise, <code>GSource</code>s created in the application "
+"may be dispatched when the application is not expecting it, causing <link href="
+"\"http://en.wikipedia.org/wiki/Reentrancy_%28computing%29\";>re-entrancy problems</"
+"link> for the application code."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:431
msgid ""
"Always remove <code>GSource</code>s from a main context before dropping the "
-"library’s last reference to the context, especially if it may have been "
-"exposed to the application (for example, as a thread-default). Otherwise the "
-"application may keep a reference to the main context and continue iterating "
-"it after the library has returned, potentially causing unexpected source "
-"dispatches in the library. This is equivalent to not assuming that dropping "
-"the library’s last reference to a main context will finalize that context."
+"library’s last reference to the context, especially if it may have been exposed to "
+"the application (for example, as a thread-default). Otherwise the application may "
+"keep a reference to the main context and continue iterating it after the library has "
+"returned, potentially causing unexpected source dispatches in the library. This is "
+"equivalent to not assuming that dropping the library’s last reference to a main "
+"context will finalize that context."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:442
msgid ""
-"If the library is designed to be used from multiple threads, or in a context-"
-"aware fashion, always document which context each callback will be "
-"dispatched in. For example, “callbacks will always be dispatched in the "
-"context which is the thread-default at the time of the object’s "
-"construction”. Developers using the library’s API need to know this "
-"information."
+"If the library is designed to be used from multiple threads, or in a context-aware "
+"fashion, always document which context each callback will be dispatched in. For "
+"example, “callbacks will always be dispatched in the context which is the thread-"
+"default at the time of the object’s construction”. Developers using the library’s "
+"API need to know this information."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:451
msgid ""
-"Use <code>g_main_context_invoke()</code> to ensure callbacks are dispatched "
-"in the right context. It’s much easier than manually using "
-"<code>g_idle_source_new()</code> to transfer work between contexts. (See: "
-"<link xref=\"#ensuring-functions-are-called-in-the-right-context\"/>.)"
+"Use <code>g_main_context_invoke()</code> to ensure callbacks are dispatched in the "
+"right context. It’s much easier than manually using <code>g_idle_source_new()</code> "
+"to transfer work between contexts. (See: <link xref=\"#ensuring-functions-are-called-"
+"in-the-right-context\"/>.)"
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:458
msgid ""
-"Libraries should never use <code>g_main_context_default()</code> (or, "
-"equivalently, pass <code>NULL</code> to a <code>GMainContext</code>-typed "
-"parameter). Always store and explicitly use a specific <code>GMainContext</"
-"code>, even if it often points to some default context. This makes the code "
-"easier to split out into threads in future, if needed, without causing hard-"
-"to-debug problems caused by callbacks being invoked in the wrong context."
+"Libraries should never use <code>g_main_context_default()</code> (or, equivalently, "
+"pass <code>NULL</code> to a <code>GMainContext</code>-typed parameter). Always store "
+"and explicitly use a specific <code>GMainContext</code>, even if it often points to "
+"some default context. This makes the code easier to split out into threads in "
+"future, if needed, without causing hard-to-debug problems caused by callbacks being "
+"invoked in the wrong context."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:468
msgid ""
"Always write things asynchronously internally (using <link xref=\"#gtask"
-"\"><code>GTask</code></link> where appropriate), and keep synchronous "
-"wrappers at the very top level of an API, where they can be implemented by "
-"calling <code>g_main_context_iteration()</code> on a specific "
-"<code>GMainContext</code>. Again, this makes future refactoring easier. This "
-"is demonstrated in the above example: the thread uses "
-"<code>g_output_stream_write_async()</code> rather than "
+"\"><code>GTask</code></link> where appropriate), and keep synchronous wrappers at "
+"the very top level of an API, where they can be implemented by calling "
+"<code>g_main_context_iteration()</code> on a specific <code>GMainContext</code>. "
+"Again, this makes future refactoring easier. This is demonstrated in the above "
+"example: the thread uses <code>g_output_stream_write_async()</code> rather than "
"<code>g_output_stream_write()</code>."
msgstr ""
@@ -4535,56 +4459,54 @@ msgstr ""
#: C/main-contexts.page:489
msgid ""
"The ‘right context’ is the thread-default main context of the <em>thread the "
-"function should be executing in</em>. This assumes the typical case that "
-"every thread has a <em>single</em> main context running in a main loop. A "
-"main context effectively provides a work or <link href=\"http://en.wikipedia.";
-"org/wiki/Message_queue\">message queue</link> for the thread — something "
-"which the thread can periodically check to determine if there is work "
-"pending from another thread. Putting a message on this queue – invoking a "
-"function in another main context – will result in it eventually being "
-"dispatched in that thread."
+"function should be executing in</em>. This assumes the typical case that every "
+"thread has a <em>single</em> main context running in a main loop. A main context "
+"effectively provides a work or <link href=\"http://en.wikipedia.org/wiki/";
+"Message_queue\">message queue</link> for the thread — something which the thread can "
+"periodically check to determine if there is work pending from another thread. "
+"Putting a message on this queue – invoking a function in another main context – will "
+"result in it eventually being dispatched in that thread."
msgstr ""
#. (itstool) path: example/p
#: C/main-contexts.page:503
msgid ""
-"For example, if an application does a long and CPU-intensive computation it "
-"should schedule this in a background thread so that UI updates in the main "
-"thread are not blocked. The results of the computation, however, might need "
-"to be displayed in the UI, so some UI update function must be called in the "
-"main thread once the computation’s complete."
+"For example, if an application does a long and CPU-intensive computation it should "
+"schedule this in a background thread so that UI updates in the main thread are not "
+"blocked. The results of the computation, however, might need to be displayed in the "
+"UI, so some UI update function must be called in the main thread once the "
+"computation’s complete."
msgstr ""
#. (itstool) path: example/p
#: C/main-contexts.page:511
msgid ""
-"Furthermore, if the computation function can be limited to a single thread, "
-"it becomes easy to eliminate the need for locking a lot of the data it "
-"accesses. This assumes that other threads are implemented similarly and "
-"hence most data is only accessed by a single thread, with threads "
-"communicating by <link href=\"http://en.wikipedia.org/wiki/Message_passing";
-"\">message passing</link>. This allows each thread to update its data at its "
-"leisure, which significantly simplifies locking."
+"Furthermore, if the computation function can be limited to a single thread, it "
+"becomes easy to eliminate the need for locking a lot of the data it accesses. This "
+"assumes that other threads are implemented similarly and hence most data is only "
+"accessed by a single thread, with threads communicating by <link href=\"http://en.";
+"wikipedia.org/wiki/Message_passing\">message passing</link>. This allows each thread "
+"to update its data at its leisure, which significantly simplifies locking."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:523
msgid ""
-"For some functions, there might be no reason to care which context they’re "
-"executed in, perhaps because they’re asynchronous and hence do not block the "
-"context. However, it is still advisable to be explicit about which context "
-"is used, since those functions may emit signals or invoke callbacks, and for "
-"reasons of thread safety it’s necessary to know which threads those signal "
-"handlers or callbacks are going to be invoked in."
+"For some functions, there might be no reason to care which context they’re executed "
+"in, perhaps because they’re asynchronous and hence do not block the context. "
+"However, it is still advisable to be explicit about which context is used, since "
+"those functions may emit signals or invoke callbacks, and for reasons of thread "
+"safety it’s necessary to know which threads those signal handlers or callbacks are "
+"going to be invoked in."
msgstr ""
#. (itstool) path: example/p
#: C/main-contexts.page:533
msgid ""
-"For example, the progress callback in <link href=\"https://developer.gnome.";
-"org/gio/stable/GFile.html#g-file-copy-async\"><code>g_file_copy_async()</"
-"code></link> is documented as being called in the thread-default main "
-"context at the time of the initial call."
+"For example, the progress callback in <link href=\"https://developer.gnome.org/gio/";
+"stable/GFile.html#g-file-copy-async\"><code>g_file_copy_async()</code></link> is "
+"documented as being called in the thread-default main context at the time of the "
+"initial call."
msgstr ""
#. (itstool) path: section/title
@@ -4595,56 +4517,54 @@ msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:544
msgid ""
-"The core principle of invoking a function in a specific context is simple, "
-"and is walked through below to explain the concepts. In practice the <link "
-"xref=\"#g-main-context-invoke-full\">convenience method, "
-"<code>g_main_context_invoke_full()</code></link> should be used instead."
+"The core principle of invoking a function in a specific context is simple, and is "
+"walked through below to explain the concepts. In practice the <link xref=\"#g-main-"
+"context-invoke-full\">convenience method, <code>g_main_context_invoke_full()</code></"
+"link> should be used instead."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:551
msgid ""
-"A <link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-";
-"Loop.html#GSource\"><code>GSource</code></link> has to be added to the "
-"target <code>GMainContext</code>, which will invoke the function when it’s "
-"dispatched. This <code>GSource</code> should almost always be an idle source "
-"created with <link href=\"https://developer.gnome.org/glib/stable/glib-The-";
-"Main-Event-Loop.html#g-idle-source-new\"><code>g_idle_source_new()</code></"
-"link>, but this doesn’t have to be the case. It could be a timeout source so "
-"that the function is executed after a delay, for example."
+"A <link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.";
+"html#GSource\"><code>GSource</code></link> has to be added to the target "
+"<code>GMainContext</code>, which will invoke the function when it’s dispatched. This "
+"<code>GSource</code> should almost always be an idle source created with <link href="
+"\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html#g-idle-";
+"source-new\"><code>g_idle_source_new()</code></link>, but this doesn’t have to be "
+"the case. It could be a timeout source so that the function is executed after a "
+"delay, for example."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:562
msgid ""
-"The <code>GSource</code> will be <link xref=\"#what-is-gmaincontext"
-"\">dispatched as soon as it’s ready</link>, calling the function on the "
-"thread’s stack. In the case of an idle source, this will be as soon as all "
-"sources at a higher priority have been dispatched — this can be tweaked "
-"using the idle source’s priority parameter with <link href=\"https://";
-"developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html#g-source-set-"
-"priority\"><code>g_source_set_priority()</code></link>. The source will "
-"typically then be destroyed so the function is only executed once (though "
+"The <code>GSource</code> will be <link xref=\"#what-is-gmaincontext\">dispatched as "
+"soon as it’s ready</link>, calling the function on the thread’s stack. In the case "
+"of an idle source, this will be as soon as all sources at a higher priority have "
+"been dispatched — this can be tweaked using the idle source’s priority parameter "
+"with <link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.";
+"html#g-source-set-priority\"><code>g_source_set_priority()</code></link>. The source "
+"will typically then be destroyed so the function is only executed once (though "
"again, this doesn’t have to be the case)."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:574
msgid ""
-"Data can be passed between threads as the <code>user_data</code> passed to "
-"the <code>GSource</code>’s callback. This is set on the source using <link "
-"href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.";
-"html#g-source-set-callback\"><code>g_source_set_callback()</code></link>, "
-"along with the callback function to invoke. Only a single pointer is "
-"provided, so if multiple data fields need passing, they must be wrapped in "
-"an allocated structure."
+"Data can be passed between threads as the <code>user_data</code> passed to the "
+"<code>GSource</code>’s callback. This is set on the source using <link href="
+"\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html#g-source-set-";
+"callback\"><code>g_source_set_callback()</code></link>, along with the callback "
+"function to invoke. Only a single pointer is provided, so if multiple data fields "
+"need passing, they must be wrapped in an allocated structure."
msgstr ""
#. (itstool) path: example/p
#: C/main-contexts.page:584
msgid ""
-"The example below demonstrates the underlying principles, but there are "
-"convenience methods explained below which simplify things."
+"The example below demonstrates the underlying principles, but there are convenience "
+"methods explained below which simplify things."
msgstr ""
#. (itstool) path: example/code
@@ -4873,51 +4793,49 @@ msgstr ""
#: C/main-contexts.page:698
msgid ""
"This invocation is <em style=\"strong\">uni-directional</em>: it calls "
-"<code>my_func()</code> in <code>thread1</code>, but there’s no way to return "
-"a value to the main thread. To do that, the same principle needs to be used "
-"again, invoking a callback function in the main thread. It’s a "
-"straightforward extension which isn’t covered here."
+"<code>my_func()</code> in <code>thread1</code>, but there’s no way to return a value "
+"to the main thread. To do that, the same principle needs to be used again, invoking "
+"a callback function in the main thread. It’s a straightforward extension which isn’t "
+"covered here."
msgstr ""
#. (itstool) path: example/p
#: C/main-contexts.page:706
msgid ""
-"To maintain thread safety, data which is potentially accessed by multiple "
-"threads must make those accesses mutually exclusive using a <link href="
-"\"http://en.wikipedia.org/wiki/Mutual_exclusion\";>mutex</link>. Data "
-"potentially accessed by multiple threads: <code>thread1_main_context</code>, "
-"passed in the fork call to <code>thread1_main</code>; and <code>some_object</"
-"code>, a reference to which is passed in the data closure. Critically, GLib "
-"guarantees that <code>GMainContext</code> is thread safe, so sharing "
-"<code>thread1_main_context</code> between threads is safe. The example "
-"assumes that other code accessing <code>some_object</code> is thread safe."
+"To maintain thread safety, data which is potentially accessed by multiple threads "
+"must make those accesses mutually exclusive using a <link href=\"http://en.wikipedia.";
+"org/wiki/Mutual_exclusion\">mutex</link>. Data potentially accessed by multiple "
+"threads: <code>thread1_main_context</code>, passed in the fork call to "
+"<code>thread1_main</code>; and <code>some_object</code>, a reference to which is "
+"passed in the data closure. Critically, GLib guarantees that <code>GMainContext</"
+"code> is thread safe, so sharing <code>thread1_main_context</code> between threads "
+"is safe. The example assumes that other code accessing <code>some_object</code> is "
+"thread safe."
msgstr ""
#. (itstool) path: example/p
#: C/main-contexts.page:720
msgid ""
-"Note that <code>some_string</code> and <code>some_int</code> cannot be "
-"accessed from both threads, because <em>copies</em> of them are passed to "
-"<code>thread1</code>, rather than the originals. This is a standard "
-"technique for making cross-thread calls thread safe without requiring "
-"locking. It also avoids the problem of synchronizing freeing "
-"<code>some_string</code>."
+"Note that <code>some_string</code> and <code>some_int</code> cannot be accessed from "
+"both threads, because <em>copies</em> of them are passed to <code>thread1</code>, "
+"rather than the originals. This is a standard technique for making cross-thread "
+"calls thread safe without requiring locking. It also avoids the problem of "
+"synchronizing freeing <code>some_string</code>."
msgstr ""
#. (itstool) path: example/p
#: C/main-contexts.page:729
msgid ""
-"Similarly, a reference to <code>some_object</code> is transferred to "
-"<code>thread1</code>, which works around the issue of synchronizing "
-"destruction of the object (see <link xref=\"memory-management\"/>)."
+"Similarly, a reference to <code>some_object</code> is transferred to <code>thread1</"
+"code>, which works around the issue of synchronizing destruction of the object (see "
+"<link xref=\"memory-management\"/>)."
msgstr ""
#. (itstool) path: example/p
#: C/main-contexts.page:735
msgid ""
-"<code>g_idle_source_new()</code> is used rather than the simpler "
-"<code>g_idle_add()</code> so the <code>GMainContext</code> to attach to can "
-"be specified."
+"<code>g_idle_source_new()</code> is used rather than the simpler <code>g_idle_add()</"
+"code> so the <code>GMainContext</code> to attach to can be specified."
msgstr ""
#. (itstool) path: section/title
@@ -4928,28 +4846,27 @@ msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:748
msgid ""
-"This is simplified greatly by the convenience method, <link href=\"https://";
-"developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html#g-main-context-"
-"invoke-full\"><code>g_main_context_invoke_full()</code></link>. It invokes a "
-"callback so that the specified <code>GMainContext</code> is owned during the "
-"invocation. Owning a main context is almost always equivalent to running it, "
-"and hence the function is invoked in the thread for which the specified "
-"context is the thread-default."
+"This is simplified greatly by the convenience method, <link href=\"https://developer.";
+"gnome.org/glib/stable/glib-The-Main-Event-Loop.html#g-main-context-invoke-full"
+"\"><code>g_main_context_invoke_full()</code></link>. It invokes a callback so that "
+"the specified <code>GMainContext</code> is owned during the invocation. Owning a "
+"main context is almost always equivalent to running it, and hence the function is "
+"invoked in the thread for which the specified context is the thread-default."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:757
msgid ""
-"<code>g_main_context_invoke()</code> can be used instead if the user data "
-"does not need to be freed by a <code>GDestroyNotify</code> callback after "
-"the invocation returns."
+"<code>g_main_context_invoke()</code> can be used instead if the user data does not "
+"need to be freed by a <code>GDestroyNotify</code> callback after the invocation "
+"returns."
msgstr ""
#. (itstool) path: example/p
#: C/main-contexts.page:764
msgid ""
-"Modifying the earlier example, the <code>invoke_my_func()</code> function "
-"can be replaced by the following:"
+"Modifying the earlier example, the <code>invoke_my_func()</code> function can be "
+"replaced by the following:"
msgstr ""
#. (itstool) path: example/code
@@ -5007,23 +4924,22 @@ msgstr ""
msgid ""
"Consider what happens if <code>invoke_my_func()</code> were called from "
"<code>thread1</code>, rather than from the main thread. With the original "
-"implementation, the idle source would be added to <code>thread1</code>’s "
-"context and dispatched on the context’s next iteration (assuming no pending "
-"dispatches with higher priorities). With the improved implementation, "
-"<code>g_main_context_invoke_full()</code> will notice that the specified "
-"context is already owned by the thread (or ownership can be acquired by it), "
-"and will call <code>my_func_idle()</code> directly, rather than attaching a "
-"source to the context and delaying the invocation to the next context "
-"iteration."
+"implementation, the idle source would be added to <code>thread1</code>’s context and "
+"dispatched on the context’s next iteration (assuming no pending dispatches with "
+"higher priorities). With the improved implementation, "
+"<code>g_main_context_invoke_full()</code> will notice that the specified context is "
+"already owned by the thread (or ownership can be acquired by it), and will call "
+"<code>my_func_idle()</code> directly, rather than attaching a source to the context "
+"and delaying the invocation to the next context iteration."
msgstr ""
#. (itstool) path: example/p
#: C/main-contexts.page:806
msgid ""
-"This subtle behavior difference doesn’t matter in most cases, but is worth "
-"bearing in mind since it can affect blocking behavior "
-"(<code>invoke_my_func()</code> would go from taking negligible time, to "
-"taking the same amount of time as <code>my_func()</code> before returning)."
+"This subtle behavior difference doesn’t matter in most cases, but is worth bearing "
+"in mind since it can affect blocking behavior (<code>invoke_my_func()</code> would "
+"go from taking negligible time, to taking the same amount of time as "
+"<code>my_func()</code> before returning)."
msgstr ""
#. (itstool) path: section/title
@@ -5034,8 +4950,8 @@ msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:820
msgid ""
-"It is useful to document which thread each function should be called in, in "
-"the form of an assertion:"
+"It is useful to document which thread each function should be called in, in the form "
+"of an assertion:"
msgstr ""
#. (itstool) path: section/code
@@ -5051,21 +4967,20 @@ msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:827
msgid ""
-"If that’s put at the top of each function, any assertion failure will "
-"highlight a case where a function has been called from the wrong thread. It "
-"is much easier to write these assertions when initially developing code, "
-"rather than debuging race conditions which can easily result from a function "
-"being called in the wrong thread."
+"If that’s put at the top of each function, any assertion failure will highlight a "
+"case where a function has been called from the wrong thread. It is much easier to "
+"write these assertions when initially developing code, rather than debugging race "
+"conditions which can easily result from a function being called in the wrong thread."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:835
msgid ""
-"This technique can also be applied to signal emissions and callbacks, "
-"improving type safety as well as asserting the right context is used. Note "
-"that signal emission via <link href=\"https://developer.gnome.org/gobject/";
-"stable/gobject-Signals.html#g-signal-emit\"><code>g_signal_emit()</code></"
-"link> is synchronous, and doesn’t involve a main context at all."
+"This technique can also be applied to signal emissions and callbacks, improving type "
+"safety as well as asserting the right context is used. Note that signal emission via "
+"<link href=\"https://developer.gnome.org/gobject/stable/gobject-Signals.html#g-";
+"signal-emit\"><code>g_signal_emit()</code></link> is synchronous, and doesn’t "
+"involve a main context at all."
msgstr ""
#. (itstool) path: example/p
@@ -5142,29 +5057,27 @@ msgstr "<code>GTask</code>"
#. (itstool) path: section/p
#: C/main-contexts.page:879
msgid ""
-"<link href=\"https://developer.gnome.org/gio/stable/GTask.html";
-"\"><code>GTask</code></link> provides a slightly different approach to "
-"invoking functions in other threads, which is more suited to the case where "
-"a function should be executed in <em>some</em> background thread, but not a "
-"specific one."
+"<link href=\"https://developer.gnome.org/gio/stable/GTask.html\";><code>GTask</code></"
+"link> provides a slightly different approach to invoking functions in other threads, "
+"which is more suited to the case where a function should be executed in <em>some</"
+"em> background thread, but not a specific one."
msgstr ""
#. (itstool) path: section/p
#: C/main-contexts.page:886
msgid ""
-"<code>GTask</code> takes a data closure and a function to execute, and "
-"provides ways to return the result from this function. It handles everything "
-"necessary to run that function in an arbitrary thread belonging to some "
-"thread pool internal to GLib."
+"<code>GTask</code> takes a data closure and a function to execute, and provides ways "
+"to return the result from this function. It handles everything necessary to run that "
+"function in an arbitrary thread belonging to some thread pool internal to GLib."
msgstr ""
#. (itstool) path: example/p
#: C/main-contexts.page:894
msgid ""
"By combining <link xref=\"#g-main-context-invoke-full"
-"\"><code>g_main_context_invoke_full()</code></link> and <code>GTask</code>, "
-"it is possible to run a task in a specific context and effortlessly return "
-"its result to the current context:"
+"\"><code>g_main_context_invoke_full()</code></link> and <code>GTask</code>, it is "
+"possible to run a task in a specific context and effortlessly return its result to "
+"the current context:"
msgstr ""
#. (itstool) path: example/code
@@ -5286,19 +5199,17 @@ msgstr "Speicherverwaltung"
#. (itstool) path: page/p
#: C/memory-management.page:50
msgid ""
-"The GNOME stack is predominantly written in C, so dynamically allocated "
-"memory has to be managed manually. Through use of GLib convenience APIs, "
-"memory management can be trivial, but programmers always need to keep memory "
-"in mind when writing code."
+"The GNOME stack is predominantly written in C, so dynamically allocated memory has "
+"to be managed manually. Through use of GLib convenience APIs, memory management can "
+"be trivial, but programmers always need to keep memory in mind when writing code."
msgstr ""
#. (itstool) path: page/p
#: C/memory-management.page:57
msgid ""
-"It is assumed that the reader is familiar with the idea of heap allocation "
-"of memory using <code>malloc()</code> and <code>free()</code>, and knows of "
-"the paired GLib equivalents, <code>g_malloc()</code> and <code>g_free()</"
-"code>."
+"It is assumed that the reader is familiar with the idea of heap allocation of memory "
+"using <code>malloc()</code> and <code>free()</code>, and knows of the paired GLib "
+"equivalents, <code>g_malloc()</code> and <code>g_free()</code>."
msgstr ""
#. (itstool) path: synopsis/p
@@ -5329,59 +5240,58 @@ msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:82
msgid ""
-"Determine and document whether each variable is owned or unowned. They must "
-"never change from one to the other at runtime. (<link xref=\"#principles\"/>)"
+"Determine and document whether each variable is owned or unowned. They must never "
+"change from one to the other at runtime. (<link xref=\"#principles\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:87
msgid ""
-"Determine and document the ownership transfers at function boundaries. "
-"(<link xref=\"#principles\"/>)"
+"Determine and document the ownership transfers at function boundaries. (<link xref="
+"\"#principles\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:91
msgid ""
-"Ensure that each assignment, function call and function return respects the "
-"relevant ownership transfers. (<link xref=\"#assignments\"/>, <link xref="
-"\"#function-calls\"/>, <link xref=\"#function-returns\"/>)"
+"Ensure that each assignment, function call and function return respects the relevant "
+"ownership transfers. (<link xref=\"#assignments\"/>, <link xref=\"#function-calls\"/"
+">, <link xref=\"#function-returns\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:96
msgid ""
-"Use reference counting rather than explicit finalization where possible. "
-"(<link xref=\"#reference-counting\"/>)"
+"Use reference counting rather than explicit finalization where possible. (<link xref="
+"\"#reference-counting\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:100
msgid ""
"Use GLib convenience functions like <link xref=\"#g-clear-object"
-"\"><code>g_clear_object()</code></link> where possible. (<link xref="
-"\"#convenience-functions\"/>)"
+"\"><code>g_clear_object()</code></link> where possible. (<link xref=\"#convenience-"
+"functions\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:105
msgid ""
-"Do not split memory management across code paths. (<link xref=\"#principles"
-"\"/>)"
+"Do not split memory management across code paths. (<link xref=\"#principles\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:109
msgid ""
-"Use the single-path cleanup pattern for large or complex functions. (<link "
-"xref=\"#single-path-cleanup\"/>)"
+"Use the single-path cleanup pattern for large or complex functions. (<link xref="
+"\"#single-path-cleanup\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:113
msgid ""
-"Leaks should be checked for using Valgrind or the address sanitizer. (<link "
-"xref=\"#verification\"/>)"
+"Leaks should be checked for using Valgrind or the address sanitizer. (<link xref="
+"\"#verification\"/>)"
msgstr ""
#. (itstool) path: section/title
@@ -5392,38 +5302,36 @@ msgstr "Prinzipien der Speicherverwaltung"
#. (itstool) path: section/p
#: C/memory-management.page:123
msgid ""
-"The normal approach to memory management is for the programmer to keep track "
-"of which variables point to allocated memory, and to manually free them when "
-"they are no longer needed. This is correct, but can be clarified by "
-"introducing the concept of <em>ownership</em>, which is the piece of code "
-"(such as a function, struct or object) which is responsible for freeing a "
-"piece of allocated memory (an <em>allocation</em>). Each allocation has "
-"exactly one owner; this owner may change as the program runs, by "
-"<em>transferring</em> ownership to another piece of code. Each variable is "
-"<em>owned</em> or <em>unowned</em>, according to whether the scope "
-"containing it is always its owner. Each function parameter and return type "
-"either transfers ownership of the values passed to it, or it doesn’t. If "
-"code which owns some memory doesn’t deallocate that memory, that’s a memory "
-"leak. If code which doesn’t own some memory frees it, that’s a double-free. "
-"Both are bad."
+"The normal approach to memory management is for the programmer to keep track of "
+"which variables point to allocated memory, and to manually free them when they are "
+"no longer needed. This is correct, but can be clarified by introducing the concept "
+"of <em>ownership</em>, which is the piece of code (such as a function, struct or "
+"object) which is responsible for freeing a piece of allocated memory (an "
+"<em>allocation</em>). Each allocation has exactly one owner; this owner may change "
+"as the program runs, by <em>transferring</em> ownership to another piece of code. "
+"Each variable is <em>owned</em> or <em>unowned</em>, according to whether the scope "
+"containing it is always its owner. Each function parameter and return type either "
+"transfers ownership of the values passed to it, or it doesn’t. If code which owns "
+"some memory doesn’t deallocate that memory, that’s a memory leak. If code which "
+"doesn’t own some memory frees it, that’s a double-free. Both are bad."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:140
msgid ""
-"By statically calculating which variables are owned, memory management "
-"becomes a simple task of unconditionally freeing the owned variables before "
-"they leave their scope, and <em>not</em> freeing the unowned variables (see "
-"<link xref=\"#single-path-cleanup\"/>). The key question to answer for all "
-"memory is: which code has ownership of this memory?"
+"By statically calculating which variables are owned, memory management becomes a "
+"simple task of unconditionally freeing the owned variables before they leave their "
+"scope, and <em>not</em> freeing the unowned variables (see <link xref=\"#single-path-"
+"cleanup\"/>). The key question to answer for all memory is: which code has ownership "
+"of this memory?"
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:149
msgid ""
-"There is an important restriction here: variables must <em style=\"strong"
-"\">never</em> change from owned to unowned (or vice-versa) at runtime. This "
-"restriction is key to simplifying memory management."
+"There is an important restriction here: variables must <em style=\"strong\">never</"
+"em> change from owned to unowned (or vice-versa) at runtime. This restriction is key "
+"to simplifying memory management."
msgstr ""
#. (itstool) path: section/p
@@ -5444,8 +5352,7 @@ msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:162
msgid ""
-"The following code has been annotated to note where the ownership transfers "
-"happen:"
+"The following code has been annotated to note where the ownership transfers happen:"
msgstr ""
#. (itstool) path: section/code
@@ -5492,43 +5399,42 @@ msgstr ""
#: C/memory-management.page:185
msgid ""
"There are a few points here: Firstly, the ‘owned’ comments by the variable "
-"declarations denote that those variables are owned by the local scope, and "
-"hence need to be freed before they go out of scope. The alternative is "
-"‘unowned’, which means the local scope does <em>not</em> have ownership, and "
-"<em>must not</em> free the variables before going out of scope. Similarly, "
-"ownership <em>must not</em> be transferred to them on assignment."
+"declarations denote that those variables are owned by the local scope, and hence "
+"need to be freed before they go out of scope. The alternative is ‘unowned’, which "
+"means the local scope does <em>not</em> have ownership, and <em>must not</em> free "
+"the variables before going out of scope. Similarly, ownership <em>must not</em> be "
+"transferred to them on assignment."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:195
msgid ""
-"Secondly, the variable type modifiers reflect whether they transfer "
-"ownership: because <code>my_str</code> is owned by the local scope, it has "
-"type <code>gchar</code>, whereas <code>template</code> is <code>const</code> "
-"to denote it is unowned. Similarly, the <code>template</code> parameter of "
-"<code>generate_string()</code> and the <code>str</code> parameter of "
-"<code>print_string()</code> are <code>const</code> because no ownership is "
-"transferred when those functions are called. As ownership <em>is</em> "
-"transferred for the string parameter of <code>g_value_take_string()</code>, "
-"we can expect its type to be <code>gchar</code>."
+"Secondly, the variable type modifiers reflect whether they transfer ownership: "
+"because <code>my_str</code> is owned by the local scope, it has type <code>gchar</"
+"code>, whereas <code>template</code> is <code>const</code> to denote it is unowned. "
+"Similarly, the <code>template</code> parameter of <code>generate_string()</code> and "
+"the <code>str</code> parameter of <code>print_string()</code> are <code>const</code> "
+"because no ownership is transferred when those functions are called. As ownership "
+"<em>is</em> transferred for the string parameter of <code>g_value_take_string()</"
+"code>, we can expect its type to be <code>gchar</code>."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:208
msgid ""
-"(Note that this is not the case for <link href=\"https://developer.gnome.org/";
-"gobject/stable/gobject-The-Base-Object-Type.html\"> <code>GObject</code></"
-"link>s and subclasses, which can never be <code>const</code>. It is only the "
-"case for strings and simple <code>struct</code>s.)"
+"(Note that this is not the case for <link href=\"https://developer.gnome.org/gobject/";
+"stable/gobject-The-Base-Object-Type.html\"> <code>GObject</code></link>s and "
+"subclasses, which can never be <code>const</code>. It is only the case for strings "
+"and simple <code>struct</code>s.)"
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:216
msgid ""
-"Finally, a few libraries use a function naming convention to indicate "
-"ownership transfer, for example using ‘take’ in a function name to indicate "
-"full transfer of parameters, as with <code>g_value_take_string()</code>. "
-"Note that different libraries use different conventions, as shown below:"
+"Finally, a few libraries use a function naming convention to indicate ownership "
+"transfer, for example using ‘take’ in a function name to indicate full transfer of "
+"parameters, as with <code>g_value_take_string()</code>. Note that different "
+"libraries use different conventions, as shown below:"
msgstr ""
#. (itstool) path: td/p
@@ -5554,7 +5460,7 @@ msgstr ""
#. (itstool) path: td/p
#: C/memory-management.page:237
msgid "get"
-msgstr ""
+msgstr "get"
#. (itstool) path: td/p
#: C/memory-management.page:238 C/memory-management.page:254
@@ -5578,7 +5484,7 @@ msgstr ""
#. (itstool) path: td/p
#: C/memory-management.page:244
msgid "dup"
-msgstr ""
+msgstr "dup"
#. (itstool) path: td/p
#: C/memory-management.page:246 C/memory-management.page:247
@@ -5590,7 +5496,7 @@ msgstr "Nicht verwendet"
#. (itstool) path: td/p
#: C/memory-management.page:251
msgid "peek"
-msgstr ""
+msgstr "peek"
#. (itstool) path: td/p
#: C/memory-management.page:258
@@ -5600,27 +5506,26 @@ msgstr "gesetzt"
#. (itstool) path: td/p
#: C/memory-management.page:265
msgid "take"
-msgstr ""
+msgstr "take"
#. (itstool) path: td/p
#: C/memory-management.page:272
msgid "steal"
-msgstr ""
+msgstr "steal"
#. (itstool) path: section/p
#: C/memory-management.page:280
msgid ""
-"Ideally, all functions have a <code>(transfer)</code> <link xref="
-"\"introspection\">introspection annotation</link> for all relevant "
-"parameters and the return value. Failing that, here is a set of guidelines "
-"to use to determine whether ownership of a return value is transferred:"
+"Ideally, all functions have a <code>(transfer)</code> <link xref=\"introspection"
+"\">introspection annotation</link> for all relevant parameters and the return value. "
+"Failing that, here is a set of guidelines to use to determine whether ownership of a "
+"return value is transferred:"
msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:288
msgid ""
-"If the type has an introspection <code>(transfer)</code> annotation, look at "
-"that."
+"If the type has an introspection <code>(transfer)</code> annotation, look at that."
msgstr ""
#. (itstool) path: item/p
@@ -5631,15 +5536,15 @@ msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:295
msgid ""
-"Otherwise, if the function documentation explicitly specifies the return "
-"value must be freed, there is full or container transfer."
+"Otherwise, if the function documentation explicitly specifies the return value must "
+"be freed, there is full or container transfer."
msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:299
msgid ""
-"Otherwise, if the function is named ‘dup’, ‘take’ or ‘steal’, there is full "
-"or container transfer."
+"Otherwise, if the function is named ‘dup’, ‘take’ or ‘steal’, there is full or "
+"container transfer."
msgstr ""
#. (itstool) path: item/p
@@ -5650,29 +5555,27 @@ msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:306
msgid ""
-"Otherwise, you need to look at the function’s code to determine whether it "
-"intends ownership to be transferred. Then file a bug against the "
-"documentation for that function, and ask for an introspection annotation to "
-"be added."
+"Otherwise, you need to look at the function’s code to determine whether it intends "
+"ownership to be transferred. Then file a bug against the documentation for that "
+"function, and ask for an introspection annotation to be added."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:314
msgid ""
-"Given this ownership and transfer infrastructure, the correct approach to "
-"memory allocation can be mechanically determined for each situation. In each "
-"case, the <code>copy()</code> function must be appropriate to the data type, "
-"for example <code>g_strdup()</code> for strings, or <code>g_object_ref()</"
-"code> for GObjects."
+"Given this ownership and transfer infrastructure, the correct approach to memory "
+"allocation can be mechanically determined for each situation. In each case, the "
+"<code>copy()</code> function must be appropriate to the data type, for example "
+"<code>g_strdup()</code> for strings, or <code>g_object_ref()</code> for GObjects."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:322
msgid ""
-"When thinking about ownership transfer, <code>malloc()</code>/<code>free()</"
-"code> and reference counting are equivalent: in the former case, a newly "
-"allocated piece of heap memory is transferred; in the latter, a newly "
-"incremented reference. See <link xref=\"#reference-counting\"/>."
+"When thinking about ownership transfer, <code>malloc()</code>/<code>free()</code> "
+"and reference counting are equivalent: in the former case, a newly allocated piece "
+"of heap memory is transferred; in the latter, a newly incremented reference. See "
+"<link xref=\"#reference-counting\"/>."
msgstr ""
#. (itstool) path: section/title
@@ -5721,8 +5624,8 @@ msgstr "owned_dest = owned_src; owned_src = NULL"
#. (itstool) path: td/p
#: C/memory-management.page:355
msgid ""
-"Pure assignment, assuming the unowned variable is not used after the owned "
-"one is freed."
+"Pure assignment, assuming the unowned variable is not used after the owned one is "
+"freed."
msgstr ""
#. (itstool) path: td/code
@@ -5858,8 +5761,8 @@ msgstr ""
#. (itstool) path: td/p
#: C/memory-management.page:449
msgid ""
-"Invalid. The source needs to be freed, so the return value would use freed "
-"memory — a use-after-free error."
+"Invalid. The source needs to be freed, so the return value would use freed memory — "
+"a use-after-free error."
msgstr ""
#. (itstool) path: td/p
@@ -5887,24 +5790,23 @@ msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:475
msgid ""
-"Documenting the ownership transfer for each function parameter and return, "
-"and the ownership for each variable, is important. While they may be clear "
-"when writing the code, they are not clear a few months later; and may never "
-"be clear to users of an API. They should always be documented."
+"Documenting the ownership transfer for each function parameter and return, and the "
+"ownership for each variable, is important. While they may be clear when writing the "
+"code, they are not clear a few months later; and may never be clear to users of an "
+"API. They should always be documented."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:482
msgid ""
-"The best way to document ownership transfer is to use the <link href="
-"\"https://wiki.gnome.org/Projects/GObjectIntrospection/";
-"Annotations#Memory_and_lifecycle_management\"> <code>(transfer)</code></"
-"link> annotation introduced by <link xref=\"introspection\">gobject-"
-"introspection</link>. Include this in the API documentation comment for each "
-"function parameter and return type. If a function is not public API, write a "
-"documentation comment for it anyway and include the <code>(transfer)</code> "
-"annotations. By doing so, the introspection tools can also read the "
-"annotations and use them to correctly introspect the API."
+"The best way to document ownership transfer is to use the <link href=\"https://wiki.";
+"gnome.org/Projects/GObjectIntrospection/Annotations#Memory_and_lifecycle_management"
+"\"> <code>(transfer)</code></link> annotation introduced by <link xref="
+"\"introspection\">gobject-introspection</link>. Include this in the API "
+"documentation comment for each function parameter and return type. If a function is "
+"not public API, write a documentation comment for it anyway and include the "
+"<code>(transfer)</code> annotations. By doing so, the introspection tools can also "
+"read the annotations and use them to correctly introspect the API."
msgstr ""
#. (itstool) path: section/code
@@ -5948,9 +5850,8 @@ msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:514
msgid ""
-"Ownership for variables can be documented using inline comments. These are "
-"non-standard, and not read by any tools, but can form a convention if used "
-"consistently."
+"Ownership for variables can be documented using inline comments. These are non-"
+"standard, and not read by any tools, but can form a convention if used consistently."
msgstr ""
#. (itstool) path: section/code
@@ -5985,18 +5886,18 @@ msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:530
msgid ""
-"Note also that owned variables should always be initialized so that freeing "
-"them is more convenient. See <link xref=\"#convenience-functions\"/>."
+"Note also that owned variables should always be initialized so that freeing them is "
+"more convenient. See <link xref=\"#convenience-functions\"/>."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:536
msgid ""
-"Also note that some types, for example basic C types like strings, can have "
-"the <code>const</code> modifier added if they are unowned, to take advantage "
-"of compiler warnings resulting from assigning those variables to owned "
-"variables (which must <em>not</em> use the <code>const</code> modifier). If "
-"so, the <code>/* unowned */</code> comment may be omitted."
+"Also note that some types, for example basic C types like strings, can have the "
+"<code>const</code> modifier added if they are unowned, to take advantage of compiler "
+"warnings resulting from assigning those variables to owned variables (which must "
+"<em>not</em> use the <code>const</code> modifier). If so, the <code>/* unowned */</"
+"code> comment may be omitted."
msgstr ""
#. (itstool) path: section/title
@@ -6007,55 +5908,52 @@ msgstr "Referenzenzählung"
#. (itstool) path: section/p
#: C/memory-management.page:548
msgid ""
-"As well as conventional <code>malloc()</code>/<code>free()</code>-style "
-"types, GLib has various reference counted types — <link href=\"https://";
-"developer.gnome.org/gobject/stable/gobject-The-Base-Object-Type.html\"> "
-"<code>GObject</code></link> being a prime example."
+"As well as conventional <code>malloc()</code>/<code>free()</code>-style types, GLib "
+"has various reference counted types — <link href=\"https://developer.gnome.org/";
+"gobject/stable/gobject-The-Base-Object-Type.html\"> <code>GObject</code></link> "
+"being a prime example."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:555
msgid ""
-"The concepts of ownership and transfer apply just as well to reference "
-"counted types as they do to allocated types. A scope <em>owns</em> a "
-"reference counted type if it holds a strong reference to the instance (for "
-"example by calling <link href=\"https://developer.gnome.org/gobject/stable/";
-"gobject-The-Base-Object-Type.html#g-object-ref\"> <code>g_object_ref()</"
-"code></link>). An instance can be ‘copied’ by calling <code>g_object_ref()</"
-"code> again. Ownership can be freed with <link href=\"https://developer.";
-"gnome.org/gobject/stable/gobject-The-Base-Object-Type.html#g-object-unref\"> "
-"<code>g_object_unref()</code></link> — even though this may not actually "
-"finalize the instance, it frees the current scope’s ownership of that "
+"The concepts of ownership and transfer apply just as well to reference counted types "
+"as they do to allocated types. A scope <em>owns</em> a reference counted type if it "
+"holds a strong reference to the instance (for example by calling <link href="
+"\"https://developer.gnome.org/gobject/stable/gobject-The-Base-Object-Type.html#g-";
+"object-ref\"> <code>g_object_ref()</code></link>). An instance can be ‘copied’ by "
+"calling <code>g_object_ref()</code> again. Ownership can be freed with <link href="
+"\"https://developer.gnome.org/gobject/stable/gobject-The-Base-Object-Type.html#g-";
+"object-unref\"> <code>g_object_unref()</code></link> — even though this may not "
+"actually finalize the instance, it frees the current scope’s ownership of that "
"instance."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:569
msgid ""
-"See <link xref=\"#g-clear-object\"/> for a convenient way of handling "
-"GObject references."
+"See <link xref=\"#g-clear-object\"/> for a convenient way of handling GObject "
+"references."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:574
msgid ""
-"There are other reference counted types in GLib, such as <link href="
-"\"https://developer.gnome.org/glib/stable/glib-Hash-Tables.html\";> "
-"<code>GHashTable</code></link> (using <link href=\"https://developer.gnome.";
-"org/glib/stable/glib-Hash-Tables.html#g-hash-table-ref\"> "
-"<code>g_hash_table_ref()</code></link> and <link href=\"https://developer.";
-"gnome.org/glib/stable/glib-Hash-Tables.html#g-hash-table-unref\"> "
-"<code>g_hash_table_unref()</code></link>), or <link href=\"https://developer.";
-"gnome.org/glib/stable/glib-GVariant.html\"> <code>GVariant</code></link> "
-"(<link href=\"https://developer.gnome.org/glib/stable/glib-GVariant.html#g-";
-"variant-ref\"> <code>g_variant_ref()</code></link>, <link href=\"https://";
-"developer.gnome.org/glib/stable/glib-GVariant.html#g-variant-unref\"> "
-"<code>g_variant_unref()</code></link>). Some types, like <code>GHashTable</"
-"code>, support both reference counting and explicit finalization. Reference "
-"counting should always be used in preference, because it allows instances to "
-"be easily shared between multiple scopes (each holding their own reference) "
-"without having to allocate multiple copies of the instance. This saves "
-"memory."
+"There are other reference counted types in GLib, such as <link href=\"https://";
+"developer.gnome.org/glib/stable/glib-Hash-Tables.html\"> <code>GHashTable</code></"
+"link> (using <link href=\"https://developer.gnome.org/glib/stable/glib-Hash-Tables.";
+"html#g-hash-table-ref\"> <code>g_hash_table_ref()</code></link> and <link href="
+"\"https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g-hash-table-unref";
+"\"> <code>g_hash_table_unref()</code></link>), or <link href=\"https://developer.";
+"gnome.org/glib/stable/glib-GVariant.html\"> <code>GVariant</code></link> (<link href="
+"\"https://developer.gnome.org/glib/stable/glib-GVariant.html#g-variant-ref\";> "
+"<code>g_variant_ref()</code></link>, <link href=\"https://developer.gnome.org/glib/";
+"stable/glib-GVariant.html#g-variant-unref\"> <code>g_variant_unref()</code></link>). "
+"Some types, like <code>GHashTable</code>, support both reference counting and "
+"explicit finalization. Reference counting should always be used in preference, "
+"because it allows instances to be easily shared between multiple scopes (each "
+"holding their own reference) without having to allocate multiple copies of the "
+"instance. This saves memory."
msgstr ""
#. (itstool) path: section/title
@@ -6066,25 +5964,25 @@ msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:598
msgid ""
-"Classes which are derived from <link href=\"https://developer.gnome.org/";
-"gobject/stable/gobject-The-Base-Object-Type.html#GInitiallyUnowned"
+"Classes which are derived from <link href=\"https://developer.gnome.org/gobject/";
+"stable/gobject-The-Base-Object-Type.html#GInitiallyUnowned"
"\"><code>GInitiallyUnowned</code></link>, as opposed to <link href=\"https://";
-"developer.gnome.org/gobject/stable/gobject-The-Base-Object-Type.html#GObject-"
-"struct\"><code>GObject</code></link> have an initial reference which is "
-"<em>floating</em>, meaning that no code owns the reference. As soon as <link "
-"href=\"https://developer.gnome.org/gobject/stable/gobject-The-Base-Object-";
-"Type.html#g-object-ref-sink\"><code>g_object_ref_sink()</code></link> is "
-"called on the object, the floating reference is converted to a strong "
-"reference, and the calling code assumes ownership of the object."
+"developer.gnome.org/gobject/stable/gobject-The-Base-Object-Type.html#GObject-struct"
+"\"><code>GObject</code></link> have an initial reference which is <em>floating</em>, "
+"meaning that no code owns the reference. As soon as <link href=\"https://developer.";
+"gnome.org/gobject/stable/gobject-The-Base-Object-Type.html#g-object-ref-sink"
+"\"><code>g_object_ref_sink()</code></link> is called on the object, the floating "
+"reference is converted to a strong reference, and the calling code assumes ownership "
+"of the object."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:610
msgid ""
-"Floating references are a convenience for use in C in APIs, such as GTK+, "
-"where large numbers of objects must be created and organized into a "
-"hierarchy. In these cases, calling <code>g_object_unref()</code> to drop all "
-"the strong references would result in a lot of code."
+"Floating references are a convenience for use in C in APIs, such as GTK+, where "
+"large numbers of objects must be created and organized into a hierarchy. In these "
+"cases, calling <code>g_object_unref()</code> to drop all the strong references would "
+"result in a lot of code."
msgstr ""
#. (itstool) path: example/p
@@ -6111,8 +6009,8 @@ msgstr ""
#. (itstool) path: example/p
#: C/memory-management.page:627
msgid ""
-"Instead, the following code can be used, with the <code>GtkContainer</code> "
-"assuming ownership of the floating reference:"
+"Instead, the following code can be used, with the <code>GtkContainer</code> assuming "
+"ownership of the floating reference:"
msgstr ""
#. (itstool) path: example/code
@@ -6128,27 +6026,25 @@ msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:636
msgid ""
-"Floating references are only used by a few APIs — in particular, "
-"<code>GtkWidget</code> and all its subclasses. You must learn which APIs "
-"support it, and which APIs consume floating references, and only use them "
-"together."
+"Floating references are only used by a few APIs — in particular, <code>GtkWidget</"
+"code> and all its subclasses. You must learn which APIs support it, and which APIs "
+"consume floating references, and only use them together."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:643
msgid ""
-"Note that <code>g_object_ref_sink()</code> is equivalent to "
-"<code>g_object_ref()</code> when called on a non-floating reference, making "
-"<code>gtk_container_add()</code> no different from any other function in "
-"such cases."
+"Note that <code>g_object_ref_sink()</code> is equivalent to <code>g_object_ref()</"
+"code> when called on a non-floating reference, making <code>gtk_container_add()</"
+"code> no different from any other function in such cases."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:650
msgid ""
-"See the <link href=\"https://developer.gnome.org/gobject/stable/gobject-The-";
-"Base-Object-Type.html#floating-ref\">GObject manual</link> for more "
-"information on floating references."
+"See the <link href=\"https://developer.gnome.org/gobject/stable/gobject-The-Base-";
+"Object-Type.html#floating-ref\">GObject manual</link> for more information on "
+"floating references."
msgstr ""
#. (itstool) path: section/title
@@ -6159,11 +6055,10 @@ msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:660
msgid ""
-"GLib provides various convenience functions for memory management, "
-"especially for GObjects. Three will be covered here, but others exist — "
-"check the GLib API documentation for more. They typically follow similar "
-"naming schemas to these three (using ‘_full’ suffixes, or the verb ‘clear’ "
-"in the function name)."
+"GLib provides various convenience functions for memory management, especially for "
+"GObjects. Three will be covered here, but others exist — check the GLib API "
+"documentation for more. They typically follow similar naming schemas to these three "
+"(using ‘_full’ suffixes, or the verb ‘clear’ in the function name)."
msgstr ""
#. (itstool) path: section/title
@@ -6174,29 +6069,27 @@ msgstr "<code>g_clear_object()</code>"
#. (itstool) path: section/p
#: C/memory-management.page:671
msgid ""
-"<link href=\"https://developer.gnome.org/gobject/stable/gobject-The-Base-";
-"Object-Type.html#g-clear-object\"> <code>g_clear_object()</code></link> is a "
-"version of <link href=\"https://developer.gnome.org/gobject/stable/gobject-";
-"The-Base-Object-Type.html#g-object-unref\"> <code>g_object_unref()</code></"
-"link> which unrefs a GObject and then clears the pointer to it to "
-"<code>NULL</code>."
+"<link href=\"https://developer.gnome.org/gobject/stable/gobject-The-Base-Object-Type.";
+"html#g-clear-object\"> <code>g_clear_object()</code></link> is a version of <link "
+"href=\"https://developer.gnome.org/gobject/stable/gobject-The-Base-Object-Type.";
+"html#g-object-unref\"> <code>g_object_unref()</code></link> which unrefs a GObject "
+"and then clears the pointer to it to <code>NULL</code>."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:679
msgid ""
-"This makes it easier to implement code that guarantees a GObject pointer is "
-"always either <code>NULL</code>, or has ownership of a GObject (but which "
-"never points to a GObject it no longer owns)."
+"This makes it easier to implement code that guarantees a GObject pointer is always "
+"either <code>NULL</code>, or has ownership of a GObject (but which never points to a "
+"GObject it no longer owns)."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:685
msgid ""
-"By initialising all owned GObject pointers to <code>NULL</code>, freeing "
-"them at the end of the scope is as simple as calling <code>g_clear_object()</"
-"code> without any checks, as discussed in <link xref=\"#single-path-cleanup"
-"\"/>:"
+"By initialising all owned GObject pointers to <code>NULL</code>, freeing them at the "
+"end of the scope is as simple as calling <code>g_clear_object()</code> without any "
+"checks, as discussed in <link xref=\"#single-path-cleanup\"/>:"
msgstr ""
#. (itstool) path: section/code
@@ -6239,13 +6132,12 @@ msgstr "<code>g_list_free_full()</code>"
#. (itstool) path: section/p
#: C/memory-management.page:709
msgid ""
-"<link href=\"https://developer.gnome.org/glib/stable/glib-Doubly-Linked-";
-"Lists.html#g-list-free-full\"> <code>g_list_free_full()</code></link> frees "
-"all the elements in a linked list, <em>and all their data</em>. It is much "
-"more convenient than iterating through the list to free all the elements’ "
-"data, then calling <link href=\"https://developer.gnome.org/glib/stable/glib-";
-"Doubly-Linked-Lists.html#g-list-free\"> <code>g_list_free()</code></link> to "
-"free the <code>GList</code> elements themselves."
+"<link href=\"https://developer.gnome.org/glib/stable/glib-Doubly-Linked-Lists.html#g-";
+"list-free-full\"> <code>g_list_free_full()</code></link> frees all the elements in a "
+"linked list, <em>and all their data</em>. It is much more convenient than iterating "
+"through the list to free all the elements’ data, then calling <link href=\"https://";
+"developer.gnome.org/glib/stable/glib-Doubly-Linked-Lists.html#g-list-free\"> "
+"<code>g_list_free()</code></link> to free the <code>GList</code> elements themselves."
msgstr ""
#. (itstool) path: section/title
@@ -6256,32 +6148,33 @@ msgstr "<code>g_hash_table_new_full()</code>"
#. (itstool) path: section/p
#: C/memory-management.page:723
msgid ""
-"<link href=\"https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g-";
-"hash-table-new-full\"> <code>g_hash_table_new_full()</code></link> is a "
-"newer version of <link href=\"https://developer.gnome.org/glib/stable/glib-";
-"Hash-Tables.html#g-hash-table-new\"> <code>g_hash_table_new()</code></link> "
-"which allows setting functions to destroy each key and value in the hash "
-"table when they are removed. These functions are then automatically called "
-"for all keys and values when the hash table is destroyed, or when an entry "
-"is removed using <code>g_hash_table_remove()</code>."
+"<link href=\"https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g-hash-";
+"table-new-full\"> <code>g_hash_table_new_full()</code></link> is a newer version of "
+"<link href=\"https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g-hash-";
+"table-new\"> <code>g_hash_table_new()</code></link> which allows setting functions "
+"to destroy each key and value in the hash table when they are removed. These "
+"functions are then automatically called for all keys and values when the hash table "
+"is destroyed, or when an entry is removed using <code>g_hash_table_remove()</code>."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:734
msgid ""
-"Essentially, it simplifies memory management of keys and values to the "
-"question of whether they are present in the hash table. See <link xref="
-"\"#container-types\"/> for a discussion on ownership of elements within "
-"container types."
+"Essentially, it simplifies memory management of keys and values to the question of "
+"whether they are present in the hash table. See <link xref=\"#container-types\"/> "
+"for a discussion on ownership of elements within container types."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:741
msgid ""
-"A similar function exists for <code>GPtrArray</code>: <link href=\"https://";
-"developer.gnome.org/glib/stable/glib-Pointer-Arrays.html#g-ptr-array-new-"
-"with-free-func\"> <code>g_ptr_array_new_with_free_func()</code></link>."
+"A similar function exists for <code>GPtrArray</code>: <link href=\"https://developer.";
+"gnome.org/glib/stable/glib-Pointer-Arrays.html#g-ptr-array-new-with-free-func\"> "
+"<code>g_ptr_array_new_with_free_func()</code></link>."
msgstr ""
+"Eine ähnliche Funktion existiert für <code>GPtrArray</code>: <link href=\"https://";
+"developer.gnome.org/glib/stable/glib-Pointer-Arrays.html#g-ptr-array-new-with-free-"
+"func\"> <code>g_ptr_array_new_with_free_func()</code></link>."
#. (itstool) path: section/title
#: C/memory-management.page:750
@@ -6291,32 +6184,29 @@ msgstr "Containertypen"
#. (itstool) path: section/p
#: C/memory-management.page:752
msgid ""
-"When using container types, such as <code>GPtrArray</code> or <code>GList</"
-"code>, an additional level of ownership is introduced: as well as the "
-"ownership of the container instance, each element in the container is either "
-"owned or unowned too. By nesting containers, multiple levels of ownership "
-"must be tracked. Ownership of owned elements belongs to the container; "
-"ownership of the container belongs to the scope it’s in (which may be "
-"another container)."
+"When using container types, such as <code>GPtrArray</code> or <code>GList</code>, an "
+"additional level of ownership is introduced: as well as the ownership of the "
+"container instance, each element in the container is either owned or unowned too. By "
+"nesting containers, multiple levels of ownership must be tracked. Ownership of owned "
+"elements belongs to the container; ownership of the container belongs to the scope "
+"it’s in (which may be another container)."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:762
msgid ""
-"A key principle for simplifying this is to ensure that all elements in a "
-"container have the same ownership: they are either all owned, or all "
-"unowned. This happens automatically if the normal <link xref=\"#convenience-"
-"functions\"/> are used for types like <code>GPtrArray</code> and "
-"<code>GHashTable</code>."
+"A key principle for simplifying this is to ensure that all elements in a container "
+"have the same ownership: they are either all owned, or all unowned. This happens "
+"automatically if the normal <link xref=\"#convenience-functions\"/> are used for "
+"types like <code>GPtrArray</code> and <code>GHashTable</code>."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:770
msgid ""
-"If elements in a container are <em>owned</em>, adding them to the container "
-"is essentially an ownership transfer. For example, for an array of strings, "
-"if the elements are owned, the definition of <code>g_ptr_array_add()</code> "
-"is effectively:"
+"If elements in a container are <em>owned</em>, adding them to the container is "
+"essentially an ownership transfer. For example, for an array of strings, if the "
+"elements are owned, the definition of <code>g_ptr_array_add()</code> is effectively:"
msgstr ""
#. (itstool) path: section/code
@@ -6378,15 +6268,15 @@ msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:802
msgid ""
-"Here, constant strings can be added without copying them: "
-"<code>g_ptr_array_add (array, \"constant string\")</code>."
+"Here, constant strings can be added without copying them: <code>g_ptr_array_add "
+"(array, \"constant string\")</code>."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:807
msgid ""
-"See <link xref=\"#documentation\"/> for examples of comments to add to "
-"variable definitions to annotate them with the element type and ownership."
+"See <link xref=\"#documentation\"/> for examples of comments to add to variable "
+"definitions to annotate them with the element type and ownership."
msgstr ""
#. (itstool) path: section/title
@@ -6397,14 +6287,13 @@ msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:816
msgid ""
-"A useful design pattern for more complex functions is to have a single "
-"control path which cleans up (frees) allocations and returns to the caller. "
-"This vastly simplifies tracking of allocations, as it’s no longer necessary "
-"to mentally work out which allocations have been freed on each code path — "
-"all code paths end at the same point, so perform all the frees then. The "
-"benefits of this approach rapidly become greater for larger functions with "
-"more owned local variables; it may not make sense to apply the pattern to "
-"smaller functions."
+"A useful design pattern for more complex functions is to have a single control path "
+"which cleans up (frees) allocations and returns to the caller. This vastly "
+"simplifies tracking of allocations, as it’s no longer necessary to mentally work out "
+"which allocations have been freed on each code path — all code paths end at the same "
+"point, so perform all the frees then. The benefits of this approach rapidly become "
+"greater for larger functions with more owned local variables; it may not make sense "
+"to apply the pattern to smaller functions."
msgstr ""
#. (itstool) path: section/p
@@ -6415,22 +6304,22 @@ msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:831
msgid ""
-"The function returns from a single point, and uses <code>goto</code> to "
-"reach that point from other paths."
+"The function returns from a single point, and uses <code>goto</code> to reach that "
+"point from other paths."
msgstr ""
#. (itstool) path: item/p
#: C/memory-management.page:835
msgid ""
-"All owned variables are set to <code>NULL</code> when initialized or when "
-"ownership is transferred away from them."
+"All owned variables are set to <code>NULL</code> when initialized or when ownership "
+"is transferred away from them."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:841
msgid ""
-"The example below is for a small function (for brevity), but should "
-"illustrate the principles for application of the pattern to larger functions:"
+"The example below is for a small function (for brevity), but should illustrate the "
+"principles for application of the pattern to larger functions:"
msgstr ""
#. (itstool) path: listing/title
@@ -6551,50 +6440,48 @@ msgstr "Überprüfung"
#. (itstool) path: section/p
#: C/memory-management.page:905
msgid ""
-"Memory leaks can be checked for in two ways: static analysis, and runtime "
-"leak checking."
+"Memory leaks can be checked for in two ways: static analysis, and runtime leak "
+"checking."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:910
msgid ""
-"Static analysis with tools like <link xref=\"tooling#coverity\">Coverity</"
-"link>, the <link xref=\"tooling#clang-static-analyzer\">Clang static "
-"analyzer</link> or <link xref=\"tooling#tartan\">Tartan</link> can catch "
-"some leaks, but require knowledge of the ownership transfer of every "
-"function called in the code. Domain-specific static analyzers like Tartan "
-"(which knows about GLib memory allocation and transfer) can perform better "
-"here, but Tartan is quite a young project and still misses things (a low "
-"true positive rate). It is recommended that code be put through a static "
-"analyzer, but the primary tool for detecting leaks should be runtime leak "
-"checking."
+"Static analysis with tools like <link xref=\"tooling#coverity\">Coverity</link>, the "
+"<link xref=\"tooling#clang-static-analyzer\">Clang static analyzer</link> or <link "
+"xref=\"tooling#tartan\">Tartan</link> can catch some leaks, but require knowledge of "
+"the ownership transfer of every function called in the code. Domain-specific static "
+"analyzers like Tartan (which knows about GLib memory allocation and transfer) can "
+"perform better here, but Tartan is quite a young project and still misses things (a "
+"low true positive rate). It is recommended that code be put through a static "
+"analyzer, but the primary tool for detecting leaks should be runtime leak checking."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:924
msgid ""
-"Runtime leak checking is done using <link xref=\"tooling#valgrind"
-"\">Valgrind</link>, using its <link xref=\"tooling#memcheck\">memcheck</"
-"link> tool. Any leak it detects as ‘definitely losing memory’ should be "
-"fixed. Many of the leaks which ‘potentially’ lose memory are not real leaks, "
-"and should be added to the suppression file."
+"Runtime leak checking is done using <link xref=\"tooling#valgrind\">Valgrind</link>, "
+"using its <link xref=\"tooling#memcheck\">memcheck</link> tool. Any leak it detects "
+"as ‘definitely losing memory’ should be fixed. Many of the leaks which ‘potentially’ "
+"lose memory are not real leaks, and should be added to the suppression file."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:933
msgid ""
-"If compiling with a recent version of Clang or GCC, the <link xref="
-"\"tooling#address-sanitizer\">address sanitizer</link> can be enabled "
-"instead, and it will detect memory leaks and overflow problems at runtime, "
-"but without the difficulty of running Valgrind in the right environment. "
-"Note, however, that it is still a young tool, so may fail in some cases."
+"If compiling with a recent version of Clang or GCC, the <link xref=\"tooling#address-"
+"sanitizer\">address sanitizer</link> can be enabled instead, and it will detect "
+"memory leaks and overflow problems at runtime, but without the difficulty of running "
+"Valgrind in the right environment. Note, however, that it is still a young tool, so "
+"may fail in some cases."
msgstr ""
#. (itstool) path: section/p
#: C/memory-management.page:942
-msgid ""
-"See <link xref=\"tooling#valgrind\"/> for more information on using Valgrind."
+msgid "See <link xref=\"tooling#valgrind\"/> for more information on using Valgrind."
msgstr ""
+"Weitere Informationen zur Nutzung von Valgrind finden Sie in <link xref="
+"\"tooling#valgrind\"/>."
#. (itstool) path: credit/years
#: C/namespacing.page:12
@@ -6614,10 +6501,10 @@ msgstr "Namensräume"
#. (itstool) path: synopsis/p
#: C/namespacing.page:27
msgid ""
-"If a library is namespaced correctly, it can define types and methods in its "
-"API which have the same names as those in another library, and a program can "
-"use both without conflicts. This is achieved by prefixing all types and "
-"method names with a namespace unique to the library."
+"If a library is namespaced correctly, it can define types and methods in its API "
+"which have the same names as those in another library, and a program can use both "
+"without conflicts. This is achieved by prefixing all types and method names with a "
+"namespace unique to the library."
msgstr ""
#. (itstool) path: section/title
@@ -6628,69 +6515,63 @@ msgstr "GObject-APIs"
#. (itstool) path: section/p
#: C/namespacing.page:38
msgid ""
-"Consistent and complete namespacing of symbols (functions and types) and "
-"files is important for two key reasons:"
+"Consistent and complete namespacing of symbols (functions and types) and files is "
+"important for two key reasons:"
msgstr ""
#. (itstool) path: item/p
#: C/namespacing.page:43
msgid ""
-"Establishing a convention which means developers have to learn fewer symbol "
-"names to use the library — they can guess them reliably instead."
+"Establishing a convention which means developers have to learn fewer symbol names to "
+"use the library — they can guess them reliably instead."
msgstr ""
#. (itstool) path: item/p
#: C/namespacing.page:47
msgid ""
-"Ensuring symbols from two projects do not conflict if included in the same "
-"file."
+"Ensuring symbols from two projects do not conflict if included in the same file."
msgstr ""
#. (itstool) path: section/p
#: C/namespacing.page:53
msgid ""
-"The second point is important — imagine what would happen if every project "
-"exported a function called <code>create_object()</code>. The headers "
-"defining them could not be included in the same file, and even if that were "
-"overcome, the programmer would not know which project each function comes "
-"from. Namespacing eliminates these problems by using a unique, consistent "
-"prefix for every symbol and filename in a project, grouping symbols into "
-"their projects and separating them from others."
+"The second point is important — imagine what would happen if every project exported "
+"a function called <code>create_object()</code>. The headers defining them could not "
+"be included in the same file, and even if that were overcome, the programmer would "
+"not know which project each function comes from. Namespacing eliminates these "
+"problems by using a unique, consistent prefix for every symbol and filename in a "
+"project, grouping symbols into their projects and separating them from others."
msgstr ""
#. (itstool) path: section/p
#: C/namespacing.page:63
msgid ""
-"The conventions below should be used for namespacing all symbols. They are "
-"<link href=\"https://developer.gnome.org/gobject/stable/gtype-conventions.";
-"html\"> used in all GLib-based projects</link>, so should be familiar to a "
-"lot of developers:"
+"The conventions below should be used for namespacing all symbols. They are <link "
+"href=\"https://developer.gnome.org/gobject/stable/gtype-conventions.html\";> used in "
+"all GLib-based projects</link>, so should be familiar to a lot of developers:"
msgstr ""
#. (itstool) path: item/p
#: C/namespacing.page:70
msgid "Functions should use <code>lower_case_with_underscores</code>."
-msgstr ""
+msgstr "Funktionen sollten <code>kleinschreibung_mit_unterstrichen</code> verwenden."
#. (itstool) path: item/p
#: C/namespacing.page:73
msgid ""
-"Structures, types and objects should use <code>CamelCaseWithoutUnderscores</"
-"code>."
+"Structures, types and objects should use <code>CamelCaseWithoutUnderscores</code>."
msgstr ""
#. (itstool) path: item/p
#: C/namespacing.page:77
-msgid ""
-"Macros and constants should use <code>UPPER_CASE_WITH_UNDERSCORES</code>."
+msgid "Macros and constants should use <code>UPPER_CASE_WITH_UNDERSCORES</code>."
msgstr ""
#. (itstool) path: item/p
#: C/namespacing.page:81
msgid ""
"All symbols should be prefixed with a short (2–4 characters) version of the "
-"namespace. This is shortened purely for ease of typing, but should still be "
-"unique."
+"namespace. This is shortened purely for ease of typing, but should still be unique."
msgstr ""
#. (itstool) path: item/p
@@ -6701,59 +6582,57 @@ msgstr ""
#. (itstool) path: section/p
#: C/namespacing.page:91
msgid ""
-"Additionally, public headers should be included from a subdirectory, "
-"effectively namespacing the header files. For example, instead of "
-"<code>#include <abc.h></code>, a project should allow its users to use "
-"<code>#include <namespace/abc.h></code>."
+"Additionally, public headers should be included from a subdirectory, effectively "
+"namespacing the header files. For example, instead of <code>#include <abc.h></"
+"code>, a project should allow its users to use <code>#include <namespace/abc.h>"
+"</code>."
msgstr ""
#. (itstool) path: section/p
#: C/namespacing.page:98
msgid ""
-"Some projects namespace their headers within this subdirectory — for "
-"example, <code>#include <namespace/ns-abc.h></code> instead of "
-"<code>#include <namespace/abc.h></code>. This is redundant, but "
-"harmless."
+"Some projects namespace their headers within this subdirectory — for example, "
+"<code>#include <namespace/ns-abc.h></code> instead of <code>#include <"
+"namespace/abc.h></code>. This is redundant, but harmless."
msgstr ""
#. (itstool) path: section/p
#: C/namespacing.page:105
msgid ""
-"For example, for a project called ‘Walbottle’, the short namespace ‘Wbl’ "
-"would be chosen. If it has a ‘schema’ class and a ‘writer’ class, it would "
-"install headers:"
+"For example, for a project called ‘Walbottle’, the short namespace ‘Wbl’ would be "
+"chosen. If it has a ‘schema’ class and a ‘writer’ class, it would install headers:"
msgstr ""
#. (itstool) path: item/p
#: C/namespacing.page:111
msgid ""
-"<file><var>$(includedir)</var>/walbottle-<var>$API_MAJOR</var>/walbottle/"
-"schema.h</file>"
+"<file><var>$(includedir)</var>/walbottle-<var>$API_MAJOR</var>/walbottle/schema.h</"
+"file>"
msgstr ""
-"<file><var>$(includedir)</var>/walbottle-<var>$API_MAJOR</var>/walbottle/"
-"schema.h</file>"
+"<file><var>$(includedir)</var>/walbottle-<var>$API_MAJOR</var>/walbottle/schema.h</"
+"file>"
#. (itstool) path: item/p
#: C/namespacing.page:114
msgid ""
-"<file><var>$(includedir)</var>/walbottle-<var>$API_MAJOR</var>/walbottle/"
-"writer.h</file>"
+"<file><var>$(includedir)</var>/walbottle-<var>$API_MAJOR</var>/walbottle/writer.h</"
+"file>"
msgstr ""
-"<file><var>$(includedir)</var>/walbottle-<var>$API_MAJOR</var>/walbottle/"
-"writer.h</file>"
+"<file><var>$(includedir)</var>/walbottle-<var>$API_MAJOR</var>/walbottle/writer.h</"
+"file>"
#. (itstool) path: section/p
#: C/namespacing.page:119
msgid ""
-"(The use of <var>$API_MAJOR</var> above is for <link xref=\"parallel-"
-"installability\">parallel installability</link>.)"
+"(The use of <var>$API_MAJOR</var> above is for <link xref=\"parallel-installability"
+"\">parallel installability</link>.)"
msgstr ""
#. (itstool) path: section/p
#: C/namespacing.page:124
msgid ""
-"For the schema class, the following symbols would be exported (amongst "
-"others), following GObject conventions:"
+"For the schema class, the following symbols would be exported (amongst others), "
+"following GObject conventions:"
msgstr ""
#. (itstool) path: item/p
@@ -6814,10 +6693,10 @@ msgstr ""
#. (itstool) path: synopsis/p
#: C/parallel-installability.page:35
msgid ""
-"If two packages can be parallel installed, then they have no filenames in "
-"common, and people developing against the package always compile against the "
-"version they expected. This applies to daemons, utility programs and "
-"configuration files as it does to header files and library binaries."
+"If two packages can be parallel installed, then they have no filenames in common, "
+"and people developing against the package always compile against the version they "
+"expected. This applies to daemons, utility programs and configuration files as it "
+"does to header files and library binaries."
msgstr ""
#. (itstool) path: item/p
@@ -6835,17 +6714,16 @@ msgstr ""
#. (itstool) path: item/p
#: C/parallel-installability.page:51
msgid ""
-"Keep package version numbers separate from soname or libtool version "
-"numbers. Be clear which part of the package version number changes with the "
-"API. (<link xref=\"#version-numbers\"/>)"
+"Keep package version numbers separate from soname or libtool version numbers. Be "
+"clear which part of the package version number changes with the API. (<link xref="
+"\"#version-numbers\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/parallel-installability.page:57
msgid ""
-"Install C header files to <file><var>$(includedir)</var>/lib<var>library</"
-"var>-<var>version</var>/<var>library</var>/</file>. (<link xref=\"#header-"
-"files\"/>)"
+"Install C header files to <file><var>$(includedir)</var>/lib<var>library</var>-"
+"<var>version</var>/<var>library</var>/</file>. (<link xref=\"#header-files\"/>)"
msgstr ""
#. (itstool) path: item/p
@@ -6858,50 +6736,48 @@ msgstr ""
#. (itstool) path: item/p
#: C/parallel-installability.page:67
msgid ""
-"Install pkg-config files to <file><var>$(libdir)</var>/pkgconfig/"
-"<var>library</var>-<var>version</var>.pc</file>. (<link xref=\"#pkg-config\"/"
-">)"
+"Install pkg-config files to <file><var>$(libdir)</var>/pkgconfig/<var>library</var>-"
+"<var>version</var>.pc</file>. (<link xref=\"#pkg-config\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/parallel-installability.page:72
msgid ""
-"Make configuration files forwards and backwards compatible, or install them "
-"to <file><var>$(sysconfdir)</var>/<var>library</var>-<var>version</var>/</"
-"file>. (<link xref=\"#configuration-files\"/>)"
+"Make configuration files forwards and backwards compatible, or install them to "
+"<file><var>$(sysconfdir)</var>/<var>library</var>-<var>version</var>/</file>. (<link "
+"xref=\"#configuration-files\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/parallel-installability.page:78
msgid ""
-"Set <code>GETTEXT_PACKAGE</code> to <code><var>library</var>-<var>version</"
-"var></code>. (<link xref=\"#gettext\"/>)"
+"Set <code>GETTEXT_PACKAGE</code> to <code><var>library</var>-<var>version</var></"
+"code>. (<link xref=\"#gettext\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/parallel-installability.page:83
msgid ""
-"Include a version number in all D-Bus interface names, service names and "
-"object paths. For example: <code>org.domain.<var>Library</var><var>Version</"
-"var>.<var>Interface</var></code>, <code>org.domain.<var>Library</"
-"var><var>Version</var></code> and <code>/org/domain/<var>Library</"
-"var><var>Version</var>/</code>. (<link xref=\"#dbus\"/>)"
+"Include a version number in all D-Bus interface names, service names and object "
+"paths. For example: <code>org.domain.<var>Library</var><var>Version</var>."
+"<var>Interface</var></code>, <code>org.domain.<var>Library</var><var>Version</var></"
+"code> and <code>/org/domain/<var>Library</var><var>Version</var>/</code>. (<link "
+"xref=\"#dbus\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/parallel-installability.page:91
msgid ""
-"Install daemon binaries to <file><var>$(libexecdir)</var>/<var>library</var>-"
-"daemon-<var>version</var></file>. (<link xref=\"#programs\"/>)"
+"Install daemon binaries to <file><var>$(libexecdir)</var>/<var>library</var>-daemon-"
+"<var>version</var></file>. (<link xref=\"#programs\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/parallel-installability.page:96
msgid ""
-"Install utility binaries to <file><var>$(bindir)</var>/<var>library</var>-"
-"utility-<var>version</var></file> and install symbolic links to <file><var>"
-"$(bindir)</var>/<var>library</var>-utility</file>. (<link xref=\"#programs\"/"
-">)"
+"Install utility binaries to <file><var>$(bindir)</var>/<var>library</var>-utility-"
+"<var>version</var></file> and install symbolic links to <file><var>$(bindir)</var>/"
+"<var>library</var>-utility</file>. (<link xref=\"#programs\"/>)"
msgstr ""
#. (itstool) path: section/title
@@ -6912,46 +6788,44 @@ msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:108
msgid ""
-"All public libraries should be designed to be parallel installed to ease API "
-"breaks later in the life of the library. If a library is used by multiple "
-"projects, and wants to break API, either all of the projects must be ported "
-"to the new API in parallel, or some of them will no longer be installable at "
-"the same time as the others, due to depending on conflicting versions of "
-"this library."
+"All public libraries should be designed to be parallel installed to ease API breaks "
+"later in the life of the library. If a library is used by multiple projects, and "
+"wants to break API, either all of the projects must be ported to the new API in "
+"parallel, or some of them will no longer be installable at the same time as the "
+"others, due to depending on conflicting versions of this library."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:117
msgid ""
-"This is unmaintainable, and asking all the projects to port to a new API at "
-"the same time is hard to organize and demoralizing, as most API breaks do "
-"not bring large new features which would motivate porting."
+"This is unmaintainable, and asking all the projects to port to a new API at the same "
+"time is hard to organize and demoralizing, as most API breaks do not bring large new "
+"features which would motivate porting."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:123
msgid ""
-"The solution is to ensure that all libraries are parallel installable, "
-"allowing the old and new versions of the API to be installed and compiled "
-"against at the same time, without conflicts. Building in support for this "
-"kind of parallel installation is much easier to do at the start of a project "
-"than it is to do retroactively."
+"The solution is to ensure that all libraries are parallel installable, allowing the "
+"old and new versions of the API to be installed and compiled against at the same "
+"time, without conflicts. Building in support for this kind of parallel installation "
+"is much easier to do at the start of a project than it is to do retroactively."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:131
msgid ""
"This eliminates the ‘chicken and egg’ problem of porting a collection of "
-"applications from one version of a library to the next, and makes breaking "
-"API a lot simpler for library maintainers, which can allow for more rapid "
-"iteration and development of new features if they desire."
+"applications from one version of a library to the next, and makes breaking API a lot "
+"simpler for library maintainers, which can allow for more rapid iteration and "
+"development of new features if they desire."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:138
msgid ""
-"The alternative, and equally valid, solution is for the library to never "
-"break API — the approach taken by <code>libc</code>."
+"The alternative, and equally valid, solution is for the library to never break API — "
+"the approach taken by <code>libc</code>."
msgstr ""
#. (itstool) path: section/title
@@ -6962,18 +6836,19 @@ msgstr "Läsung"
#. (itstool) path: section/p
#: C/parallel-installability.page:147
msgid ""
-"The solution to the problem is essentially to rename the library, and in "
-"most cases the nicest way to do so is to include the version number in the "
-"path of every file it installs. This means multiple versions of the library "
-"can be installed at the same time."
+"The solution to the problem is essentially to rename the library, and in most cases "
+"the nicest way to do so is to include the version number in the path of every file "
+"it installs. This means multiple versions of the library can be installed at the "
+"same time."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:154
msgid ""
-"For example, say that library <code>Foo</code> traditionally installs these "
-"files:"
+"For example, say that library <code>Foo</code> traditionally installs these files:"
msgstr ""
+"Nehmen wir an, die Bibliothek <code>Foo</code> installiert traditionell diese "
+"Dateien:"
#. (itstool) path: item/p
#: C/parallel-installability.page:159 C/parallel-installability.page:284
@@ -7007,8 +6882,7 @@ msgstr "<file>/usr/bin/foo-utility</file>"
#. (itstool) path: section/p
#: C/parallel-installability.page:167
-msgid ""
-"You might modify <code>Foo</code> version 4 to install these files instead:"
+msgid "You might modify <code>Foo</code> version 4 to install these files instead:"
msgstr ""
#. (itstool) path: item/p
@@ -7044,7 +6918,7 @@ msgstr "<file>/usr/bin/foo-utility-4</file>"
#. (itstool) path: section/p
#: C/parallel-installability.page:180
msgid "It could then be parallel installed with version 5:"
-msgstr ""
+msgstr "Es kann dann parallel mit Version 5 installiert werden:"
#. (itstool) path: item/p
#: C/parallel-installability.page:184 C/parallel-installability.page:262
@@ -7079,11 +6953,11 @@ msgstr "<file>/usr/bin/foo-utility-5</file>"
#. (itstool) path: section/p
#: C/parallel-installability.page:192
msgid ""
-"This is easily supported using <link href=\"http://www.freedesktop.org/wiki/";
-"Software/pkg-config/\"> <cmd>pkg-config</cmd></link>: <file>foo-4.pc</file> "
-"would add <file>/usr/include/foo-4</file> to the include path and "
-"<file>libfoo-4.so</file> to the list of libraries to link; <file>foo-5.pc</"
-"file> would add <file>/usr/include/foo-5</file> and <file>libfoo-5.so</file>."
+"This is easily supported using <link href=\"http://www.freedesktop.org/wiki/Software/";
+"pkg-config/\"> <cmd>pkg-config</cmd></link>: <file>foo-4.pc</file> would add <file>/"
+"usr/include/foo-4</file> to the include path and <file>libfoo-4.so</file> to the "
+"list of libraries to link; <file>foo-5.pc</file> would add <file>/usr/include/foo-5</"
+"file> and <file>libfoo-5.so</file>."
msgstr ""
#. (itstool) path: section/title
@@ -7094,27 +6968,26 @@ msgstr "Versionsnummern"
#. (itstool) path: section/p
#: C/parallel-installability.page:206
msgid ""
-"The version number that goes in filenames is an <em>ABI/API</em> version. It "
-"should not be the full version number of your package — just the part which "
-"signifies an API break. If using the standard <code><var>major</var>."
-"<var>minor</var>.<var>micro</var></code> scheme for project versioning, the "
-"API version is typically the major version number."
+"The version number that goes in filenames is an <em>ABI/API</em> version. It should "
+"not be the full version number of your package — just the part which signifies an "
+"API break. If using the standard <code><var>major</var>.<var>minor</var>.<var>micro</"
+"var></code> scheme for project versioning, the API version is typically the major "
+"version number."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:214
msgid ""
-"Minor releases (typically where API is added but <em>not</em> changed or "
-"removed) and micro releases (typically bug fixes) do not affect <link xref="
-"\"api-stability\">API backwards compatibility</link> so do not require "
-"moving all the files."
+"Minor releases (typically where API is added but <em>not</em> changed or removed) "
+"and micro releases (typically bug fixes) do not affect <link xref=\"api-stability"
+"\">API backwards compatibility</link> so do not require moving all the files."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:221
msgid ""
-"The examples in the following sections assume that the API version and "
-"soname are exported from <file>configure.ac</file> using the following code:"
+"The examples in the following sections assume that the API version and soname are "
+"exported from <file>configure.ac</file> using the following code:"
msgstr ""
#. (itstool) path: listing/title
@@ -7124,8 +6997,7 @@ msgstr "API-Versionierung in Autoconf"
#. (itstool) path: listing/desc
#: C/parallel-installability.page:228
-msgid ""
-"Code to export the API version and soname from <file>configure.ac</file>"
+msgid "Code to export the API version and soname from <file>configure.ac</file>"
msgstr ""
#. (itstool) path: listing/code
@@ -7156,9 +7028,9 @@ msgstr "C-Kopfdateien"
#. (itstool) path: section/p
#: C/parallel-installability.page:251
msgid ""
-"Header files should always be installed in a versioned subdirectory that "
-"requires an <cmd>-I</cmd> flag to the C compiler. For example, if my header "
-"is <file>foo.h</file>, and applications do this:"
+"Header files should always be installed in a versioned subdirectory that requires an "
+"<cmd>-I</cmd> flag to the C compiler. For example, if my header is <file>foo.h</"
+"file>, and applications do this:"
msgstr ""
#. (itstool) path: section/code
@@ -7175,26 +7047,25 @@ msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:265
msgid ""
-"Applications should pass the flag <cmd>-I/usr/include/foo-4</cmd> or <cmd>-I/"
-"usr/include/foo-5</cmd> to the C compiler. Again, this is facilitated by "
-"using <cmd>pkg-config</cmd>."
+"Applications should pass the flag <cmd>-I/usr/include/foo-4</cmd> or <cmd>-I/usr/"
+"include/foo-5</cmd> to the C compiler. Again, this is facilitated by using <cmd>pkg-"
+"config</cmd>."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:271
msgid ""
-"Note the extra <file>foo/</file> subdirectory. This namespaces the <code "
-"mime=\"text/x-csrc\">#include</code> to avoid file naming collisions with "
-"other libraries. For example, if two different libraries install headers "
-"called <file>utils.h</file>, which one gets included when you use <code mime="
-"\"text/x-csrc\">#include <utils.h></code>?"
+"Note the extra <file>foo/</file> subdirectory. This namespaces the <code mime=\"text/"
+"x-csrc\">#include</code> to avoid file naming collisions with other libraries. For "
+"example, if two different libraries install headers called <file>utils.h</file>, "
+"which one gets included when you use <code mime=\"text/x-csrc\">#include <utils."
+"h></code>?"
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:279
msgid ""
-"There’s some temptation to keep one of the header files outside of any "
-"subdirectory:"
+"There’s some temptation to keep one of the header files outside of any subdirectory:"
msgstr ""
#. (itstool) path: item/p
@@ -7205,18 +7076,15 @@ msgstr "<file>/usr/include/foo-5/foo.h</file>"
#. (itstool) path: section/p
#: C/parallel-installability.page:288
msgid ""
-"The problem there is that users are always accidentally getting the wrong "
-"header, since <cmd>-I/usr/include</cmd> seems to find its way onto compile "
-"command lines with some regularity. If you must do this, at least add a "
-"check to the library that detects applications using the wrong header file "
-"when the library is initialized."
+"The problem there is that users are always accidentally getting the wrong header, "
+"since <cmd>-I/usr/include</cmd> seems to find its way onto compile command lines "
+"with some regularity. If you must do this, at least add a check to the library that "
+"detects applications using the wrong header file when the library is initialized."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:296
-msgid ""
-"Versioned header files can be installed from automake using the following "
-"code:"
+msgid "Versioned header files can be installed from automake using the following code:"
msgstr ""
#. (itstool) path: listing/title
@@ -7274,8 +7142,8 @@ msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:325
msgid ""
-"As well as correct versioning, all APIs in installed headers should be <link "
-"xref=\"namespacing\">namespaced correctly</link>."
+"As well as correct versioning, all APIs in installed headers should be <link xref="
+"\"namespacing\">namespaced correctly</link>."
msgstr ""
#. (itstool) path: section/title
@@ -7291,15 +7159,15 @@ msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:342
msgid ""
-"This allows applications to get exactly the one they want at compile time, "
-"and ensures that versions 4 and 5 have no files in common."
+"This allows applications to get exactly the one they want at compile time, and "
+"ensures that versions 4 and 5 have no files in common."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:347
msgid ""
-"Versioned libraries can be built and installed from automake using the "
-"following code:"
+"Versioned libraries can be built and installed from automake using the following "
+"code:"
msgstr ""
#. (itstool) path: listing/title
@@ -7309,8 +7177,7 @@ msgstr "Bibliotehken in Automake"
#. (itstool) path: listing/desc
#: C/parallel-installability.page:353
-msgid ""
-"Code to build and install versioned libraries from <file>Makefile.am</file>"
+msgid "Code to build and install versioned libraries from <file>Makefile.am</file>"
msgstr ""
#. (itstool) path: listing/code
@@ -7353,17 +7220,17 @@ msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:375
msgid ""
-"Library sonames (also known as libtool version numbers) only address the "
-"problem of runtime linking previously-compiled applications. They don’t "
-"address the issue of compiling applications that require a previous version, "
-"and they don’t address anything other than libraries."
+"Library sonames (also known as libtool version numbers) only address the problem of "
+"runtime linking previously-compiled applications. They don’t address the issue of "
+"compiling applications that require a previous version, and they don’t address "
+"anything other than libraries."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:382
msgid ""
-"For this reason, sonames should be used, but <em>in addition</em> to "
-"versioned names for libraries. The two solutions address different problems."
+"For this reason, sonames should be used, but <em>in addition</em> to versioned names "
+"for libraries. The two solutions address different problems."
msgstr ""
#. (itstool) path: section/title
@@ -7379,18 +7246,17 @@ msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:401
msgid ""
-"Since each pkg-config file contains versioned information about the library "
-"name and include paths, any project which depends on the library should be "
-"able to switch from one version to another simply by changing their pkg-"
-"config check from <file>foo-4</file> to <file>foo-5</file> (and doing any "
-"necessary API porting)."
+"Since each pkg-config file contains versioned information about the library name and "
+"include paths, any project which depends on the library should be able to switch "
+"from one version to another simply by changing their pkg-config check from "
+"<file>foo-4</file> to <file>foo-5</file> (and doing any necessary API porting)."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:409
msgid ""
-"Versioned pkg-config files can be installed from autoconf and automake using "
-"the following code:"
+"Versioned pkg-config files can be installed from autoconf and automake using the "
+"following code:"
msgstr ""
#. (itstool) path: listing/title
@@ -7401,8 +7267,8 @@ msgstr "pkg-config-Dateien in Autoconf und Automake"
#. (itstool) path: listing/desc
#: C/parallel-installability.page:415
msgid ""
-"Code to install versioned pkg-config files from <file>configure.ac</file> "
-"and <file>Makefile.am</file>"
+"Code to install versioned pkg-config files from <file>configure.ac</file> and "
+"<file>Makefile.am</file>"
msgstr ""
#. (itstool) path: listing/code
@@ -7440,19 +7306,18 @@ msgstr "Konfigurationsdateien"
#. (itstool) path: section/p
#: C/parallel-installability.page:438
msgid ""
-"From a user standpoint, the best approach to configuration files is to keep "
-"the format both <link xref=\"api-stability\">forward and backward "
-"compatible</link> (both library versions understand exactly the same "
-"configuration file syntax and semantics). Then the same configuration file "
-"can be used for all versions of the library, and no versioning is needed on "
-"the configuration file itself."
+"From a user standpoint, the best approach to configuration files is to keep the "
+"format both <link xref=\"api-stability\">forward and backward compatible</link> "
+"(both library versions understand exactly the same configuration file syntax and "
+"semantics). Then the same configuration file can be used for all versions of the "
+"library, and no versioning is needed on the configuration file itself."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:448
msgid ""
-"If you can’t do that, the configuration files should simply be renamed, and "
-"users will have to configure each version of the library separately."
+"If you can’t do that, the configuration files should simply be renamed, and users "
+"will have to configure each version of the library separately."
msgstr ""
#. (itstool) path: section/title
@@ -7463,11 +7328,11 @@ msgstr "Gettext-Übersetzungen"
#. (itstool) path: section/p
#: C/parallel-installability.page:457
msgid ""
-"If you use gettext for translations in combination with autoconf and "
-"automake, normally things are set up to install the translations to <file>/"
-"usr/share/locale/<var>lang</var>/LC_MESSAGES/<var>package</var></file>. "
-"You’ll need to change <var>package</var>. The convention used in GNOME is to "
-"put this in <file>configure.ac</file>:"
+"If you use gettext for translations in combination with autoconf and automake, "
+"normally things are set up to install the translations to <file>/usr/share/locale/"
+"<var>lang</var>/LC_MESSAGES/<var>package</var></file>. You’ll need to change "
+"<var>package</var>. The convention used in GNOME is to put this in <file>configure."
+"ac</file>:"
msgstr ""
#. (itstool) path: section/code
@@ -7478,13 +7343,16 @@ msgid ""
"AC_SUBST([GETTEXT_PACKAGE])\n"
"AC_DEFINE_UNQUOTED([GETTEXT_PACKAGE],[\"$GETTEXT_PACKAGE\"])"
msgstr ""
+"GETTEXT_PACKAGE=foo-4\n"
+"AC_SUBST([GETTEXT_PACKAGE])\n"
+"AC_DEFINE_UNQUOTED([GETTEXT_PACKAGE],[\"$GETTEXT_PACKAGE\"])"
#. (itstool) path: section/p
#: C/parallel-installability.page:469
msgid ""
-"Then use <code>GETTEXT_PACKAGE</code> as the package name to pass to <code "
-"mime=\"text/x-csrc\">bindtextdomain()</code>, <code mime=\"text/x-csrc"
-"\">textdomain()</code>, and <code mime=\"text/x-csrc\">dgettext()</code>."
+"Then use <code>GETTEXT_PACKAGE</code> as the package name to pass to <code mime="
+"\"text/x-csrc\">bindtextdomain()</code>, <code mime=\"text/x-csrc\">textdomain()</"
+"code>, and <code mime=\"text/x-csrc\">dgettext()</code>."
msgstr ""
#. (itstool) path: section/title
@@ -7495,18 +7363,18 @@ msgstr "D-Bus-Schnittstellen"
#. (itstool) path: section/p
#: C/parallel-installability.page:484
msgid ""
-"A D-Bus interface is another form of API, similar to a C API except that "
-"resolution of the version is done at runtime rather than compile time. "
-"Versioning D-Bus interfaces is otherwise no different to C APIs: version "
-"numbers must be included in interface names, service names and object paths."
+"A D-Bus interface is another form of API, similar to a C API except that resolution "
+"of the version is done at runtime rather than compile time. Versioning D-Bus "
+"interfaces is otherwise no different to C APIs: version numbers must be included in "
+"interface names, service names and object paths."
msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:492
msgid ""
-"For example, for a service <code>org.example.Foo</code> exposing interfaces "
-"<code>A</code> and <code>B</code> on objects <code>Controller</code> and "
-"<code>Client</code>, versions 4 and 5 of the D-Bus API would look like this:"
+"For example, for a service <code>org.example.Foo</code> exposing interfaces <code>A</"
+"code> and <code>B</code> on objects <code>Controller</code> and <code>Client</code>, "
+"versions 4 and 5 of the D-Bus API would look like this:"
msgstr ""
#. (itstool) path: list/title
@@ -7527,7 +7395,7 @@ msgstr "<code>org.example.Foo5</code>"
#. (itstool) path: list/title
#: C/parallel-installability.page:504
msgid "Interface Names"
-msgstr ""
+msgstr "Schnittstellennamen"
#. (itstool) path: item/p
#: C/parallel-installability.page:505
@@ -7582,9 +7450,9 @@ msgstr ""
#. (itstool) path: section/p
#: C/parallel-installability.page:529
msgid ""
-"Desktop applications generally do not need to be versioned, as they are not "
-"depended on by any other modules. Daemons and utility programs, however, "
-"interact with other parts of the system and hence need versioning."
+"Desktop applications generally do not need to be versioned, as they are not depended "
+"on by any other modules. Daemons and utility programs, however, interact with other "
+"parts of the system and hence need versioning."
msgstr ""
#. (itstool) path: section/p
@@ -7620,9 +7488,9 @@ msgstr "<file>/usr/bin/foo-lookup-utility-4</file>"
#. (itstool) path: section/p
#: C/parallel-installability.page:551
msgid ""
-"You may want to install a symbolic link from <file>/usr/bin/foo-lookup-"
-"utility</file> to the recommended versioned copy of the utility, to make it "
-"more convenient for users to use."
+"You may want to install a symbolic link from <file>/usr/bin/foo-lookup-utility</"
+"file> to the recommended versioned copy of the utility, to make it more convenient "
+"for users to use."
msgstr ""
#. (itstool) path: info/desc
@@ -7640,17 +7508,16 @@ msgstr ""
#: C/preconditions.page:26
msgid ""
"An important part of secure coding is ensuring that incorrect data does not "
-"propagate far through code — the further some malicious input can propagate, "
-"the more code it sees, and the greater potential there is for an exploit to "
-"be possible."
+"propagate far through code — the further some malicious input can propagate, the "
+"more code it sees, and the greater potential there is for an exploit to be possible."
msgstr ""
#. (itstool) path: section/p
#: C/preconditions.page:33
msgid ""
-"A standard way of preventing the propagation of invalid data is to check all "
-"inputs to, and outputs from, all publicly visible functions in a library or "
-"module. There are two levels of checking:"
+"A standard way of preventing the propagation of invalid data is to check all inputs "
+"to, and outputs from, all publicly visible functions in a library or module. There "
+"are two levels of checking:"
msgstr ""
#. (itstool) path: item/title
@@ -7662,9 +7529,7 @@ msgstr "Zusicherungen"
#. (itstool) path: item/p
#: C/preconditions.page:41
msgid "Check for programmer errors and abort the program on failure."
-msgstr ""
-"Auf Programmierfehler prüfen und das Programm im Problemfall abbrechen "
-"lassen."
+msgstr "Auf Programmierfehler prüfen und das Programm im Problemfall abbrechen lassen."
#. (itstool) path: item/title
#: C/preconditions.page:46
@@ -7679,49 +7544,47 @@ msgstr ""
#. (itstool) path: section/p
#: C/preconditions.page:53
msgid ""
-"Validation is a complex topic, and is handled using <link xref=\"gerror"
-"\">GErrors</link>. The remainder of this section discusses pre- and post-"
-"condition assertions, which are purely for catching programmer errors. A "
-"programmer error is where a function is called in a way which is documented "
-"as disallowed. For example, if <code>NULL</code> is passed to a parameter "
-"which is documented as requiring a non-<code>NULL</code> value to be passed; "
-"or if a negative value is passed to a function which requires a positive "
-"value. Programmer errors can happen on output too — for example, returning "
-"<code>NULL</code> when it is not documented to, or not setting a GError "
-"output when it fails."
+"Validation is a complex topic, and is handled using <link xref=\"gerror\">GErrors</"
+"link>. The remainder of this section discusses pre- and post-condition assertions, "
+"which are purely for catching programmer errors. A programmer error is where a "
+"function is called in a way which is documented as disallowed. For example, if "
+"<code>NULL</code> is passed to a parameter which is documented as requiring a non-"
+"<code>NULL</code> value to be passed; or if a negative value is passed to a function "
+"which requires a positive value. Programmer errors can happen on output too — for "
+"example, returning <code>NULL</code> when it is not documented to, or not setting a "
+"GError output when it fails."
msgstr ""
#. (itstool) path: section/p
#: C/preconditions.page:67
msgid ""
-"Adding pre- and post-condition assertions to code is as much about ensuring "
-"the behavior of each function is correctly and completely documented as it "
-"is about adding the assertions themselves. All assertions should be "
-"documented, preferably by using the relevant <link xref=\"introspection"
-"\">introspection annotations</link>, such as <code>(nullable)</code>."
+"Adding pre- and post-condition assertions to code is as much about ensuring the "
+"behavior of each function is correctly and completely documented as it is about "
+"adding the assertions themselves. All assertions should be documented, preferably by "
+"using the relevant <link xref=\"introspection\">introspection annotations</link>, "
+"such as <code>(nullable)</code>."
msgstr ""
#. (itstool) path: section/p
#: C/preconditions.page:76
msgid ""
-"Pre- and post-condition assertions are implemented using <link href="
-"\"https://developer.gnome.org/glib/stable/glib-Warnings-and-Assertions.";
-"html#g-return-if-fail\"><code>g_return_if_fail()</code></link> and <link "
-"href=\"https://developer.gnome.org/glib/stable/glib-Warnings-and-Assertions.";
-"html#g-return-val-if-fail\"><code>g_return_val_if_fail()</code></link>."
+"Pre- and post-condition assertions are implemented using <link href=\"https://";
+"developer.gnome.org/glib/stable/glib-Warnings-and-Assertions.html#g-return-if-fail"
+"\"><code>g_return_if_fail()</code></link> and <link href=\"https://developer.gnome.";
+"org/glib/stable/glib-Warnings-and-Assertions.html#g-return-val-if-fail"
+"\"><code>g_return_val_if_fail()</code></link>."
msgstr ""
#. (itstool) path: section/p
#: C/preconditions.page:83
msgid ""
-"The pre-conditions should check each parameter at the start of the function, "
-"before any other code is executed (even retrieving the private data "
-"structure from a GObject, for example, since the GObject pointer could be "
-"<code>NULL</code>). The post-conditions should check the return value and "
-"any output parameters at the end of the function — this requires a single "
-"<code>return</code> statement and use of <code>goto</code> to merge other "
-"control paths into it. See <link xref=\"memory-management#single-path-cleanup"
-"\"/> for an example."
+"The pre-conditions should check each parameter at the start of the function, before "
+"any other code is executed (even retrieving the private data structure from a "
+"GObject, for example, since the GObject pointer could be <code>NULL</code>). The "
+"post-conditions should check the return value and any output parameters at the end "
+"of the function — this requires a single <code>return</code> statement and use of "
+"<code>goto</code> to merge other control paths into it. See <link xref=\"memory-"
+"management#single-path-cleanup\"/> for an example."
msgstr ""
#. (itstool) path: info/desc
@@ -7737,18 +7600,15 @@ msgstr "Threading"
#. (itstool) path: item/p
#: C/threading.page:27
msgid ""
-"Do not use threads if at all possible. (<link xref=\"#when-to-use-threading"
-"\"/>)"
+"Do not use threads if at all possible. (<link xref=\"#when-to-use-threading\"/>)"
msgstr ""
-"Verwenden Sie, wenn möglich, keine Threads. (<link xref=\"#when-to-use-"
-"threading\"/>)"
+"Verwenden Sie, wenn möglich, keine Threads. (<link xref=\"#when-to-use-threading\"/>)"
#. (itstool) path: item/p
#: C/threading.page:31
msgid ""
-"If threads have to be used, use <code>GTask</code> or <code>GThreadPool</"
-"code> and isolate the threaded code as much as possible. (<link xref="
-"\"#using-threading\"/>)"
+"If threads have to be used, use <code>GTask</code> or <code>GThreadPool</code> and "
+"isolate the threaded code as much as possible. (<link xref=\"#using-threading\"/>)"
msgstr ""
"Wenn Threads notwendig sind, verwenden Sie <code>GTask</code> oder "
"<code>GThreadPool</code> und isolieren Sie den betreffenden Code so weit wie "
@@ -7764,9 +7624,9 @@ msgstr ""
#. (itstool) path: item/p
#: C/threading.page:42
msgid ""
-"Be careful about the <code>GMainContext</code> which code is executed in if "
-"using threads. Executing code in the wrong context can cause race "
-"conditions, or block the main loop. (<link xref=\"#using-threading\"/>)"
+"Be careful about the <code>GMainContext</code> which code is executed in if using "
+"threads. Executing code in the wrong context can cause race conditions, or block the "
+"main loop. (<link xref=\"#using-threading\"/>)"
msgstr ""
#. (itstool) path: section/title
@@ -7777,28 +7637,26 @@ msgstr "Anwendungsfälle für Threading"
#. (itstool) path: section/p
#: C/threading.page:54
msgid ""
-"When writing projects using GLib, the default approach should be to <em "
-"style=\"strong\">never use threads</em>. Instead, make proper use of the "
-"<link xref=\"main-contexts\">GLib main context</link> which, through the use "
-"of asynchronous operations, allows most blocking I/O operations to continue "
-"in the background while the main context continues to process other events. "
-"Analysis, review and debugging of threaded code becomes very hard, very "
-"quickly."
+"When writing projects using GLib, the default approach should be to <em style="
+"\"strong\">never use threads</em>. Instead, make proper use of the <link xref=\"main-"
+"contexts\">GLib main context</link> which, through the use of asynchronous "
+"operations, allows most blocking I/O operations to continue in the background while "
+"the main context continues to process other events. Analysis, review and debugging "
+"of threaded code becomes very hard, very quickly."
msgstr ""
#. (itstool) path: section/p
#: C/threading.page:64
msgid ""
-"Threading should only be necessary when using an external library which has "
-"blocking functions which need to be called from GLib code. If the library "
-"provides a non-blocking alternative, or one which integrates with a <link "
-"href=\"http://pubs.opengroup.org/onlinepubs/009695399/functions/poll.html";
-"\"><code>poll()</code></link> loop, that should be used in preference. If "
-"the blocking function really must be used, a thin wrapper should be written "
-"for it to convert it to the normal <link href=\"https://developer.gnome.org/";
-"gio/stable/GAsyncResult.html\"><code>GAsyncResult</code> style</link> of "
-"GLib asynchronous function, running the blocking operation in a worker "
-"thread."
+"Threading should only be necessary when using an external library which has blocking "
+"functions which need to be called from GLib code. If the library provides a non-"
+"blocking alternative, or one which integrates with a <link href=\"http://pubs.";
+"opengroup.org/onlinepubs/009695399/functions/poll.html\"><code>poll()</code></link> "
+"loop, that should be used in preference. If the blocking function really must be "
+"used, a thin wrapper should be written for it to convert it to the normal <link href="
+"\"https://developer.gnome.org/gio/stable/GAsyncResult.html\";><code>GAsyncResult</"
+"code> style</link> of GLib asynchronous function, running the blocking operation in "
+"a worker thread."
msgstr ""
#. (itstool) path: example/code
@@ -8025,12 +7883,11 @@ msgstr ""
#: C/threading.page:187
msgid ""
"See the <link href=\"https://developer.gnome.org/gio/stable/GAsyncResult.html";
-"\"><code>GAsyncResult</code> documentation</link> for more details. A simple "
-"way to implement the worker thread is to use <link href=\"https://developer.";
-"gnome.org/gio/stable/GTask.html\"><code>GTask</code></link> and <link href="
-"\"https://developer.gnome.org/gio/stable/GTask.html#g-task-run-in-thread";
-"\"><code>g_task_run_in_thread()</code></link>. (See also: <link xref=\"main-"
-"contexts#gtask\"/>.)"
+"\"><code>GAsyncResult</code> documentation</link> for more details. A simple way to "
+"implement the worker thread is to use <link href=\"https://developer.gnome.org/gio/";
+"stable/GTask.html\"><code>GTask</code></link> and <link href=\"https://developer.";
+"gnome.org/gio/stable/GTask.html#g-task-run-in-thread\"><code>g_task_run_in_thread()</"
+"code></link>. (See also: <link xref=\"main-contexts#gtask\"/>.)"
msgstr ""
#. (itstool) path: section/title
@@ -8041,68 +7898,64 @@ msgstr "Threading verwenden"
#. (itstool) path: section/p
#: C/threading.page:202
msgid ""
-"If <code>GTask</code> is not suitable for writing the worker thread, a more "
-"low-level approach must be used. This should be considered very carefully, "
-"as it is very easy to get threading code wrong in ways which will "
-"unpredictably cause bugs at runtime, cause deadlocks, or consume too many "
-"resources and terminate the program."
+"If <code>GTask</code> is not suitable for writing the worker thread, a more low-"
+"level approach must be used. This should be considered very carefully, as it is very "
+"easy to get threading code wrong in ways which will unpredictably cause bugs at "
+"runtime, cause deadlocks, or consume too many resources and terminate the program."
msgstr ""
#. (itstool) path: section/p
#: C/threading.page:210
msgid ""
-"A full manual on writing threaded code is beyond the scope of this document, "
-"but here are a number of guidelines to follow which should reduce the "
-"potential for bugs in threading code. The overriding principle is to reduce "
-"the amount of code and data which can be affected by threading — for "
-"example, reducing the number of threads, the complexity of worker thread "
-"implementation, and the amount of data shared between threads."
+"A full manual on writing threaded code is beyond the scope of this document, but "
+"here are a number of guidelines to follow which should reduce the potential for bugs "
+"in threading code. The overriding principle is to reduce the amount of code and data "
+"which can be affected by threading — for example, reducing the number of threads, "
+"the complexity of worker thread implementation, and the amount of data shared "
+"between threads."
msgstr ""
#. (itstool) path: item/p
#: C/threading.page:222
msgid ""
-"Use <link href=\"https://developer.gnome.org/glib/stable/glib-Thread-Pools.";
-"html\"><code>GThreadPool</code></link> instead of manually creating <link "
-"href=\"https://developer.gnome.org/glib/stable/glib-Threads.html";
-"\"><code>GThread</code>s</link> if possible. <code>GThreadPool</code> "
-"supports a work queue, limits on the number of spawned threads, and "
-"automatically joins finished threads so they are not leaked."
+"Use <link href=\"https://developer.gnome.org/glib/stable/glib-Thread-Pools.html";
+"\"><code>GThreadPool</code></link> instead of manually creating <link href=\"https://";
+"developer.gnome.org/glib/stable/glib-Threads.html\"><code>GThread</code>s</link> if "
+"possible. <code>GThreadPool</code> supports a work queue, limits on the number of "
+"spawned threads, and automatically joins finished threads so they are not leaked."
msgstr ""
#. (itstool) path: item/p
#: C/threading.page:232
msgid ""
-"If it is not possible to use a <code>GThreadPool</code> (which is rarely the "
-"case):"
+"If it is not possible to use a <code>GThreadPool</code> (which is rarely the case):"
msgstr ""
#. (itstool) path: item/p
#: C/threading.page:239
msgid ""
-"Use <link href=\"https://developer.gnome.org/glib/stable/glib-Threads.html#g-";
-"thread-try-new\"><code>g_thread_try_new()</code></link> to spawn threads, "
-"instead of <link href=\"https://developer.gnome.org/glib/stable/glib-Threads.";
-"html#g-thread-new\"><code>g_thread_new()</code></link>, so errors due to the "
-"system running out of threads can be handled gracefully rather than "
-"unconditionally aborting the program."
+"Use <link href=\"https://developer.gnome.org/glib/stable/glib-Threads.html#g-thread-";
+"try-new\"><code>g_thread_try_new()</code></link> to spawn threads, instead of <link "
+"href=\"https://developer.gnome.org/glib/stable/glib-Threads.html#g-thread-new";
+"\"><code>g_thread_new()</code></link>, so errors due to the system running out of "
+"threads can be handled gracefully rather than unconditionally aborting the program."
msgstr ""
#. (itstool) path: item/p
#: C/threading.page:248
msgid ""
-"Explicitly join threads using <link href=\"https://developer.gnome.org/glib/";
-"stable/glib-Threads.html#g-thread-join\"><code>g_thread_join()</code></link> "
-"to avoid leaking the thread resources."
+"Explicitly join threads using <link href=\"https://developer.gnome.org/glib/stable/";
+"glib-Threads.html#g-thread-join\"><code>g_thread_join()</code></link> to avoid "
+"leaking the thread resources."
msgstr ""
#. (itstool) path: item/p
#: C/threading.page:257
msgid ""
-"Use message passing to transfer data between threads, rather than manual "
-"locking with mutexes. <code>GThreadPool</code> explicitly supports this with "
-"<link href=\"https://developer.gnome.org/glib/stable/glib-Thread-Pools.";
-"html#g-thread-pool-push\"><code>g_thread_pool_push()</code></link>."
+"Use message passing to transfer data between threads, rather than manual locking "
+"with mutexes. <code>GThreadPool</code> explicitly supports this with <link href="
+"\"https://developer.gnome.org/glib/stable/glib-Thread-Pools.html#g-thread-pool-push";
+"\"><code>g_thread_pool_push()</code></link>."
msgstr ""
#. (itstool) path: item/p
@@ -8113,30 +7966,29 @@ msgstr ""
#. (itstool) path: item/p
#: C/threading.page:271
msgid ""
-"Isolate threading code as much as possible, keeping mutexes private within "
-"classes, and tightly bound to very specific class members."
+"Isolate threading code as much as possible, keeping mutexes private within classes, "
+"and tightly bound to very specific class members."
msgstr ""
#. (itstool) path: item/p
#: C/threading.page:278
msgid ""
-"All mutexes should be clearly commented beside their declaration, indicating "
-"which other structures or variables they protect access to. Similarly, those "
-"variables should be commented saying that they should <em>only</em> be "
-"accessed with that mutex held."
+"All mutexes should be clearly commented beside their declaration, indicating which "
+"other structures or variables they protect access to. Similarly, those variables "
+"should be commented saying that they should <em>only</em> be accessed with that "
+"mutex held."
msgstr ""
#. (itstool) path: item/p
#: C/threading.page:288
msgid ""
-"Be careful about interactions between main contexts and threads. For "
-"example, <link href=\"https://developer.gnome.org/glib/stable/glib-The-Main-";
-"Event-Loop.html#g-timeout-add-seconds\"><code>g_timeout_add_seconds()</"
-"code></link> adds a timeout <em>to be executed in the global default main "
-"context</em>, which is being run in the main thread, <em>not necessarily</"
-"em> the current thread. Getting this wrong can mean that work intended for a "
-"worker thread accidentally ends up being executed in the main thread anyway. "
-"(See also: <link xref=\"main-contexts#default-contexts\"/>.)"
+"Be careful about interactions between main contexts and threads. For example, <link "
+"href=\"https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html#g-";
+"timeout-add-seconds\"><code>g_timeout_add_seconds()</code></link> adds a timeout "
+"<em>to be executed in the global default main context</em>, which is being run in "
+"the main thread, <em>not necessarily</em> the current thread. Getting this wrong can "
+"mean that work intended for a worker thread accidentally ends up being executed in "
+"the main thread anyway. (See also: <link xref=\"main-contexts#default-contexts\"/>.)"
msgstr ""
#. (itstool) path: section/title
@@ -8147,16 +7999,16 @@ msgstr "Debugging"
#. (itstool) path: section/p
#: C/threading.page:306
msgid ""
-"Debugging threading issues is tricky, both because they are hard to "
-"reproduce, and because they are hard to reason about. This is one of the big "
-"reasons for avoiding using threads in the first place."
+"Debugging threading issues is tricky, both because they are hard to reproduce, and "
+"because they are hard to reason about. This is one of the big reasons for avoiding "
+"using threads in the first place."
msgstr ""
#. (itstool) path: section/p
#: C/threading.page:312
msgid ""
-"However, if a threading issue does arise, <link xref=\"tooling#helgrind-and-"
-"drd\">Valgrind’s drd and helgrind tools are useful</link>."
+"However, if a threading issue does arise, <link xref=\"tooling#helgrind-and-drd"
+"\">Valgrind’s drd and helgrind tools are useful</link>."
msgstr ""
#. (itstool) path: info/desc
@@ -8172,42 +8024,39 @@ msgstr ""
#. (itstool) path: page/p
#: C/tooling.page:22
msgid ""
-"Development tools are much more than just a text editor and a compiler. "
-"Correct use of the right tools can drastically ease debugging and tracking "
-"down of complex problems with memory allocation and system calls, amongst "
-"other things. Some of the most commonly used tools are described below; "
-"other tools exist for more specialized use cases, and should be used when "
-"appropriate."
+"Development tools are much more than just a text editor and a compiler. Correct use "
+"of the right tools can drastically ease debugging and tracking down of complex "
+"problems with memory allocation and system calls, amongst other things. Some of the "
+"most commonly used tools are described below; other tools exist for more specialized "
+"use cases, and should be used when appropriate."
msgstr ""
#. (itstool) path: page/p
#: C/tooling.page:31
msgid ""
-"An overarching principle to use when developing is to always have as many "
-"debugging options enabled as possible, rather than keeping them disabled "
-"until near release time. By constantly testing code with all available debug "
-"tooling, bugs can be caught early on, before they become ingrained in code "
-"and thus harder to remove."
+"An overarching principle to use when developing is to always have as many debugging "
+"options enabled as possible, rather than keeping them disabled until near release "
+"time. By constantly testing code with all available debug tooling, bugs can be "
+"caught early on, before they become ingrained in code and thus harder to remove."
msgstr ""
#. (itstool) path: page/p
#: C/tooling.page:39
msgid ""
-"Practically, this means having all compiler and other tool warnings enabled "
-"and set to fail the build process with an error if they are emitted."
+"Practically, this means having all compiler and other tool warnings enabled and set "
+"to fail the build process with an error if they are emitted."
msgstr ""
#. (itstool) path: item/p
#: C/tooling.page:48
-msgid ""
-"Compile frequently with a second compiler. (<link xref=\"#gcc-and-clang\"/>)"
+msgid "Compile frequently with a second compiler. (<link xref=\"#gcc-and-clang\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/tooling.page:52
msgid ""
-"Enable a large selection of compiler warnings and make them fatal. (<link "
-"xref=\"#gcc-and-clang\"/>)"
+"Enable a large selection of compiler warnings and make them fatal. (<link xref="
+"\"#gcc-and-clang\"/>)"
msgstr ""
#. (itstool) path: item/p
@@ -8218,36 +8067,35 @@ msgstr ""
#. (itstool) path: item/p
#: C/tooling.page:59
msgid ""
-"Use Valgrind to analyze memory usage, memory errors, cache and CPU "
-"performance and threading errors. (<link xref=\"#valgrind\"/>)"
+"Use Valgrind to analyze memory usage, memory errors, cache and CPU performance and "
+"threading errors. (<link xref=\"#valgrind\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/tooling.page:63
msgid ""
-"Use gcov and lcov to analyze unit test coverage. (<link xref=\"#gcov-and-lcov"
-"\"/>)"
+"Use gcov and lcov to analyze unit test coverage. (<link xref=\"#gcov-and-lcov\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/tooling.page:67
msgid ""
-"Use compiler sanitizers to analyze memory, thread and undefined behavior "
-"problems. (<link xref=\"#sanitizers\"/>)"
+"Use compiler sanitizers to analyze memory, thread and undefined behavior problems. "
+"(<link xref=\"#sanitizers\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/tooling.page:71
msgid ""
-"Submit to Coverity as a cronjob and eliminate static analysis errors as they "
-"appear. (<link xref=\"#coverity\"/>)"
+"Submit to Coverity as a cronjob and eliminate static analysis errors as they appear. "
+"(<link xref=\"#coverity\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/tooling.page:75
msgid ""
-"Use Clang static analyzer and Tartan regularly to eliminate statically "
-"analysable errors locally. (<link xref=\"#clang-static-analyzer\"/>)"
+"Use Clang static analyzer and Tartan regularly to eliminate statically analysable "
+"errors locally. (<link xref=\"#clang-static-analyzer\"/>)"
msgstr ""
#. (itstool) path: section/title
@@ -8258,58 +8106,54 @@ msgstr "GCC und Clang"
#. (itstool) path: section/p
#: C/tooling.page:85
msgid ""
-"<link href=\"https://gcc.gnu.org/onlinedocs/gcc/\";>GCC</link> is the "
-"standard C compiler for Linux. An alternative exists in the form of <link "
-"href=\"http://clang.llvm.org/docs/UsersManual.html\";>Clang</link>, with "
-"comparable functionality. Choose one (probably GCC) to use as a main "
-"compiler, but occasionally use the other to compile the code, as the two "
-"detect slightly different sets of errors and warnings in code. Clang also "
-"comes with a static analyzer tool which can be used to detect errors in code "
-"without compiling or running it; see <link xref=\"#clang-static-analyzer\"/>."
+"<link href=\"https://gcc.gnu.org/onlinedocs/gcc/\";>GCC</link> is the standard C "
+"compiler for Linux. An alternative exists in the form of <link href=\"http://clang.";
+"llvm.org/docs/UsersManual.html\">Clang</link>, with comparable functionality. Choose "
+"one (probably GCC) to use as a main compiler, but occasionally use the other to "
+"compile the code, as the two detect slightly different sets of errors and warnings "
+"in code. Clang also comes with a static analyzer tool which can be used to detect "
+"errors in code without compiling or running it; see <link xref=\"#clang-static-"
+"analyzer\"/>."
msgstr ""
#. (itstool) path: section/p
#: C/tooling.page:97
msgid ""
-"Both compilers should be used with as many warning flags enabled as "
-"possible. Although compiler warnings do occasionally provide false "
-"positives, most warnings legitimately point to problems in the code, and "
-"hence should be fixed rather than ignored. A development policy of enabling "
-"all warning flags and also specifying the <code>-Werror</code> flag (which "
-"makes all warnings fatal to compilation) promotes fixing warnings as soon as "
-"they are introduced. This helps code quality. The alternative of ignoring "
-"warnings leads to long debugging sessions to track down bugs caused by "
-"issues which would have been flagged up by the warnings. Similarly, ignoring "
-"warnings until the end of the development cycle, then spending a block of "
+"Both compilers should be used with as many warning flags enabled as possible. "
+"Although compiler warnings do occasionally provide false positives, most warnings "
+"legitimately point to problems in the code, and hence should be fixed rather than "
+"ignored. A development policy of enabling all warning flags and also specifying the "
+"<code>-Werror</code> flag (which makes all warnings fatal to compilation) promotes "
+"fixing warnings as soon as they are introduced. This helps code quality. The "
+"alternative of ignoring warnings leads to long debugging sessions to track down bugs "
+"caused by issues which would have been flagged up by the warnings. Similarly, "
+"ignoring warnings until the end of the development cycle, then spending a block of "
"time enabling and fixing them all wastes time."
msgstr ""
#. (itstool) path: section/p
#: C/tooling.page:112
msgid ""
-"Both GCC and Clang support a wide range of compiler flags, only some of "
-"which are related to modern, multi-purpose code (for example, others are "
-"outdated or architecture-specific). Finding a reasonable set of flags to "
-"enable can be tricky, and hence the <link href=\"http://www.gnu.org/software/";
-"autoconf-archive/ax_compiler_flags.html\"> <code>AX_COMPILER_FLAGS</code></"
-"link> macro exists."
+"Both GCC and Clang support a wide range of compiler flags, only some of which are "
+"related to modern, multi-purpose code (for example, others are outdated or "
+"architecture-specific). Finding a reasonable set of flags to enable can be tricky, "
+"and hence the <link href=\"http://www.gnu.org/software/autoconf-archive/";
+"ax_compiler_flags.html\"> <code>AX_COMPILER_FLAGS</code></link> macro exists."
msgstr ""
#. (itstool) path: section/p
#: C/tooling.page:121
msgid ""
-"<code>AX_COMPILER_FLAGS</code> enables a consistent set of compiler "
-"warnings, and also tests that the compiler supports each flag before "
-"enabling it. This accounts for differences in the set of flags supported by "
-"GCC and Clang. To use it, add <code>AX_COMPILER_FLAGS</code> to "
-"<file>configure.ac</file>. If you are using in-tree copies of autoconf-"
-"archive macros, copy <link href=\"http://git.savannah.gnu.org/gitweb/?";
-"p=autoconf-archive.git;a=blob_plain;f=m4/ax_compiler_flags.m4\"> "
-"<file>ax_compiler_flags.m4</file></link> to the <file>m4/</file> directory "
-"of your project. Note that it depends on the following autoconf-archive "
-"macros which are GPL-licenced so potentially cannot be copied in-tree. They "
-"may have to remain in autoconf-archive, with that as a build time dependency "
-"of the project:"
+"<code>AX_COMPILER_FLAGS</code> enables a consistent set of compiler warnings, and "
+"also tests that the compiler supports each flag before enabling it. This accounts "
+"for differences in the set of flags supported by GCC and Clang. To use it, add "
+"<code>AX_COMPILER_FLAGS</code> to <file>configure.ac</file>. If you are using in-"
+"tree copies of autoconf-archive macros, copy <link href=\"http://git.savannah.gnu.";
+"org/gitweb/?p=autoconf-archive.git;a=blob_plain;f=m4/ax_compiler_flags.m4\"> "
+"<file>ax_compiler_flags.m4</file></link> to the <file>m4/</file> directory of your "
+"project. Note that it depends on the following autoconf-archive macros which are GPL-"
+"licenced so potentially cannot be copied in-tree. They may have to remain in "
+"autoconf-archive, with that as a build time dependency of the project:"
msgstr ""
#. (itstool) path: item/p
@@ -8335,20 +8179,19 @@ msgstr "<code>ax_require_defined.m4</code>"
#. (itstool) path: section/p
#: C/tooling.page:142
msgid ""
-"<code>AX_COMPILER_FLAGS</code> supports disabling <code>-Werror</code> for "
-"release builds, so that releases may always be built against newer compilers "
-"which have introduced more warnings. Set its third parameter to ‘yes’ for "
-"release builds (and only release builds) to enable this functionality. "
-"Development and CI builds should always have <code>-Werror</code> enabled."
+"<code>AX_COMPILER_FLAGS</code> supports disabling <code>-Werror</code> for release "
+"builds, so that releases may always be built against newer compilers which have "
+"introduced more warnings. Set its third parameter to ‘yes’ for release builds (and "
+"only release builds) to enable this functionality. Development and CI builds should "
+"always have <code>-Werror</code> enabled."
msgstr ""
#. (itstool) path: section/p
#: C/tooling.page:151
msgid ""
-"Release builds can be detected using the <link href=\"http://www.gnu.org/";
-"software/autoconf-archive/ax_is_release.html\"><code>AX_IS_RELEASE</code></"
-"link> macro, the result of which can be passed directly to "
-"<code>AX_COMPILER_FLAGS</code>:"
+"Release builds can be detected using the <link href=\"http://www.gnu.org/software/";
+"autoconf-archive/ax_is_release.html\"><code>AX_IS_RELEASE</code></link> macro, the "
+"result of which can be passed directly to <code>AX_COMPILER_FLAGS</code>:"
msgstr ""
#. (itstool) path: section/code
@@ -8364,9 +8207,9 @@ msgstr ""
#. (itstool) path: section/p
#: C/tooling.page:160
msgid ""
-"The choice of release stability policy (the first argument to "
-"<code>AX_IS_RELEASE</code>) should be made per project, taking the project’s "
-"<link xref=\"versioning\">versioning stability</link> into account."
+"The choice of release stability policy (the first argument to <code>AX_IS_RELEASE</"
+"code>) should be made per project, taking the project’s <link xref=\"versioning"
+"\">versioning stability</link> into account."
msgstr ""
#. (itstool) path: section/title
@@ -8377,38 +8220,37 @@ msgstr "GDB"
#. (itstool) path: section/p
#: C/tooling.page:171
msgid ""
-"GDB is the standard debugger for C on Linux. Its most common uses are for "
-"debugging crashes, and for stepping through code as it executes. A full "
-"tutorial for using GDB is given <link href=\"https://sourceware.org/gdb/";
-"current/onlinedocs/gdb/\"> here</link>."
+"GDB is the standard debugger for C on Linux. Its most common uses are for debugging "
+"crashes, and for stepping through code as it executes. A full tutorial for using GDB "
+"is given <link href=\"https://sourceware.org/gdb/current/onlinedocs/gdb/\";> here</"
+"link>."
msgstr ""
#. (itstool) path: section/p
#: C/tooling.page:179
msgid ""
-"To run GDB on a program from within the source tree, use: <cmd>libtool exec "
-"gdb --args <var>./program-name</var> <var>--some --arguments --here</var></"
-"cmd>"
+"To run GDB on a program from within the source tree, use: <cmd>libtool exec gdb --"
+"args <var>./program-name</var> <var>--some --arguments --here</var></cmd>"
msgstr ""
#. (itstool) path: section/p
#: C/tooling.page:184
msgid ""
-"This is necessary due to libtool wrapping each compiled binary in the source "
-"tree in a shell script which sets up some libtool variables. It is not "
-"necessary for debugging installed executables."
+"This is necessary due to libtool wrapping each compiled binary in the source tree in "
+"a shell script which sets up some libtool variables. It is not necessary for "
+"debugging installed executables."
msgstr ""
#. (itstool) path: section/p
#: C/tooling.page:190
msgid ""
-"GDB has many advanced features which can be combined to essentially create "
-"small debugging scripts, triggered by different breakpoints in code. "
-"Sometimes this is a useful approach (for example, for <link href=\"https://";
-"tecnocode.co.uk/2010/07/12/reference-count-debugging-with-gdb/\"> reference "
-"count debugging</link>), but sometimes simply using <link href=\"https://";
-"developer.gnome.org/glib/stable/glib-Message-Logging.html#g-debug\"> "
-"<code>g_debug()</code></link> to output a debug message is simpler."
+"GDB has many advanced features which can be combined to essentially create small "
+"debugging scripts, triggered by different breakpoints in code. Sometimes this is a "
+"useful approach (for example, for <link href=\"https://tecnocode.co.uk/2010/07/12/";
+"reference-count-debugging-with-gdb/\"> reference count debugging</link>), but "
+"sometimes simply using <link href=\"https://developer.gnome.org/glib/stable/glib-";
+"Message-Logging.html#g-debug\"> <code>g_debug()</code></link> to output a debug "
+"message is simpler."
msgstr ""
#. (itstool) path: section/title
@@ -8419,75 +8261,78 @@ msgstr "Valgrind"
#. (itstool) path: section/p
#: C/tooling.page:204
msgid ""
-"Valgrind is a suite of tools for instrumenting and profiling programs. Its "
-"most famous tool is <link xref=\"#memcheck\">memcheck</link>, but it has "
-"several other powerful and useful tools too. They are covered separately in "
-"the sections below."
+"Valgrind is a suite of tools for instrumenting and profiling programs. Its most "
+"famous tool is <link xref=\"#memcheck\">memcheck</link>, but it has several other "
+"powerful and useful tools too. They are covered separately in the sections below."
msgstr ""
#. (itstool) path: section/p
#: C/tooling.page:211
msgid ""
"A useful way of running Valgrind is to run a program’s unit test suite under "
-"Valgrind, setting Valgrind to return a status code indicating the number of "
-"errors it encountered. When run as part of <cmd>make check</cmd>, this will "
-"cause the checks to succeed if Valgrind finds no problems, and fail "
-"otherwise. However, running <cmd>make check</cmd> under Valgrind is not "
-"trivial to do on the command line. A macro, <link href=\"http://www.gnu.org/";
-"software/autoconf-archive/ax_valgrind_check.html\"> <code>AX_VALGRIND_CHECK</"
-"code></link> can be used which adds a new <cmd>make check-valgrind</cmd> "
-"target to automate this. To use it:"
+"Valgrind, setting Valgrind to return a status code indicating the number of errors "
+"it encountered. When run as part of <cmd>make check</cmd>, this will cause the "
+"checks to succeed if Valgrind finds no problems, and fail otherwise. However, "
+"running <cmd>make check</cmd> under Valgrind is not trivial to do on the command "
+"line. A macro, <link href=\"http://www.gnu.org/software/autoconf-archive/";
+"ax_valgrind_check.html\"> <code>AX_VALGRIND_CHECK</code></link> can be used which "
+"adds a new <cmd>make check-valgrind</cmd> target to automate this. To use it:"
msgstr ""
#. (itstool) path: item/p
#: C/tooling.page:224
msgid ""
"Copy <link href=\"http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;";
-"a=blob_plain;f=m4/ax_valgrind_check.m4\"> <file>ax_valgrind_check.m4</file></"
-"link> to the <file>m4/</file> directory of your project."
+"a=blob_plain;f=m4/ax_valgrind_check.m4\"> <file>ax_valgrind_check.m4</file></link> "
+"to the <file>m4/</file> directory of your project."
msgstr ""
+"Kopieren Sie <link href=\"http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;";
+"a=blob_plain;f=m4/ax_valgrind_check.m4\"> <file>ax_valgrind_check.m4</file></link> "
+"in den Ordner <file>m4/</file> Ihres Projekts."
#. (itstool) path: item/p
#: C/tooling.page:230
msgid "Add <code>AX_VALGRIND_CHECK</code> to <file>configure.ac</file>."
-msgstr ""
+msgstr "Fügen Sie <code>AX_VALGRIND_CHECK</code> zu <file>configure.ac</file> hinzu."
#. (itstool) path: item/p
#: C/tooling.page:233
msgid ""
-"Add <code>@VALGRIND_CHECK_RULES</code> to the top-level <file>Makefile.am</"
-"file>."
+"Add <code>@VALGRIND_CHECK_RULES@</code> to the <file>Makefile.am</file> in each "
+"directory which contains unit tests."
msgstr ""
+"Fügen Sie <code>@VALGRIND_CHECK_RULES@</code> zur Datei <file>Makefile.am</file> in "
+"jedem Ordner hinzu, der Unit-Tests enthält."
#. (itstool) path: section/p
#: C/tooling.page:239
msgid ""
-"When <cmd>make check-valgrind</cmd> is run, it will save its results in "
-"<file>test-suite-*.log</file>, one log file per tool."
+"When <cmd>make check-valgrind</cmd> is run, it will save its results in <file>test-"
+"suite-*.log</file>, one log file per tool. Note that you will need to run it from "
+"the directory containing the unit tests."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:250
+#: C/tooling.page:251
msgid ""
"Valgrind has a way to suppress false positives, by using <link href=\"http://";
-"valgrind.org/docs/manual/manual-core.html#manual-core.suppress\"> "
-"suppression files</link>. These list patterns which may match error stack "
-"traces. If a stack trace from an error matches part of a suppression entry, "
-"it is not reported. For various reasons, GLib currently causes a number of "
-"false positives in <link xref=\"#memcheck\">memcheck</link> and <link xref="
-"\"#helgrind-and-drd\">helgrind and drd</link> which must be suppressed by "
-"default for Valgrind to be useful. For this reason, every project should use "
-"a standard GLib suppression file as well as a project specific one."
+"valgrind.org/docs/manual/manual-core.html#manual-core.suppress\"> suppression files</"
+"link>. These list patterns which may match error stack traces. If a stack trace from "
+"an error matches part of a suppression entry, it is not reported. For various "
+"reasons, GLib currently causes a number of false positives in <link xref=\"#memcheck"
+"\">memcheck</link> and <link xref=\"#helgrind-and-drd\">helgrind and drd</link> "
+"which must be suppressed by default for Valgrind to be useful. For this reason, "
+"every project should use a standard GLib suppression file as well as a project "
+"specific one."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:263
-msgid ""
-"Suppression files are supported by the <code>AX_VALGRIND_CHECK</code> macro:"
+#: C/tooling.page:264
+msgid "Suppression files are supported by the <code>AX_VALGRIND_CHECK</code> macro:"
msgstr ""
#. (itstool) path: section/code
-#: C/tooling.page:267
+#: C/tooling.page:268
#, no-wrap
msgid ""
"@VALGRIND_CHECK_RULES@\n"
@@ -8499,462 +8344,446 @@ msgstr ""
"EXTRA_DIST = $(VALGRIND_SUPPRESSIONS_FILES)"
#. (itstool) path: section/title
-#: C/tooling.page:272
+#: C/tooling.page:273
msgid "memcheck"
msgstr "memcheck"
#. (itstool) path: section/p
-#: C/tooling.page:274
+#: C/tooling.page:275
msgid ""
-"memcheck is a memory usage and allocation analyzer. It detects problems with "
-"memory accesses and modifications of the heap (allocations and frees). It is "
-"a highly robust and mature tool, and its output can be entirely trusted. If "
-"it says there is ‘definitely’ a memory leak, there is definitely a memory "
-"leak which should be fixed. If it says there is ‘potentially’ a memory leak, "
-"there may be a leak to be fixed, or it may be memory allocated at "
-"initialization time and used throughout the life of the program without "
-"needing to be freed."
+"memcheck is a memory usage and allocation analyzer. It detects problems with memory "
+"accesses and modifications of the heap (allocations and frees). It is a highly "
+"robust and mature tool, and its output can be entirely trusted. If it says there is "
+"‘definitely’ a memory leak, there is definitely a memory leak which should be fixed. "
+"If it says there is ‘potentially’ a memory leak, there may be a leak to be fixed, or "
+"it may be memory allocated at initialization time and used throughout the life of "
+"the program without needing to be freed."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:285
+#: C/tooling.page:286
msgid "To run memcheck manually on an installed program, use:"
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:288
+#: C/tooling.page:289
msgid ""
-"<cmd>valgrind --tool=memcheck --leak-check=full <var>my-program-name</var></"
-"cmd>"
+"<cmd>valgrind --tool=memcheck --leak-check=full <var>my-program-name</var></cmd>"
msgstr ""
-"<cmd>valgrind --tool=memcheck --leak-check=full <var>my-program-name</var></"
-"cmd>"
+"<cmd>valgrind --tool=memcheck --leak-check=full <var>my-program-name</var></cmd>"
#. (itstool) path: section/p
-#: C/tooling.page:292
+#: C/tooling.page:293
msgid ""
-"Or, if running your program from the source directory, use the following to "
-"avoid running leak checking on the libtool helper scripts:"
+"Or, if running your program from the source directory, use the following to avoid "
+"running leak checking on the libtool helper scripts:"
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:296
+#: C/tooling.page:297
msgid ""
-"<cmd>libtool exec valgrind --tool=memcheck --leak-check=full <var>./my-"
-"program-name</var></cmd>"
+"<cmd>libtool exec valgrind --tool=memcheck --leak-check=full <var>./my-program-name</"
+"var></cmd>"
msgstr ""
-"<cmd>libtool exec valgrind --tool=memcheck --leak-check=full <var>./my-"
-"program-name</var></cmd>"
+"<cmd>libtool exec valgrind --tool=memcheck --leak-check=full <var>./my-program-name</"
+"var></cmd>"
#. (itstool) path: section/p
-#: C/tooling.page:300
+#: C/tooling.page:301
msgid ""
-"Valgrind lists each memory problem it detects, along with a short backtrace "
-"(if you’ve compiled your program with debug symbols), allowing the cause of "
-"the memory error to be pinpointed and fixed."
+"Valgrind lists each memory problem it detects, along with a short backtrace (if "
+"you’ve compiled your program with debug symbols), allowing the cause of the memory "
+"error to be pinpointed and fixed."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:306
+#: C/tooling.page:307
msgid ""
-"A full tutorial on using memcheck is <link href=\"http://valgrind.org/docs/";
-"manual/mc-manual.html\">here</link>."
+"A full tutorial on using memcheck is <link href=\"http://valgrind.org/docs/manual/mc-";
+"manual.html\">here</link>."
msgstr ""
-"Ein vollständiges Tutorial zu Memcheck finden Sie <link href=\"http://";
-"valgrind.org/docs/manual/mc-manual.html\">hier</link>."
+"Ein vollständiges Tutorial zu Memcheck finden Sie <link href=\"http://valgrind.org/";
+"docs/manual/mc-manual.html\">hier</link>."
#. (itstool) path: section/title
-#: C/tooling.page:313
+#: C/tooling.page:314
msgid "cachegrind and KCacheGrind"
msgstr "cachegrind und KCacheGrind"
#. (itstool) path: section/p
-#: C/tooling.page:315
+#: C/tooling.page:316
msgid ""
-"cachegrind is a cache performance profiler which can also measure "
-"instruction execution, and hence is very useful for profiling general "
-"performance of a program. <link href=\"http://kcachegrind.sourceforge.net/";
-"html/Home.html\"> KCacheGrind</link> is a useful UI for it which allows "
-"visualization and exploration of the profiling data, and the two tools "
-"should rarely be used separately."
+"cachegrind is a cache performance profiler which can also measure instruction "
+"execution, and hence is very useful for profiling general performance of a program. "
+"<link href=\"http://kcachegrind.sourceforge.net/html/Home.html\";> KCacheGrind</link> "
+"is a useful UI for it which allows visualization and exploration of the profiling "
+"data, and the two tools should rarely be used separately."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:325
+#: C/tooling.page:326
msgid ""
-"cachegrind works by simulating the processor’s memory hierarchy, so there "
-"are situations where it is <link href=\"http://valgrind.org/docs/manual/cg-";
-"manual.html#cg-manual.annopts.accuracy\"> not perfectly accurate</link>. "
-"However, its results are always representative enough to be very useful in "
-"debugging performance hotspots."
+"cachegrind works by simulating the processor’s memory hierarchy, so there are "
+"situations where it is <link href=\"http://valgrind.org/docs/manual/cg-manual.";
+"html#cg-manual.annopts.accuracy\"> not perfectly accurate</link>. However, its "
+"results are always representative enough to be very useful in debugging performance "
+"hotspots."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:334
+#: C/tooling.page:335
msgid ""
-"A full tutorial on using cachegrind is <link href=\"http://valgrind.org/docs/";
-"manual/cg-manual.html\">here</link>."
+"A full tutorial on using cachegrind is <link href=\"http://valgrind.org/docs/manual/";
+"cg-manual.html\">here</link>."
msgstr ""
-"Ein vollständiges Tutorial zu Cachegrind finden Sie <link href=\"http://";
-"valgrind.org/docs/manual/cg-manual.html\">hier</link>."
+"Ein vollständiges Tutorial zu Cachegrind finden Sie <link href=\"http://valgrind.org/";
+"docs/manual/cg-manual.html\">hier</link>."
#. (itstool) path: section/title
-#: C/tooling.page:341
+#: C/tooling.page:342
msgid "helgrind and drd"
msgstr "helgrind und drd"
#. (itstool) path: section/p
-#: C/tooling.page:343
+#: C/tooling.page:344
msgid ""
-"helgrind and drd are threading error detectors, checking for race conditions "
-"in memory accesses, and abuses of the <link href=\"http://pubs.opengroup.org/";
-"onlinepubs/9699919799/basedefs/pthread.h.html\"> POSIX pthreads API</link>. "
-"They are similar tools, but are implemented using different techniques, so "
-"both should be used."
+"helgrind and drd are threading error detectors, checking for race conditions in "
+"memory accesses, and abuses of the <link href=\"http://pubs.opengroup.org/";
+"onlinepubs/9699919799/basedefs/pthread.h.html\"> POSIX pthreads API</link>. They are "
+"similar tools, but are implemented using different techniques, so both should be "
+"used."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:351
+#: C/tooling.page:352
msgid ""
-"The kinds of errors detected by helgrind and drd are: data accessed from "
-"multiple threads without consistent locking, changes in lock acquisition "
-"order, freeing a mutex while it is locked, locking a locked mutex, unlocking "
-"an unlocked mutex, and several other errors. Each error, when detected, is "
-"printed to the console in a little report, with a separate report giving the "
-"allocation or spawning details of the mutexes or threads involved so that "
-"their definitions can be found."
+"The kinds of errors detected by helgrind and drd are: data accessed from multiple "
+"threads without consistent locking, changes in lock acquisition order, freeing a "
+"mutex while it is locked, locking a locked mutex, unlocking an unlocked mutex, and "
+"several other errors. Each error, when detected, is printed to the console in a "
+"little report, with a separate report giving the allocation or spawning details of "
+"the mutexes or threads involved so that their definitions can be found."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:361
+#: C/tooling.page:362
msgid ""
-"helgrind and drd can produce more false positives than memcheck or "
-"cachegrind, so their output should be studied a little more carefully. "
-"However, threading problems are notoriously elusive even to experienced "
-"programmers, so helgrind and drd errors should not be dismissed lightly."
+"helgrind and drd can produce more false positives than memcheck or cachegrind, so "
+"their output should be studied a little more carefully. However, threading problems "
+"are notoriously elusive even to experienced programmers, so helgrind and drd errors "
+"should not be dismissed lightly."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:368
+#: C/tooling.page:369
msgid ""
-"Full tutorials on using helgrind and drd are <link href=\"http://valgrind.";
-"org/docs/manual/hg-manual.html\">here</link> and <link href=\"http://";
-"valgrind.org/docs/manual/drd-manual.html\"> here</link>."
+"Full tutorials on using helgrind and drd are <link href=\"http://valgrind.org/docs/";
+"manual/hg-manual.html\">here</link> and <link href=\"http://valgrind.org/docs/manual/";
+"drd-manual.html\"> here</link>."
msgstr ""
-"Vollständiges Tutorials zu Helgrind und drd finden Sie <link href=\"http://";
-"valgrind.org/docs/manual/hg-manual.html\">hier</link> und <link href="
-"\"http://valgrind.org/docs/manual/drd-manual.html\";> hier</link>."
+"Vollständiges Tutorials zu Helgrind und drd finden Sie <link href=\"http://valgrind.";
+"org/docs/manual/hg-manual.html\">hier</link> und <link href=\"http://valgrind.org/";
+"docs/manual/drd-manual.html\"> hier</link>."
#. (itstool) path: section/title
-#: C/tooling.page:377
+#: C/tooling.page:378
msgid "sgcheck"
msgstr "sgcheck"
#. (itstool) path: section/p
-#: C/tooling.page:379
+#: C/tooling.page:380
msgid ""
-"sgcheck is an array bounds checker, which detects accesses to arrays which "
-"have overstepped the length of the array. However, it is a very young tool, "
-"still marked as experimental, and hence may produce more false positives "
-"than other tools."
+"sgcheck is an array bounds checker, which detects accesses to arrays which have "
+"overstepped the length of the array. However, it is a very young tool, still marked "
+"as experimental, and hence may produce more false positives than other tools."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:386
+#: C/tooling.page:387
msgid ""
-"As it is experimental, sgcheck must be run by passing <cmd>--tool=exp-"
-"sgcheck</cmd> to Valgrind, rather than <cmd>--tool=sgcheck</cmd>."
+"As it is experimental, sgcheck must be run by passing <cmd>--tool=exp-sgcheck</cmd> "
+"to Valgrind, rather than <cmd>--tool=sgcheck</cmd>."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:392
+#: C/tooling.page:393
msgid ""
-"A full tutorial on using sgcheck is <link href=\"http://valgrind.org/docs/";
-"manual/sg-manual.html\">here</link>."
+"A full tutorial on using sgcheck is <link href=\"http://valgrind.org/docs/manual/sg-";
+"manual.html\">here</link>."
msgstr ""
-"Ein vollständiges Tutorial zu sgcheck finden Sie <link href=\"http://";
-"valgrind.org/docs/manual/sg-manual.html\">hier</link>."
+"Ein vollständiges Tutorial zu sgcheck finden Sie <link href=\"http://valgrind.org/";
+"docs/manual/sg-manual.html\">hier</link>."
#. (itstool) path: section/title
-#: C/tooling.page:400
+#: C/tooling.page:401
msgid "gcov and lcov"
msgstr "gcov und lcov"
#. (itstool) path: section/p
-#: C/tooling.page:402
+#: C/tooling.page:403
msgid ""
"<link href=\"https://gcc.gnu.org/onlinedocs/gcc/Gcov.html\";>gcov</link> is a "
-"profiling tool built into GCC, which instruments code by adding extra "
-"instructions at compile time. When the program is run, this code generates "
-"<file>.gcda</file> and <file>.gcno</file> profiling output files. These "
-"files can be analyzed by the <cmd>lcov</cmd> tool, which generates visual "
-"reports of code coverage at runtime, highlighting lines of code in the "
-"project which are run more than others."
+"profiling tool built into GCC, which instruments code by adding extra instructions "
+"at compile time. When the program is run, this code generates <file>.gcda</file> and "
+"<file>.gcno</file> profiling output files. These files can be analyzed by the "
+"<cmd>lcov</cmd> tool, which generates visual reports of code coverage at runtime, "
+"highlighting lines of code in the project which are run more than others."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:412
+#: C/tooling.page:413
msgid ""
-"A critical use for this code coverage data collection is when running the "
-"unit tests: if the amount of code covered (for example, which particular "
-"lines were run) by the unit tests is known, it can be used to guide further "
-"expansion of the unit tests. By regularly checking the code coverage "
-"attained by the unit tests, and expanding them towards 100%, you can be sure "
-"that the entire project is being tested. Often it is the case that a unit "
-"test exercises most of the code, but not a particular control flow path, "
-"which then harbours residual bugs."
+"A critical use for this code coverage data collection is when running the unit "
+"tests: if the amount of code covered (for example, which particular lines were run) "
+"by the unit tests is known, it can be used to guide further expansion of the unit "
+"tests. By regularly checking the code coverage attained by the unit tests, and "
+"expanding them towards 100%, you can be sure that the entire project is being "
+"tested. Often it is the case that a unit test exercises most of the code, but not a "
+"particular control flow path, which then harbours residual bugs."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:423
+#: C/tooling.page:424
msgid ""
"lcov supports <link href=\"http://en.wikipedia.org/wiki/";
-"Code_coverage#Basic_coverage_criteria\"> branch coverage measurement</link>, "
-"so is not suitable for demonstrating coverage of safety critical code. It is "
-"perfectly suitable for non-safety critical code."
+"Code_coverage#Basic_coverage_criteria\"> branch coverage measurement</link>, so is "
+"not suitable for demonstrating coverage of safety critical code. It is perfectly "
+"suitable for non-safety critical code."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:431
+#: C/tooling.page:432
msgid ""
-"As code coverage has to be enabled at both compile time and run time, a "
-"macro is provided to make things simpler. The <link href=\"http://www.gnu.";
-"org/software/autoconf-archive/ax_code_coverage.html\"> "
-"<code>AX_CODE_COVERAGE</code></link> macro adds a <cmd>make check-code-"
-"coverage</cmd> target to the build system, which runs the unit tests with "
-"code coverage enabled, and generates a report using <cmd>lcov</cmd>."
+"As code coverage has to be enabled at both compile time and run time, a macro is "
+"provided to make things simpler. The <link href=\"http://www.gnu.org/software/";
+"autoconf-archive/ax_code_coverage.html\"> <code>AX_CODE_COVERAGE</code></link> macro "
+"adds a <cmd>make check-code-coverage</cmd> target to the build system, which runs "
+"the unit tests with code coverage enabled, and generates a report using <cmd>lcov</"
+"cmd>."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:441
+#: C/tooling.page:442
msgid "To add <code>AX_CODE_COVERAGE</code> support to a project:"
msgstr ""
-"So fügen Sie Unterstützung für <code>AX_CODE_COVERAGE</code> zu einem "
-"Projekt hinzu:"
+"So fügen Sie Unterstützung für <code>AX_CODE_COVERAGE</code> zu einem Projekt hinzu:"
#. (itstool) path: item/p
-#: C/tooling.page:445
+#: C/tooling.page:446
msgid ""
"Copy <link href=\"http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;";
-"a=blob_plain;f=m4/ax_code_coverage.m4\"> <file>ax_code_coverage.m4</file></"
-"link> to the <file>m4/</file> directory of your project."
+"a=blob_plain;f=m4/ax_code_coverage.m4\"> <file>ax_code_coverage.m4</file></link> to "
+"the <file>m4/</file> directory of your project."
msgstr ""
-"Kopieren Sie <link href=\"http://git.savannah.gnu.org/gitweb/?p=autoconf-";
-"archive.git;a=blob_plain;f=m4/ax_code_coverage.m4\"> <file>ax_code_coverage."
-"m4</file></link> in den <file>m4/</file>-Ordner Ihres Projekts."
+"Kopieren Sie <link href=\"http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;";
+"a=blob_plain;f=m4/ax_code_coverage.m4\"> <file>ax_code_coverage.m4</file></link> in "
+"den <file>m4/</file>-Ordner Ihres Projekts."
#. (itstool) path: item/p
-#: C/tooling.page:451
+#: C/tooling.page:452
msgid "Add <code>AX_CODE_COVERAGE</code> to <file>configure.ac</file>."
-msgstr ""
-"Fügen Sie <code>AX_CODE_COVERAGE</code> zu <file>configure.ac</file> hinzu."
+msgstr "Fügen Sie <code>AX_CODE_COVERAGE</code> zu <file>configure.ac</file> hinzu."
#. (itstool) path: item/p
-#: C/tooling.page:454
+#: C/tooling.page:455
msgid ""
-"Add <code>@CODE_COVERAGE_RULES</code> to the top-level <file>Makefile.am</"
-"file>."
+"Add <code>@CODE_COVERAGE_RULES</code> to the top-level <file>Makefile.am</file>."
msgstr ""
-"Fügen Sie <code>@CODE_COVERAGE_RULES</code> zur Datei <file>Makefile.am</"
-"file> der obersten Ebene hinzu."
+"Fügen Sie <code>@CODE_COVERAGE_RULES</code> zur Datei <file>Makefile.am</file> der "
+"obersten Ebene hinzu."
#. (itstool) path: item/p
-#: C/tooling.page:458
+#: C/tooling.page:459
msgid ""
-"Add <code>$(CODE_COVERAGE_CFLAGS)</code> to the automake <code><var>*</"
-"var>_CFLAGS</code> variable for each target you want coverage for, for "
-"example for all libraries but no unit test code. Do the same for <code>"
-"$(CODE_COVERAGE_LDFLAGS)</code> and <code><var>*</var>_LDFLAGS</code>."
+"Add <code>$(CODE_COVERAGE_CFLAGS)</code> to the automake <code><var>*</var>_CFLAGS</"
+"code> variable for each target you want coverage for, for example for all libraries "
+"but no unit test code. Do the same for <code>$(CODE_COVERAGE_LDFLAGS)</code> and "
+"<code><var>*</var>_LDFLAGS</code>."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:467
+#: C/tooling.page:468
msgid ""
-"Documentation on using gcov and lcov is <link href=\"http://ltp.sourceforge.";
-"net/coverage/lcov.php\">here</link>."
+"Documentation on using gcov and lcov is <link href=\"http://ltp.sourceforge.net/";
+"coverage/lcov.php\">here</link>."
msgstr ""
-"Dokumentation zur Verwendung von gcov und lcov finden Sie <link href="
-"\"http://ltp.sourceforge.net/coverage/lcov.php\";>hier</link>."
+"Dokumentation zur Verwendung von gcov und lcov finden Sie <link href=\"http://ltp.";
+"sourceforge.net/coverage/lcov.php\">hier</link>."
#. (itstool) path: section/title
-#: C/tooling.page:474
+#: C/tooling.page:475
msgid "Address, Thread and Undefined Behavior Sanitizers"
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:476
+#: C/tooling.page:477
msgid ""
-"GCC and Clang both support several sanitizers: sets of extra code and checks "
-"which can be optionally compiled in to an application and used to flag "
-"various incorrect behaviors at runtime. They are powerful tools, but have to "
-"be enabled specially, recompiling your application to enable and disable "
-"them. They cannot be enabled at the same time as each other, or used at the "
-"same time as <link xref=\"#valgrind\">Valgrind</link>. They are still young, "
-"so have little integration with other tooling."
+"GCC and Clang both support several sanitizers: sets of extra code and checks which "
+"can be optionally compiled in to an application and used to flag various incorrect "
+"behaviors at runtime. They are powerful tools, but have to be enabled specially, "
+"recompiling your application to enable and disable them. They cannot be enabled at "
+"the same time as each other, or used at the same time as <link xref=\"#valgrind"
+"\">Valgrind</link>. They are still young, so have little integration with other "
+"tooling."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:486
+#: C/tooling.page:487
msgid ""
-"All sanitizers are available for both GCC and Clang, accepting the same set "
-"of compiler options."
+"All sanitizers are available for both GCC and Clang, accepting the same set of "
+"compiler options."
msgstr ""
#. (itstool) path: section/title
-#: C/tooling.page:499
+#: C/tooling.page:500
msgid "Address Sanitizer"
msgstr "Address Sanitizer"
#. (itstool) path: section/p
-#: C/tooling.page:501
+#: C/tooling.page:502
msgid ""
-"The <link href=\"https://code.google.com/p/address-sanitizer/\";>address "
-"sanitizer</link> (‘asan’) detects use-after-free and buffer overflow bugs in "
-"C and C++ programs. A full tutorial on using asan is <link href=\"http://";
-"clang.llvm.org/docs/AddressSanitizer.html#usage\">available for Clang</link> "
-"— the same instructions should work for GCC."
+"The <link href=\"https://code.google.com/p/address-sanitizer/\";>address sanitizer</"
+"link> (‘asan’) detects use-after-free and buffer overflow bugs in C and C++ "
+"programs. A full tutorial on using asan is <link href=\"http://clang.llvm.org/docs/";
+"AddressSanitizer.html#usage\">available for Clang</link> — the same instructions "
+"should work for GCC."
msgstr ""
#. (itstool) path: section/title
-#: C/tooling.page:511
+#: C/tooling.page:512
msgid "Thread Sanitizer"
msgstr "Thread Sanitizer"
#. (itstool) path: section/p
-#: C/tooling.page:513
+#: C/tooling.page:514
msgid ""
-"The <link href=\"https://code.google.com/p/thread-sanitizer/\";>thread "
-"sanitizer</link> (‘tsan’) detects data races on memory locations, plus a "
-"variety of invalid uses of POSIX threading APIs. A full tutorial on using "
-"tsan is <link href=\"http://clang.llvm.org/docs/ThreadSanitizer.html#usage";
-"\">available for Clang</link> — the same instructions should work for GCC."
+"The <link href=\"https://code.google.com/p/thread-sanitizer/\";>thread sanitizer</"
+"link> (‘tsan’) detects data races on memory locations, plus a variety of invalid "
+"uses of POSIX threading APIs. A full tutorial on using tsan is <link href=\"http://";
+"clang.llvm.org/docs/ThreadSanitizer.html#usage\">available for Clang</link> — the "
+"same instructions should work for GCC."
msgstr ""
#. (itstool) path: section/title
-#: C/tooling.page:524
+#: C/tooling.page:525
msgid "Undefined Behavior Sanitizer"
msgstr "Undefined Behavior Sanitizer"
#. (itstool) path: section/p
-#: C/tooling.page:526
+#: C/tooling.page:527
msgid ""
"The undefined behavior sanitizer (‘ubsan’) is a collection of smaller "
-"instrumentations which detect various potentially undefined behaviors in C "
-"programs. A set of instructions for enabling ubsan is <link href=\"http://";
-"clang.llvm.org/docs/UsersManual.html#controlling-code-generation\">available "
-"for Clang</link> — the same instructions should work for GCC."
+"instrumentations which detect various potentially undefined behaviors in C programs. "
+"A set of instructions for enabling ubsan is <link href=\"http://clang.llvm.org/docs/";
+"UsersManual.html#controlling-code-generation\">available for Clang</link> — the same "
+"instructions should work for GCC."
msgstr ""
#. (itstool) path: section/title
-#: C/tooling.page:537
+#: C/tooling.page:538
msgid "Coverity"
msgstr "Coverity"
#. (itstool) path: section/p
-#: C/tooling.page:539
+#: C/tooling.page:540
msgid ""
-"<link href=\"http://scan.coverity.com/\";>Coverity</link> is one of the most "
-"popular and biggest commercial static analyzer tools available. However, it "
-"is available to use free for Open Source projects, and any project is "
-"encouraged to <link href=\"https://scan.coverity.com/users/sign_up\";>sign "
-"up</link>. <link href=\"https://scan.coverity.com/faq#how-get-project-";
-"included-in-scan\"> Analysis is performed</link> by running some analysis "
-"tools locally, then uploading the source code and results as a tarball to "
-"Coverity’s site. The results are then visible online to members of the "
-"project, as annotations on the project’s source code (similarly to how lcov "
-"presents its results)."
+"<link href=\"http://scan.coverity.com/\";>Coverity</link> is one of the most popular "
+"and biggest commercial static analyzer tools available. However, it is available to "
+"use free for Open Source projects, and any project is encouraged to <link href="
+"\"https://scan.coverity.com/users/sign_up\";>sign up</link>. <link href=\"https://";
+"scan.coverity.com/faq#how-get-project-included-in-scan\"> Analysis is performed</"
+"link> by running some analysis tools locally, then uploading the source code and "
+"results as a tarball to Coverity’s site. The results are then visible online to "
+"members of the project, as annotations on the project’s source code (similarly to "
+"how lcov presents its results)."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:552
+#: C/tooling.page:553
msgid ""
-"As Coverity cannot be run entirely locally, it cannot be integrated properly "
-"into the build system. However, scripts do exist to automatically scan a "
-"project and upload the tarball to Coverity regularly. The recommended "
-"approach is to run these scripts regularly on a server (typically as a "
-"cronjob), using a clean checkout of the project’s git repository. Coverity "
-"automatically e-mails project members about new static analysis problems it "
-"finds, so the same approach as for <link xref=\"#gcc-and-clang\">compiler "
-"warnings</link> can be taken: eliminate all the static analysis warnings, "
-"then eliminate new ones as they are detected."
+"As Coverity cannot be run entirely locally, it cannot be integrated properly into "
+"the build system. However, scripts do exist to automatically scan a project and "
+"upload the tarball to Coverity regularly. The recommended approach is to run these "
+"scripts regularly on a server (typically as a cronjob), using a clean checkout of "
+"the project’s git repository. Coverity automatically e-mails project members about "
+"new static analysis problems it finds, so the same approach as for <link xref=\"#gcc-"
+"and-clang\">compiler warnings</link> can be taken: eliminate all the static analysis "
+"warnings, then eliminate new ones as they are detected."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:565
+#: C/tooling.page:566
msgid ""
-"Coverity is good, but it is not perfect, and it does produce a number of "
-"false positives. These should be marked as ignored in the online interface."
+"Coverity is good, but it is not perfect, and it does produce a number of false "
+"positives. These should be marked as ignored in the online interface."
msgstr ""
#. (itstool) path: section/title
-#: C/tooling.page:573
+#: C/tooling.page:574
msgid "Clang Static Analyzer"
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:575
+#: C/tooling.page:576
msgid ""
-"One tool which can be used to perform static analysis locally is the <link "
-"href=\"http://clang-analyzer.llvm.org/\";>Clang static analyzer</link>, which "
-"is a tool co-developed with the <link xref=\"#gcc-and-clang\">Clang "
-"compiler</link>. It detects a variety of problems in C code which compilers "
-"cannot, and which would otherwise only be detectable at run time (using unit "
-"tests)."
+"One tool which can be used to perform static analysis locally is the <link href="
+"\"http://clang-analyzer.llvm.org/\";>Clang static analyzer</link>, which is a tool co-"
+"developed with the <link xref=\"#gcc-and-clang\">Clang compiler</link>. It detects a "
+"variety of problems in C code which compilers cannot, and which would otherwise only "
+"be detectable at run time (using unit tests)."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:584
+#: C/tooling.page:585
msgid ""
-"Clang produces some false positives, and there is no easy way to ignore "
-"them. The recommended thing to do is to <link href=\"http://clang-analyzer.";
-"llvm.org/faq.html#suppress_issue\">file a bug report against the static "
-"analyzer</link>, so that the false positive can be fixed in future."
+"Clang produces some false positives, and there is no easy way to ignore them. The "
+"recommended thing to do is to <link href=\"http://clang-analyzer.llvm.org/faq.";
+"html#suppress_issue\">file a bug report against the static analyzer</link>, so that "
+"the false positive can be fixed in future."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:592
+#: C/tooling.page:593
msgid ""
-"A full tutorial on using Clang is <link href=\"http://clang-analyzer.llvm.";
-"org/scan-build.html\">here</link>."
+"A full tutorial on using Clang is <link href=\"http://clang-analyzer.llvm.org/scan-";
+"build.html\">here</link>."
msgstr ""
-"Ein vollständiges Tutorial zu Clang finden Sie <link href=\"http://clang-";
-"analyzer.llvm.org/scan-build.html\">hier</link>."
+"Ein vollständiges Tutorial zu Clang finden Sie <link href=\"http://clang-analyzer.";
+"llvm.org/scan-build.html\">hier</link>."
#. (itstool) path: section/title
-#: C/tooling.page:598
+#: C/tooling.page:599
msgid "Tartan"
msgstr "Tartan"
#. (itstool) path: section/p
-#: C/tooling.page:600
+#: C/tooling.page:601
msgid ""
-"However, for all the power of the Clang static analyzer, it cannot detect "
-"problems with specific libraries, such as GLib. This is a problem if a "
-"project uses GLib exclusively, and rarely uses POSIX APIs (which Clang does "
-"understand). There is a plugin available for the Clang static analyzer, "
-"called <link href=\"http://people.collabora.com/~pwith/tartan/\";>Tartan</"
-"link>, which extends Clang to support checks against some of the common GLib "
-"APIs."
+"However, for all the power of the Clang static analyzer, it cannot detect problems "
+"with specific libraries, such as GLib. This is a problem if a project uses GLib "
+"exclusively, and rarely uses POSIX APIs (which Clang does understand). There is a "
+"plugin available for the Clang static analyzer, called <link href=\"http://people.";
+"collabora.com/~pwith/tartan/\">Tartan</link>, which extends Clang to support checks "
+"against some of the common GLib APIs."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:611
+#: C/tooling.page:612
msgid ""
-"Tartan is still young software, and will produce false positives and may "
-"crash when run on some code. However, it can find legitimate bugs quite "
-"quickly, and is worth running over a code base frequently to detect new "
-"errors in the use of GLib in the code. Please <link href=\"http://people.";
-"collabora.com/~pwith/tartan/#troubleshooting\"> report any problems with "
-"Tartan</link>."
+"Tartan is still young software, and will produce false positives and may crash when "
+"run on some code. However, it can find legitimate bugs quite quickly, and is worth "
+"running over a code base frequently to detect new errors in the use of GLib in the "
+"code. Please <link href=\"http://people.collabora.com/~pwith/tartan/#troubleshooting";
+"\"> report any problems with Tartan</link>."
msgstr ""
#. (itstool) path: section/p
-#: C/tooling.page:620
+#: C/tooling.page:621
msgid ""
-"A full tutorial on enabling Tartan for use with the Clang static analyzer is "
-"<link href=\"http://people.collabora.com/~pwith/tartan/#usage-standalone\";> "
-"here</link>. If set up correctly, the output from Tartan will be mixed "
-"together with the normal static analyzer output."
+"A full tutorial on enabling Tartan for use with the Clang static analyzer is <link "
+"href=\"http://people.collabora.com/~pwith/tartan/#usage-standalone\";> here</link>. "
+"If set up correctly, the output from Tartan will be mixed together with the normal "
+"static analyzer output."
msgstr ""
#. (itstool) path: info/desc
@@ -8970,52 +8799,52 @@ msgstr ""
#. (itstool) path: synopsis/p
#: C/unit-testing.page:25
msgid ""
-"Unit testing should be the primary method of testing the bulk of code "
-"written, because a unit test can be written once and run many times — manual "
-"tests have to be planned once and then manually run each time."
+"Unit testing should be the primary method of testing the bulk of code written, "
+"because a unit test can be written once and run many times — manual tests have to be "
+"planned once and then manually run each time."
msgstr ""
#. (itstool) path: synopsis/p
#: C/unit-testing.page:31
msgid ""
-"Development of unit tests starts with the architecture and API design of the "
-"code to be tested: code should be designed to be easily testable, or will "
-"potentially be very difficult to test."
+"Development of unit tests starts with the architecture and API design of the code to "
+"be tested: code should be designed to be easily testable, or will potentially be "
+"very difficult to test."
msgstr ""
#. (itstool) path: item/p
#: C/unit-testing.page:38
msgid ""
-"Write unit tests to be as small as possible, but no smaller. (<link xref="
-"\"#writing-unit-tests\"/>)"
+"Write unit tests to be as small as possible, but no smaller. (<link xref=\"#writing-"
+"unit-tests\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/unit-testing.page:42
msgid ""
-"Use code coverage tools to write tests to get high code coverage. (<link "
-"xref=\"#writing-unit-tests\"/>)"
+"Use code coverage tools to write tests to get high code coverage. (<link xref="
+"\"#writing-unit-tests\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/unit-testing.page:46
msgid ""
-"Run all unit tests under Valgrind to check for leaks and other problems. "
-"(<link xref=\"#leak-checking\"/>)"
+"Run all unit tests under Valgrind to check for leaks and other problems. (<link xref="
+"\"#leak-checking\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/unit-testing.page:50
msgid ""
-"Use appropriate tools to automatically generate unit tests where possible. "
-"(<link xref=\"#test-generation\"/>)"
+"Use appropriate tools to automatically generate unit tests where possible. (<link "
+"xref=\"#test-generation\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/unit-testing.page:54
msgid ""
-"Design code to be testable from the beginning. (<link xref=\"#writing-"
-"testable-code\"/>)"
+"Design code to be testable from the beginning. (<link xref=\"#writing-testable-code"
+"\"/>)"
msgstr ""
#. (itstool) path: section/title
@@ -9027,40 +8856,37 @@ msgstr ""
#: C/unit-testing.page:64
msgid ""
"Unit tests should be written in conjunction with looking at <link xref="
-"\"tooling#gcov-and-lcov\">code coverage information gained from running the "
-"tests</link>. This typically means writing an initial set of unit tests, "
-"running them to get coverage data, then reworking and expanding them to "
-"increase the code coverage levels. Coverage should be increased first by "
-"ensuring all functions are covered (at least in part), and then by ensuring "
-"all lines of code are covered. By covering functions first, API problems "
-"which will prevent effective testing can be found quickly. These typically "
-"manifest as internal functions which cannot easily be called from unit "
-"tests. Overall, coverage levels of over 90% should be aimed for; don’t just "
-"test cases covered by project requirements, test everything."
+"\"tooling#gcov-and-lcov\">code coverage information gained from running the tests</"
+"link>. This typically means writing an initial set of unit tests, running them to "
+"get coverage data, then reworking and expanding them to increase the code coverage "
+"levels. Coverage should be increased first by ensuring all functions are covered (at "
+"least in part), and then by ensuring all lines of code are covered. By covering "
+"functions first, API problems which will prevent effective testing can be found "
+"quickly. These typically manifest as internal functions which cannot easily be "
+"called from unit tests. Overall, coverage levels of over 90% should be aimed for; "
+"don’t just test cases covered by project requirements, test everything."
msgstr ""
#. (itstool) path: section/p
#: C/unit-testing.page:79
msgid ""
-"Like <link xref=\"version-control\">git commits</link>, each unit test "
-"should be ‘as small as possible, but no smaller’, testing a single specific "
-"API or behavior. Each test case must be able to be run individually, without "
-"depending on state from other test cases. This is important to allow "
-"debugging of a single failing test, without having to step through all the "
-"other test code as well. It also means that a single test failure can easily "
-"be traced back to a specific API, rather than a generic ‘unit tests failed "
-"somewhere’ message."
+"Like <link xref=\"version-control\">git commits</link>, each unit test should be ‘as "
+"small as possible, but no smaller’, testing a single specific API or behavior. Each "
+"test case must be able to be run individually, without depending on state from other "
+"test cases. This is important to allow debugging of a single failing test, without "
+"having to step through all the other test code as well. It also means that a single "
+"test failure can easily be traced back to a specific API, rather than a generic "
+"‘unit tests failed somewhere’ message."
msgstr ""
#. (itstool) path: section/p
#: C/unit-testing.page:90
msgid ""
-"GLib has support for unit testing with its <link href=\"https://developer.";
-"gnome.org/glib/stable/glib-Testing.html\">GTest framework</link>, allowing "
-"tests to be arranged in groups and hierarchies. This means that groups of "
-"related tests can be run together for enhanced debugging too, by running the "
-"test binary with the <cmd>-p</cmd> argument: <cmd>./test-suite-name -p /path/"
-"to/test/group</cmd>."
+"GLib has support for unit testing with its <link href=\"https://developer.gnome.org/";
+"glib/stable/glib-Testing.html\">GTest framework</link>, allowing tests to be "
+"arranged in groups and hierarchies. This means that groups of related tests can be "
+"run together for enhanced debugging too, by running the test binary with the <cmd>-"
+"p</cmd> argument: <cmd>./test-suite-name -p /path/to/test/group</cmd>."
msgstr ""
#. (itstool) path: section/title
@@ -9071,25 +8897,24 @@ msgstr "Installierte Tests"
#. (itstool) path: section/p
#: C/unit-testing.page:103
msgid ""
-"All unit tests should be installed system-wide, following the <link href="
-"\"https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests\";>installed-"
-"tests standard</link>."
+"All unit tests should be installed system-wide, following the <link href=\"https://";
+"wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests\">installed-tests standard</"
+"link>."
msgstr ""
#. (itstool) path: section/p
#: C/unit-testing.page:109
msgid ""
-"By installing the unit tests, continuous integration (CI) is made easier, "
-"since tests for one project can be re-run after changes to other projects in "
-"the CI environment, thus testing the interfaces between modules. That is "
-"useful for a highly-coupled set of projects like GNOME."
+"By installing the unit tests, continuous integration (CI) is made easier, since "
+"tests for one project can be re-run after changes to other projects in the CI "
+"environment, thus testing the interfaces between modules. That is useful for a "
+"highly-coupled set of projects like GNOME."
msgstr ""
#. (itstool) path: section/p
#: C/unit-testing.page:116
msgid ""
-"To add support for installed-tests, add the following to <file>configure.ac</"
-"file>:"
+"To add support for installed-tests, add the following to <file>configure.ac</file>:"
msgstr ""
#. (itstool) path: section/code
@@ -9205,23 +9030,21 @@ msgstr ""
#. (itstool) path: section/p
#: C/unit-testing.page:173
msgid ""
-"Once unit tests with high code coverage have been written, they can be run "
-"under various dynamic analysis tools, such as <link xref=\"tooling#valgrind"
-"\">Valgrind</link> to check for leaks, threading errors, allocation "
-"problems, etc. across the entire code base. The higher the code coverage of "
-"the unit tests, the more confidence the Valgrind results can be treated "
-"with. See <link xref=\"tooling\"/> for more information, including build "
-"system integration instructions."
+"Once unit tests with high code coverage have been written, they can be run under "
+"various dynamic analysis tools, such as <link xref=\"tooling#valgrind\">Valgrind</"
+"link> to check for leaks, threading errors, allocation problems, etc. across the "
+"entire code base. The higher the code coverage of the unit tests, the more "
+"confidence the Valgrind results can be treated with. See <link xref=\"tooling\"/> "
+"for more information, including build system integration instructions."
msgstr ""
#. (itstool) path: section/p
#: C/unit-testing.page:183
msgid ""
-"Critically, this means that unit tests should not leak memory or other "
-"resources themselves, and similarly should not have any threading problems. "
-"Any such problems would effectively be false positives in the analysis of "
-"the actual project code. (False positives which need to be fixed by fixing "
-"the unit tests.)"
+"Critically, this means that unit tests should not leak memory or other resources "
+"themselves, and similarly should not have any threading problems. Any such problems "
+"would effectively be false positives in the analysis of the actual project code. "
+"(False positives which need to be fixed by fixing the unit tests.)"
msgstr ""
#. (itstool) path: section/title
@@ -9232,12 +9055,11 @@ msgstr ""
#. (itstool) path: section/p
#: C/unit-testing.page:195
msgid ""
-"Certain types of code are quite repetitive, and require a lot of unit tests "
-"to gain good coverage; but are appropriate for <link href=\"http://en.";
-"wikipedia.org/wiki/Test_data_generation\">test data generation</link>, where "
-"a tool is used to automatically generate test vectors for the code. This can "
-"drastically reduce the time needed for writing unit tests, for code in these "
-"specific domains."
+"Certain types of code are quite repetitive, and require a lot of unit tests to gain "
+"good coverage; but are appropriate for <link href=\"http://en.wikipedia.org/wiki/";
+"Test_data_generation\">test data generation</link>, where a tool is used to "
+"automatically generate test vectors for the code. This can drastically reduce the "
+"time needed for writing unit tests, for code in these specific domains."
msgstr ""
#. (itstool) path: section/title
@@ -9248,20 +9070,19 @@ msgstr "JSON"
#. (itstool) path: section/p
#: C/unit-testing.page:207
msgid ""
-"One example of a domain amenable to test data generation is parsing, where "
-"the data to be parsed is required to follow a strict schema — this is the "
-"case for XML and JSON documents. For JSON, a tool such as <link href="
-"\"http://people.collabora.com/~pwith/walbottle/\";>Walbottle</link> can be "
-"used to generate test vectors for all types of valid and invalid input "
-"according to the schema."
+"One example of a domain amenable to test data generation is parsing, where the data "
+"to be parsed is required to follow a strict schema — this is the case for XML and "
+"JSON documents. For JSON, a tool such as <link href=\"http://people.collabora.com/";
+"~pwith/walbottle/\">Walbottle</link> can be used to generate test vectors for all "
+"types of valid and invalid input according to the schema."
msgstr ""
#. (itstool) path: section/p
#: C/unit-testing.page:216
msgid ""
-"Every type of JSON document should have a <link href=\"http://json-schema.";
-"org/\">JSON Schema</link> defined for it, which can then be passed to "
-"Walbottle to generate test vectors:"
+"Every type of JSON document should have a <link href=\"http://json-schema.org/";
+"\">JSON Schema</link> defined for it, which can then be passed to Walbottle to "
+"generate test vectors:"
msgstr ""
#. (itstool) path: section/code
@@ -9279,9 +9100,9 @@ msgstr ""
#. (itstool) path: section/p
#: C/unit-testing.page:225
msgid ""
-"These test vectors can then be passed to the code under test in its unit "
-"tests. The JSON instances generated by <cmd>--valid-only</cmd> should be "
-"accepted; those from <cmd>--invalid-only</cmd> should be rejected."
+"These test vectors can then be passed to the code under test in its unit tests. The "
+"JSON instances generated by <cmd>--valid-only</cmd> should be accepted; those from "
+"<cmd>--invalid-only</cmd> should be rejected."
msgstr ""
#. (itstool) path: section/title
@@ -9292,31 +9113,29 @@ msgstr ""
#. (itstool) path: section/p
#: C/unit-testing.page:236
msgid ""
-"Code should be written with testability in mind from the design stage, as it "
-"affects API design and architecture in fundamental ways. A few key "
-"principles:"
+"Code should be written with testability in mind from the design stage, as it affects "
+"API design and architecture in fundamental ways. A few key principles:"
msgstr ""
#. (itstool) path: item/p
#: C/unit-testing.page:242
msgid ""
-"Do not use global state. Singleton objects are usually a bad idea as they "
-"can’t be instantiated separately or controlled in the unit tests."
+"Do not use global state. Singleton objects are usually a bad idea as they can’t be "
+"instantiated separately or controlled in the unit tests."
msgstr ""
#. (itstool) path: item/p
#: C/unit-testing.page:246
msgid ""
-"Separate out use of external state, such as databases, networking, or the "
-"file system. The unit tests can then replace the accesses to external state "
-"with mocked objects. A common approach to this is to use dependency "
-"injection to pass a file system wrapper object to the code under test. For "
-"example, a class should not load a global database (from a fixed location in "
-"the file system) because the unit tests would then potentially overwrite the "
-"running system’s copy of the database, and could never be executed in "
-"parallel. They should be passed an object which provides an interface to the "
-"database: in a production system, this would be a thin wrapper around the "
-"database API; for testing, it would be a mock object which checks the "
+"Separate out use of external state, such as databases, networking, or the file "
+"system. The unit tests can then replace the accesses to external state with mocked "
+"objects. A common approach to this is to use dependency injection to pass a file "
+"system wrapper object to the code under test. For example, a class should not load a "
+"global database (from a fixed location in the file system) because the unit tests "
+"would then potentially overwrite the running system’s copy of the database, and "
+"could never be executed in parallel. They should be passed an object which provides "
+"an interface to the database: in a production system, this would be a thin wrapper "
+"around the database API; for testing, it would be a mock object which checks the "
"requests given to it and returns hard-coded responses for various tests."
msgstr ""
@@ -9328,9 +9147,9 @@ msgstr ""
#. (itstool) path: item/p
#: C/unit-testing.page:263
msgid ""
-"Split projects up into collections of small, private libraries which are "
-"then linked together with a minimal amount of glue code into the overall "
-"executable. Each can be tested separately."
+"Split projects up into collections of small, private libraries which are then linked "
+"together with a minimal amount of glue code into the overall executable. Each can be "
+"tested separately."
msgstr ""
#. (itstool) path: section/p
@@ -9341,11 +9160,11 @@ msgstr ""
#. (itstool) path: item/p
#: C/unit-testing.page:278
msgid ""
-"<link href=\"http://msdn.microsoft.com/en-us/magazine/dd263069.aspx\";>Design "
-"for testability</link>"
+"<link href=\"http://msdn.microsoft.com/en-us/magazine/dd263069.aspx\";>Design for "
+"testability</link>"
msgstr ""
-"<link href=\"http://msdn.microsoft.com/en-us/magazine/dd263069.aspx\";>Design "
-"for testability</link>"
+"<link href=\"http://msdn.microsoft.com/en-us/magazine/dd263069.aspx\";>Design for "
+"testability</link>"
#. (itstool) path: item/p
#: C/unit-testing.page:282
@@ -9368,11 +9187,11 @@ msgstr ""
#. (itstool) path: item/p
#: C/unit-testing.page:290
msgid ""
-"<link href=\"http://c2.com/cgi/wiki?SoftwareDesignForTesting\";>Software "
-"design for testing</link>"
+"<link href=\"http://c2.com/cgi/wiki?SoftwareDesignForTesting\";>Software design for "
+"testing</link>"
msgstr ""
-"<link href=\"http://c2.com/cgi/wiki?SoftwareDesignForTesting\";>Software "
-"design for testing</link>"
+"<link href=\"http://c2.com/cgi/wiki?SoftwareDesignForTesting\";>Software design for "
+"testing</link>"
#. (itstool) path: info/desc
#: C/version-control.page:17
@@ -9387,39 +9206,36 @@ msgstr "Versionsverwaltung"
#. (itstool) path: synopsis/p
#: C/version-control.page:25
msgid ""
-"git is used for version control for all GNOME projects. This page assumes "
-"good working knowledge of git; some introductory material is available <link "
-"href=\"https://www.atlassian.com/git/tutorials/\";>here</link>, and a <link "
-"href=\"https://training.github.com/kit/downloads/github-git-cheat-sheet.pdf";
-"\">git cheatsheet is here</link>."
+"git is used for version control for all GNOME projects. This page assumes good "
+"working knowledge of git; some introductory material is available <link href="
+"\"https://www.atlassian.com/git/tutorials/\";>here</link>, and a <link href=\"https://";
+"training.github.com/kit/downloads/github-git-cheat-sheet.pdf\">git cheatsheet is "
+"here</link>."
msgstr ""
#. (itstool) path: item/p
#: C/version-control.page:34
msgid ""
-"Make atomic, revertable commits. (<link xref=\"#guidelines-for-making-commits"
-"\"/>)"
+"Make atomic, revertable commits. (<link xref=\"#guidelines-for-making-commits\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/version-control.page:38
msgid ""
-"Include full reasoning in commit messages, plus links to relevant bug "
-"reports or specifications. (<link xref=\"#guidelines-for-making-commits\"/>)"
+"Include full reasoning in commit messages, plus links to relevant bug reports or "
+"specifications. (<link xref=\"#guidelines-for-making-commits\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/version-control.page:43
msgid ""
-"Keep large changes, such as renames, in separate commits. (<link xref="
-"\"#guidelines-for-making-commits\"/>)"
+"Keep large changes, such as renames, in separate commits. (<link xref=\"#guidelines-"
+"for-making-commits\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/version-control.page:47
-msgid ""
-"Merge changes from feature branches by rebasing. (<link xref=\"#use-of-git\"/"
-">)"
+msgid "Merge changes from feature branches by rebasing. (<link xref=\"#use-of-git\"/>)"
msgstr ""
#. (itstool) path: section/title
@@ -9435,25 +9251,23 @@ msgstr "Die meisten GNOME-Repositories folgen diesen Regeln:"
#. (itstool) path: item/p
#: C/version-control.page:61
msgid ""
-"No forced pushes. Except for branches with the <code>wip/</code> prefix "
-"(work-in-progress), the commits’ history must not be modified, as "
-"contributors rely on it."
+"No forced pushes. Except for branches with the <code>wip/</code> prefix (work-in-"
+"progress), the commits’ history must not be modified, as contributors rely on it."
msgstr ""
#. (itstool) path: item/p
#: C/version-control.page:66
msgid ""
-"Rebase commits rather than merging, to have a linear history (which is "
-"easier to follow)."
+"Rebase commits rather than merging, to have a linear history (which is easier to "
+"follow)."
msgstr ""
#. (itstool) path: item/p
#: C/version-control.page:70
msgid ""
-"Work on feature branches on GNOME git in <code>wip/</code> branches, then "
-"rebase on master and fast-forward merge the changes. It is a good practice "
-"to also add your nickname to the branch name, as <code>wip/nickname/feature</"
-"code>."
+"Work on feature branches on GNOME git in <code>wip/</code> branches, then rebase on "
+"master and fast-forward merge the changes. It is a good practice to also add your "
+"nickname to the branch name, as <code>wip/nickname/feature</code>."
msgstr ""
#. (itstool) path: item/p
@@ -9472,25 +9286,24 @@ msgstr "Richtlinien für Commits"
#: C/version-control.page:86
#, fuzzy
msgid ""
-"Commits should be as small as possible, but no smaller. Each commit should "
-"address a single issue, containing only changes related to that issue. The "
-"message for each commit should describe the issue, explain what causes it, "
-"and explain how it has been fixed if it is not obvious. If the commit is "
-"associated with a bug report, the full URI for the bug report should be put "
-"on a line by itself at the bottom of the commit message. Similarly, the ID "
-"for the git commit (from <cmd>git log --oneline</cmd>) should be copied into "
-"the bug report once the commit has been pushed, so it is easy to find one "
-"from the other."
+"Commits should be as small as possible, but no smaller. Each commit should address a "
+"single issue, containing only changes related to that issue. The message for each "
+"commit should describe the issue, explain what causes it, and explain how it has "
+"been fixed if it is not obvious. If the commit is associated with a bug report, the "
+"full URI for the bug report should be put on a line by itself at the bottom of the "
+"commit message. Similarly, the ID for the git commit (from <cmd>git log --oneline</"
+"cmd>) should be copied into the bug report once the commit has been pushed, so it is "
+"easy to find one from the other."
msgstr "Commits sollten so klein wie möglich sein, aber nicht kleiner."
#. (itstool) path: section/p
#: C/version-control.page:98
msgid ""
-"The changes in each commit should be easy to read. For example, they should "
-"not unnecessarily change whitespace or indentation. Large, mechanical "
-"changes, such as renaming a file or function, should be put in separate "
-"commits from modifications to code inside that file or function, so that the "
-"latter changes do not get buried and lost in the former."
+"The changes in each commit should be easy to read. For example, they should not "
+"unnecessarily change whitespace or indentation. Large, mechanical changes, such as "
+"renaming a file or function, should be put in separate commits from modifications to "
+"code inside that file or function, so that the latter changes do not get buried and "
+"lost in the former."
msgstr ""
#. (itstool) path: section/p
@@ -9501,34 +9314,33 @@ msgstr ""
#. (itstool) path: item/p
#: C/version-control.page:110
msgid ""
-"Each commit should take the repository from one working state to another, "
-"otherwise <link href=\"http://git-scm.com/book/en/v2/Git-Tools-Debugging-";
-"with-Git#Binary-Search\">bisection</link> is impossible."
+"Each commit should take the repository from one working state to another, otherwise "
+"<link href=\"http://git-scm.com/book/en/v2/Git-Tools-Debugging-with-Git#Binary-Search";
+"\">bisection</link> is impossible."
msgstr ""
#. (itstool) path: item/p
#: C/version-control.page:116
msgid ""
-"Each commit should be individually revertable. If it later turns out that "
-"the commit was a bad idea, <cmd>git revert <var>commit ID</var></cmd> should "
-"take the repository from a working state to another working state."
+"Each commit should be individually revertable. If it later turns out that the commit "
+"was a bad idea, <cmd>git revert <var>commit ID</var></cmd> should take the "
+"repository from a working state to another working state."
msgstr ""
#. (itstool) path: item/p
#: C/version-control.page:122
msgid ""
-"The reasoning for each commit, and its relationship to external resources "
-"like specifications and bug reports, should be clear, to the extent that "
-"commits written by one developer a year in the past should still be "
-"understandable by a second developer without having to trace through the "
-"changes and work out what they do."
+"The reasoning for each commit, and its relationship to external resources like "
+"specifications and bug reports, should be clear, to the extent that commits written "
+"by one developer a year in the past should still be understandable by a second "
+"developer without having to trace through the changes and work out what they do."
msgstr ""
#. (itstool) path: item/p
#: C/version-control.page:129
msgid ""
-"Each commit should be written once, and designed to be read many times, by "
-"many reviewers and future programmers."
+"Each commit should be written once, and designed to be read many times, by many "
+"reviewers and future programmers."
msgstr ""
#. (itstool) path: section/title
@@ -9582,36 +9394,29 @@ msgstr ""
#. (itstool) path: item/p
#: C/version-control.page:164
msgid ""
-"<link href=\"https://sethrobertson.github.io/GitBestPractices/\";>Git best "
-"practices</link>"
+"<link href=\"https://sethrobertson.github.io/GitBestPractices/\";>Git best practices</"
+"link>"
msgstr ""
-"<link href=\"https://sethrobertson.github.io/GitBestPractices/\";>Git best "
-"practices</link>"
+"<link href=\"https://sethrobertson.github.io/GitBestPractices/\";>Git best practices</"
+"link>"
#. (itstool) path: item/p
#: C/version-control.page:167
-msgid ""
-"<link href=\"https://help.github.com/categories/using-git/\";>Git FAQ</link>"
-msgstr ""
-"<link href=\"https://help.github.com/categories/using-git/\";>Git FAQ</link>"
+msgid "<link href=\"https://help.github.com/categories/using-git/\";>Git FAQ</link>"
+msgstr "<link href=\"https://help.github.com/categories/using-git/\";>Git FAQ</link>"
#. (itstool) path: item/p
#: C/version-control.page:170
msgid ""
-"<link href=\"https://www.atlassian.com/git/tutorials/\";>Atlassian git "
-"tutorial</link>"
+"<link href=\"https://www.atlassian.com/git/tutorials/\";>Atlassian git tutorial</link>"
msgstr ""
-"<link href=\"https://www.atlassian.com/git/tutorials/\";>Atlassian git "
-"tutorial</link>"
+"<link href=\"https://www.atlassian.com/git/tutorials/\";>Atlassian git tutorial</link>"
#. (itstool) path: item/p
#: C/version-control.page:173
-msgid ""
-"<link href=\"http://git-scm.com/docs/gittutorial\";>Official git tutorial</"
-"link>"
+msgid "<link href=\"http://git-scm.com/docs/gittutorial\";>Official git tutorial</link>"
msgstr ""
-"<link href=\"http://git-scm.com/docs/gittutorial\";>Offizielles Git-Tutorial</"
-"link>"
+"<link href=\"http://git-scm.com/docs/gittutorial\";>Offizielles Git-Tutorial</link>"
#. (itstool) path: item/p
#: C/version-control.page:176
@@ -9620,50 +9425,48 @@ msgstr "<link href=\"https://try.github.io/\";>Interaktives Git-Tutorial</link>"
#. (itstool) path: item/p
#: C/version-control.page:179
-msgid ""
-"<link href=\"http://www.git-tower.com/learn/\";>git-tower tutorial</link>"
-msgstr ""
-"<link href=\"http://www.git-tower.com/learn/\";>Tutorial zu git-tower</link>"
+msgid "<link href=\"http://www.git-tower.com/learn/\";>git-tower tutorial</link>"
+msgstr "<link href=\"http://www.git-tower.com/learn/\";>Tutorial zu git-tower</link>"
#. (itstool) path: info/desc
#: C/versioning.page:17
msgid "Versioning and releasing libraries and applications"
-msgstr ""
+msgstr "Versionierung und Veröffentlichung von Bibliotheken und Anwendungen"
#. (itstool) path: synopsis/p
#: C/versioning.page:25
msgid ""
-"Module versioning differs for libraries and applications: libraries need a "
-"libtool version specified in addition to their package version. Applications "
-"just have a package version."
+"Module versioning differs for libraries and applications: libraries need a libtool "
+"version specified in addition to their package version. Applications just have a "
+"package version."
msgstr ""
#. (itstool) path: item/p
#: C/versioning.page:32
msgid ""
-"Libraries and applications have a package version of the form <em>major."
-"minor.micro</em>. (<link xref=\"#package-versioning\"/>)"
+"Libraries and applications have a package version of the form <em>major.minor.micro</"
+"em>. (<link xref=\"#package-versioning\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/versioning.page:36
msgid ""
-"Libraries additionally have a libtool version of the form <em>current:"
-"revision:age</em>. (<link xref=\"#libtool-versioning\"/>)"
+"Libraries additionally have a libtool version of the form <em>current:revision:age</"
+"em>. (<link xref=\"#libtool-versioning\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/versioning.page:40
msgid ""
-"Version numbers should be updated for each release (using release and post-"
-"release increments). (<link xref=\"#release-process\"/>)"
+"Version numbers should be updated for each release (using release and post-release "
+"increments). (<link xref=\"#release-process\"/>)"
msgstr ""
#. (itstool) path: item/p
#: C/versioning.page:44
msgid ""
-"Package versions should be incremented for feature changes or additions. "
-"(<link xref=\"#package-versioning\"/>)"
+"Package versions should be incremented for feature changes or additions. (<link xref="
+"\"#package-versioning\"/>)"
msgstr ""
#. (itstool) path: item/p
@@ -9688,52 +9491,51 @@ msgstr "Paket-Versionierung"
#. (itstool) path: section/p
#: C/versioning.page:62
msgid ""
-"Both libraries and applications have a package version of the form <em>major."
-"minor.micro</em>."
+"Both libraries and applications have a package version of the form <em>major.minor."
+"micro</em>."
msgstr ""
-"Sowohl Bibliotheken als auch Anwendungen haben eine Paketversion der Form "
-"<em>major.minor.micro</em>."
+"Sowohl Bibliotheken als auch Anwendungen haben eine Paketversion der Form <em>major."
+"minor.micro</em>."
#. (itstool) path: section/p
#: C/versioning.page:67
msgid ""
-"The package version number is that passed to <code>AC_INIT()</code>, and the "
-"one which is typically known as the project’s version number. For example, "
-"the Debian package for a library will use the library’s package version "
-"(though may also include the major version number in the package name to "
-"allow for <link xref=\"parallel-installability\">parallel installability</"
-"link>). Package versions are updated by the following rules:"
+"The package version number is that passed to <code>AC_INIT()</code>, and the one "
+"which is typically known as the project’s version number. For example, the Debian "
+"package for a library will use the library’s package version (though may also "
+"include the major version number in the package name to allow for <link xref="
+"\"parallel-installability\">parallel installability</link>). Package versions are "
+"updated by the following rules:"
msgstr ""
#. (itstool) path: item/p
#: C/versioning.page:77
msgid ""
-"If breaking <link xref=\"api-stability\">API compatibility</link> in a "
-"library, or making a large change to an application which affects everything "
-"(such as a UI redesign), increment major and set minor and micro to 0."
+"If breaking <link xref=\"api-stability\">API compatibility</link> in a library, or "
+"making a large change to an application which affects everything (such as a UI "
+"redesign), increment major and set minor and micro to 0."
msgstr ""
#. (itstool) path: item/p
#: C/versioning.page:83
msgid ""
-"Otherwise, if changing or adding a feature, or adding any API, increment "
-"minor and set micro to 0."
+"Otherwise, if changing or adding a feature, or adding any API, increment minor and "
+"set micro to 0."
msgstr ""
#. (itstool) path: item/p
#: C/versioning.page:87
msgid ""
-"Otherwise (if making a release containing only bug fixes and translation "
-"updates), increment micro."
+"Otherwise (if making a release containing only bug fixes and translation updates), "
+"increment micro."
msgstr ""
#. (itstool) path: section/p
#: C/versioning.page:93
-msgid ""
-"Note that the minor version number should be updated if any API is added."
+msgid "Note that the minor version number should be updated if any API is added."
msgstr ""
-"Beachten Sie, dass die Minor-Versionsnummer aktualisiert werden sollte, "
-"sobald eine API hinzugefügt wird."
+"Beachten Sie, dass die Minor-Versionsnummer aktualisiert werden sollte, sobald eine "
+"API hinzugefügt wird."
#. (itstool) path: section/title
#: C/versioning.page:99
@@ -9743,31 +9545,29 @@ msgstr "Libtool-Versionierung"
#. (itstool) path: section/p
#: C/versioning.page:101
msgid ""
-"Libraries have two version numbers: a libtool version which tracks ABI "
-"backwards compatibility (see <link xref=\"api-stability\"/>), and a package "
-"version which tracks feature changes. These are normally incremented in "
-"synchronization, but should be kept separate because ABI backwards "
-"compatibility is not necessarily related to feature changes or bug fixes. "
-"Furthermore, the two version numbers have different semantics, and cannot be "
-"automatically generated from each other."
+"Libraries have two version numbers: a libtool version which tracks ABI backwards "
+"compatibility (see <link xref=\"api-stability\"/>), and a package version which "
+"tracks feature changes. These are normally incremented in synchronization, but "
+"should be kept separate because ABI backwards compatibility is not necessarily "
+"related to feature changes or bug fixes. Furthermore, the two version numbers have "
+"different semantics, and cannot be automatically generated from each other."
msgstr ""
#. (itstool) path: section/p
#: C/versioning.page:112
msgid ""
-"A good overview of libtool versioning, and the differences from package "
-"versioning, is given in the <link href=\"https://autotools.io/libtool/";
-"version.html\">Autotools Mythbuster</link>; another is in the <link href="
-"\"http://www.gnu.org/s/libtool/manual/html_node/Updating-version-info.html";
-"\">libtool manual</link>."
+"A good overview of libtool versioning, and the differences from package versioning, "
+"is given in the <link href=\"https://autotools.io/libtool/version.html\";>Autotools "
+"Mythbuster</link>; another is in the <link href=\"http://www.gnu.org/s/libtool/";
+"manual/html_node/Updating-version-info.html\">libtool manual</link>."
msgstr ""
#. (itstool) path: section/p
#: C/versioning.page:121
msgid ""
-"To update the libtool version, follow the algorithm given in the comments "
-"below. This is a typical <file>configure.ac</file> snippet for setting up "
-"libtool versioning:"
+"To update the libtool version, follow the algorithm given in the comments below. "
+"This is a typical <file>configure.ac</file> snippet for setting up libtool "
+"versioning:"
msgstr ""
#. (itstool) path: section/code
@@ -9791,8 +9591,8 @@ msgstr ""
#. (itstool) path: section/p
#: C/versioning.page:140
msgid ""
-"The following snippet can be used in a <file>Makefile.am</file> to pass that "
-"version info to libtool:"
+"The following snippet can be used in a <file>Makefile.am</file> to pass that version "
+"info to libtool:"
msgstr ""
"Der folgende Code kann in <file>Makefile.am</file> verwendet werden, um die "
"Versionsnummer an libtool zu übergeben:"
@@ -9811,29 +9611,25 @@ msgstr "Stabile und instabile Paketversionen"
#. (itstool) path: section/p
#: C/versioning.page:150
msgid ""
-"Most GNOME modules follow a convention for stable and unstable releases. The "
-"minor version is even for stable releases and is odd for unstable releases. "
-"For example, the 3.20.* versions are stable, but the 3.19.* versions are "
-"unstable. The 3.19.* versions can be seen as alpha and beta releases of the "
-"3.20 version."
+"Most GNOME modules follow a convention for stable and unstable releases. The minor "
+"version is even for stable releases and is odd for unstable releases. For example, "
+"the 3.20.* versions are stable, but the 3.19.* versions are unstable. The 3.19.* "
+"versions can be seen as alpha and beta releases of the 3.20 version."
msgstr ""
#. (itstool) path: section/p
#: C/versioning.page:158
msgid ""
-"A new micro <em>stable</em> version (e.g. 3.20.0 → 3.20.1) doesn’t add new "
-"features, only translation updates and bug fixes. On the other hand, "
-"<em>unstable</em> micro releases (e.g. 3.19.1 → 3.19.2) can add API, or "
-"change or remove API which was added in a previous micro release in that "
-"minor series."
+"A new micro <em>stable</em> version (e.g. 3.20.0 → 3.20.1) doesn’t add new features, "
+"only translation updates and bug fixes. On the other hand, <em>unstable</em> micro "
+"releases (e.g. 3.19.1 → 3.19.2) can add API, or change or remove API which was added "
+"in a previous micro release in that minor series."
msgstr ""
#. (itstool) path: section/p
#: C/versioning.page:166
msgid "The libtool version should be updated only for stable package versions."
-msgstr ""
-"Die libtool-Version sollte nur die stabile Paketversionen aktualisiert "
-"werden."
+msgstr "Die libtool-Version sollte nur die stabile Paketversionen aktualisiert werden."
#. (itstool) path: section/title
#: C/versioning.page:172
@@ -9843,20 +9639,18 @@ msgstr "Veröffentlichungsprozess"
#. (itstool) path: section/p
#: C/versioning.page:174
msgid ""
-"The standard process for making a release of a module increments the libtool "
-"version (if the module is a library) at the time of release, then increments "
-"the package version number immediately afterwards (this is called a post-"
-"release increment)."
+"The standard process for making a release of a module increments the libtool version "
+"(if the module is a library) at the time of release, then increments the package "
+"version number immediately afterwards (this is called a post-release increment)."
msgstr ""
#. (itstool) path: section/p
#: C/versioning.page:181
msgid ""
-"Updating the libtool versions at the time of release means that they are "
-"only incremented once for all ABI changes in a release. The use of post-"
-"release increment for package versions means the package version number is "
-"not outdated (still equal to the previous release) during the development "
-"cycle."
+"Updating the libtool versions at the time of release means that they are only "
+"incremented once for all ABI changes in a release. The use of post-release increment "
+"for package versions means the package version number is not outdated (still equal "
+"to the previous release) during the development cycle."
msgstr ""
#. (itstool) path: section/p
@@ -9877,17 +9671,16 @@ msgstr "Stellen Sie sicher, dass der Code aktuell ist: <cmd>git pull</cmd>"
#: C/versioning.page:199
msgid "Make sure you have no local changes: <cmd>git status</cmd>"
msgstr ""
-"Stellen Sie sicher, dass es keine lokalen Änderungen gibt: <cmd>git status</"
-"cmd>"
+"Stellen Sie sicher, dass es keine lokalen Änderungen gibt: <cmd>git status</cmd>"
#. (itstool) path: item/p
#: C/versioning.page:202
msgid ""
-"If the release is for a stable package version, increment the libtool "
-"version number in <file>configure.ac</file> (if it exists)"
+"If the release is for a stable package version, increment the libtool version number "
+"in <file>configure.ac</file> (if it exists)"
msgstr ""
-"Falls es sich um ein Release einer stabilen Paketversion handelt, erhöhen "
-"Sie die libtool-Versionsnummer in <file>configure.ac</file> (falls vorhanden)"
+"Falls es sich um ein Release einer stabilen Paketversion handelt, erhöhen Sie die "
+"libtool-Versionsnummer in <file>configure.ac</file> (falls vorhanden)"
#. (itstool) path: item/p
#: C/versioning.page:206
@@ -9897,22 +9690,23 @@ msgstr "Fügen Sie einen Eintrag zur <file>NEWS</file>-Datei hinzu"
#. (itstool) path: item/p
#: C/versioning.page:210
msgid ""
-"Run <cmd>./autogen.sh && make && make install && "
-"make distcheck</cmd> and ensure it succeeds"
+"Run <cmd>./autogen.sh && make && make install && make "
+"distcheck</cmd> and ensure it succeeds"
msgstr ""
+"Führen Sie <cmd>./autogen.sh && make && make install && make "
+"distcheck</cmd> aus und prüfen Sie, ob es erfolgreich durchläuft"
#. (itstool) path: item/p
#: C/versioning.page:216
-msgid ""
-"Fix any issues which come up, commit those changes, and restart at step 3"
+msgid "Fix any issues which come up, commit those changes, and restart at step 3"
msgstr ""
#. (itstool) path: item/p
#: C/versioning.page:222
msgid ""
-"If <cmd>make distcheck</cmd> finishes with “[archive] is ready for "
-"distribution”, run <cmd>git commit -a -m \"Release version x.y.z\"</cmd> "
-"(where ‘x.y.z’ is the package version number)"
+"If <cmd>make distcheck</cmd> finishes with “[archive] is ready for distribution”, "
+"run <cmd>git commit -a -m \"Release version x.y.z\"</cmd> (where ‘x.y.z’ is the "
+"package version number)"
msgstr ""
#. (itstool) path: item/p
@@ -9923,32 +9717,30 @@ msgstr "Führen Sie <cmd>git push</cmd> aus"
#. (itstool) path: item/p
#: C/versioning.page:232
msgid ""
-"If that fails due to other commits having been pushed in the meantime, run "
-"<cmd>git pull</cmd> to merge your commit on the branch followed by a second "
-"<cmd>git push</cmd>. This is an exception to the GNOME guideline to have a "
-"linear Git history (<link xref=\"version-control#use-of-git\"/>). If you "
-"prefer to have a linear history, you need to restart at step 1."
+"If that fails due to other commits having been pushed in the meantime, run <cmd>git "
+"pull</cmd> to merge your commit on the branch followed by a second <cmd>git push</"
+"cmd>. This is an exception to the GNOME guideline to have a linear Git history "
+"(<link xref=\"version-control#use-of-git\"/>). If you prefer to have a linear "
+"history, you need to restart at step 1."
msgstr ""
#. (itstool) path: item/p
#: C/versioning.page:242
msgid ""
-"Tag the release: <cmd>git tag -s x.y.z</cmd> (where ‘x.y.z’ is the package "
-"version number)"
+"Tag the release: <cmd>git tag -s x.y.z</cmd> (where ‘x.y.z’ is the package version "
+"number)"
msgstr ""
#. (itstool) path: item/p
#: C/versioning.page:246
msgid ""
-"Run <cmd>git push origin x.y.z</cmd> (where ‘x.y.z’ is the package version "
-"number)"
+"Run <cmd>git push origin x.y.z</cmd> (where ‘x.y.z’ is the package version number)"
msgstr ""
#. (itstool) path: section/p
#: C/versioning.page:252
msgid ""
-"The release is now complete, and the post-release version increment can be "
-"done:"
+"The release is now complete, and the post-release version increment can be done:"
msgstr ""
#. (itstool) path: item/p
@@ -9959,17 +9751,16 @@ msgstr "Erhöhen Sie die Paketversionsnummer in <file>configure.ac</file>"
#. (itstool) path: item/p
#: C/versioning.page:260
msgid "Run <cmd>git commit -a -m \"Post-release version increment\"</cmd>"
-msgstr ""
-"Führen Sie <cmd>git commit -a -m \"Post-release version increment\"</cmd> aus"
+msgstr "Führen Sie <cmd>git commit -a -m \"Post-release version increment\"</cmd> aus"
#. (itstool) path: section/p
#: C/versioning.page:268
msgid ""
-"The package archive generated by <cmd>make distcheck</cmd> can now be "
-"uploaded to download.gnome.org or distributed in other ways."
+"The package archive generated by <cmd>make distcheck</cmd> can now be uploaded to "
+"download.gnome.org or distributed in other ways."
msgstr ""
-"Das von <cmd>make distcheck</cmd> erzeugte Paketarchiv kann nun zu download."
-"gnome.org hochgeladen oder auf andere Weise verteilt werden."
+"Das von <cmd>make distcheck</cmd> erzeugte Paketarchiv kann nun zu download.gnome."
+"org hochgeladen oder auf andere Weise verteilt werden."
#. (itstool) path: info/desc
#: C/writing-good-code.page:25
@@ -9984,52 +9775,49 @@ msgstr "Die Bedeutung von gutem Code"
#. (itstool) path: page/p
#: C/writing-good-code.page:30
msgid ""
-"GNOME is a very ambitious free software project, and it is composed of many "
-"software packages that are more or less independent of each other. A lot of "
-"the work in GNOME is done by volunteers: although there are many people "
-"working on GNOME full-time or part-time for here, volunteers still make up a "
-"large percentage of our contributors. Programmers may come and go at any "
-"time and they will be able to dedicate different amounts of time to the "
-"GNOME project. People’s “real world” responsibilities may change, and this "
-"will be reflected in the amount of time that they can devote to GNOME."
+"GNOME is a very ambitious free software project, and it is composed of many software "
+"packages that are more or less independent of each other. A lot of the work in GNOME "
+"is done by volunteers: although there are many people working on GNOME full-time or "
+"part-time for here, volunteers still make up a large percentage of our contributors. "
+"Programmers may come and go at any time and they will be able to dedicate different "
+"amounts of time to the GNOME project. People’s “real world” responsibilities may "
+"change, and this will be reflected in the amount of time that they can devote to "
+"GNOME."
msgstr ""
#. (itstool) path: page/p
#: C/writing-good-code.page:43
msgid ""
-"Software development takes long amounts of time and painstaking effort. This "
-"is why most part-time volunteers cannot start big projects by themselves; it "
-"is much easier and more rewarding to contribute to existing projects, as "
-"this yields results that are immediately visible and usable."
+"Software development takes long amounts of time and painstaking effort. This is why "
+"most part-time volunteers cannot start big projects by themselves; it is much easier "
+"and more rewarding to contribute to existing projects, as this yields results that "
+"are immediately visible and usable."
msgstr ""
#. (itstool) path: page/p
#: C/writing-good-code.page:51
msgid ""
-"Thus, we conclude that it is very important for existing projects to make it "
-"as easy as possible for people to contribute to them. One way of doing this "
-"is by making sure that programs are easy to read, understand, modify, and "
-"maintain."
+"Thus, we conclude that it is very important for existing projects to make it as easy "
+"as possible for people to contribute to them. One way of doing this is by making "
+"sure that programs are easy to read, understand, modify, and maintain."
msgstr ""
#. (itstool) path: page/p
#: C/writing-good-code.page:58
msgid ""
-"Messy code is hard to read, and people may lose interest if they cannot "
-"decipher what the code tries to do. Also, it is important that programmers "
-"be able to understand the code quickly so that they can start contributing "
-"with bug fixes and enhancements in a short amount of time. Source code is a "
-"form of <em>communication</em>, and it is more for people than for "
-"computers. Just as someone would not like to read a novel with spelling "
-"errors, bad grammar, and sloppy punctuation, programmers should strive to "
-"write good code that is easy to understand and modify by others."
+"Messy code is hard to read, and people may lose interest if they cannot decipher "
+"what the code tries to do. Also, it is important that programmers be able to "
+"understand the code quickly so that they can start contributing with bug fixes and "
+"enhancements in a short amount of time. Source code is a form of <em>communication</"
+"em>, and it is more for people than for computers. Just as someone would not like to "
+"read a novel with spelling errors, bad grammar, and sloppy punctuation, programmers "
+"should strive to write good code that is easy to understand and modify by others."
msgstr ""
#. (itstool) path: page/p
#: C/writing-good-code.page:71
msgid "The following are some important qualities of good code:"
-msgstr ""
-"Im folgenden finden Sie einige wichtige Qualitätsmerkmale von gutem Code:"
+msgstr "Im folgenden finden Sie einige wichtige Qualitätsmerkmale von gutem Code:"
#. (itstool) path: item/title
#: C/writing-good-code.page:77
@@ -10039,10 +9827,9 @@ msgstr ""
#. (itstool) path: item/p
#: C/writing-good-code.page:78
msgid ""
-"Clean code is easy to read with minimum effort. This lets people start to "
-"understand it easily. This includes the coding style itself (brace "
-"placement, indentation, variable names), and the actual control flow of the "
-"code."
+"Clean code is easy to read with minimum effort. This lets people start to understand "
+"it easily. This includes the coding style itself (brace placement, indentation, "
+"variable names), and the actual control flow of the code."
msgstr ""
#. (itstool) path: item/title
@@ -10053,11 +9840,11 @@ msgstr "Konsistenz"
#. (itstool) path: item/p
#: C/writing-good-code.page:88
msgid ""
-"Consistent code makes it easy for people to understand how a program works. "
-"When reading consistent code, one subconsciously forms a number of "
-"assumptions and expectations about how the code works, so it is easier and "
-"safer to make modifications to it. Code that <em>looks</em> the same in two "
-"places should <em>work</em> the same, too."
+"Consistent code makes it easy for people to understand how a program works. When "
+"reading consistent code, one subconsciously forms a number of assumptions and "
+"expectations about how the code works, so it is easier and safer to make "
+"modifications to it. Code that <em>looks</em> the same in two places should "
+"<em>work</em> the same, too."
msgstr ""
#. (itstool) path: item/title
@@ -10068,11 +9855,11 @@ msgstr "Erweiterbarkeit"
#. (itstool) path: item/p
#: C/writing-good-code.page:100
msgid ""
-"General-purpose code is easier to reuse and modify than very specific code "
-"with lots of hardcoded assumptions. When someone wants to add a new feature "
-"to a program, it will obviously be easier to do so if the code was designed "
-"to be extensible from the beginning. Code that was not written this way may "
-"lead people into having to implement ugly hacks to add features."
+"General-purpose code is easier to reuse and modify than very specific code with lots "
+"of hardcoded assumptions. When someone wants to add a new feature to a program, it "
+"will obviously be easier to do so if the code was designed to be extensible from the "
+"beginning. Code that was not written this way may lead people into having to "
+"implement ugly hacks to add features."
msgstr ""
#. (itstool) path: item/title
@@ -10083,12 +9870,11 @@ msgstr "Korrektheit"
#. (itstool) path: item/p
#: C/writing-good-code.page:113
msgid ""
-"Finally, code that is designed to be correct lets people spend less time "
-"worrying about bugs, and more time enhancing the features of a program. "
-"Users also appreciate correct code, since nobody likes software that "
-"crashes. Code that is written for correctness and safety (i.e. code that "
-"explicitly tries to ensure that the program remains in a consistent state) "
-"prevents many kinds of silly bugs."
+"Finally, code that is designed to be correct lets people spend less time worrying "
+"about bugs, and more time enhancing the features of a program. Users also appreciate "
+"correct code, since nobody likes software that crashes. Code that is written for "
+"correctness and safety (i.e. code that explicitly tries to ensure that the program "
+"remains in a consistent state) prevents many kinds of silly bugs."
msgstr ""
#. (itstool) path: section/title
@@ -10098,10 +9884,8 @@ msgstr "Bücher"
#. (itstool) path: item/p
#: C/writing-good-code.page:129
-msgid ""
-"<link href=\"http://www.cc2e.com\";>Code Complete</link>, by Steve McConnell."
-msgstr ""
-"<link href=\"http://www.cc2e.com\";>Code Complete</link> von Steve McConnell"
+msgid "<link href=\"http://www.cc2e.com\";>Code Complete</link>, by Steve McConnell."
+msgstr "<link href=\"http://www.cc2e.com\";>Code Complete</link> von Steve McConnell"
#. (itstool) path: item/p
#: C/writing-good-code.page:132
@@ -10115,16 +9899,19 @@ msgstr ""
#. (itstool) path: item/p
#: C/writing-good-code.page:137
msgid ""
-"<link href=\"http://en.wikipedia.org/wiki/Design_Patterns\";> Design "
-"Patterns: Elements of Reusable Object-Oriented Software </link>, by Erich "
-"Gamma, Richard Helm, Ralph Johnson and John Vlissides."
+"<link href=\"http://en.wikipedia.org/wiki/Design_Patterns\";> Design Patterns: "
+"Elements of Reusable Object-Oriented Software </link>, by Erich Gamma, Richard Helm, "
+"Ralph Johnson and John Vlissides."
msgstr ""
+"<link href=\"http://en.wikipedia.org/wiki/Design_Patterns\";> Design Patterns: "
+"Elements of Reusable Object-Oriented Software </link> von Erich Gamma, Richard Helm, "
+"Ralph Johnson und John Vlissides."
#. (itstool) path: item/p
#: C/writing-good-code.page:142
msgid ""
-"<link href=\"http://astore.amazon.com/gnomestore-20/detail/020163385X\";> "
-"Object-Oriented Design Heuristics </link>, by Arthur Riel."
+"<link href=\"http://astore.amazon.com/gnomestore-20/detail/020163385X\";> Object-"
+"Oriented Design Heuristics </link>, by Arthur Riel."
msgstr ""
-"<link href=\"http://astore.amazon.com/gnomestore-20/detail/020163385X\";> "
-"Object-Oriented Design Heuristics </link> von by Arthur Riel"
+"<link href=\"http://astore.amazon.com/gnomestore-20/detail/020163385X\";> Object-"
+"Oriented Design Heuristics </link> von by Arthur Riel"
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
