问题描述
我希望允许我的用户使用Unicode作为密码.
I would like to allow my users to use Unicode for their passwords.
但是，我发现很多网站不支持该功能(例如Gmail，Hotmail).
However I see a lot of sites don't support that (e.g. Gmail, Hotmail).
所以我想知道是否存在一些我忽略的技术或可用性问题.
So I'm wondering if there's some technical or usability issue that I'm overlooking.
我在想这是否一定是可用性问题，因为默认情况下.NET接受Unicode，并且是否在此基础上构建了Hotmail(即新的Live邮件)，我不明白他们为什么会限制它
I'm thinking if anything it must be a usability issue since by default .NET accepts Unicode and if Hotmail--er, the new Live mail--is built on that, I don't see why they would restrict it.
有人遇到过类似的问题吗?
Has anyone encountered similar issues?
推荐答案
我确定没有技术问题，但是gmail和hotmail可能不故意支持该问题.这种网站具有广泛的受众，应该可以从任何地方访问.
I am sure there is no technical problem but maybe gmail and hotmail are not supporting that on purpose. This kind of websites have a wide audience and should be accessible from everywhere.
让我们假设用户使用日语密码，但是他正在旅行并去网吧，并且没有日语支持，因此用户将无法登录.
Let's imagine the user have a password in Japanese but he is on travel and go to a cyber cafe and there is no Japanese support the user won't be able to login.
另一个问题是分析密码的复杂性，要确保用户没有输入英文通用词不是那么困难，但是用中文/俄语/泰语输入呢?随着添加更多语言，分析密码的复杂性要困难得多.
One other problem is to analyze the password complexity, it's not so difficult to make sure the user didn't type a common word in English but what about in Chinese/Russian/Thai. It is much more difficult to analyze the complexity of a password as you add more languages.
因此，如果您希望系统可访问，最好确保用户能够在各种设备/操作系统/环境上键入其密码，因此，使用具有最常见符号的字母数字密码(等.)是随处可见的一组好字符.
So in case you want your system to be accessible, it's better to ensure that the user would be able to type his password on every kind of devices/OSes/environments, so the alpha numeric password with most common symbols(!<>"#$%& etc..) is kind of good set of characters available everywhere.
这篇关于我应该在密码中支持Unicode吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！