Changes between Version 3 and Version 4 of TracDev/UnicodeGuidelines

Timestamp:

May 2, 2006, 12:28:43 PM (18 years ago)

Author:

Christian Boos

Comment:

Several typos fixed + link to unicode related issues added

TracDev/UnicodeGuidelines

@@ -98 +98 @@
      (NB: as we have seen above, 'iso-8859-15' is a fixed-byte encoding
      with a mapping defined for all the 0..255 range, so decoding ''any'' 
-     input with such an encoding will ''always'' succeed).
+     input assuming such an encoding will ''always'' succeed).
      {{{
      >>> unicode('ndr\xe9 Le', 'utf-8')
@@ -121 +121 @@
      * One possibility would be to use replacement characters:
        {{{
-       >>> unicode('ndr\xe9 Le', 'utf-8')
+       >>> unicode('ndr\xe9 Le', 'utf-8', 'replace')
        u'ndr\ufffde'
        }}}
@@ -183 +183 @@
    in this situation.
 
- ''FIXME: talk a bit about the other utilities''
-
- ''FIXME: Those utilities are currently placed in the `trac.util` package,
- though I'm thinking about moving the in the `trac.util.text` package:
-  * some of the corresponding unit tests are already in `trac.util.tests.text`
-  * `to_unicode` could then be used in the `Markup` class''
+''FIXME: talk a bit about the other utilities''
+
+''FIXME: Those utilities are currently placed in the `trac.util` package,
+though I'm thinking about moving them in the `trac.util.text` package:
+ * ''some of the corresponding unit tests are already in `trac.util.tests.text`''
+ * ''`to_unicode` could then be used in the `Markup` class''
 
 === The Mimeview component ===
@@ -247 +247 @@
 
 In Subversion, there are clear rules about the pathnames used
-by the SVN Bindings for Python: those should UTF-8 encoded `str` objects.
-
-Therefore, `unicode` pathnames should 'utf-8' encoded before
+by the SVN Bindings for Python: those should be UTF-8 encoded `str` objects.
+
+Therefore, `unicode` pathnames should be 'utf-8' encoded before
 being passed to the bindings, and pathnames returned by 
 the bindings should be decoded using 'utf-8' before being
@@ -292 +292 @@
 should be used.
 
-  ''FIXME: and logging?''
+The logging API seems to handle `unicode` objects just fine.
 
 === Interaction with plugins ===
@@ -302 +302 @@
 == Questions/Suggestions... ==
 
-Sorry, there are certainly a ton of typos there, hopefully
-no more serious errors. But I had to have a first draft of this.
-
 Feel free to correct me, ask questions, etc.; this is a Wiki. :)
+
+---- 
+See also TracUnicode, [query:?keywords=~unicode&milestone=0.10&group=status unicode related tickets]