GNOME.org
 

[gnome-doc-utils] Added German doc translation

commit 67ec83bf5335818e06fc7d26c101b0685c3bee4b
Author: Mario Blättermann <mariobl gnome org>
Date:   Sun Jun 21 15:32:49 2009 +0200

    Added German doc translation

 doc/xslt/Makefile.am |    2 +-
 doc/xslt/de/de.po    | 1108 ++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 1109 insertions(+), 1 deletions(-)
---
diff --git a/doc/xslt/Makefile.am b/doc/xslt/Makefile.am
index 70ad54f..264812d 100644
--- a/doc/xslt/Makefile.am
+++ b/doc/xslt/Makefile.am
@@ -75,4 +75,4 @@ EXTRA_DIST = xsldoc.awk xsldoc-fill.xsl xsldoc-check.xsl xsldoc-docbook.xsl
 DOC_MODULE = gnome-doc-xslt
 DOC_INCLUDES = legal.xml translating.xml $(patsubst %,%.xml,$(xsldoc_base))
 
-DOC_LINGUAS =
+DOC_LINGUAS = de
\ No newline at end of file
diff --git a/doc/xslt/de/de.po b/doc/xslt/de/de.po
new file mode 100644
index 0000000..c798bf4
--- /dev/null
+++ b/doc/xslt/de/de.po
@@ -0,0 +1,1108 @@
+# German translation of the gnome-doc-utils xslt manual.
+# Mario Blättermann <mariobl gnome org>, 2009.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"POT-Creation-Date: 2009-06-21 15:12+0200\n"
+"PO-Revision-Date: 2009-06-21 15:31+0200\n"
+"Last-Translator: Mario Blättermann <mariobl gnome org>\n"
+"Language-Team: German <gnome-de gnome org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Poedit-Language: German\n"
+"X-Poedit-Country: GERMANY\n"
+
+#: translating.xml:16(title)
+msgid "Translating the Stylesheets"
+msgstr "Ã?bersetzung der Stilvorlagen"
+
+#: translating.xml:17(para)
+msgid ""
+"The Gnome documentation stylesheets provide support for localizing the "
+"rendered output from DocBook documents. Localizable strings in the "
+"stylesheets are marked for translation and extracted into PO files and "
+"<command>intltool</command>. After they have been translated, "
+"<command>intltool</command> merges them into an XML file called "
+"<filename>l10n.xml</filename>, which is then used by the stylesheets to "
+"localize the output."
+msgstr ""
+
+#: translating.xml:24(para)
+msgid ""
+"Providing full internationalization support for the DocBook stylesheets is "
+"not trivial, and providing localizations requires translators to understand "
+"how documents are formatted and, to some extent, how DocBook works. DocBook "
+"is a high-level markup language, and it requires processing applications to "
+"provide much of the formatting for documents. DocBook applications must "
+"resolve cross references, create tables of contents, format headers, and "
+"perform other formatting tasks that need to be localized. Localizing these "
+"tasks involves more than translating stand-alone sentences. In effect, the "
+"very formatting code itself is localizable."
+msgstr ""
+
+#: translating.xml:35(title)
+msgid "Help Us Help You"
+msgstr ""
+
+#: translating.xml:36(para)
+msgid ""
+"Document formatting varies greatly across the world. Each locale has a long "
+"history of formatting conventions and methods. The maintainers of these "
+"stylesheets do not know all the nuances of formatting documents in all "
+"locales. The only way we can create better output for your locale is if you "
+"tell us when you encounter problems."
+msgstr ""
+
+#: translating.xml:43(para)
+msgid ""
+"Although all localization is done by translating strings in a PO file, there "
+"are many cases where the translatable string is not a simple sentence or "
+"phrase. Rather, translators must provide data using XML fragments. These "
+"structured fragments can be used to work with plural forms, provide "
+"alternative formattings based on context, or provide format strings."
+msgstr ""
+
+#: translating.xml:50(title)
+msgid "Simple Strings"
+msgstr "Einfache Zeichenketten"
+
+#: translating.xml:52(para)
+msgid ""
+"Translated strings are extracted in the stylesheets by a template called "
+"<function role=\"xsl-template\" moreinfo=\"refentry\">l10n.gettext</"
+"function>. This template extracts strings from an XML file, which is built "
+"from PO files by <command>intltool</command>. For example, consider the "
+"string <wordasword>Caution</wordasword>, which is used as a heading for "
+"<sgmltag>caution</sgmltag> elements. The stylesheets would call <function "
+"role=\"xsl-template\" moreinfo=\"refentry\">l10n.gettext</function> to "
+"extract the translated value of this string for the document's language. The "
+"<filename>l10n.xml</filename> file would have an entry similar to this:"
+msgstr ""
+
+#: translating.xml:107(para)
+msgid ""
+"Translators, however, will work only with the PO files. Using PO files for "
+"these strings is no different than any other simple string translation. The "
+"PO entry in the <literal>sr</literal> locale for the above string would look "
+"like this:"
+msgstr ""
+
+#: translating.xml:119(title)
+msgid "Plurals"
+msgstr "Pluralformen"
+
+#: translating.xml:121(para)
+msgid ""
+"In many cases, a static string is insufficient for proper localized content. "
+"For these cases, the stylesheets allow for alternate strings by placing the "
+"strings in a structured XML fragment. Alternate strings are used in two ways: "
+"to provide plural forms according to the plural rules of the language, and to "
+"provide alternate formattings based on a specified role. This section "
+"discusses plurals. See <xref linkend=\"translating-roles\"/> for a discussion "
+"of roles."
+msgstr ""
+
+#: translating.xml:129(para)
+msgid ""
+"Plural forms are handled similarly to how they are handled in other "
+"applications. A rule is provided to transform a number into a plural index, "
+"and a translation is provided for each of those indexes. Unfortunately, there "
+"is no standard way to encode this information into XML; thus, there is no "
+"mechanism in <command>intltool</command>'s XML mode. Consequently, "
+"translators must place their translations in an XML fragment. This fragment "
+"is merged into the <filename>l10n.xml</filename> file, and the stylesheets "
+"extract the appropriate form."
+msgstr ""
+
+#: translating.xml:137(para)
+msgid "Here is an example entry in the <filename>l10n.xml</filename> file:"
+msgstr ""
+
+#: translating.xml:153(para)
+msgid ""
+"Since the Serbian language has three plural forms, three translations have "
+"been provided. Each of these is placed in a <sgmltag>msgstr</sgmltag> "
+"element, and the <sgmltag role=\"attribute\">form</sgmltag> attribute is used "
+"to indicate for which plural form they are used."
+msgstr ""
+
+#: translating.xml:158(para)
+msgid ""
+"Again, translators will only see the entries in their PO files. The PO file "
+"entry for the above translation looks like this:"
+msgstr ""
+
+#: translating.xml:173(para)
+msgid ""
+"Since <command>intltool</command> often alters whitespace, the entry in the "
+"PO file might not look as nice as this. When creating the translated message "
+"strings, translators may add or remove whitespace between <sgmltag>msgstr</"
+"sgmltag> elements if they choose. This extra text content is ignored by "
+"<function role=\"xsl-template\" moreinfo=\"refentry\">l10n.gettext</function>."
+msgstr ""
+
+#: translating.xml:179(para)
+msgid ""
+"Note that translators may add a <sgmltag>msgstr</sgmltag> element without a "
+"<sgmltag class=\"attribute\">form</sgmltag> attribute as a fallback "
+"translation. In the example above, the last two <sgmltag>msgstr</sgmltag> "
+"elements could have been replaced by a single <sgmltag>msgstr</sgmltag> "
+"element without a <sgmltag class=\"attribute\">form</sgmltag> attribute. The "
+"<function role=\"xsl-template\" moreinfo=\"refentry\">l10n.gettext</function> "
+"template would match the first element whenever the plural form is 0, and the "
+"fallback element otherwise."
+msgstr ""
+
+#: translating.xml:187(para)
+msgid ""
+"The plural form is selected using the <function role=\"xsl-template\" "
+"moreinfo=\"refentry\">l10n.plural.form</function> template. This templates "
+"takes the number of items as a parameter, and returns the numeric index of "
+"the plural form to use. Currently, the rule cannot be automatically extracted "
+"from the <literal>Plural-Forms</literal> entry in the PO file, though this "
+"feature is planned for the future. Until this feature is added, plural rules "
+"have to be coded manually in the stylesheets. Translators need to notify the "
+"maintainers when they begin translating the stylesheets."
+msgstr ""
+
+#: translating.xml:198(title)
+msgid "Roles"
+msgstr ""
+
+#: translating.xml:200(para)
+msgid ""
+"In many cases, how to render an element depends on various conditions, such "
+"as the grammatical role. For these cases, the stylesheets allow translators "
+"to provide multiple translations, each marked with a <sgmltag role=\"attribute"
+"\">role</sgmltag> attribute from a fixed vocabulary. The list of valid roles "
+"will depend on the template, and should be given in the translator comment "
+"accompanying each string. However, there are a number of common cases, "
+"particularly for labels and cross references."
+msgstr ""
+
+#: translating.xml:210(para)
+msgid ""
+"Translating using roles is similar to translating using plural forms. A "
+"translation consists of any number of <sgmltag>msgstr</sgmltag> elements, "
+"each with a <sgmltag class=\"attribute\">role</sgmltag> attribute. A "
+"<sgmltag>msgstr</sgmltag> element without an attribute can be provided as a "
+"default if none of the roles match."
+msgstr ""
+
+#: translating.xml:216(para)
+msgid ""
+"For example, the <sgmltag>citetitle</sgmltag> element in DocBook is used to "
+"cite the title of a publication. The type of the publication is specified in "
+"the <sgmltag class=\"attribute\">class</sgmltag> attribute. In many English "
+"publications, article titles are placed in quotes, while book titles are "
+"italicized. The following fragment will quote article titles, but italicize "
+"all other cited titles."
+msgstr ""
+
+#: translating.xml:228(para)
+msgid ""
+"The Serbian translation team has chosen to follow the same convention of "
+"quoting article titles and italicizing all others. The entry in <filename>sr."
+"po</filename> follows."
+msgstr ""
+
+#: translating.xml:243(para)
+msgid ""
+"The meaning of the markup inside the <sgmltag>msgstr</sgmltag> elements will "
+"be explained in <xref linkend=\"translating-formats\"/>. For now, simply note "
+"that multiple strings have been provided, each in a <sgmltag>msgstr</sgmltag> "
+"element. The only difference between the original string and the Serbian "
+"string is that Serbian is using a different opening quote character, aligned "
+"at the baseline."
+msgstr ""
+
+#: translating.xml:250(para)
+msgid ""
+"Note also that the original translation contains an additional "
+"<sgmltag>msgid</sgmltag> element. This element is redundant in the merged "
+"XML; its only purpose is to distinguish the string from other strings, which "
+"may potentially have the same formatting in English. Redundant "
+"<sgmltag>msgid</sgmltag> elements are sometimes used even when neither plural "
+"forms nor roles are being used. In those cases, the sole translatable string "
+"is placed in a <sgmltag>msgstr</sgmltag> element with no attributes."
+msgstr ""
+
+#: translating.xml:261(title)
+msgid "Format Strings"
+msgstr ""
+
+#: translating.xml:263(para)
+msgid ""
+"Using specialized format strings, the Gnome documentation stylesheets can "
+"translate more than just simple strings. These format strings are similar in "
+"principle to format strings used in C programs, except that XML is used to "
+"insert named parameters, rather than special format tokens being used to "
+"insert positional parameters."
+msgstr ""
+
+#: translating.xml:269(para)
+msgid ""
+"For instance, DocBook provides the <sgmltag>quote</sgmltag> element, used to "
+"mark inline quotations. How to render an inline quotation depends on the "
+"typographic conventions of the language. In U.S. English, they are rendered "
+"inside â??double inverted-commaâ?? quotation marks. In Serbian, they are "
+"typically rendered with the opening quotation â??aligned at the baselineâ??. The "
+"entry in the Serbian PO file for this format string follows."
+msgstr ""
+
+#: translating.xml:287(para)
+msgid ""
+"Multiple <sgmltag>msgstr</sgmltag> elements have been provided with roles. "
+"These are used to distinguish inner quotes from outer quotes. Roles were "
+"described in <xref linkend=\"translating-roles\"/>. The <sgmltag>msgstr</"
+"sgmltag> elements also contain inline markup. This markup is used to insert "
+"additional content. In this case, only the <sgmltag class=\"emptytag\">node</"
+"sgmltag> element has been used. This element is replaced by the contents of "
+"the quotation element being processed."
+msgstr ""
+
+#: translating.xml:296(para)
+msgid ""
+"Each format string has a set number of named arguments available. These "
+"arguments should be documented in the translator comments that accompany the "
+"string. Note that the default translation may not make use of all the "
+"available arguments."
+msgstr ""
+
+#: translating.xml:301(para)
+msgid ""
+"In addition to marker elements in format strings, translators may also use "
+"simple inline formatting markup. Any content can be wrapped in a "
+"<sgmltag>span</sgmltag> element with certain attributes to control "
+"formatting. The attributes are a subset of CSS properties. For HTML output, "
+"they are converted directly into the corresponding CSS. The list of allowed "
+"attributes is as follows:"
+msgstr ""
+
+#: translating.xml:310(sgmltag)
+msgid "font-family"
+msgstr "font-family"
+
+#: translating.xml:311(para)
+msgid ""
+"This attribute sets the font family. Specifying exact font is generally a not "
+"advisable. Rather, this should be used to provide a generic family: serif, "
+"sans-serif, cursive, fantasy, or monospace."
+msgstr ""
+
+#: translating.xml:317(sgmltag)
+msgid "font-style"
+msgstr "font-style"
+
+#: translating.xml:318(para)
+msgid ""
+"This attribute can be used to italicize the text. The allowed values are "
+"italic, oblique, and normal."
+msgstr ""
+
+#: translating.xml:322(sgmltag)
+msgid "font-variant"
+msgstr "font-variant"
+
+#: translating.xml:323(para)
+msgid ""
+"This attribute can be used to set the text in small caps. Small caps prints "
+"lowercase letters with smaller versions of the uppercase glyphs. The allowed "
+"values are small-caps and normal."
+msgstr ""
+
+#: translating.xml:329(sgmltag)
+msgid "font-weight"
+msgstr "font-weight"
+
+#: translating.xml:330(para)
+msgid ""
+"This attribute can be used to mark the text bold. CSS allows any number from "
+"100 to 900, with normal text being 400 and bold being 700. In addition to "
+"numerical values, you can use one of bold, bolder, lighter, or normal to use "
+"pre-defined values. Only bold and normal should generally be needed."
+msgstr ""
+
+#: translating.xml:337(sgmltag)
+msgid "font-stretch"
+msgstr "font-stretch"
+
+#: translating.xml:338(para)
+msgid ""
+"This attribute can be used to stretch or condense the font. CSS allows a "
+"number of keywords to specify by exactly how much to stretch the font. In "
+"practice, only wider, narrower, and normal should generally be used."
+msgstr ""
+
+#: translating.xml:344(sgmltag)
+msgid "font-size"
+msgstr "font-size"
+
+#: translating.xml:345(para)
+msgid ""
+"This attribute sets the size of the font. CSS allows both absolute font sizes "
+"using keywords or numeric lenghts, as well as relative font sizes using "
+"keywords or percentages. Generally, only larger, smaller, and normal should "
+"be used for this attribute. Better, use the <sgmltag>big</sgmltag> and "
+"<sgmltag>small</sgmltag> convenience elements described below. They are "
+"defined to respect the size scales used throughout the stylesheets."
+msgstr ""
+
+#: translating.xml:355(sgmltag)
+msgid "text-decoration"
+msgstr "text-decoration"
+
+#: translating.xml:356(para)
+msgid ""
+"This attribute can set various effects on the text. The allowed values are "
+"none, underline, overline, line-through, and blink. Don't use blink."
+msgstr ""
+
+#: translating.xml:362(para)
+msgid ""
+"Additionally, extra inline elements are provided for convenience. The "
+"formatting done by these elements could also be done using the <sgmltag>span</"
+"sgmltag> element. Using these elements is just easier for common formatting "
+"tasks."
+msgstr ""
+
+#: translating.xml:369(sgmltag)
+msgid "big"
+msgstr "big"
+
+#: translating.xml:370(para)
+msgid ""
+"Make the text larger. This is preferred over using the <sgmltag>font-size</"
+"sgmltag> attribute, because it is defined to use the size scale used "
+"throughout the stylesheets."
+msgstr ""
+
+#: translating.xml:375(sgmltag)
+msgid "small"
+msgstr "small"
+
+#: translating.xml:376(para)
+msgid ""
+"Make the text smaller. This is preferred over using the <sgmltag>font-size</"
+"sgmltag> attribute, because it is defined to use the size scale used "
+"throughout the stylesheets."
+msgstr ""
+
+#: translating.xml:381(sgmltag)
+msgid "sub"
+msgstr "sub"
+
+#: translating.xml:382(para)
+msgid "Render the text as a subscript."
+msgstr ""
+
+#: translating.xml:385(sgmltag)
+msgid "sup"
+msgstr "sup"
+
+#: translating.xml:386(para)
+msgid "Render the text as a superscript."
+msgstr ""
+
+#: translating.xml:389(sgmltag)
+msgid "b"
+msgstr "b"
+
+#: translating.xml:390(para)
+msgid ""
+"Make the text bold. This is equivalent to setting the <sgmltag>font-weight</"
+"sgmltag> attribute to bold."
+msgstr ""
+
+#: translating.xml:394(sgmltag) translating.xml:590(literal)
+msgid "i"
+msgstr "i"
+
+#: translating.xml:395(para)
+msgid ""
+"Make the text italic. This is equivalent to setting the <sgmltag>font-style</"
+"sgmltag> attribute to italic."
+msgstr ""
+
+#: translating.xml:399(sgmltag)
+msgid "tt"
+msgstr "tt"
+
+#: translating.xml:400(para)
+msgid ""
+"Make the text monospace. This is equivalent to setting the <sgmltag>font-"
+"family</sgmltag> attribute to monospace."
+msgstr ""
+
+#: translating.xml:404(sgmltag)
+msgid "u"
+msgstr "u"
+
+#: translating.xml:405(para)
+msgid ""
+"Underline the text. This is equivalent to setting the <sgmltag>text-"
+"decoration</sgmltag> attribute to underline."
+msgstr ""
+
+#: translating.xml:413(title)
+msgid "Common Formatter Types"
+msgstr ""
+
+#: translating.xml:415(para)
+msgid ""
+"There are a number of common types of format strings that are marked for "
+"translation in the stylesheets. DocBook contains a lot of structural markup, "
+"and many of the same sorts of formatting tasks have to be performed on "
+"different elements. For example, chapters, appendixes, and sections all have "
+"similar formatting needs, but they usually need to be handled distinctly. The "
+"stylesheets do not expose every distinct element of DocBook; rather, they "
+"only make distinctions when they matter from a document presentation "
+"viewpoint."
+msgstr ""
+
+#: translating.xml:424(para)
+msgid ""
+"This section outlines many of the common types of strings translators will "
+"encounter. Strings of the same type will generally have the same format "
+"arguments and the same set of roles."
+msgstr ""
+
+#: translating.xml:429(title)
+msgid "Label Formatters"
+msgstr ""
+
+#: translating.xml:430(para)
+msgid ""
+"Labels are used before titles in headers and contents listings. Usually, a "
+"label will contain the object's number followed by some punctuation. Formal "
+"block objects, such as tables and figures, often have more information in the "
+"label."
+msgstr ""
+
+#: translating.xml:435(para) translating.xml:531(para)
+msgid "The Serbian label formatters for sections and figures follow."
+msgstr ""
+
+#: translating.xml:461(para)
+msgid ""
+"In both cases, translations are provided for the <literal>header</literal> "
+"and <literal>li</literal> roles. Additionally, a fallback formatting has been "
+"provided to format labels when no role is provided. Label formatters will "
+"generally use the same two roles. Fallback translations should be provided as "
+"well."
+msgstr ""
+
+#: translating.xml:468(para)
+msgid ""
+"Most label formatters provide three format arguments which can be used in the "
+"translations:"
+msgstr ""
+
+#: translating.xml:473(sgmltag) translating.xml:624(sgmltag)
+msgid "title"
+msgstr "title"
+
+#: translating.xml:474(para)
+msgid ""
+"Insert the title of the element being labeled. For most types of element, the "
+"title is simply provided by the <sgmltag>title</sgmltag> in DocBook. A few "
+"DocBook elements, notably <sgmltag>refentry</sgmltag>, have more complicated "
+"content models. Translators need only reference the argument, and the "
+"stylesheets will determine the title."
+msgstr ""
+
+#: translating.xml:482(sgmltag) translating.xml:633(sgmltag)
+msgid "titleabbrev"
+msgstr "titleabbrev"
+
+#: translating.xml:483(para)
+msgid ""
+"Insert the abbreviated title of the element being labeled. Abbreviated titles "
+"are provided by the <sgmltag>titleabbrev</sgmltag> element in DocBook. If the "
+"labeled element does not have an abbreviated title, the title is used instead."
+msgstr ""
+
+#: translating.xml:490(sgmltag) translating.xml:641(sgmltag)
+msgid "number"
+msgstr "number"
+
+#: translating.xml:491(para)
+msgid ""
+"Insert the fully qualified number of the element being labeled. For most "
+"label formatters, there is a corresponding number formatter that will be "
+"called for this argument."
+msgstr ""
+
+#: translating.xml:497(para)
+msgid ""
+"Since labels are used before titles, most label formatters should only need "
+"to use the number of the element."
+msgstr ""
+
+#: translating.xml:502(title)
+msgid "Number Formatters"
+msgstr ""
+
+#: translating.xml:503(para)
+msgid ""
+"Numbers are used in labels, cross references, and other identifiers. Numbers "
+"identify elements by their position in the document. Numbers can be as simple "
+"as single-level positions, or they may indicate a hierarchy. For example, the "
+"third subsection of the fourth section in the second chapter would be Section "
+"2.4.3. The job of number formatters is to put together the hierarchical "
+"number string. Thus, number formatters are not called for single-level "
+"numbers."
+msgstr ""
+
+#: translating.xml:511(para)
+msgid ""
+"The single-level number of an element in its parent is referred to as that "
+"element's <firstterm>digit</firstterm>. Number formatters work by specifying "
+"how to combine the parent element's number with the current element's digit. "
+"Two format arguments are allowed:"
+msgstr ""
+
+#: translating.xml:518(sgmltag)
+msgid "parent"
+msgstr "parent"
+
+#: translating.xml:519(para)
+msgid ""
+"Insert the fully qualified number of the element's parent. In many cases, "
+"this number is constructed by calling the number formatter for the parent "
+"element."
+msgstr ""
+
+#: translating.xml:524(sgmltag)
+msgid "digit"
+msgstr "digit"
+
+#: translating.xml:525(para)
+msgid ""
+"Insert the single-level position of the element in its parent element. How "
+"the digit is displayed is determined by the corresponding digit format."
+msgstr ""
+
+#: translating.xml:549(para)
+msgid ""
+"Note that <sgmltag>msgstr</sgmltag> elements are used to contain the strings, "
+"even though neither plural forms nor roles are being used. This is because a "
+"<sgmltag>msgid</sgmltag> has been inserted into the translatable string to "
+"allow number formatters for different elements to be distinct messages in PO "
+"files."
+msgstr ""
+
+#: translating.xml:557(title)
+msgid "Digit Formats"
+msgstr ""
+
+#: translating.xml:558(para)
+msgid ""
+"Digits are the part of an element's number that specify its position in its "
+"parent element. An element's number consists of its parent number and its "
+"digit. Digits can be formatted using a number of numbering systems."
+msgstr ""
+
+#: translating.xml:563(para)
+msgid ""
+"Digit formats aren't actually format strings, nor are they user-visible "
+"strings. They're simply tokens that specify how to format a number. "
+"Currently, only the following five digit formats are supported:"
+msgstr ""
+
+#: translating.xml:570(literal)
+msgid "1"
+msgstr "1"
+
+#: translating.xml:571(para)
+msgid ""
+"Format the number using Arabic numerals: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, "
+"12."
+msgstr ""
+
+#: translating.xml:575(literal)
+msgid "A"
+msgstr "A"
+
+#: translating.xml:576(para)
+msgid ""
+"Format the number using uppercase Latin letters: A, B, C, D, E, F, G, H, I, "
+"J, K, L."
+msgstr ""
+
+#: translating.xml:580(literal)
+msgid "a"
+msgstr "a"
+
+#: translating.xml:581(para)
+msgid ""
+"Format the number using lowercase Latin letters: a, b, c, d, e, f, g, h, i, "
+"j, k, l."
+msgstr ""
+
+#: translating.xml:585(literal)
+msgid "I"
+msgstr "I"
+
+#: translating.xml:586(para)
+msgid ""
+"Format the number using uppercase Roman numerals: I, II, III, IV, V, VI, VII, "
+"VIII, IX, X, XI, XII:"
+msgstr ""
+
+#: translating.xml:591(para)
+msgid ""
+"Format the number using lowercase Roman numerals: i, ii, iii, iv, v, vi, vii, "
+"viii, ix, x, xi, xii:"
+msgstr ""
+
+#: translating.xml:596(para)
+msgid ""
+"These five numbering systems are unlikely to be sufficient, particularly for "
+"non-Western languages. Translators who would like to format numbers "
+"differently should contact the maintainers, and we can try to add additional "
+"digit formats."
+msgstr ""
+
+#: translating.xml:603(title)
+msgid "Cross Reference Formatters"
+msgstr ""
+
+#: translating.xml:604(para)
+msgid ""
+"Cross reference formatters are used to format the text of a link to another "
+"element in the document. In many languages, how best to format an individual "
+"cross reference will depend on its usage. Often, cross references will need "
+"to be formatted differently based on their grammatical role in a sentence."
+msgstr ""
+
+#: translating.xml:610(para)
+msgid ""
+"The cross reference formatters allow translators to provide multiple "
+"formattings using roles. Documentation authors and translators can then "
+"select the format for a cross reference using the <sgmltag class=\"attribute"
+"\">xrefstyle</sgmltag> attribute on the <sgmltag>xref</sgmltag> element. The "
+"Gnome documentation stylesheets allow <sgmltag class=\"attribute\">xrefstyle</"
+"sgmltag> attributes of the form <sgmltag class=\"attvalue\">role:"
+"<replaceable>somerole</replaceable></sgmltag>, where <replaceable>somerole</"
+"replaceable> is the role to be passed to the cross reference formatter."
+msgstr ""
+
+#: translating.xml:619(para)
+msgid ""
+"Cross reference formatters generally provide the following three format "
+"arguments:"
+msgstr ""
+
+#: translating.xml:625(para)
+msgid ""
+"Insert the title of the element being referenced. For most types of element, "
+"the title is simply provided by the <sgmltag>title</sgmltag> in DocBook. A "
+"few DocBook elements, notably <sgmltag>refentry</sgmltag>, have more "
+"complicated content models. Translators need only reference the argument, and "
+"the stylesheets will determine the title."
+msgstr ""
+
+#: translating.xml:634(para)
+msgid ""
+"Insert the abbreviated title of the element being referenced. Abbreviated "
+"titles are provided by the <sgmltag>titleabbrev</sgmltag> element in DocBook. "
+"If the labeled element does not have an abbreviated title, the title is used "
+"instead."
+msgstr ""
+
+#: translating.xml:642(para)
+msgid ""
+"Insert the fully qualified number of the element being referenced. For most "
+"label formatters, there is a corresponding number formatter that will be "
+"called for this argument."
+msgstr ""
+
+#: translating.xml:648(remark)
+msgid "Insert an example here"
+msgstr ""
+
+#: translating.xml:652(title)
+msgid "Tooltip Formatters"
+msgstr ""
+
+#: translating.xml:653(para)
+msgid ""
+"Each hyperlink in the HTML output is given a tooltip by the stylesheets. "
+"Since hyperlinks can be created using a number of different semantic linking "
+"mechanisms in DocBook, the stylesheets are able to provide rich information "
+"in the hyperlink tooltips. The stylesheets provide tooltip formatters for "
+"various linking mechanisms. These can then be translated to provide rich "
+"information about hyperlinks in any language."
+msgstr ""
+
+#: translating.xml:661(para)
+msgid ""
+"For example, the <sgmltag>email</sgmltag> element in DocBook is converted "
+"into a hyperlink allowing users to send email to the given address. The "
+"Serbian translation for this formatter follows."
+msgstr ""
+
+#: translating.xml:674(para)
+msgid ""
+"Each tooltip formatter will have its own format arguments. Generally, only a "
+"single format argument will be needed, and the translator comments for the "
+"string should clearly specify the valid arguments."
+msgstr ""
+
+#: legal.xml:2(para)
+msgid ""
+"Permission is granted to copy, distribute and/or modify this document under "
+"the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any "
+"later version published by the Free Software Foundation with no Invariant "
+"Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy "
+"of the GFDL at this <ulink url=\"ghelp:fdl\">link</ulink> or in the file "
+"COPYING-DOCS distributed with this manual."
+msgstr ""
+"Das vorliegende Dokument kann gemä� den Bedingungen der GNU Free "
+"Documentation License (GFDL), Version 1.1 oder jeder späteren, von der Free "
+"Software Foundation veröffentlichten Version ohne unveränderbare Abschnitte "
+"sowie ohne Texte auf dem vorderen und hinteren Buchdeckel kopiert, verteilt "
+"und/oder modifiziert werden. Eine Kopie der GFDL finden Sie unter diesem "
+"<ulink type=\"help\" url=\"ghelp:fdl\">Link</ulink> oder in der mit diesem "
+"Handbuch gelieferten Datei COPYING-DOCS."
+
+#: legal.xml:11(para)
+msgid ""
+"This manual is part of a collection of GNOME manuals distributed under the "
+"GFDL. If you want to distribute this manual separately from the collection, "
+"you can do so by adding a copy of the license to the manual, as described in "
+"section 6 of the license."
+msgstr ""
+"Dieses Handbuch ist Teil einer Sammlung von GNOME-Handbüchern, die unter der "
+"GFDL veröffentlicht werden. Wenn Sie dieses Handbuch getrennt von der "
+"Sammlung weiterverbreiten möchten, können Sie das tun, indem Sie eine Kopie "
+"der Lizenz zum Handbuch hinzufügen, wie es in Abschnitt 6 der Lizenz "
+"beschrieben ist."
+
+#: legal.xml:17(para)
+msgid ""
+"Many of the names used by companies to distinguish their products and "
+"services are claimed as trademarks. Where those names appear in any GNOME "
+"documentation, and the members of the GNOME Documentation Project are made "
+"aware of those trademarks, then the names are in capital letters or initial "
+"capital letters."
+msgstr ""
+"Viele der Namen, die von Unternehmen verwendet werden, um ihre Produkte und "
+"Dienstleistungen von anderen zu unterscheiden, sind eingetragene "
+"Warenzeichen. An den Stellen, an denen diese Namen in einer GNOME-"
+"Dokumentation erscheinen, werden die Namen in GroÃ?buchstaben oder mit einem "
+"groÃ?en Anfangsbuchstaben geschrieben, wenn das GNOME-Dokumentationsprojekt "
+"auf diese Warenzeichen hingewiesen wird."
+
+#: legal.xml:30(para)
+msgid ""
+"DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS, WITHOUT WARRANTY OF ANY KIND, "
+"EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT "
+"THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS FREE OF DEFECTS "
+"MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK "
+"AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR MODIFIED "
+"VERSION OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR MODIFIED VERSION "
+"PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY "
+"CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR "
+"CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS "
+"LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS "
+"AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND"
+msgstr ""
+"DIESES DOKUMENT WIRD »WIE VORLIEGEND« GELIEFERT, OHNE GARANTIEN IRGENDEINER "
+"ART, SOWOHL AUSDRÃ?CKLICH GENANNTE ALS AUCH ANGEDEUTETE. DIES BEZIEHT SICH "
+"AUCH OHNE EINSCHRÃ?NKUNG AUF GARANTIEN, DASS DIESES DOKUMENT ODER VERÃ?NDERTE "
+"FASSUNGEN DIESES DOKUMENTS FREI VON HANDELSDEFEKTEN, FÃ?R EINEN BESTIMMTEN "
+"ZWECK GEEIGNET IST ODER DASS ES KEINE RECHTE DRITTER VERLETZT. DAS VOLLE "
+"RISIKO WAS QUALITÃ?T, GENAUIGKEIT UND LEISTUNG DES DOKUMENTS ODER VERÃ?NDERTE "
+"FASSUNGEN DES DOKUMENTS LIEGT BEI IHNEN. SOLLTE EIN DOKUMENT ODER EINE "
+"VERÃ?NDERTE FASSUNG DAVON FEHLER IRGENDEINER ART BEINHALTEN, TRAGEN SIE (NICHT "
+"DER URSPRUNGSAUTOR, DER AUTOR ODER EIN MITWIRKENDER) DIE KOSTEN FÃ?R "
+"NOTWENDIGE DIENSTLEISTUNGEN, REPARATUREN ODER FEHLERKORREKTUREN. DIESER "
+"HAFTUNGSAUSSCHLUSS IST EIN ESSENZIELLER TEIL DIESER LIZENZ. DIE VERWENDUNG "
+"EINES DOKUMENTS ODER EINER VERÃ?NDERTEN VERSION DES DOKUMENTS IST NICHT "
+"GESTATTET AUÃ?ER UNTER BEACHTUNG DIESES HAFTUNGSAUSSCHLUSSES UND"
+
+#: legal.xml:47(para)
+msgid ""
+"UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING "
+"NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY "
+"CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE "
+"DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR "
+"ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY "
+"CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK "
+"STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR "
+"LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED "
+"VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE "
+"POSSIBILITY OF SUCH DAMAGES."
+msgstr ""
+"UNTER KEINEN UMSTÃ?NDEN UND AUF BASIS KEINER RECHTSGRUNDLAGE, EGAL OB DURCH "
+"UNERLAUBTEN HANDLUNGEN (EINSCHLIEÃ?LICH FAHRLÃ?SSIGKEIT), VERTRAG ODER "
+"ANDERWEITIG KANN DER AUTOR, URSPRUNGSAUTOR, EIN MITWIRKENDER ODER EIN "
+"VERTRIEBSPARTNER DIESES DOKUMENTS ODER EINER VERÃ?NDERTEN FASSUNG DES "
+"DOKUMENTS ODER EIN ZULIEFERER EINER DIESER PARTEIEN, HAFTBAR GEMACHT WERDEN "
+"FÃ?R DIREKTE, INDIREKTE, SPEZIELLE, VERSEHENTLICHE ODER FOLGESCHÃ?DEN JEGLICHER "
+"ART, EINSCHLIEÃ?LICH UND OHNE EINSCHRÃ?NKUNGEN SCHÃ?DEN DURCH VERLUST VON "
+"KULANZ, ARBEITSAUSFALL, COMPUTERVERSAGEN ODER COMPUTERFEHLFUNKTIONEN ODER "
+"ALLE ANDEREN SCHÃ?DEN ODER VERLUSTE, DIE SICH AUS ODER IN VERBINDUNG MIT DER "
+"VERWENDUNG DES DOKUMENTS UND VERÃ?NDERTER FASSUNGEN DES DOKUMENTS ERGEBEN, "
+"AUCH WENN DIE OBEN GENANNTEN PARTEIEN Ã?BER DIE MÃ?GLICHKEIT SOLCHER SCHÃ?DEN "
+"INFORMIERT WAREN."
+
+#: legal.xml:24(para)
+msgid ""
+"DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS "
+"OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: "
+"<placeholder-1/>"
+msgstr ""
+"DAS DOKUMENT UND VERÃ?NDERTE FASSUNGEN DES DOKUMENTS WERDEN UNTER DEN "
+"BEDINGUNGEN DER GNU FREE DOCUMENTATION LICENSE ZUR VERFÃ?GUNG GESTELLT MIT DEM "
+"WEITERGEHENDEN VERSTÃ?NDNIS, DASS: <placeholder-1/>"
+
+#: gnome-doc-xslt.xml:7(title)
+msgid "GNOME Documentation XSLT Manual"
+msgstr "GNOME Dokumentation-XSLT-Handbuch"
+
+#: gnome-doc-xslt.xml:10(para)
+msgid ""
+"The GNOME Documentation XSLT stylesheets were created to provide fast DocBook "
+"to HTML conversion for real-time document viewing in GNOME's help browser, "
+"<application>Yelp.</application>"
+msgstr ""
+
+#: gnome-doc-xslt.xml:15(year)
+msgid "2004"
+msgstr "2004"
+
+#: gnome-doc-xslt.xml:17(holder)
+msgid "Shaun McCance"
+msgstr "Shaun McCance"
+
+#: gnome-doc-xslt.xml:21(publishername) gnome-doc-xslt.xml:33(orgname)
+#: gnome-doc-xslt.xml:45(orgname)
+msgid "GNOME Documentation Project"
+msgstr "GNOME-Dokumentationsprojekt"
+
+#: gnome-doc-xslt.xml:28(firstname)
+msgid "Shaun"
+msgstr "Shaun"
+
+#: gnome-doc-xslt.xml:30(surname)
+msgid "McCance"
+msgstr "McCance"
+
+#: gnome-doc-xslt.xml:36(email)
+msgid "shaunm gnome org"
+msgstr "shaunm gnome org"
+
+#: gnome-doc-xslt.xml:40(firstname)
+msgid "Brent"
+msgstr "Brent"
+
+#: gnome-doc-xslt.xml:42(surname)
+msgid "Smith"
+msgstr "Smith"
+
+#: gnome-doc-xslt.xml:48(email)
+msgid "gnome nextreality net"
+msgstr "gnome nextreality net"
+
+#: gnome-doc-xslt.xml:54(revnumber)
+msgid "0.1"
+msgstr "0.1"
+
+#: gnome-doc-xslt.xml:56(date)
+msgid "2004-03-31"
+msgstr "31. März 2004"
+
+#: gnome-doc-xslt.xml:60(revnumber)
+msgid "0.2"
+msgstr "0.2"
+
+#: gnome-doc-xslt.xml:62(date)
+msgid "2006-02-11"
+msgstr "11. Februar 2006"
+
+#: gnome-doc-xslt.xml:68(title)
+msgid "Introduction"
+msgstr "Einführung"
+
+#: gnome-doc-xslt.xml:70(para)
+msgid "The GNOME XSLT Stylesheets are used to generate HTML from DocBook files."
+msgstr ""
+"Die GNOME XSLT-Stilvorlagen werden verwendet, um HTML aus DocBook-Dateien zu "
+"erzeugen."
+
+#: gnome-doc-xslt.xml:75(para)
+msgid ""
+"To provide real-time translation of DocBook into HTML. The GNOME Help "
+"Browser, <application>Yelp</application>, uses these stylesheets to format "
+"help documents."
+msgstr ""
+"Bereitstellung einer Ã?bertragung von DocBook in HTML in Echtzeit. Der GNOME "
+"Hilfebrowser <application>Yelp</application> verwendet diese Stilvorlagen zur "
+"Formatierung von Hilfedokumenten."
+
+#: gnome-doc-xslt.xml:81(para)
+msgid "To provide a customized look and feel for GNOME's documentation."
+msgstr ""
+"Bereitstellung eines benutzerdefinierten Erscheinungsbildes für die "
+"Dokumentation von GNOME."
+
+#: gnome-doc-xslt.xml:86(para)
+msgid "To provide translation support for GNOME documentation."
+msgstr "Unterstützung für die �bersetzung der GNOME-Dokumentation."
+
+#: gnome-doc-xslt.xml:73(para)
+msgid "Some of the goals of these stylesheets are:<placeholder-1/>"
+msgstr "Einige der Ziele dieser Stilvorlagen sind:<placeholder-1/>"
+
+#: gnome-doc-xslt.xml:92(title)
+msgid "Using the Stylesheets"
+msgstr "Verwendung der Stilvorlagen"
+
+#: gnome-doc-xslt.xml:94(para)
+msgid ""
+"To use the stylesheets you should be familiar with the <application>xsltproc</"
+"application> application. The first argument is the location of the "
+"<filename>db2html.xsl</filename> stylesheet. The second argument is the top-"
+"level docbook file for which to generate the HTML."
+msgstr ""
+"Um die Stilvorlagen zu verwenden, sollten Sie mit der Anwendung "
+"<application>xsltproc</application> vertraut sein. Das erste Argument ist der "
+"Ort der <filename>db2html.xsl</filename>-Stilvorlage. Das zweite Argument ist "
+"die Basis-DocBook-Datei, aus welcher HTML erzeugt werden soll."
+
+#: gnome-doc-xslt.xml:101(title)
+msgid "Generating HTML from a DocBook file"
+msgstr "Erstellung von HTML aus einer DocBook-Datei"
+
+#: gnome-doc-xslt.xml:103(prompt)
+msgid "$"
+msgstr "$"
+
+#: gnome-doc-xslt.xml:103(screen)
+#, no-wrap
+msgid "<placeholder-1/> xsltproc /usr/share/xml/gnome/xslt/docbook/html/db2html.xsl &lt;docbook file&gt;"
+msgstr "<placeholder-1/> xsltproc /usr/share/xml/gnome/xslt/docbook/html/db2html.xsl &lt;docbook file&gt;"
+
+#: gnome-doc-xslt.xml:106(para)
+msgid ""
+"For more information on <application>xsltproc</application> and the "
+"<application>libxslt</application> libraries, see <ulink url=\"http://www.";
+"xmlsoft.org/\">http://xmlsoft.org/</ulink>."
+msgstr ""
+"Weitere Informationen über <application>xsltproc</application> und die "
+"<application>libxslt</application>-Bibliotheken finden Sie auf <ulink url="
+"\"http://www.xmlsoft.org/\";>http://xmlsoft.org/</ulink>."
+
+#: gnome-doc-xslt.xml:111(title)
+msgid "XInclude Processing"
+msgstr "XInclude-Verarbeitung"
+
+#: gnome-doc-xslt.xml:113(para)
+msgid ""
+"If you make use of <ulink url=\"http://www.w3.org/TR/xinclude/\";>XInclude</"
+"ulink> to include other files in your document, then you must use the "
+"<parameter>--xinclude</parameter> parameter to generate the complete DocBook "
+"file before processing it with the <filename>db2html.xsl</filename> stylesheet"
+"(s)."
+msgstr ""
+
+#: gnome-doc-xslt.xml:123(title)
+msgid "Specifying Parameters"
+msgstr "Angeben von Parametern"
+
+#: gnome-doc-xslt.xml:125(para)
+msgid ""
+"There are a number of parameters available in the stylesheets which you can "
+"set to customize the generated html. An exhaustive list is available in the "
+"following sections, but we will go over a few of the more commonly used ones "
+"in this section."
+msgstr ""
+
+#: gnome-doc-xslt.xml:130(para)
+msgid ""
+"To specify a parameter to the stylesheets, use the <parameter>--stringparam</"
+"parameter> option of the <application>xsltproc</application> application."
+msgstr ""
+
+#: gnome-doc-xslt.xml:136(term)
+msgid "db.chunk.chunk_top"
+msgstr "db.chunk.chunk_top"
+
+#: gnome-doc-xslt.xml:141(para)
+msgid ""
+"Chunking refers to creating a separate output file for an element. For "
+"example, if there are three <literal>&lt;sect1&gt;</literal> elements within "
+"a document, (with no subsections) then there will be three files generated "
+"for each element. Incidentally, the name of the files will be the same as the "
+"element's <literal>id</literal> attribute."
+msgstr ""
+
+#: gnome-doc-xslt.xml:139(para)
+msgid ""
+"Set this parameter to <literal>1</literal> if you want the stylesheets to "
+"chunk<placeholder-1/> the top level element (<literal>&lt;article&gt;</"
+"literal> or <literal>&lt;book&gt;</literal>) into a file called "
+"<filename>index.xhtml</filename>."
+msgstr ""
+
+#: gnome-doc-xslt.xml:156(term)
+msgid "db.chunk.max_depth"
+msgstr "db.chunk.max_depth"
+
+#: gnome-doc-xslt.xml:159(para)
+msgid ""
+"Specifies the maximum depth of chunked elements specified in <parameter>db."
+"chunk.chunks</parameter> parameter."
+msgstr ""
+
+#: gnome-doc-xslt.xml:165(term)
+msgid "db.chunk.extension"
+msgstr "db.chunk.extension"
+
+#: gnome-doc-xslt.xml:168(para)
+msgid ""
+"Set this parameter to <literal>the extension</literal> you would like for the "
+"chunked output files."
+msgstr ""
+
+#: gnome-doc-xslt.xml:175(title)
+msgid "Example of specifying stylesheet parameters"
+msgstr ""
+
+#: gnome-doc-xslt.xml:177(para)
+msgid ""
+"<screen><prompt>$</prompt> xsltproc \\\n"
+"   --stringparam db.chunk.chunk_top 1        \\\n"
+"   --stringparam db.chunk.max_depth 1        \\\n"
+"   --stringparam db.chunk.extension '.html'  \\\n"
+"   /usr/share/xml/gnome/xslt/docbook/html/db2html.xsl \\\n"
+"   &lt;path to docbook file&gt;</screen><xref linkend=\"example-parameters\"/"
+"> will chunk the top level element, chunk to a maximum depth of 1 and chunk "
+"the title page."
+msgstr ""
+
+#: gnome-doc-xslt.xml:189(title)
+msgid "Limitations"
+msgstr "Einschränkungen"
+
+#: gnome-doc-xslt.xml:191(para)
+msgid ""
+"Currently, the stylesheets require that there be an <literal>id</literal> "
+"attribute on each chunked element."
+msgstr ""
+"Gegenwärtig erfordern die Stilvorlagen ein <literal>id</literal>-Attribut zu "
+"jedem enthaltenen Element."
+
+#: gnome-doc-xslt.xml:198(title)
+msgid "Stylesheet Reference"
+msgstr "Referenz der Stilvorlagen"
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
+#: gnome-doc-xslt.xml:0(None)
+msgid "translator-credits"
+msgstr "Mario Blättermann <mariobl gnome org>, 2009"
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]