RetroSearch Browse

Thu Oct 6 03:28:58 CEST 2011 · https://mail.python.org/pipermail/python-dev/2011-October/113869.html

On 10/5/2011 7:53 PM, Victor Stinner wrote:
> Le mercredi 5 octobre 2011 21:25:22, Terry Reedy a écrit :
>>> +           - PyUnicode_1BYTE_KIND (1):
>>> +
>>> +             * character type = Py_UCS1 (8 bits, unsigned)
>>> +             * if ascii is 1, at least one character must be in range
>>> +               U+80-U+FF, otherwise all characters must be in range
>>> U+00-U+7F
>>
>> Given that 1==True, this looks backwards.
>
> I changed the doc to:
>
> PyUnicode_1BYTE_KIND (1):
>
>   * character type = Py_UCS1 (8 bits, unsigned)
>   * if ascii is set, all characters must be in range
>     U+0000-U+007F, otherwise at least one character must be in range
>     U+0080-U+00FF
>
> Is it better?

yes

>>> +           - PyUnicode_2BYTE_KIND (2):
>>> +
>>> +             * character type = Py_UCS2 (16 bits, unsigned)
>>> +             * at least one character must be in range U+0100-U+1FFFF
>>
>> /U+1FFFF/U+FFFF/ ?
>
> Oops, correct. I fixed the doc, thanks for the review.

Glad I could help with that, even though not the code details.

-- 
Terry Jan Reedy

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-October/113869.html below:

[Python-Dev] [Python-checkins] cpython: Document requierements of Unicode kinds