James Gardner wrote:
yoink Is it considered standard practice to allow
non-ascii usernames though? Particularly since usernames are supposed to
be case-insensitive in AuthKit?
I'd like to make allowing non-ascii usernames standard practice, trying to
make pylons i18n the best possible.
Hi, list...
I'm using AuthKit in my application and seem to have trouble when the
login form gets me the username as a Unicode string. I use the famous
line:
form_username = request.params.get('username')
request.environ['paste.auth_tkt.set_user'](form_username)
This leads to Unicode errors (I
Hi Christoph,
I've just tested AuthKit 0.4 with an Arabic username and yes, there is a
problem because the browser encodes the Arabic as HTML entities because
there is no charset specified when the form is produced. Other than that
it all seems to work fine. Is it considered standard practice
Hi Christoph,
If you use the latest AuthKit 0.4 and specify:
form_charset=UTF-8
to the authenticate middleware you should find your unicode strings work
OK. You'll need to make sure your Python source files are properly
encoded though so the users information correctly picks up the unicode
