Does window.location.hash contain the encoded or decoded representation of the url part?
When I open the same url (http://localhost/something/#%C3
Answering to my own question, my current solution is to parse window.location.href instead of using window.location.hash, because the former is always (i.e. in every browser) url-encoded. Therefore the decodeURIComponent function CMS proposed can always be used safely. YUI does the same, therefore it can't be that wrong...