A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2000-May/003886.html below:

[I18n-sig] Re: [Python-Dev] Unicode debate

[I18n-sig] Re: [Python-Dev] Unicode debate [I18n-sig] Re: [Python-Dev] Unicode debatePaul Prescod paul@prescod.net
Tue, 02 May 2000 11:25:33 -0500
Guido van Rossum wrote:
> 
> Aha, then we'll see u == v even though type(u) is type(v) and len(u)
> != len(v).  /F's world will collapse. :-)

There are many levels of equality that are interesting. I don't think we
would move to grapheme equivalence until "the rest of the world" (XML,
Java, W3C, SQL) did. 

If we were going to move to grapheme equivalence (some day), the right
way would be to normalize characters in the construction of the Unicode
string. This is known as "Early normalization":

http://www.w3.org/TR/charmod/#NormalizationApplication

-- 
 Paul Prescod  - ISOGEN Consulting Engineer speaking for himself
It's difficult to extract sense from strings, but they're the only
communication coin we can count on. 
	- http://www.cs.yale.edu/~perlis-alan/quotes.html



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4