summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-07-06 01:56:53 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-07-06 01:56:53 +0000
commitdcb7fd85f287e70eef6fedb2dabcdb7c3d16ef20 (patch)
treee0c77e555b584d9dc7b31e3cdb27fa9ac8f48522
parentddf02844e58f7c7b2c12ce6f32c61e7412b90ed2 (diff)
web commit by http://dmarti.myopenid.com/
-rw-r--r--doc/bugs/UTF-8_BOM_showing_up_inside_a_page__63__.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/bugs/UTF-8_BOM_showing_up_inside_a_page__63__.mdwn b/doc/bugs/UTF-8_BOM_showing_up_inside_a_page__63__.mdwn
new file mode 100644
index 000000000..e81d25e4b
--- /dev/null
+++ b/doc/bugs/UTF-8_BOM_showing_up_inside_a_page__63__.mdwn
@@ -0,0 +1,7 @@
+I have a git-backed ikiwiki install, and when I commit and push a file from an x86 host (LANG=en_US.UTF-8) to the Ikiwiki box, which is Debian GNU/Linux on Sparc, I sometimes get unusual characters (ef bb ff) before the first character of the wiki text. It seems that this is a UTF-8 "byte order mark" that is getting inserted automatically into the .wiki file by my editor: http://vim.wikia.com/wiki/VimTip246#Tip:_.23246_-_Working_with_Unicode
+
+Example:
+
+ http://monkey.linuxworld.com/lwce-2007/
+
+Is there any way for ikiwiki to spot when .wiki files have this BOM and deal with it, or should I make sure to strip it out before committing? \ No newline at end of file