X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/29507e94a46d0f2006671d31ac6812ebd0715cee..12eb056b33e1f01a63c4fcee408c9ac0d96c6b5e:/doc/todo/utf8.mdwn?ds=inline

diff --git a/doc/todo/utf8.mdwn b/doc/todo/utf8.mdwn
index b905e4633..278fb9382 100644
--- a/doc/todo/utf8.mdwn
+++ b/doc/todo/utf8.mdwn
@@ -7,35 +7,12 @@ Currently ikiwiki is belived to be utf-8 clean itself; it tells perl to use
 binmode when reading possibly binary files (such as images) and it uses
 utf-8 compatable regexps etc.
 
-utf-8 IO is not enabled by default though. While you can probably embed
-utf-8 in pages anyway, ikiwiki will not treat it right in the cases where
-it deals with things on a per-character basis (mostly when escaping and
-de-escaping special characters in filenames).
+There may be the odd corner where utf-8 still doesn't work; these are being
+fixed as they're found.
 
-To enable utf-8, edit ikiwiki and add -CSD to the perl hashbang line.
-(This should probably be configurable via a --utf8 or better --encoding=
-switch.)
-
-The following problems have been observed when running ikiwiki this way:
-
-* If invalid utf-8 creeps into a file, ikiwiki will crash rendering it as
-  follows:
-
-	Malformed UTF-8 character (unexpected continuation byte 0x97, with no preceding start byte) in substitution iterator at /usr/bin/markdown line 1317.
-	Malformed UTF-8 character (fatal) at /usr/bin/markdown line 1317.
-
-  In this example, a literal 0x97 character had gotten into a markdown
-  file.
-
-  Running this before markdown can avoid it:
-
-  $content = Encode::encode_utf8($content);
-
-  I'm not sure how, or what should be done after markdown to get the string
-  back into a form that perl can treat as utf-8.
+Notes:
 
 * Apache "AddDefaultCharset on" settings will not play well with utf-8
-  pages.
+  pages. Turn it off.
 
-* CGI::FormBuilder needs to be told to set `charset => "utf-8"` so that
-  utf-8 is used in the edit form. (done)
+[[todo/done]]