This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html Multipage: http://www.whatwg.org/C#the-id-attribute Complete: http://www.whatwg.org/c#the-id-attribute Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: how to specify UNICODE characters in a URL for id? Posted from: 2601:7:f00:2ca:b011:20b5:a96c:ac11 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0
when encoding a hash (#) in a URL to jump to an id, you can't use numeric entities in the URL because it already has a hash mark and it has a special meaning. so I am curious if UNICODE characters are put directly into the URL as characters to solve this problem. Example UNICODE character: ʼ (Modifier Letter Apostrophe) somefile.html#ownerʼs obviously doesn't work for URLs because there are 2 #'s, though probably perfectly valid for id's which would be id="ownerʼs"
numeric entities also cause a problem if they are put in earlier in a URL. just thinking that maybe this possible bug belongs in URL category? so changing to URL. has this already been resolved? sorry about the mixup.
You can use the actual character or a sequence of utf-8 bytes that is percentage-escaped. See the URL Standard.