jens wille [30.01.2007 08:41]:
> anyway, i'll probably have to look into this myself, following
> yours and michael's pointers.
well... finally, some news for you: not that i know the reason for
this problem, but at least i was able to find out what caused it. i
have a custom filter function that is called when sorting/indexing.
in it was a substitution to delete remaining non-word characters
(\W) which obviously caused all these buffer overruns. commenting
out that particular line, everything went fine :-) actually, for
sorting it could stay, only when filtering in the indexing stage
things break due to this substitution.
unfortunately, i can't claim to understand it. it was only - more or
less - by trial & error that i arrived there. and after all, i don't
think emanuel's problem was exactly the same. so this might not be
of any help to you, emanuel, sorry ;-)