[fontconfig.git] / debian / po / zh_CN.po

#
#    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 debconf\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2005-03-02 13:41-0800\n"
"PO-Revision-Date: 2004-11-03 00:14+1300\n"
"Last-Translator: Carlos Liu <carlosliu@users.sourceforge.net>\n"
"Language-Team: Debian Chinese [GB] <debian-chinese-gb@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\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 "您希望使用哪种文本渲染方式？"

#. 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 "默认使用点阵字体吗？"

#. 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 ""
"默认状态下，仅有轮廓字体可以被支持 fontconfig 的程序所使用。轮廓字体可以在不"
"同的尺寸上进行平滑缩放。而相反的，点阵字体通常只能提供低质量的显示效果。开启"
"此选项将会影响整个系统的默认设置。当然，此选项以及其它很多 fontconfig 设置都"
"可以基于每个用户单独进行开启或关闭。"

#~ msgid ""
#~ "Bytecode interpreter (CRT screens), Autohinter, Subpixel rendering (LCD "
#~ "screens)"
#~ msgstr "Bytecode 解释器 (CRT 显示器), 自动微调, 次像素渲染 (LCD 液晶显示器)"

#~ 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 ""
#~ "Freetype 字体库程序可以使用多种不同的方法进行字体渲染。根据您的硬件和通常"
#~ "所使用的字体，其中某些方法会有较好的显示效果。"

#~ 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 ""
#~ "自动微调模块是默认的选项，它能对大多数配置提供正确的显示结果。Bytecode 解"
#~ "释器的字体渲染效果非常锐利，比较适合用于阴极射线管显示器。而次像素渲染方式"
#~ "则是针对液晶显示器上高质量渲染的优化设置。"
Commit	Line	Data
dc2e06ab KP	1	#
	2	# Translators, if you are not familiar with the PO format, gettext
	3	# documentation is worth reading, especially sections dedicated to
	4	# this format, e.g. by running:
	5	# info -n '(gettext)PO Files'
	6	# info -n '(gettext)Header Entry'
	7	#
	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	#
	12	# Developers do not need to manually edit POT or PO files.
	13	#
	14	msgid ""
	15	msgstr ""
	16	"Project-Id-Version: fontconfig debconf\n"
	17	"Report-Msgid-Bugs-To: \n"
	18	"POT-Creation-Date: 2005-03-02 13:41-0800\n"
	19	"PO-Revision-Date: 2004-11-03 00:14+1300\n"
	20	"Last-Translator: Carlos Liu <carlosliu@users.sourceforge.net>\n"
	21	"Language-Team: Debian Chinese [GB] <debian-chinese-gb@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
	26	#. Type: select
	27	#. Choices
	28	#: ../fontconfig.templates:3
	29	msgid "Native, Autohinter, None"
	30	msgstr ""
	31
	32	#. Type: select
	33	#. Description
	34	#: ../fontconfig.templates:5
	35	#, fuzzy
	36	msgid "With what method should fonts be hinted?"
	37	msgstr "您希望使用哪种文本渲染方式？"
	38
	39	#. Type: select
	40	#. Description
	41	#: ../fontconfig.templates:5
	42	msgid ""
	43	"The FreeType font library can adjust glyph outlines to accomodate the pixel "
	44	"grid for improved legibility. This process is called \"hinting\". FreeType "
	45	"can either use the hints built-in to each font or it can use a format-"
	46	"indepedent Autohinter. For most font formats, using the format-specific "
	47	"hints generates better results. However, many freely available TrueType "
	48	"format fonts don't include any hints at all. When loading such a font, "
	49	"unless you specifically ask to use the Autohinter, these fonts will end up "
	50	"unhinted, which will make them appear fuzzy on the screen."
	51	msgstr ""
	52
	53	#. Type: select
	54	#. Description
	55	#: ../fontconfig.templates:5
	56	msgid ""
	57	"If the TrueType fonts you use most include hints, then the Native hinter "
	58	"gives better results. However, if the fonts you use most do not include "
	59	"such hints, then the Autohinter will work better. Yes, FreeType should do "
	60	"this automatically."
	61	msgstr ""
	62
	63	#. Type: select
	64	#. Description
