# translation of fontconfig_2.2.2-2_templates.po to German # # Translators, if you are not familiar with the PO format, gettext # documentation is worth reading, especially sections dedicated to # this format, e.g. by running: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # Some information specific to po-debconf are available at # /usr/share/doc/po-debconf/README-trans # or http://www.debian.org/intl/l10n/po-debconf/README-trans# # Developers do not need to manually edit POT or PO files. # Erik Schanze , 2004. # msgid "" msgstr "" "Project-Id-Version: fontconfig_2.2.3-3_de\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2005-03-02 13:41-0800\n" "PO-Revision-Date: 2004-11-13 17:50+0100\n" "Last-Translator: Erik Schanze \n" "Language-Team: German \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: KBabel 1.3.1\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Type: select #. Choices #: ../fontconfig.templates:3 msgid "Native, Autohinter, None" msgstr "" #. Type: select #. Description #: ../fontconfig.templates:5 #, fuzzy msgid "With what method should fonts be hinted?" msgstr "Wie sollen Schriften gerendert werden?" #. Type: select #. Description #: ../fontconfig.templates:5 msgid "" "The FreeType font library can adjust glyph outlines to accomodate the pixel " "grid for improved legibility. This process is called \"hinting\". FreeType " "can either use the hints built-in to each font or it can use a format-" "indepedent Autohinter. For most font formats, using the format-specific " "hints generates better results. However, many freely available TrueType " "format fonts don't include any hints at all. When loading such a font, " "unless you specifically ask to use the Autohinter, these fonts will end up " "unhinted, which will make them appear fuzzy on the screen." msgstr "" #. Type: select #. Description #: ../fontconfig.templates:5 msgid "" "If the TrueType fonts you use most include hints, then the Native hinter " "gives better results. However, if the fonts you use most do not include " "such hints, then the Autohinter will work better. Yes, FreeType should do " "this automatically." msgstr "" #. Type: select #. Description #: ../fontconfig.templates:5 msgid "" "You can also select None to disable all hinting and make your screen look " "like Mac OS X." msgstr "" #. Type: select #. Choices #: ../fontconfig.templates:28 msgid "Automatic, Enable, Disable" msgstr "" #. Type: select #. Description #: ../fontconfig.templates:30 msgid "Should font be rendered using sub-pixel elements?" msgstr "" #. Type: select #. Description #: ../fontconfig.templates:30 msgid "" "With known sub-pixel geometry, LCD screens can synthesize higher resolution " "in one dimension. Taking advantage of this when rendering glyphs sharpens " "the appearance of text on the screen. This can cause color artifacts, " "especially when rendering unhinted or autohinted fonts." msgstr "" #. Type: select #. Description #: ../fontconfig.templates:30 msgid "" "This option selects when sub-pixel rendering should be used. Automatic " "enables sub-pixel rendering whenever the X server detects an LCD monitor, " "which it can generally do when the monitor is built into the computer or " "connected with a digital (DVI) cable. Enable forces the system to use sub-" "pixel rendering while Disable forces the system to not use sub-pixel " "rendering." msgstr "" #. Type: boolean #. Description #: ../fontconfig.templates:46 msgid "Enable bitmapped fonts by default?" msgstr "Standardmäßig Bitmap-Schriften verwenden?" #. Type: boolean #. Description #: ../fontconfig.templates:46 msgid "" "By default, only outline fonts are used by applications which support " "fontconfig. Outline fonts are fonts which scale well to various sizes. In " "contrast, bitmapped fonts are often lower quality. Enabling this option will " "affect the systemwide default; this and many other fontconfig options may be " "enabled or disabled on a per-user basis." msgstr "" "Standardmäßig werden von Anwendungen, die fontconfig unterstützen, nur " "Outline-Schriften verwendet. Outline-Schriften können gut in verschiedene " "Größen skaliert werden. Bitmap-Schriften sind im Gegensatz dazu oft von " "geringerer Qualität. Mit dem Einschalten dieser Option wird sie zum " "systemweiten Standard; diese und viele andere Einstellungen von fontconfig " "können benutzerbezogen ein- und ausgeschaltet werden." #~ msgid "" #~ "Bytecode interpreter (CRT screens), Autohinter, Subpixel rendering (LCD " #~ "screens)" #~ msgstr "" #~ "Bytecode-Interpreter (Röhrenmonitore), Autohinter, Subpixel-Rendering " #~ "(Flachbildschirme)" #~ msgid "" #~ "The Freetype font library is able to render fonts with different methods. " #~ "Depending on your hardware and the fonts you generally use, some will " #~ "give better results." #~ msgstr "" #~ "Die Schriftart-Bibliothek Freetype kann Schriften verschiedenartig " #~ "rendern. Von Ihren Geräten und den normalerweise genutzten Schriften, " #~ "hängt es ab, welche Methode zu besseren Ergebnissen führt." #~ msgid "" #~ "The autohinter module is the default; it gives correct results on most " #~ "configurations. The bytecode interpreter renders fonts very sharply, and " #~ "is often a better choice if you are using a cathode-ray screen. On the " #~ "other hand, the subpixel rendering method is optimized for high-quality " #~ "rendering on most liquid crystal displays." #~ msgstr "" #~ "Das Modul Autohinter ist voreingestellt; es führt mit den meisten Geräten " #~ "zu guten Ergebnissen. Der Bytecode-Interpreter stellt Schriften sehr " #~ "scharfkantig dar und ist bei Kathodenstrahl-Monitoren meist die bessere " #~ "Wahl. Dagegen ist das Subpixel-Rendering auf hohe Render-Qualität für die " #~ "meisten Flüssigkristall-Bildschirme optimiert."