Explicitly figure out handling of internationalized domain names
We should explicitly figure out and document how HTTPS Everywhere works with internationalized domain names (IDN), and make sure that it actually works according to the documented behavior. Do you write rules using UTF-8 internationalized names, punycode-encoded names, or neither? Do the rules actually trigger and rewrite correctly?
A potential problem about this was reported at
https://mail1.eff.org/pipermail/https-everywhere/2012-May/001435.html
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information