Hallo Janne, I've just read all mails and the corresponding wiki page again. It's a bit confusing because all participants have quite different points of view. Here are my comments / my point of view :-)
I think clear rules are still missing on how an arbitrary link is
translated into a WikiName. These should really be tight rules like
you already wrote about MediaWiki:
> Mediawiki (which powers Wikipedia) has a simple regexp for filtering
> out illegal characters. At the moment it is as follows:
>
> "The list of illegal characters is as follows: #<>[]|{}, non-
> printable characters 0 through 31, and 'delete' character 127)."
>
> Everything else is allowed in wiki names. I think that if they can
> do it and have no problems, we can do it too.
Regarding backwards compatibility, I'd recommend ignoring old special
cases (where existing) in favor of allowing for simple rules for 3.0+.
Especially the hidden platform dependencies, which are obviously
existing in the file-based provider up to 2.8 should be eliminated.
In order to achieve backwards compatibility, there are two
possibilities.
* The simple way: Implement some fallback rules in wiki page lookup in
order not to break existing links. If feasible, the corresponding code
should be marked as being for this purpose only.
Problem: What if some old link isn't valid any more and therefore
gets permanently redirected by this code? Then, someone creates a
new page whose name is just this old link's name. This would break
the old link without touching it directly.
* If the simple way isn't feasible, implement a migration tool which
converts the page names and links in existing repositories.
Regards
Florian
smime.p7s
Description: S/MIME Cryptographic Signature
