Changes between Version 73 and Version 74 of TracUnicode
- Timestamp:
- Jan 3, 2015, 1:41:34 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracUnicode
v73 v74 3 3 [[TranslatedPages]] 4 4 5 Trac stores all text using UTF-8 encoding, including text in tickets and wiki pages. Internal processing of text uses true Unicode representations.5 Trac encodes all text using [http://en.wikipedia.org/wiki/UTF-8 UTF-8], including text in tickets and wiki pages. Internal processing of text uses true [http://en.wikipedia.org/wiki/Unicode Unicode] representations. As such, it supports most (all?) commonly used character encodings. 6 6 7 As such, it supports most (all?) commonly used character encodings. 8 9 If the default encoding in your source code repository is not UTF-8, you can specify it in the [TracIni#trac-section trac.ini], for example: 7 If the default encoding in your source code repository is not UTF-8, you can specify it in the [TracIni#trac-section trac.ini]: 10 8 {{{ 11 9 default_charset = gbk 12 10 }}} 13 11 14 You also must make sure that your [trac:DatabaseBackend database backend] stores its data in UTF-8; otherwise strange things will happen.12 Also ensure that your [trac:DatabaseBackend database] stores its data in UTF-8, otherwise results may be unpredictable. 15 13 16 To 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]] 17 You can use [http://www.gnu.org/software/libiconv/documentation/libiconv/iconv.1.html iconv] to convert the dump. 18 14 To convert your database to UTF-8, the easiest way is to create a dump of the database, convert it into UTF-8, for example using [http://www.gnu.org/software/libiconv/documentation/libiconv/iconv.1.html iconv], and then import it back into the database. 19 15 20 16 == Examples ==