Re: Better default namechooser

On 2007-10-12 10:21:28 +0200, Philipp von Weitershausen=20
<[email protected]> said:

> Christian Zagrodnick wrote:
>> I constantly run into the fact that the default namechooser in Zope 3=20
>> is too dumb.
>>=20
>> Does anybody object in making it a little more smart? That is:
>>=20
>> * replace all non us-ascii and otherwise harmful chars by something  =20
>> useful (base-form or alike)
>=20
> Why would you want to replace all non-ASCII characters by default?=20
> Names of contained objects can be unicode, and URLs can contain unicode=
=20
> segments as well (encoded as UTF-8). Having the default namechooser=20
> make the arbitrary decision of disallowing everything that's not ASCII=20
> seems quite arbitrary.

Of course they can. But looking from the browser/user perspective any=20
URL containing %XY looks just strange. Also those urls are often=20
garbled by mail programms or alike.

>=20
>> * replace spaces by - or _
>=20
> Again, object names may contain spaces. I don't understand why this=20
> should be the *default* policy. If you need this kind of stuff, then I=20
> suggest you write your own namechooser; it's quite trivial.

Of course it's trival. Only that I've *always* had to replace it with=20
something else for every single project so far. So from my perspective=20
the default might work but is sort of useless.

But well, maybe it's not work the effort since we've eggs now.

--=20
Christian Zagrodnick

gocept gmbh & co. kg  =B7  forsterstrasse 29 =B7 06112 halle/saale
www.gocept.com =B7 fon. +49 345 12298894 =B7 fax. +49 345 12298891