More NTFS filename compatability problems.

diff --git a/doc/bugs/Filenames_with_colons_cause_problems_for_Windows_users.mdwn b/doc/bugs/Filenames_with_colons_cause_problems_for_Windows_users.mdwn
index 0fccd1dcb01a3c7d1a074fb814d6ce323749386c..7559e6d0a24485c1c0585791f271708dc7c1cab2 100644 (file)
--- a/doc/bugs/Filenames_with_colons_cause_problems_for_Windows_users.mdwn
+++ b/doc/bugs/Filenames_with_colons_cause_problems_for_Windows_users.mdwn
@@ -68,3 +68,8 @@ Windows does not support filenames containing any of these characters: `/ \ * :
 >>> ikiwiki on windows, including its assumption that the directory
 >>> separator is "/". Windows will be supported when someone sends me a
 >>> comprehansive and not ugly or performance impacting patch. :-) --[[Joey]]
 >>> ikiwiki on windows, including its assumption that the directory
 >>> separator is "/". Windows will be supported when someone sends me a
 >>> comprehansive and not ugly or performance impacting patch. :-) --[[Joey]]

+
+> Speaking of Windows filename problems, how do I keep directories ending in a
+> period from being created? The following didn't seem to work.
+> `wiki_file_chars => "-[:alnum:]+/._",`
+> `wiki_file_regex => '[-[:alnum:]+_]$',`