88# zkonge, 2018
99# Freesand Leo <[email protected] >, 20181010# allenjuly7 <[email protected] >, 201911+ # Siyuan Xu <[email protected] >, 20191112#
1213#, fuzzy
1314msgid ""
@@ -16,7 +17,7 @@ msgstr ""
1617"Report-Msgid-Bugs-To : \n "
1718"POT-Creation-Date : 2019-05-18 11:29+0900\n "
1819"PO-Revision-Date : 2017-02-16 17:46+0000\n "
19- "
Last-Translator :
allenjuly7 <[email protected] >, 2019\n"
20+ "
Last-Translator :
Siyuan Xu <[email protected] >, 2019\n"
2021"Language-Team : Chinese (China) (https://www.transifex.com/python-doc/teams/5390/zh_CN/)\n "
2122"MIME-Version : 1.0\n "
2223"Content-Type : text/plain; charset=UTF-8\n "
@@ -84,6 +85,9 @@ msgid ""
8485" from the uppercase letter 'I'. They'll usually look the same, but these "
8586"are two different characters that have different meanings."
8687msgstr ""
88+ "一个**字符**是文本的最小可能部件。‘A’、‘B’、‘C’ 等都是不同的字符。‘È’ 和 ‘Í’ "
89+ "也一样。字符会随着语言或者上下文的变化而变化。比如,‘Ⅰ’ 是一个表示 “罗马数字 1” 的字符,它与大写字母 ‘I’ "
90+ "不同。它们常常看起来相同,但这是两个有着不同含义的不同字符。"
8791
8892#: ../../howto/unicode.rst:42
8993msgid ""
@@ -93,12 +97,14 @@ msgid ""
9397"standard and in this document, a code point is written using the notation "
9498"``U+265E`` to mean the character with value ``0x265e`` (9,822 in decimal)."
9599msgstr ""
100+ "Unicode 标准描述了**码位**如何表示字符。一个码位的值是在 0 到 0x10FFFF (大约 110 万个值,目前有其中 11 "
101+ "万个被指派)。在这一标准中并且在这一文档中,一个码位写作 ``U+265E`` 来表示拥有值 ``0x265e`` 的字符(十进制下为 9,822)。"
96102
97103#: ../../howto/unicode.rst:49
98104msgid ""
99105"The Unicode standard contains a lot of tables listing characters and their "
100106"corresponding code points:"
101- msgstr ""
107+ msgstr "Unicode 标准包含了许多表格来列出字符和对应的码位。 "
102108
103109#: ../../howto/unicode.rst:70
104110msgid ""
@@ -108,6 +114,8 @@ msgid ""
108114" KNIGHT', '♞'. In informal contexts, this distinction between code points "
109115"and characters will sometimes be forgotten."
110116msgstr ""
117+ "严格地说,这些定义暗示了这样的说法是没有意义的:“这是字符 ``U+265E``”。``U+265E`` 是一个码位,其代表了某特定的字符 —— "
118+ "在这一情形下,它代表了字符 “国际象棋黑方骑士(黑马)” ‘♞’。在非正式上下文中,码位和字符的差异有时会被忽略。"
111119
112120#: ../../howto/unicode.rst:77
113121msgid ""
@@ -118,10 +126,13 @@ msgid ""
118126"to worry about glyphs; figuring out the correct glyph to display is "
119127"generally the job of a GUI toolkit or a terminal's font renderer."
120128msgstr ""
129+ "一个字符在屏幕上或在纸上被表示为一组图形元素,被称为**字形**。比如,大写字母 A "
130+ "的字形,是斜向的两笔和水平的一笔,而具体的细节取决于所使用的字体。大部分 Python "
131+ "代码不必担心字形,找到应被显示的正确字形一般来说是用户图形界面工具箱或者终端的字体渲染器的工作。"
121132
122133#: ../../howto/unicode.rst:86
123134msgid "Encodings"
124- msgstr ""
135+ msgstr "编码 "
125136
126137#: ../../howto/unicode.rst:88
127138msgid ""
@@ -132,13 +143,18 @@ msgid ""
132143"rules for translating a Unicode string into a sequence of bytes are called a"
133144" **character encoding**, or just an **encoding**."
134145msgstr ""
146+ "上一段可以归结为:一个 Unicode 字符串是一系列码位(从 0 到 ``0x10FFFF`` 或者说十进制的 1,114,111 "
147+ "的数字)组成的序列。这一序列在内存中需要被表示为一组**码元**,然后**码元** 会对应到包含八个二进制位的字节。将 Unicode "
148+ "字符串翻译成字节序列的规则被称为**字符编码**,或者**编码**。"
135149
136150#: ../../howto/unicode.rst:96
137151msgid ""
138152"The first encoding you might think of is using 32-bit integers as the code "
139153"unit, and then using the CPU's representation of 32-bit integers. In this "
140154"representation, the string \" Python\" might look like this:"
141155msgstr ""
156+ "你可能会想到的第一种编码是使用一个 32 位的整数来代表一个代码位,然后使用 CPU 对 32 位整数的表达方式。在这一表达方式中,字符串 "
157+ "“Python” 可能看起来像是这样:"
142158
143159#: ../../howto/unicode.rst:106
144160msgid ""
0 commit comments