Edgewall Software

Changes between Version 10 and Version 11 of TracDev/UnicodeGuidelines


Ignore:
Timestamp:
Sep 26, 2008, 3:42:07 PM (14 years ago)
Author:
Christian Boos
Comment:

Add some additional information about unicode at system boundaries

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/UnicodeGuidelines

    v10 v11  
    225225[source:/trunk/trac/db/sqlite_backend.py@head#L58 SQLiteUnicodeCursor], for pysqlite1.
    226226
     227=== The console ===
     228
     229When reading from the console, we assume the text is encoded
     230using `sys.stdin.encoding`.
     231
     232When writing to the console, we assume that the `sys.stdout.encoding`
     233should be used.
     234
     235The logging API seems to handle `unicode` objects just fine.
     236
    227237=== Filesystem objects ===
    228238
     
    236246using non-ascii characters. In Python, it should be safe to provide `unicode`
    237247objects for all the `os` filesystem related functions.
     248
     249Look also at r7360, r7361, r7362.
     250
     251More information about how Python deals with Python at system boundaries can be found here: http://kofoto.rosdahl.net/wiki/UnicodeInPython.
     252
     253
    238254
    239255=== `versioncontrol` subsystem ===
     
    282298If this is the case, that encoding is used.
    283299
    284 === The console ===
    285 
    286 When reading from the console, we assume the text is encoded
    287 using `sys.stdin.encoding`.
    288 
    289 When writing to the console, we assume that the `sys.stdout.encoding`
    290 should be used.
    291 
    292 The logging API seems to handle `unicode` objects just fine.
    293 
    294300=== Interaction with plugins ===
    295301