I think it's right about on target. My only disappointment is that
the
reliance on jcr properties means that normalization cannot be
introduced
prior to 3.0...
Or can it?
Is there any desire to see this introduced in the 2.8 branch? If this
is just a 3.0 task, then it will likely lie fallow for quite some
time.
It would be possible, but that might mean database conversion work.
Or forcing a translation table to be kept in memory.
<side-note>
There was mention of a repository export/import tool. The tool should
apply the normalizations and alert if more than one page in the set
normalize to the same name.
</side-note>
Yes, this is a good idea.
This could be introduced in 2.8 by stubbing in a WikiName class that
pulls in all .cleanLink and .wikifyLink calls but this would trend to
bigger modifications for 2.8 than I thought would be entertained. (I
thought we were looking for moderately clean and simply hack for 2.8).
I'd just like to fix this once and for all :-)
I'm not sure if this would be 2.8 *incompatible* as such; it's just
that currently we store the wiki names as file names, and the fix
would be needed to be applied in such a way that the repository
itself would not need conversion.
So perhaps the correct place to put this would be the PageManager or
the CachingProvider?
For now, I might take my current hack and push it into a custom 2.8
build and see how it plays live for a week or so. My biggest problem
will be that I'll have to clean my repository of "duplicate" names
(users have managed to get "Test%20Name" "Test+Name" and "TestName"
all
existing on disk believe it or not.) But this is a bit of
housekeeping
I should do anyway.
A good test suite would be a good idea.
Let me know if there is any desire to push this further at this time.
I would certainly like to see this resolved for 3.0 timeframe - any
changes after that are going to be painful again.
/Janne
