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

Showing content from https://mail.python.org/pipermail/python-dev/2009-April/089189.html below:

Non-decodable Bytes in System Character Interfaces

• Previous message: [Python-Dev] PEP 383: Non-decodable Bytes in System Character Interfaces
• Next message: [Python-Dev] PEP 383: Non-decodable Bytes in System Character Interfaces
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Glenn Linderman a écrit :
> 
> 3. When an undecodable byte 0xPQ is found, decode to the escape 
> codepoint, followed by codepoint U+01PQ, where P and Q are hex digits.
> 

The problem with this strategy is: paths are often sliced, so your 2 codepoints 
could get separated. The good thing with the PEP's strategy is that 1 character 
stays 1 character.

Baptiste

• Previous message: [Python-Dev] PEP 383: Non-decodable Bytes in System Character Interfaces
• Next message: [Python-Dev] PEP 383: Non-decodable Bytes in System Character Interfaces
• 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