From: Joey Hess <joey@gnu.kitenet.net>
Date: Fri, 3 Apr 2009 18:37:53 +0000 (-0400)
Subject: response
X-Git-Tag: 3.09~2
X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/commitdiff_plain/90da6cc05ca92ab856b21eff1a35cfb7d84db5f6

response
---

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]]