155 lines
5.5 KiB
Plaintext
155 lines
5.5 KiB
Plaintext
|
#
|
|||
|
|
# 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.
|
|||
|
|
#
|
|||
|
|
msgid ""
|
|||
|
|
msgstr ""
|
|||
|
|
"Project-Id-Version: fontconfig\n"
|
|||
|
|
"Report-Msgid-Bugs-To: \n"
|
|||
|
|
"POT-Creation-Date: 2005-03-02 13:41-0800\n"
|
|||
|
|
"PO-Revision-Date: 2004-10-24 18:49+0200\n"
|
|||
|
|
"Last-Translator: Miroslav Kure <kurem@debian.cz>\n"
|
|||
|
|
"Language-Team: Czech <kurem@debian.cz>\n"
|
|||
|
|
"MIME-Version: 1.0\n"
|
|||
|
|
"Content-Type: text/plain; charset=ISO-8859-2\n"
|
|||
|
|
"Content-Transfer-Encoding: 8bit\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 "Kter<65> metoda se m<> pou<6F><75>t pro vykreslov<6F>n<EFBFBD> textu?"
|
|||
|
|
|
|||
|
|
#. 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 "Povolit implicitn<74> bitmapov<6F> fonty?"
|
|||
|
|
|
|||
|
|
#. 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 ""
|
|||
|
|
"Standardn<64> jsou v aplikac<61>ch podporuj<75>c<EFBFBD>ch fontconfig pou<6F><75>v<EFBFBD>ny pouze "
|
|||
|
|
"obrysov<6F> fonty. Tyto fonty se velmi dob<6F>e zv<7A>t<EFBFBD>uj<75> a zmen<65>uj<75>. Oproti nim "
|
|||
|
|
"mohou zv<7A>t<EFBFBD>ovan<61> bitmapov<6F> fonty vypadat kostrbat<61>. Tato volba ovlivn<76> "
|
|||
|
|
"implicitn<74> nastaven<65> cel<65>ho syst<73>mu, nicm<63>n<EFBFBD> u<>ivatel<65> si ji mohou zm<7A>nit ve "
|
|||
|
|
"sv<73>m osobn<62>m nastaven<65>."
|
|||
|
|
|
|||
|
|
#~ msgid ""
|
|||
|
|
#~ "Bytecode interpreter (CRT screens), Autohinter, Subpixel rendering (LCD "
|
|||
|
|
#~ "screens)"
|
|||
|
|
#~ msgstr ""
|
|||
|
|
#~ "Interpret bytek<65>du (CRT monitory), Autohinter, Podpixelov<6F> renderov<6F>n<EFBFBD> "
|
|||
|
|
#~ "(LCD obrazovky)"
|
|||
|
|
|
|||
|
|
#~ 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 ""
|
|||
|
|
#~ "Knihovna Freetype um<75> vykreslovat p<>sma r<>zn<7A>mi metodami. Podle va<76>eho "
|
|||
|
|
#~ "hardwaru a typu pou<6F>it<69>ch font<6E> m<><6D>ete s n<>kter<65>mi metodami dos<6F>hnout "
|
|||
|
|
#~ "lep<65><70>ch v<>sledk<64>."
|
|||
|
|
|
|||
|
|
#~ 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 ""
|
|||
|
|
#~ "Modul autohinter je implicitn<74>, proto<74>e d<>v<EFBFBD> spr<70>vn<76> v<>sledky na v<>t<EFBFBD>in<69> "
|
|||
|
|
#~ "konfigurac<61>. Interpret bytek<65>du kresl<73> p<>sma velmi ost<73>e a pokud m<>te "
|
|||
|
|
#~ "klasick<63> monitor, b<>v<EFBFBD> <20>asto lep<65><70> volbou. Analogicky je podpixelov<6F> "
|
|||
|
|
#~ "renderov<6F>n<EFBFBD> p<>izp<7A>sobeno pro vysoce kvalitn<74> v<>stup na v<>t<EFBFBD>in<69> LCD "
|
|||
|
|
#~ "monitor<6F>."
|