Changes between Version 1 and Version 2 of TracUnicode


Ignore:
Timestamp:
Mar 28, 2008, 2:16:35 PM (17 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracUnicode

    v1 v2  
    55
    66As such, it supports most (all?) commonly used character encodings.
     7
     8If your encoding is not UTF-8, you can use [wiki:TracModPython mod_python] to handle it.  For example, if your local encoding is gbk, you can set
     9   default_charset = gbk
     10in trac.ini.
     11
     12You also must make sure that your [wiki:DatabaseBackend database backend] stores its data in UTF-8; otherwise strange things will happen.
     13
     14To convert your database to UTF-8, the easiest way is to dump the database, convert the dump into UTF-8 and then import the converted dump back into the database.[[BR]]
     15You can use [http://www.gnu.org/software/libiconv/documentation/libiconv/iconv.1.html iconv] to convert the dump.
     16
    717
    818== Examples ==
     
    7484
    7585=== Polish ===
    76 Pchn?? w t? ?ód? je?a lub o?m skrzy? fig
     86Pchn?? w t? ?ód? je?a lub osiem skrzy? fig; Nocna g?eg?ó?ka zawsze dzienn? przekuka.
    7787
    7888=== Portuguese ===