Changes between Version 3 and Version 4 of TracUnicode
- Timestamp:
- 07/19/2024 04:41:09 PM (7 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracUnicode
v3 v4 3 3 [[TracGuideToc]] 4 4 5 Trac encodes all text using [ wikipedia:UTF-8], including text in tickets and wiki pages. Internal processing of text uses true [wikipedia:Unicode] representations. As such, it supports the most commonly used character encodings.5 Trac encodes all text using [https://en.wikipedia.org/wiki/UTF-8 UTF-8], including text in tickets and wiki pages. Internal processing of text uses true [https://en.wikipedia.org/wiki/Unicode Unicode] representations. As such, it supports the most commonly used character encodings. 6 6 7 7 If the default encoding of your source code repository is not UTF-8, you can specify it in [TracIni#trac-default_charset-option "[trac] default_charset"]: … … 12 12 Ensure that your [trac:DatabaseBackend database] stores its data in UTF-8, otherwise results may be unpredictable. 13 13 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 re-import it.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 [https://www.gnu.org/software/libiconv/documentation/libiconv/iconv.1.html iconv], and then re-import it. 15 15 16 16 == Examples … … 37 37 38 38 Ako podržava srpski i slovenski mora podržavati i Hrvatski - čćžšđ ČĆŽŠĐ. 39 40 === Dutch 41 42 Enquêtes in de privésfeer zijn altijd geëngageerd. 39 43 40 44 === English