3 ms·
For file names, URLs, domain names, etc. it's usually the safe thing to do.
by olalonde 14y ago
For file names, URLs, domain names, etc. it's usually the safe thing to do.
- recursive 14y agoNot as often as often as handling all characters.
- UnoriginalGuy 14y agoWho's filenames aren't unicode? Also domains and URLs can be unicode too.
- esrauch 14y agohttp://en.wikipedia.org/wiki/IDN_homograph_attack http://en.wikipedia.org/wiki/IDN_homograph_attack
- olalonde 14y ago> Who's filenames aren't unicode? Many filesystems don't support unicode or support only a subset of it: https://en.wikipedia.org/wiki/Filename#Comparison_of_filename_limitations https://en.wikipedia.org/wiki/Filename#Comparison_of_filenam... > Also domains and URLs can be unicode too. Domains: it depends at which level you are dealing with them. See https://en.wikipedia.org/wiki/Internationalized_domain_name https://en.wikipedia.org/wiki/Internationalized_domain_name Internationalized domain names are stored in the Domain Name System as ASCII strings using Punycode transcription. URLs: Unicode characters are not allowed in URLs. See http://www.faqs.org/rfcs/rfc1738.html http://www.faqs.org/rfcs/rfc1738.html and http://www.blooberry.com/indexdot/html/topics/urlencoding.htm http://www.blooberry.com/indexdot/html/topics/urlencoding.ht... only alphanumerics, the special characters "$-_.+!*'(),", and reserved characters used for their reserved purposes may be used unencoded within a URL.