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

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

[Python-Dev] UTF-16 code point comparison

• Previous message: [Python-Dev] UTF-16 code point comparison
• Next message: [Python-Dev] [ Patch #100990 ] UTF-16 code point comparison
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I wrote:

> now generates UTF-16 encoded data.  (so does \N{}, but
> that's a non-issue:=20

...because all characters in the current name database
have 16-bit codes.

</F>

• Previous message: [Python-Dev] UTF-16 code point comparison
• Next message: [Python-Dev] [ Patch #100990 ] UTF-16 code point comparison
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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