Tim Peters wrote: > > [Mark Hammond] > > ... > > Where should the "real" documentation go? It seems maybe we need a > > new sub-heading under the "6.1 - os -- Misc. OS Interface" - something > > like: > > > > 6.1.x - Unicode and the file system > > - general discussion. > > - Windows specific > > - Mac specific should that appear. > > - OS' with no special support (ie, "the rest") > > > > Does that make sense? > > So far is it goes, yes. I think the manual desperately needs a Unicode > section for other reasons, though: from traffic on c.l.py, it's clear that > few people can figure out how to do *anything* with Unicode now unless their > first name begins with "M" (Mark, Martin, Marc -- definitely not Skip > <wink>). There's no overview and there are no examples. The primary string > method doesn't even mention Unicode (here paraphrasing questions that pop > up): > [...] True. The main source of documentation for Unicode still is the proposal itself (Misc/unicode.txt). It needs some reordering and a few examples, but does contain all the information needed to grasp what the implementation intends and how it works. If that's still not enough, there are numerous doc-strings in the codecs.py module, more technical docs in the API reference and finally the unicodeobject.h header file itself. Another source for documentation and examples is the i18n-sig page on python.org. -- Marc-Andre Lemburg ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.lemburg.com/python/
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