Changes between Version 6 and Version 7 of TracUnicode

Timestamp:

Nov 21, 2023, 2:25:04 PM (5 months ago)

Author:

trac

Comment:

--

TracUnicode

@@ -3 +3 @@
 [[TracGuideToc]]
 
-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.
+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.
 
 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.
 
-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.
+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.
 
 == Examples
@@ -37 +37 @@
 
 Ako podržava srpski i slovenski mora podržavati i Hrvatski - čćžšđ ČĆŽŠĐ.
+
+=== Dutch
+
+Enquêtes in de privésfeer zijn altijd geëngageerd.
 
 === English