aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-07-25 02:34:48 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-07-25 02:34:48 +0000
commit2210c65083465bf8e515418cf2528e18f7326bc0 (patch)
treed943525db15d25c51d5347a41e07939c150708e9 /doc/bugs
parentde9104d4e2571dcdf28659b3fd244c3c77f02740 (diff)
downloadikiwiki-2210c65083465bf8e515418cf2528e18f7326bc0.tar
ikiwiki-2210c65083465bf8e515418cf2528e18f7326bc0.tar.gz
more triage
Diffstat (limited to 'doc/bugs')
-rw-r--r--doc/bugs/Does_not_support_non-UTF8_files.mdwn5
-rw-r--r--doc/bugs/assumes_system_perl.mdwn14
-rw-r--r--doc/bugs/discussion_removal.mdwn2
-rw-r--r--doc/bugs/i18n_characters_in_post_title.mdwn59
4 files changed, 2 insertions, 78 deletions
diff --git a/doc/bugs/Does_not_support_non-UTF8_files.mdwn b/doc/bugs/Does_not_support_non-UTF8_files.mdwn
deleted file mode 100644
index 7d4cace7a..000000000
--- a/doc/bugs/Does_not_support_non-UTF8_files.mdwn
+++ /dev/null
@@ -1,5 +0,0 @@
-Ikiwiki does not seem to support non-UTF-8 file content, although there's no reason it should assume anything other than ASCII-compatibility from the encoding, at least if the Web interface is not used. It suffices that users use the same encoding as the templates specify. If I try to run it on `.mdwn` with content in ISO-8859-1 format, in an ISO-8859-1 locale, I get:
-
- Malformed UTF-8 character (unexpected non-continuation byte 0x74, immediately after start byte 0xe4) in substitution iterator at /usr/local/share/perl/5.8.8/IkiWiki.pm line 640.
-
-I hope Ikiwiki is not part of the UTF-8 monoculturist movement...
diff --git a/doc/bugs/assumes_system_perl.mdwn b/doc/bugs/assumes_system_perl.mdwn
deleted file mode 100644
index 9df61bc80..000000000
--- a/doc/bugs/assumes_system_perl.mdwn
+++ /dev/null
@@ -1,14 +0,0 @@
-ikiwiki 1.45 doesn't work properly for perl installs not in the system path.
-
-ie:
-
-~/tools/perl-5.8.8/perl Makefile.PL
-make
-
-fails, as the 'make' command attempts to use the perl install in PATH, rather than the one ikiwiki is being installed for.
-
-The installed bin/ikiwiki file also refers to /usr/bin/perl rather than the perl it is being installed for.
-
-> I will acdept sufficiently nonintrusive patches to make ikiwiki work better on strange systems like
-> yours, but do not plan to work on it myself, since I do not use systems
-> where /usr/bin/perl is not a sane default. --[[Joey]]
diff --git a/doc/bugs/discussion_removal.mdwn b/doc/bugs/discussion_removal.mdwn
index af3c6c1cb..ef84a9b74 100644
--- a/doc/bugs/discussion_removal.mdwn
+++ b/doc/bugs/discussion_removal.mdwn
@@ -1,3 +1,5 @@
If a page has a discussion page, which is then removed, ikiwiki seems not
to notice that the discussion page has gone away, and does not update the
link to it in the action bar.
+
+> Reprocued with 2.5 --[[Joey]]
diff --git a/doc/bugs/i18n_characters_in_post_title.mdwn b/doc/bugs/i18n_characters_in_post_title.mdwn
deleted file mode 100644
index 8bd25bfd1..000000000
--- a/doc/bugs/i18n_characters_in_post_title.mdwn
+++ /dev/null
@@ -1,59 +0,0 @@
-It seems that I can't use Polish characters in post title.
-When I try to do it, then I can see error message: "Błąd: bad page name".
-
-I hope it's a bug, not a feature and you fix it soon :) --[[Paweł|ptecza]]
-
-> ikiwiki only allows a very limited set of characters raw in page names,
-> this is done as a deny-by-default security thing. All other characters
-> need to be encoded in __code__ format, where "code" is the character
-> number. This is normally done for you, but if you're adding a page
-> manually, you need to handle it yourself. --[[Joey]]
-
->> Assume I have my own blog and I want to send a new post with Polish
->> characters in a title. I think it's totally normal and common thing
->> in our times. Do you want to tell me I shouldn't use my native
->> characters in the title? It can't be true ;)
-
->> In my opinion encoding of title is a job for the wiki engine,
->> not for me. Joey, please try to look at a problem from my point
->> of view. I'm only user and I don't have to understand
->> what the character number is. I only want to blog :)
-
->> BTW, why don't you use the modified-UTF7 coding for page names
->> as used in IMAP folder names with non-Latin letters? --[[Paweł|ptecza]]
-
->>> Joey, do you intend to fix that bug or it's a feature
->>> for you? ;) --[[Paweł|ptecza]]
-
->>>> Of course you can put Polish characters in the title. but the page
->>>> title and filename are not identical. Ikiwiki has to place some limits
->>>> on what filenames are legal to prevent abuse. Since
->>>> the safest thing to do in a security context is to deny by default and
->>>> only allow a few well-defined safe things, that's what it does, so
->>>> filenames are limited to basic alphanumeric characters.
->>>>
->>>> It's not especially hard to transform your title into get a legal
->>>> ikiwiki filename:
-
- joey@kodama:~>perl -MIkiWiki -le 'print IkiWiki::titlepage(shift).".mdwn"' "Błąd"
- B__197____130____196____133__d.mdwn
-
->>>>> Thanks for the hint! It's good for me, but rather not for common users :)
-
->>>>>> Interesting... I have another result:
->>>>>>
->>>>>> perl -MIkiWiki -le 'print IkiWiki::titlepage(shift).".mdwn"' "Błąd"
->>>>>> B__179____177__d.mdwn
->>>>>>
->>>>>> What's your locale? I have both pl\_PL (ISO-8859-2) and pl\_PL.UTF-8,
->>>>>> but I use pl\_PL. Is it wrong? --[[Paweł|ptecza]]
-
->>>> Now, as to UTF7, in retrospect, using a standard encoding might be a
->>>> better idea than coming up with my own encoding for filenames. Can
->>>> you provide a pointer to a description to modified-UTF7? --[[Joey]]
-
->>>>> The modified form of UTF7 is defined in [RFC 2060](http://www.ietf.org/rfc/rfc2060.txt)
->>>>> for IMAP4 protocol (please see section 5.1.3 for details).
-
->>>>> There is a Perl [Unicode::IMAPUtf7](http://search.cpan.org/~fabpot/Unicode-IMAPUtf7-2.01/lib/Unicode/IMAPUtf7.pm)
->>>>> module at the CPAN, but probably it hasn't been debianized yet :( --[[Paweł|ptecza]]