aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2009-04-03 14:37:53 -0400
committerJoey Hess <joey@gnu.kitenet.net>2009-04-03 14:37:53 -0400
commit90da6cc05ca92ab856b21eff1a35cfb7d84db5f6 (patch)
tree2317bff9b684f248270c6e0d9add2892e1603f30 /doc
parenteec38e8eeb63f6a93c60fc7b9e7e23b28e3b13e8 (diff)
downloadikiwiki-90da6cc05ca92ab856b21eff1a35cfb7d84db5f6.tar
ikiwiki-90da6cc05ca92ab856b21eff1a35cfb7d84db5f6.tar.gz
response
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/How_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/forum/How_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn b/doc/forum/How_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn
index b5e8a14dd..0b3895357 100644
--- a/doc/forum/How_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn
+++ b/doc/forum/How_to_fix___34__does_not_map_to_Unicode__34___errors__63__.mdwn
@@ -6,3 +6,15 @@ I think it's because some of my files contain non-utf8, non-unicode, or somehow
Thanks
-- seanh
+
+> Unfortunatly, these messages are logged by perl so there's no way to add
+> a filename to them.
+>
+> If you run the build in --verbose mode, you should see which page ikiwiki
+> is working on, and unless it inlines some other page, you can be pretty
+> sure that page contains invalid utf-8 if the message is then printed.
+>
+> Another option is to use the `isutf8` program from
+> moreutils](http://kitenet.net/~joey/code/moreutils/),
+> and run it on each file, it will tell you the line number
+> and character position that is invalid. --[[Joey]]