Changes between Version 5 and Version 6 of TracDev/UnicodeGuidelines

Timestamp:

Aug 29, 2006, 9:37:41 AM (18 years ago)

Author:

Christian Boos

Comment:

Some updates concerning trac.util.text and several links to examples in the code added. Also added a caveat about the Mimeview API future changes.

TracDev/UnicodeGuidelines

@@ -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 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''
+There are a few other unicode related utilies besides `to_unicode` in the [source:/trunk/trac/util/text.py trac.util.text] module.
 
 === The Mimeview component ===
@@ -213 +208 @@
  * `Mimeview.to_unicode(self, content, mimetype=None, charset=None)` [[br]]
    uses the `to_unicode` utility and eventually guess the charset if needed
- * ''`Mimeview.is_binary(self, filename, content, mimetype)`'' '''TBD''' [[br]]
-   guess if the `content` is textual data or not
-
+'''Note that the Mimeview API is currently behing overhauled and will most probably change in the next releases. See #3332'''.
 
 == Trac boundaries for Unicode Data ==
@@ -228 +221 @@
 Each database connector should configure its database driver 
 so that the `Cursor` objects are able to accept and will return
-`unicode` objects.
+`unicode` objects. This sometimes involve writing a wrapper class
+for the original Cursor class. See for example
+[trac/db/sqlite_backend.py@head#L58 SQLiteUnicodeCursor], for pysqlite1.
 
 === Filesystem objects ===
@@ -271 +266 @@
 converted to UTF-8 encoded `str` objects just before being inserted in the "HDF"
 (the data structure used by the template engine to fill in the templates).
-
-The body of those templates (the `.cs` files) must also use this encoding.
+This is done automatically by our 
+[source:/trunk/trac/web/clearsilver.py@head#L22 HDFWrapper] class, so anywhere else 
+in the code one can safely associate unicode values to entries in `req.hdf`.
+
+The body of those templates (the `.cs` files) must also use the UTF-8 encoding.
 
 === The Web interface ===