[gnome-devel-docs] [l10n] Added German translation

[Mario Blättermann <mariobl src gnome org>]

commit b1fc75a926caf407d5565662c1fd7c941150d87f
Author: Mario Blättermann <mariobl gnome org>
Date:   Thu Mar 31 13:44:10 2011 +0200

    [l10n] Added German translation

 style-guide/de/de.po |  693 ++++++++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 693 insertions(+), 0 deletions(-)
---
diff --git a/style-guide/de/de.po b/style-guide/de/de.po
new file mode 100644
index 0000000..15af694
--- /dev/null
+++ b/style-guide/de/de.po
@@ -0,0 +1,693 @@
+# German translation of the Documentation Style Guide.
+# Mario Blättermann <mariobl freenet de>, 2011.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: gnome-devel-docs master\n"
+"POT-Creation-Date: 2011-03-31 12:17+0200\n"
+"PO-Revision-Date: 2011-03-31 13:40+0100\n"
+"Last-Translator: Mario Blättermann <mariobl freenet de>\n"
+"Language-Team: Deutsch <gnome-de gnome org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: terms-widgets.page:26(None)
+msgid "@@image: 'media/button.png'; md5=THIS FILE DOESN'T EXIST"
+msgstr "a"
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: terms-widgets.page:34(None)
+msgid "@@image: 'media/list.png'; md5=THIS FILE DOESN'T EXIST"
+msgstr "a"
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: terms-widgets.page:42(None)
+msgid "@@image: 'media/checkbox.png'; md5=THIS FILE DOESN'T EXIST"
+msgstr "a"
+
+#: terms-widgets.page:9(desc)
+msgid "The terms to use when referring to a widget in the user interface."
+msgstr ""
+"Zu verwendende Begriffe, wenn Sie auf ein Element der Benutzeroberfläche "
+"Bezug nehmen."
+
+#: terms-widgets.page:14(name) terms-principles.page:14(name)
+#: terms-objects.page:14(name) terms-interactions.page:14(name)
+#: terms-desktop.page:14(name) terms-complete.page:14(name)
+#: style-tone.page:14(name) style-principles.page:14(name)
+#: style-language-conventions.page:14(name) index.page:12(name)
+msgid "GNOME Documentation Project"
+msgstr "GNOME-Dokumentationsprojekt"
+
+#: terms-widgets.page:15(email) terms-principles.page:15(email)
+#: terms-objects.page:15(email) terms-interactions.page:15(email)
+#: terms-desktop.page:15(email) terms-complete.page:15(email)
+#: style-tone.page:15(email) style-principles.page:15(email)
+#: style-language-conventions.page:15(email) index.page:13(email)
+msgid "gnome-doc-list gnome org"
+msgstr "gnome-doc-list gnome org"
+
+#: terms-widgets.page:20(title)
+msgid "Widgets"
+msgstr "Widgets"
+
+#: terms-widgets.page:25(title)
+msgid "Button"
+msgstr "Knopf"
+
+#: terms-widgets.page:27(p)
+msgid "Examples of buttons."
+msgstr "Beispiele für Knöpfe."
+
+#: terms-widgets.page:33(title)
+msgid "List"
+msgstr "Liste"
+
+#: terms-widgets.page:35(p)
+msgid "Examples of lists."
+msgstr "Beispiele für Listen."
+
+#: terms-widgets.page:41(title)
+msgid "Checkbox"
+msgstr "Ankreuzfeld"
+
+#: terms-widgets.page:43(p)
+msgid "Examples of checkboxes."
+msgstr "Beispiele für Ankreuzfelder."
+
+#: terms-principles.page:9(desc)
+msgid "Some guiding principles to help you decide which terminology to use."
+msgstr ""
+"Einige Leitprinzipien, die Ihnen die Entscheidung bei der Wahl der Begriffe "
+"erleichtern."
+
+#: terms-principles.page:20(title)
+msgid "Choosing terminology"
+msgstr "Wahl der Begriffe"
+
+#: terms-principles.page:22(p)
+msgid ""
+"Using poor or complicated terminology confuses and slows-down users. In "
+"general, avoiding jargon is a very good idea, even if this results in a less "
+"concise term being used to describe an object or concept. Here are some "
+"guidelines to help you choose terminology well:"
+msgstr ""
+
+#: terms-principles.page:26(p)
+msgid "Simple"
+msgstr "Einfach"
+
+#: terms-principles.page:27(p)
+msgid ""
+"Use non-technical, simple language. Complicated and rarely-used words should "
+"be avoided. Terms that are well-known inside the computer industry, but not "
+"in everydaylife, should be used with caution."
+msgstr ""
+"Verwenden Sie eine einfache, nicht allzu technische Sprache. Komplizierte und "
+"selten verwendete Wörter sollten vermieden werden. Gerade Begriffe, die in "
+"der Computerindustrie gängig sind, aber im täglichen Leben eher selten "
+"vorkommen, sollten sparsam und mit Vorsicht eingesetzt werden."
+
+#: terms-principles.page:30(p)
+msgid "Unambiguous"
+msgstr "Unzweideutig"
+
+#: terms-principles.page:31(p)
+msgid ""
+"It should be obvious what a term refers to. Describe things rather than "
+"trying to assign a name to them if a sensible name isn't availble."
+msgstr ""
+
+#: terms-principles.page:34(p)
+msgid "Recognizable"
+msgstr ""
+
+#: terms-principles.page:35(p)
+msgid ""
+"If at all possible, choose terms that users will be instantly familiar with. "
+"Everyday words are preferred."
+msgstr ""
+
+#: terms-principles.page:38(p)
+msgid "Not overly-specific"
+msgstr ""
+
+#: terms-principles.page:39(p)
+msgid ""
+"If a general term is appropriate, use that instead of a set of more specific "
+"ones. Categorizing things can lead to ambiguity when you must decide how to "
+"refer to something which doesn't cleany fit into your pre-defined categories."
+msgstr ""
+
+#: terms-principles.page:40(p)
+msgid ""
+"Categorizing objects which look or behave in very similar ways can also "
+"confuse the user, who may not understand the subtle distinction between the "
+"categories. There is no need to choose terms for different types of window, "
+"for example."
+msgstr ""
+"Die Kategorisierung von ähnlich erscheinenden oder sich verhaltenden Objekten "
+"kann den Benutzer ebenfalls verwirren. Er könnte die marginalen Unterschiede "
+"zwischen Ihren Kategorien vielleicht gar nicht richtig erfassen. Es besteht "
+"beispielsweise keine Notwendigkeit, zwischen verschiedenen Fenstertypen zu "
+"unterscheiden."
+
+#: terms-principles.page:41(p)
+msgid ""
+"If you are defining a terminology guide for your project, think about what it "
+"is necessary to define and what can be left up to the writer. Consistency in "
+"terminology is important for readers, but specifying too much makes it "
+"difficult for writers to follow your guidelines."
+msgstr ""
+"Wenn Sie in Ihrem Projekt eine Richtlinie für die zu verwendenden Begriffe "
+"anlegen, sollten Sie darüber nachdenken, was wirklich unmittelbar notwendig "
+"ist und was Sie eher dem Dokumentationsautor überlassen sollten. Konsistenz "
+"in der Verwendung von Begriffen ist für Leser sehr wohl von Bedeutung, doch "
+"wenn Sie zu vieles vordefinieren, erschweren Sie dem Dokumentationsautor, "
+"Ihren Richtlinien zu folgen."
+
+#: terms-principles.page:44(p)
+msgid "Not necessarily correct"
+msgstr "Nicht notwendigerweise korrekt"
+
+#: terms-principles.page:45(p)
+msgid ""
+"Technical correctness should not be your primary concern when choosing "
+"terminology. The important thing is describing something in a way which makes "
+"sense to users and doesn't cause confusion. It's OK to be a little bit wrong."
+msgstr ""
+"Technische Korrektheit sollte bei der Begriffswahl nicht unbedingt an erster "
+"Stelle stehen. Es ist vielmehr von Bedeutung, dass Sie Dinge so beschreiben, "
+"dass sie für den Benutzer einen Sinn ergeben und keine Verwirrung stiften. Es "
+"ist durchaus in Ordnung, ein wenig »falsch« zu schreiben."
+
+#: terms-principles.page:50(title)
+msgid "Ask real users"
+msgstr "Fragen Sie reale Benutzer"
+
+#: terms-principles.page:51(p)
+msgid ""
+"When deciding on what terminology to use, you should test it on real end-"
+"users. This will help to ensure that your choices are relevant, "
+"understandable and sensible."
+msgstr ""
+"Wenn Sie sich für Begriffe zu entscheiden haben, sollten Sie diese bei realen "
+"Benutzern testen. Dadurch können sie sicher stellen, dass Ihre Begriffe "
+"relevant, verständlich und sinnvoll sind."
+
+#. When image changes, this message will be marked fuzzy or untranslated for you.
+#. It doesn't matter what you translate it to: it's not used at all.
+#: terms-objects.page:26(None)
+msgid "@@image: 'media/xxx.png'; md5=THIS FILE DOESN'T EXIST"
+msgstr "a"
+
+#: terms-objects.page:9(desc)
+msgid ""
+"Terms for describing objects that the user encounters in the user interface, "
+"such as files and folders."
+msgstr ""
+"Begriffe zur Beschreibung von Objekten, denen ein Benutzer in der grafischen "
+"Benutzeroberfläche begegnet, wie Dateien und Ordner."
+
+#: terms-objects.page:20(title)
+msgid "Objects in the UI"
+msgstr "Objekte in der Benutzeroberfläche"
+
+#: terms-objects.page:25(title)
+msgid "xxx"
+msgstr "xxx"
+
+#: terms-objects.page:27(p)
+msgid "Examples of xxx."
+msgstr "Beispiele für xxx."
+
+#: terms-interactions.page:9(desc)
+msgid "How to describe the way the user interacts with the user interface."
+msgstr ""
+"Beschreibung der Art, wie Benutzer mit der Benutzeroberfläche interagieren."
+
+#: terms-interactions.page:20(title)
+msgid "Interactions"
+msgstr "Interaktionen"
+
+#: terms-interactions.page:23(title)
+msgid "Mouse and keyboard actions"
+msgstr "Interaktionen mit Maus und Tastatur"
+
+#: terms-interactions.page:24(p)
+msgid ""
+"Users should be able to distinguish between actions which they have to "
+"perform with the mouse or with the keyboard, respectively."
+msgstr ""
+"Benutzer sollten in der Lage sein, zwischen Aktionen zu unterscheiden, die "
+"sie entweder mit der Tastatur oder mit der Maus auszuführen haben."
+
+#: terms-interactions.page:27(p)
+msgid "To perform this action, click <gui>Apply</gui>."
+msgstr "To perform this action, click <gui>Apply</gui>."
+
+#: terms-interactions.page:28(p)
+msgid "To perform this action, press <key>Enter</key>."
+msgstr "To perform this action, press <key>Enter</key>."
+
+#: terms-interactions.page:31(p)
+msgid ""
+"This is unique for the user to decide whether he has to click a button in the "
+"UI or to press a key on his keyboard. Please don't use it as follows:"
+msgstr ""
+"Dies ist eindeutig für den Benutzer, ob er einen Knopf in der "
+"Benutzeroberfläche anzuklicken oder eine Taste auf der Tastatur zu drücken "
+"hat. Bitte schreiben Sie nicht:"
+
+#: terms-interactions.page:34(p)
+msgid "To perform this action, press the <gui>Apply</gui> button."
+msgstr "To perform this action, press the <gui>Apply</gui> button."
+
+#: terms-interactions.page:37(p)
+msgid ""
+"In fact, we cannot <em>press</em> a button. The physical process <em>to "
+"press</em> isn't adaptable to a virtual object. Instead, we <em>click</em> "
+"with the mouse or another pointing device."
+msgstr ""
+"In fact, we cannot <em>press</em> a button. The physical process <em>to "
+"press</em> isn't adaptable to a virtual object. Instead, we <em>click</em> "
+"with the mouse or another pointing device."
+
+#: terms-desktop.page:9(desc)
+msgid ""
+"Terms to be used when referring to the major components of the desktop "
+"environment."
+msgstr ""
+"Zu verwendende Begriffe, wenn auf die Grundkomponenten der Arbeitsumgebung "
+"Bezug genommen wird."
+
+#: terms-desktop.page:20(title)
+msgid "Desktop components"
+msgstr "Komponenten der Arbeitsumgebung"
+
+#: terms-desktop.page:22(p)
+msgid "Workspaces, etc."
+msgstr "Arbeitsflächen usw."
+
+#: terms-complete.page:9(desc)
+msgid "A complete list of terminology recommendations."
+msgstr "Eine vollständige Liste von empfohlenen Begriffen."
+
+#: terms-complete.page:20(title)
+msgid "Complete list of terms"
+msgstr "Vollständige Begriffliste"
+
+#: style-tone.page:9(desc)
+msgid "Writing in an appropriate tone will help readers relate to the text."
+msgstr ""
+"Das Schreiben in einem entsprechenden Ton hilft dem Leser, Bezüge zum Text "
+"herzustellen."
+
+#: style-tone.page:20(title)
+msgid "Tone"
+msgstr "Ton"
+
+#: style-tone.page:22(p)
+msgid ""
+"The tone of a piece of writing affects the reader's attitude towards it. You "
+"want the reader to be receptive to your writing; don't alienate them. Here "
+"are some key words to help you set the tone of your writing:"
+msgstr ""
+
+#: style-tone.page:26(p)
+msgid "Casual; friendly; light."
+msgstr ""
+
+#: style-tone.page:27(p)
+msgid ""
+"Stuffy, overly-formal writing can bore people, but imposing your bubbly "
+"personality on people can grate. A happy medium can be found: try to sound "
+"helpful and approachable, but maintain a neutral mood."
+msgstr ""
+"Ein steifer, zu formeller Ton langweilt Ihre Leser, aber das Zurschaustellen "
+"Ihrer eigenen Persönlichkeit kann auch ätzend sein. Finden Sie die goldene "
+"Mitte: einen hilfreichen, ansprechenden Ton, aber halten Sie Ihre Texte in "
+"einer neutralen Stimmung."
+
+#: style-tone.page:30(p)
+msgid "Competent; knowledgeable; sensible; confident; honest."
+msgstr ""
+
+#: style-tone.page:31(p)
+msgid ""
+"Sound like you know what you are talking about. Avoid seeming biased or "
+"radical. The reader will trust that they are receiving useful, correct "
+"information."
+msgstr ""
+
+#: style-tone.page:34(p)
+msgid "Professional interest; weakly personal; genuine."
+msgstr ""
+
+#: style-tone.page:35(p)
+msgid ""
+"Make the reader feel like they are being personally addressed by your "
+"writing, but don't be overly-familiar or superficially friendly."
+msgstr ""
+"Geben Sie dem Leser das Gefühl, dass er von dem, was Sie schreiben, "
+"persönlich angesprochen wird. Vermeiden Sie jedoch übertriebene Vertrautheit "
+"oder Freundlichkeit."
+
+#: style-tone.page:40(title)
+msgid "Examples"
+msgstr "Beispiele"
+
+#: style-tone.page:41(p)
+msgid "Here are some examples of writing in the tone we are aiming for."
+msgstr "Hier einige Beispiele dafür, welcher Ton erwartet wird:"
+
+#: style-tone.page:43(cite)
+msgid "Desktop Help"
+msgstr "Desktop Help"
+
+#: style-tone.page:44(p)
+msgid ""
+"Depending on your screen and screen resolution settings, the fonts displayed "
+"on your computer may need some adjustments. The text may look either too big, "
+"too small, or may even look fuzzy and/or distorted. To fix this, you will "
+"need to make changes to your font resolution settings. You can just change "
+"the resolution settings to suit your personal preference too."
+msgstr ""
+"Depending on your screen and screen resolution settings, the fonts displayed "
+"on your computer may need some adjustments. The text may look either too big, "
+"too small, or may even look fuzzy and/or distorted. To fix this, you will "
+"need to make changes to your font resolution settings. You can just change "
+"the resolution settings to suit your personal preference too."
+
+#: style-tone.page:47(cite)
+msgid "Empathy Help"
+msgstr "Empathy Help"
+
+#: style-tone.page:48(p)
+msgid ""
+"On some IRC networks, you can register your nickname with a service called "
+"NickServ. By sending special messages to NickServ, you can set your password "
+"and identify yourself. Some IRC chat rooms may not allow you to join without "
+"a registered nickname."
+msgstr ""
+"On some IRC networks, you can register your nickname with a service called "
+"NickServ. By sending special messages to NickServ, you can set your password "
+"and identify yourself. Some IRC chat rooms may not allow you to join without "
+"a registered nickname."
+
+#: style-tone.page:51(cite)
+msgid "Guitar Tuner developer tutorial"
+msgstr "Guitar Tuner developer tutorial"
+
+#: style-tone.page:52(p)
+msgid ""
+"This signal handler has two arguments: a pointer to the GtkWidget that called "
+"the function (in our case, always a GtkButton), and a pointer to some \"user "
+"data\" that you can define, but which we won't be using here. (You can set "
+"the user data by calling <code>gtk_builder_connect_signals</code>; it is "
+"normally used to pass a pointer to a data structure that you might need to "
+"access inside the signal handler.)"
+msgstr ""
+"This signal handler has two arguments: a pointer to the GtkWidget that called "
+"the function (in our case, always a GtkButton), and a pointer to some \"user "
+"data\" that you can define, but which we won't be using here. (You can set "
+"the user data by calling <code>gtk_builder_connect_signals</code>; it is "
+"normally used to pass a pointer to a data structure that you might need to "
+"access inside the signal handler.)"
+
+#: style-principles.page:9(desc)
+msgid "Guiding principles for writing documentation."
+msgstr "Leitprinzipien zum Schreiben von Dokumentationen."
+
+#: style-principles.page:20(title)
+msgid "Style Principles"
+msgstr "Stilprinzipien"
+
+#: style-principles.page:23(cite)
+msgid "Henry David Thoreau"
+msgstr "Henry David Thoreau"
+
+#: style-principles.page:24(p)
+msgid "Our life is frittered away by detail.... Simplify, simplify."
+msgstr "Our life is frittered away by detail.... Simplify, simplify."
+
+#: style-principles.page:28(cite)
+msgid "<em>The Elements of Style</em>, William Strunck Jr. and E. B. White"
+msgstr "<em>The Elements of Style</em>, William Strunck Jr. and E. B. White"
+
+#: style-principles.page:29(p)
+msgid ""
+"Vigorous writing is concise. A sentence should contain no unnecessary words, "
+"a paragraph no unnecessary sentences, for the same reason that a drawing "
+"should have no unnecessary lines and a machine no unnecessary parts. This "
+"requires not that the writer make all his sentences short, or that he should "
+"avoid all detail and treat his subjects only in outline, but that every "
+"sentence tell."
+msgstr ""
+"Schreiben Sie knapp und kraftvoll. Ein Satz sollte keine unnötigen Wörter "
+"enthalten und ein Abschnitt keine unnötigen Sätze, aus dem gleichen Grund, "
+"weshalb eine Zeichnung keine unnötigen Linien und eine Maschine keine "
+"unnötigen Teile enthält. Das bedeutet allerdings nicht zwangsläufig für den "
+"Schreiber, dass alle Sätze kurz gehalten werden müssen und Details vermieden "
+"werden oder der eigentliche Zweck der Dokumentation nur in Umrissen erkennbar "
+"ist. Jeder Satz sollte sinnvoll sein und Informationen vermitteln.."
+
+#: style-principles.page:33(cite)
+msgid "Thomas Mann"
+msgstr "Thomas Mann"
+
+#: style-principles.page:34(p)
+msgid ""
+"A writer is someone for whom writing is more difficult than it is for other "
+"people."
+msgstr ""
+
+#: style-principles.page:38(cite)
+msgid "John Ruskin"
+msgstr "John Ruskin"
+
+#: style-principles.page:39(p)
+msgid ""
+"Say all you have to say in the fewest possible words, or your reader will be "
+"sure to skip them; and in the plainest possible words or he will certainly "
+"misunderstand them."
+msgstr ""
+
+#: style-principles.page:43(title)
+msgid "You are human, and so are your readers"
+msgstr "Sie sind ein Mensch, und Ihre Leser sind es auch"
+
+#: style-principles.page:44(p)
+msgid ""
+"There is a tendency in technical writing to be formulaic, to rely on using "
+"the same structures again and again. This makes your writing boring and "
+"unsatisfying. Avoid this at all costs - readers won't take the information on "
+"board as effectively if they are bored, and you won't be getting the "
+"satisfaction of exercising your creativity."
+msgstr ""
+
+#: style-principles.page:45(p)
+msgid ""
+"Having said that, you're not writing a novel. \"Pleasant to read\" is enough "
+"- don't obscure the content by desperately trying to work something "
+"interesting in there. Some topics are genuinely dull."
+msgstr ""
+
+#: style-principles.page:49(title)
+msgid "Write simply"
+msgstr "Schreiben Sie einfach"
+
+#: style-principles.page:50(p)
+msgid ""
+"Write in a way that is easy for your audience to understand. This shouldn't "
+"imply that you're writing for an unintelligent audience; rather, you're "
+"trying to save your readers unnecessary mental overhead. Simple writing is "
+"easier to understand, and the point of our technical writing is to help "
+"people to understand things."
+msgstr ""
+"Schreiben Sie so, dass es für Ihr Publikum verständlich ist. Das bedeutet "
+"keineswegs, dass Ihre Zielgruppe als unintelligent anzusehen ist oder dass "
+"Sie die ungenutzten mentalen Fähigkeiten Ihrer Leser ungenutzt lassen "
+"sollten. Einfaches Schreiben ist einfacher zu verstehen. Das Ziel Ihrer "
+"technischen Dokumentation ist es, Leuten zu helfen, Dinge auf einfache Weise "
+"zu verstehen."
+
+#: style-principles.page:51(p)
+msgid ""
+"\"Simple\" also means \"non-technical\". Use words that the reader will "
+"understand and know about, or at least be able to correctly guess the meaning "
+"of. Just because a word is widely used in the computer industry doesn't mean "
+"that real users will know what it means."
+msgstr ""
+"»Einfach« bedeutet auch »nicht-technisch«. Verwenden Sie Wörter, die der "
+"Leser kennt und versteht, oder deren Bedeutung zumindest korrekt herleiten "
+"und zuordnen kann. Nur weil ein Wort in der Computerindustrie häufig "
+"verwendet wird, müssen nicht zwangsläufig reale Benutzer verstehen, worum es "
+"dabei geht."
+
+#: style-principles.page:55(title)
+msgid "Be direct"
+msgstr "Seien Sie direkt."
+
+#: style-principles.page:56(p)
+msgid ""
+"Write directly to your reader. It's fine to use \"you\" and \"your\" - there "
+"is no need to always write abstractly, or for the third person. That doesn't "
+"mean that every sentence should be addressed directly to the reader, though."
+msgstr ""
+"Sprechen Sie Ihren Leser direkt an. Wörter wie »you« und »your« sind "
+"erwünscht. Es ist nicht notwendig, abstrakt oder gar in der dritten Person zu "
+"schreiben. Allerdings muss deshalb nicht jeder Satz direkt an den Leser "
+"adressiert sein."
+
+#: style-principles.page:57(p)
+msgid ""
+"Being direct also means cutting out waffle. Don't labor points (unless it's "
+"important to do so), don't over-describe things, and don't waste the user's "
+"time with introductory text. The most important information should go first - "
+"defer asides until later on."
+msgstr ""
+
+#: style-principles.page:58(p)
+msgid ""
+"Prefer shorter sentences with fewer clauses, but keep your writing friendly "
+"and natural. Being a little terse is OK as long as the text flows well."
+msgstr ""
+"Bevorzugen Sie kürzere Sätze und Satzteile, aber halten Sie Ihren Text "
+"angenehm und natürlich. Knappheit ist in Ordnung, so lange der Textfluss "
+"erhalten bleibt."
+
+#: style-principles.page:59(p)
+msgid ""
+"You should also refrain from using flowery or excessively exuberant language. "
+"Trying to write in a poetic or learned manner can obscure the meaning of the "
+"content; too much enthusiasm can be offputting or patronizing."
+msgstr ""
+"Verzichten Sie auch auf eine allzu blumige oder überschwängliche Sprache. "
+"Eine zu poetische Schreibweise kann den eigentlichen Sinn des Inhalt in den "
+"Hintergrund schieben, und zu viel Enthusiasmus kann abschreckend und "
+"schulmeisterlich wirken."
+
+#: style-principles.page:63(title)
+msgid "Sufficient is better than complete"
+msgstr "Ausreichend ist besser als vollständig"
+
+#: style-principles.page:64(p)
+msgid ""
+"Write enough that the reader know what you are talking about, but not much "
+"more. There is a tendency to over-explain things in documentation, usually "
+"for reasons of completeness. It's OK to miss out bits of a topic that aren't "
+"as important or interesting. You can skim over steps that are obvious."
+msgstr ""
+"Schreiben Sie genug, um den Leser begreifen zu lassen, worum es geht, aber "
+"nicht viel mehr. Es besteht eine Tendenz, Dinge in Dokumentationen übermä�ig "
+"erschöpfend zu beschreiben, wohl aus Gründen der Vollständigkeit. Es ist in "
+"Ordnung, Teile eines Themas wegzulassen, die vielleicht nicht so bedeutend "
+"oder interessant sind. Sie können Schritte überspringen, die offensichtlich "
+"sind."
+
+#: style-principles.page:65(p)
+msgid ""
+"Likewise, your choice of topics shouldn't be dictated by completeness. Do "
+"users really need a topic on starting or exiting your app? Or would it be "
+"sufficient to leave those topics out?"
+msgstr ""
+"GleichermaÃ?en sollte die Wahl Ihrer Themen nicht von erzwungener "
+"Vollständigkeit bestimmt werden. Brauchen Benutzer wirklich Informationen "
+"darüber, wie Ihre Anwendung geöffnet oder beendet werden kann, oder wäre es "
+"sinnvoller, diese Themen wegzulassen?"
+
+#: style-principles.page:69(title)
+msgid "Be useful"
+msgstr ""
+
+#: style-principles.page:70(p)
+msgid ""
+"What you write should be useful to the reader. Writing about something simply "
+"because you <em>feel you should</em> isn't good enough; you'll end up with "
+"lazy, uninformative writing that doesn't answer your reader's questions."
+msgstr ""
+
+#: style-principles.page:71(p)
+msgid ""
+"Always think about what your intended readership is looking for before you "
+"start writing. This will help you to write something that gets straight to "
+"the heart of the matter, and fast. And if you can't think of anything that a "
+"reader might want to know about a topic, perhaps you don't really need to "
+"write that topic after all?"
+msgstr ""
+"Denken Sie vor dem Schreiben darüber nach, wonach Ihr Zielpublikum suchen "
+"könnte. Dadurch trifft Ihre Hilfe vielleicht schneller und ohne Verrenkungen "
+"den Punkt. Falls Ihnen zu einem Thema nichts einfällt, was den Leser "
+"interessieren könnte, tun Sie vielleicht besser daran, dieses Thema gar nicht "
+"erst in Angriff zu nehmen."
+
+#: style-principles.page:75(title)
+msgid "Break rules if it makes for better writing"
+msgstr "Weichen Sie von Regeln ab, wenn es dem Geschriebenen dient"
+
+#: style-principles.page:76(p)
+msgid ""
+"Dogged adherence to rules can lead to awkward-sounding text. If it makes more "
+"sense to say something in a particular way, even if it's <em>technically</em> "
+"wrong, you should say it anyway."
+msgstr ""
+"Wenn Sie den Regeln wie ein treuer Hund immer folgen, kann das auch zu "
+"unbeholfen und holprig klingendem Text führen. Falls es sinnvoller ist, etwas "
+"in einer abweichenden Art und Weise zu beschreiben, auch wenn es "
+"<em>technisch</em> falsch ist, dann sollten Sie es trotzdem tun."
+
+#: style-principles.page:77(p)
+msgid ""
+"There is a difference <em>bad</em> grammar and <em>not-quite-correct</em> "
+"grammar, however. Avoid the former; the rules of grammar are there to help "
+"avoid ambiguity and other confusions (even if they're not perfect)."
+msgstr ""
+"Es gibt einen Unterschied zwischen <em>schlechter</em> und <em>nicht ganz "
+"korrekter</em> Grammatik, wie auch immer. Vermeiden Sie das Erstgenannte. Die "
+"Regeln der Grammatik sind da, um Zweideutigkeiten und andere Unklarheiten zu "
+"vermeiden, auch wenn sie nicht perfekt sind."
+
+#: style-principles.page:78(p)
+msgid ""
+"Likewise, absolute technical correctness is vehemently <em>not</em> the aim "
+"of our technical writing. It's fine to abuse terms if doing so would make "
+"your text more understandable for the reader."
+msgstr ""
+"GleichermaÃ?en ist absolute technische Korrektheit <em>nicht</em> oberstes "
+"Ziel unserer technischen Dokumentationen. »Missbrauchen« Sie ruhig Begriffe, "
+"wenn es der Verständlichkeit Ihres Texts zuträglich ist."
+
+#: style-language-conventions.page:9(desc)
+msgid "How you should construct sentences."
+msgstr "Regeln zum Formulieren von Sätzen."
+
+#: style-language-conventions.page:20(title)
+msgid "Language Conventions"
+msgstr "Sprachkonventionen"
+
+#: index.page:7(desc)
+msgid "Guidelines for writers for the GNOME platform."
+msgstr "Richtlinien für Dokumentationsautoren der GNOME-Plattform."
+
+#: index.page:18(title)
+msgid "Style and Terminology"
+msgstr "Stil und Begriffe"
+
+#: index.page:22(title)
+msgid "Writing Style"
+msgstr "Schreibstil"
+
+#: index.page:26(title)
+msgid "Terminology"
+msgstr "Begriffe"
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
+#: index.page:0(None)
+msgid "translator-credits"
+msgstr "Mario Blättermann <mariobl freenet de>, 2011"