Is there any way we can modify the script to allow diacritics in usernames, eg: Renée rather than Renee?

Should we even be thinking about it?

Same question, put in a different way: Is there a necessary reason to limit usernames to 7-bit alphanumeric characters?

Is it something to do with accepting mixed-case logins?

off hand, I'd have to say it has to do with compatibility.

But, if your system is set up to allow the extended character sets, then it should work. I'm sure GT has dealt with this before, so maybe leave a message/inquiry for support, if someone doesn't answer it here.

Not only community, but the associated apps have to be set up to recognize the extended sets. In a new installation, that may not be a problem. In an existing, or migrated one, it might be.


PUGDOG� Enterprises, Inc.

The best way to contact me is to NOT use Email.
Please leave a PM here.

It fails a regex -- but it is not obvious what we would have to hack to get it to work.

The default GComm header template contains the line
which shows that the script expects 8-bit characters.

We think this is a serious flaw. We can't ask our non-Anglo users to avoid characters which are on their keyboards.

In the meantime -- we are prepared to hack. GT? What should we do?

Hi,

You can change the regex in community.conf:

'signup_username_regex' => '^[\w\-\.]{3,}$',

I believe the main reason for it is compatibility with Gossamer Mail which does not allow those in the username.

Cheers,

Alex
--
Gossamer Threads Inc.

We have changed it towhich seems to do what we want.