summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-07-08 17:25:50 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-07-08 17:25:50 +0000
commit5a809bdd98723ebc650398010dce57a29d25b6cd (patch)
tree7f38c6e935f697a7b52b80854bec5615e8abccac
parentb910d991f0cace9bf6f31ca6430836a99c6d4456 (diff)
response
-rw-r--r--doc/bugs/UTF-8_BOM_showing_up_inside_a_page__63__.mdwn8
1 files changed, 7 insertions, 1 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
index e81d25e4b..5324f7991 100644
--- 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
@@ -4,4 +4,10 @@ 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
+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?
+
+> It would be easy to make ikiwiki strip out the BOM. For example, a simple
+> plugin could be written to s/// them out as a filter.
+>
+> I'm unsure if ikiwiki should do this by default. --[[Joey]]