debian/po/de.po

   1 # translation of fontconfig_2.2.2-2_templates.po to German
   2 #
   3 #    Translators, if you are not familiar with the PO format, gettext
   4 #    documentation is worth reading, especially sections dedicated to
   5 #    this format, e.g. by running:
   6 #         info -n '(gettext)PO Files'
   7 #         info -n '(gettext)Header Entry'
   8 #    Some information specific to po-debconf are available at
   9 #            /usr/share/doc/po-debconf/README-trans
  10 #         or http://www.debian.org/intl/l10n/po-debconf/README-trans#
  11 #    Developers do not need to manually edit POT or PO files.
  12 # Erik Schanze <mail@erikschanze.de>, 2004.
  13 #
  14 msgid ""
  15 msgstr ""
  16 "Project-Id-Version: fontconfig_2.2.3-3_de\n"
  17 "Report-Msgid-Bugs-To: \n"
  18 "POT-Creation-Date: 2005-03-02 13:41-0800\n"
  19 "PO-Revision-Date: 2004-11-13 17:50+0100\n"
  20 "Last-Translator: Erik Schanze <mail@erikschanze.de>\n"
  21 "Language-Team: German <debian-l10n-german@lists.debian.org>\n"
  22 "MIME-Version: 1.0\n"
  23 "Content-Type: text/plain; charset=UTF-8\n"
  24 "Content-Transfer-Encoding: 8bit\n"
  25 "X-Generator: KBabel 1.3.1\n"
  26 "Plural-Forms:  nplurals=2; plural=(n != 1);\n"
  27
  28 #. Type: select
  29 #. Choices
  30 #: ../fontconfig.templates:3
  31 msgid "Native, Autohinter, None"
  32 msgstr ""
  33
  34 #. Type: select
  35 #. Description
  36 #: ../fontconfig.templates:5
  37 #, fuzzy
  38 msgid "With what method should fonts be hinted?"
  39 msgstr "Wie sollen Schriften gerendert werden?"
  40
  41 #. Type: select
  42 #. Description
  43 #: ../fontconfig.templates:5
  44 msgid ""
  45 "The FreeType font library can adjust glyph outlines to accomodate the pixel "
  46 "grid for improved legibility.  This process is called \"hinting\".  FreeType "
  47 "can either use the hints built-in to each font or it can use a format-"
  48 "indepedent Autohinter.  For most font formats, using the format-specific "
  49 "hints generates better results.  However, many freely available TrueType "
  50 "format fonts don't include any hints at all. When loading such a font, "
  51 "unless you specifically ask to use the Autohinter, these fonts will end up "
  52 "unhinted, which will make them appear fuzzy on the screen."
  53 msgstr ""
  54
  55 #. Type: select
  56 #. Description
  57 #: ../fontconfig.templates:5
  58 msgid ""
  59 "If the TrueType fonts you use most include hints, then the Native hinter "
  60 "gives better results.  However, if the fonts you use most do not include "
  61 "such hints, then the Autohinter will work better.  Yes, FreeType should do "
  62 "this automatically."
  63 msgstr ""
  64
  65 #. Type: select
  66 #. Description
  67 #: ../fontconfig.templates:5
  68 msgid ""
  69 "You can also select None to disable all hinting and make your screen look "
  70 "like Mac OS X."
  71 msgstr ""
  72
  73 #. Type: select
  74 #. Choices
  75 #: ../fontconfig.templates:28
  76 msgid "Automatic, Enable, Disable"
  77 msgstr ""
  78
  79 #. Type: select
  80 #. Description
  81 #: ../fontconfig.templates:30
  82 msgid "Should font be rendered using sub-pixel elements?"
  83 msgstr ""
  84
  85 #. Type: select
  86 #. Description
  87 #: ../fontconfig.templates:30
  88 msgid ""
  89 "With known sub-pixel geometry, LCD screens can synthesize higher resolution "
  90 "in one dimension.  Taking advantage of this when rendering glyphs sharpens "
  91 "the appearance of text on the screen.  This can cause color artifacts, "
  92 "especially when rendering unhinted or autohinted fonts."
  93 msgstr ""
  94
  95 #. Type: select
  96 #. Description
  97 #: ../fontconfig.templates:30
  98 msgid ""
  99 "This option selects when sub-pixel rendering should be used.  Automatic "
 100 "enables sub-pixel rendering whenever the X server detects an LCD monitor, "
 101 "which it can generally do when the monitor is built into the computer or "
 102 "connected with a digital (DVI) cable.  Enable forces the system to use sub-"
 103 "pixel rendering while Disable forces the system to not use sub-pixel "
 104 "rendering."
 105 msgstr ""
 106
 107 #. Type: boolean
 108 #. Description
 109 #: ../fontconfig.templates:46
 110 msgid "Enable bitmapped fonts by default?"
 111 msgstr "Standardmäßig Bitmap-Schriften verwenden?"
 112
 113 #. Type: boolean
 114 #. Description
 115 #: ../fontconfig.templates:46
 116 msgid ""
 117 "By default, only outline fonts are used by applications which support "
 118 "fontconfig.  Outline fonts are fonts which scale well to various sizes.  In "
 119 "contrast, bitmapped fonts are often lower quality. Enabling this option will "
 120 "affect the systemwide default; this and many other fontconfig options may be "
 121 "enabled or disabled on a per-user basis."
 122 msgstr ""
 123 "Standardmäßig werden von Anwendungen, die fontconfig unterstützen, nur "
 124 "Outline-Schriften verwendet.  Outline-Schriften können gut in verschiedene "
 125 "Größen skaliert werden.  Bitmap-Schriften sind im Gegensatz dazu oft von "
 126 "geringerer Qualität. Mit dem Einschalten dieser Option wird sie zum "
 127 "systemweiten Standard; diese und viele andere Einstellungen von fontconfig "
 128 "können benutzerbezogen ein- und ausgeschaltet werden."
 129
 130 #~ msgid ""
 131 #~ "Bytecode interpreter (CRT screens), Autohinter, Subpixel rendering (LCD "
 132 #~ "screens)"
 133 #~ msgstr ""
 134 #~ "Bytecode-Interpreter (Röhrenmonitore), Autohinter, Subpixel-Rendering "
 135 #~ "(Flachbildschirme)"
 136
 137 #~ msgid ""
 138 #~ "The Freetype font library is able to render fonts with different methods. "
 139 #~ "Depending on your hardware and the fonts you generally use, some will "
 140 #~ "give better results."
 141 #~ msgstr ""
 142 #~ "Die Schriftart-Bibliothek Freetype kann Schriften verschiedenartig "
 143 #~ "rendern. Von Ihren Geräten und den normalerweise genutzten Schriften, "
 144 #~ "hängt es ab, welche Methode zu besseren Ergebnissen führt."
 145
 146 #~ msgid ""
 147 #~ "The autohinter module is the default; it gives correct results on most "
 148 #~ "configurations. The bytecode interpreter renders fonts very sharply, and "
 149 #~ "is often a better choice if you are using a cathode-ray screen. On the "
 150 #~ "other hand, the subpixel rendering method is optimized for high-quality "
 151 #~ "rendering on most liquid crystal displays."
 152 #~ msgstr ""
 153 #~ "Das Modul Autohinter ist voreingestellt; es führt mit den meisten Geräten "
 154 #~ "zu guten Ergebnissen. Der Bytecode-Interpreter stellt Schriften sehr "
 155 #~ "scharfkantig dar und ist bei Kathodenstrahl-Monitoren meist die bessere "
 156 #~ "Wahl. Dagegen ist das Subpixel-Rendering auf hohe Render-Qualität für die "
 157 #~ "meisten Flüssigkristall-Bildschirme optimiert."