65	#: ../fontconfig.templates:5
66	msgid ""
67	"You can also select None to disable all hinting and make your screen look "
68	"like Mac OS X."
69	msgstr ""
70
71	#. Type: select
72	#. Choices
73	#: ../fontconfig.templates:28
74	msgid "Automatic, Enable, Disable"
75	msgstr ""
76
77	#. Type: select
78	#. Description
79	#: ../fontconfig.templates:30
80	msgid "Should font be rendered using sub-pixel elements?"
81	msgstr ""
82
83	#. Type: select
84	#. Description
85	#: ../fontconfig.templates:30
86	msgid ""
87	"With known sub-pixel geometry, LCD screens can synthesize higher resolution "
88	"in one dimension. Taking advantage of this when rendering glyphs sharpens "
89	"the appearance of text on the screen. This can cause color artifacts, "
90	"especially when rendering unhinted or autohinted fonts."
91	msgstr ""
92
93	#. Type: select
94	#. Description
95	#: ../fontconfig.templates:30
96	msgid ""
97	"This option selects when sub-pixel rendering should be used. Automatic "
98	"enables sub-pixel rendering whenever the X server detects an LCD monitor, "
99	"which it can generally do when the monitor is built into the computer or "
100	"connected with a digital (DVI) cable. Enable forces the system to use sub-"
101	"pixel rendering while Disable forces the system to not use sub-pixel "
102	"rendering."
103	msgstr ""
104
105	#. Type: boolean
106	#. Description
107	#: ../fontconfig.templates:46
108	msgid "Enable bitmapped fonts by default?"
109	msgstr "默认使用点阵字体吗？"
110
111	#. Type: boolean
112	#. Description
113	#: ../fontconfig.templates:46
114	msgid ""
115	"By default, only outline fonts are used by applications which support "
116	"fontconfig. Outline fonts are fonts which scale well to various sizes. In "
117	"contrast, bitmapped fonts are often lower quality. Enabling this option will "
118	"affect the systemwide default; this and many other fontconfig options may be "
119	"enabled or disabled on a per-user basis."
120	msgstr ""
121	"默认状态下，仅有轮廓字体可以被支持 fontconfig 的程序所使用。轮廓字体可以在不"
122	"同的尺寸上进行平滑缩放。而相反的，点阵字体通常只能提供低质量的显示效果。开启"
123	"此选项将会影响整个系统的默认设置。当然，此选项以及其它很多 fontconfig 设置都"
124	"可以基于每个用户单独进行开启或关闭。"
125
126	#~ msgid ""
127	#~ "Bytecode interpreter (CRT screens), Autohinter, Subpixel rendering (LCD "
128	#~ "screens)"
129	#~ msgstr "Bytecode 解释器 (CRT 显示器), 自动微调, 次像素渲染 (LCD 液晶显示器)"
130
131	#~ msgid ""
132	#~ "The Freetype font library is able to render fonts with different methods. "
133	#~ "Depending on your hardware and the fonts you generally use, some will "
134	#~ "give better results."
135	#~ msgstr ""
136	#~ "Freetype 字体库程序可以使用多种不同的方法进行字体渲染。根据您的硬件和通常"
137	#~ "所使用的字体，其中某些方法会有较好的显示效果。"
138
139	#~ msgid ""
140	#~ "The autohinter module is the default; it gives correct results on most "
141	#~ "configurations. The bytecode interpreter renders fonts very sharply, and "
142	#~ "is often a better choice if you are using a cathode-ray screen. On the "
143	#~ "other hand, the subpixel rendering method is optimized for high-quality "
144	#~ "rendering on most liquid crystal displays."
145	#~ msgstr ""
146	#~ "自动微调模块是默认的选项，它能对大多数配置提供正确的显示结果。Bytecode 解"
147	#~ "释器的字体渲染效果非常锐利，比较适合用于阴极射线管显示器。而次像素渲染方式"
148	#~ "则是针对液晶显示器上高质量渲染的优化设置。"