Differences between revisions 12 and 13
Revision 12 as of 2005-09-14 18:07:31
Size: 6917
Comment:
Revision 13 as of 2005-09-14 21:18:09
Size: 6726
Editor: LionKimbro
Comment: Thank you! (+ summarized supported encodings discussion)
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
 * WikiPedia:Unicode -- Wikipedia unicode entry
Line 40: Line 41:

=== Supported Encodings ===

There is a [http://docs.python.org/lib/standard-encodings.html list of standard encodings in the Python documentation.]

Encodings can be registered at runtime, as well, with the codecs module.

Python2.4 supports many codecs that 2.2 and 2.3 do not, including Chinese bg2312.

Encodings are specified in files found in a directory called "encodings"; one way to find the encodings with your Python distribution is to check the contents of this directory:

{{{#! python
>>> import encodings, os
>>> [n for n in os.listdir(os.path.dirname(encodings.__file__))
... if n[0] != '_' and n.endswith('.py')]
['aliases.py', 'ascii.py', 'base64_codec.py', 'charmap.py', 'cp037.py', ...]
>>> from encodings import aliases
>>> aliases.aliases
{'base64': 'base64_codec', 'us_ascii': 'ascii', ...}
}}}

Contributors: LionKimbro, FredDrake, JürgenHermann.
Line 109: Line 132:

=== Registry ===

Is there any way to get a listing of the encodings registered? I don't see anything in [http://www.python.org/doc/current/lib/module-codecs.html codecs].

-- LionKimbro [[DateTime(2005-09-09T23:04:29Z)]]

Sure you do: it's one of the subsections linked from that page:
[http://docs.python.org/lib/standard-encodings.html Standard Encodings].

-- FredDrake [[DateTime(2005-09-10T01:13:02Z)]]

No: Dynamically. Python2.4 supports codecs that 2.2 does not.

Users can also register encodings with the codecs module.

The run-time list of registered encodings, both user-created and that come with Python, is what I'm looking for.

-- 216.254.10.144 [[DateTime(2005-09-11T18:18:08Z)]]

Builtin stuff:
{{{#! python
>>> import encodings, os
>>> [n for n in os.listdir(os.path.dirname(encodings.__file__))
... if n[0] != '_' and n.endswith('.py')]
['aliases.py', 'ascii.py', 'base64_codec.py', 'charmap.py', 'cp037.py', ...]
>>> from encodings import aliases
>>> aliases.aliases
{'base64': 'base64_codec', 'us_ascii': 'ascii', ...}
}}}

-- JürgenHermann [[DateTime(2005-09-14T18:07:29Z)]]

Resources to help you learn how to handle Unicode in your Python programs:

TableOfContents

General Unicode Resources

Python-Specific Resources

Standard Reference

Search the Python reference for:

Tutorials

Sample Code

Pitfalls

Supported Encodings

There is a [http://docs.python.org/lib/standard-encodings.html list of standard encodings in the Python documentation.]

Encodings can be registered at runtime, as well, with the codecs module.

Python2.4 supports many codecs that 2.2 and 2.3 do not, including Chinese bg2312.

Encodings are specified in files found in a directory called "encodings"; one way to find the encodings with your Python distribution is to check the contents of this directory:

>>> import encodings, os
>>> [n for n in os.listdir(os.path.dirname(encodings.__file__))
...     if n[0] != '_' and n.endswith('.py')]
['aliases.py', 'ascii.py', 'base64_codec.py', 'charmap.py', 'cp037.py', ...]
>>> from encodings import aliases
>>> aliases.aliases
{'base64': 'base64_codec', 'us_ascii': 'ascii', ...}

Contributors: LionKimbro, FredDrake, JürgenHermann.

Discussion

Here's a conversation that I had on [http://communitywiki.org/ CommunityWiki;] I'd like to bring the main ideas into here.

Conversation between Lion and Bayle

That looks like 32-bits per character, so I'd say it's some form of little-endian utf-32.

And for some strange reason, Python only comes with "utf-8" and "utf-16" as valid "decode" values.

You can:

   1 >>> bytes = "H\x00i\x00\n\x00"
   2 >>> unistring = bytes.decode('utf-16')
   3 >>> print unistring
   4 u'Hi\n'

You can do that for either "utf-8" or "utf-16." But for some reason, I can't say "utf-32" or "utf-32LE" (LE=little endian). I have no idea why. I also don't know how it is that my Python programs are producing UTF-32 for you..!

I've been wanting to diagram how Python unicode works, like how I diagrammed it's time use, and regex use.

Basically, "encode" is meant to be called from unicode data, and "decode" is meant to be called from bytes data. Continuing from above:

   1 >>> bytes
   2 'H\x00i\x00\n\x00'
   3 >>> unistring = bytes.decode('utf-16')
   4 >>> unistring
   5 u'Hi\n'
   6 >>> unistring.encode('utf-8')
   7 'Hi\n'
   8 >>> unistring.encode('utf-16')
   9 '\xff\xfeH\x00i\x00\n\x00'
  10 >>> unistring.encode('utf-32')
  11 Traceback (most recent call last):
  12   File "<stdin>", line 1, in ?
  13 LookupError: unknown encoding: utf-32

I'm guessing that the "\xff" at the beginning of the utf-16 encoding is a byte-order marker, saying "this is little endian."

I learned about unicode stuff about 2-3 weeks ago. I kept notes about what I thought were the largest mental misconceptions, and what were the most revealing ways of thinking about it. Sadly, I've forgotten about all that. (Should'a documented it in the wiki!)

In Python, the data in a unicode or byte string is exactly the same. The difference is only in how Python treats and presents the data. I found it super-helpful to not think about what the console said, or work with the console, because the console lies. That is, the characters go through conversions even being printed to the screen: Your console has an understanding of encoding, and your fonts have an understanding of encoding, and I had a lot of difficulty seperating it out.

I had a lot easier time thinking about the concepts, instead of the concrete representations. (Which is opposite my usual course of thinking.)

"Decoded," to Python's mind, is data being treated as unicode data. "Encoded," to Python's mind, is data being treated as bytes. The data isn't actually changing form, at all. It's just the treatment of the same data that is being changed. But there is no actual conversion taking place.

So, you only ever run "decode" on a byte string. (Another thing: Don't think of native Python strings as "strings." Think of them as "bytes." And indeed: In the new Python 3.0, they're calling it just that: strings are called "bytes" in Python3, and unicode strings are called just "strings" in Python3.)

So you can decode bytes, and encode unicode strings.

Don't think about decoding unicode strings, and don't think about encoding bytes. The bytes are already coded. Only unicode strings live in pure, abstract, heavenly, platonic form. There is no code there, only perfect clarity. (At least, that's how Python makes it seem for you.)

Again, sadly, I have no idea how to get from UTF-32 to Python unicode. I don't see the path. I saw something somewhere about being able to compile something in to your Python.

That said, if I'm actually serving UTF-32 to you somehow,... ...then there's probably a way I just don't know.

(Discussion continued)

On side-notes, I think the diagrams I've posted for WorkingWithTime and RegularExpressions were eaten up in the transition to MoinMoin 1.3; I'll repost them soon, after I get [http://wiki.taoriver.net/ my own wiki] upgraded to 1.3.

-- LionKimbro DateTime(2005-02-06T02:56:28Z)

Unicode (last edited 2008-11-15 14:00:16 by localhost)

Unable to edit the page? See the FrontPage for instructions.