The setup wizard should accept unicode email addresses. That means the email addresses need to be UTF-8 encoded before being uploaded to the server in Weave.Service.createAccount() and before hashing the value to compute the username.
This is WONTFIX in the BrowserID Sync world. I wonder if BID supports unicode email addresses...
(In reply to Gregory Szorc [:gps] from comment #1) > I wonder if BID supports unicode email addresses... From talking to lloyd on #identity, the current browserid frontend would reject the email address.  However I couldn't find anything the in protocol spec that disallowed unicode. Assuming the backend supports unicode, there shouldn't be a problem.  - https://github.com/mozilla/browserid/blob/dev/resources/static/shared/validation.js#L9
Dchan, there is an open ticket for unicode support in bid, but the bid folks do not seem super convinced it is worthwhile? https://github.com/mozilla/browserid/issues/1294 philikon: is there a sample unicode email address I can throw at them? ^