RetroSearch Browse

Tue Oct 25 01:13:51 CEST 2005 · http://mail.python.org/pipermail/python-dev/2005-October/057605.html

M.-A. Lemburg:

> Unicode has the concept of combining code points, e.g. you can
> store an "é" (e with a accent) as "e" + "'". Now if you slice
> off the accent, you'll break the character that you encoded
> using combining code points.
> ...
>     next_<indextype>(u, index) -> integer
>
>         Returns the Unicode object index for the start of the next
>         <indextype> found after u[index] or -1 in case no next element
>         of this type exists.

   Should entity breakage be further discouraged by returning a slice
here rather than an object index?

   Something like:

i = first_grapheme(u)
x = 0
while x < width and u[i] != "\n":
   x, _ = draw(u[i], (x, y))
   i = next_grapheme(u, i)

   Neil

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

Showing content from http://mail.python.org/pipermail/python-dev/2005-October/057605.html below:

[Python-Dev] Divorcing str and unicode (no more implicit conversions).