Changes between Version 1 and Version 2 of TracUnicode

Show
Ignore:
Timestamp:
04/01/08 05:51:22 (14 years ago)
Author:
trac (IP: 127.0.0.1)
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 === 
Home
About PCA
Reference Data Services (RDS)
RDS Operations Support
Meetings and Conferences
ISO 15926
Special Interest Groups
Technical Advisory Board
Norwegian Continental Shelf Std
Projects
Search