Changes between Version 3 and Version 4 of TracUnicode


Ignore:
Timestamp:
Jan 3, 2024, 10:40:13 AM (5 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracUnicode

    v3 v4  
    33[[TracGuideToc]]
    44
    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.
     5Trac 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.
    66
    77If 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"]:
     
    1212Ensure that your [trac:DatabaseBackend database] stores its data in UTF-8, otherwise results may be unpredictable.
    1313
    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.
     14To 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.
    1515
    1616== Examples
     
    3737
    3838Ako podržava srpski i slovenski mora podržavati i Hrvatski - čćžšđ ČĆŽŠĐ.
     39
     40=== Dutch
     41
     42Enquêtes in de privésfeer zijn altijd geëngageerd.
    3943
    4044=== English