- From: Dave McAlpin <Dave.McAlpin@epok.net>
- Date: Thu, 22 Jul 2004 02:30:23 -0400
- To: "Martin Duerst" <duerst@w3.org>, <uri@w3.org>
- Message-ID: <1636C74D3A020E4781DC433A4D901D950F15E9@empire.dc.epokinc.com>
Got it. I knew ASCII characters were valid UTF-8 sequences so I'm not sure why that sentence tripped me up. It may be because I assumed the previous sentence, which requires UTF-8 encoding for non-ASCII characters, already disallowed non-UTF-8 encoded characters in host. Anyway, I just read too much into it. Thanks for the clarification. Dave ________________________________ From: Martin Duerst [mailto:duerst@w3.org] Sent: Wed 7/21/2004 9:59 PM To: Dave McAlpin; uri@w3.org Subject: Re: Percent-encoding in host Hello Dave, UTF-8 includes US-ASCII, so there should be no problem. You say 'From the context, a "UTF-8 character sequence" seems to apply only to non-ASCII characters.'. How did you come to that conclusion? Regards, Martin. At 17:34 04/07/21 -0400, Dave McAlpin wrote: >I apologize for raising this issue so late in the process, but I'm >confused by the sentence in the last paragraph of section 3.2.2 that >reads, "URI producing applications must not use percent-encoding in host >unless it is used to represent a UTF-8 character sequence." From the >context, a "UTF-8 character sequence" seems to apply only to non-ASCII >characters. Is the rule effectively that you're not allowed to >percent-encode ASCII characters in host? >If that's the case, what's the proper way to represent characters in the ><sub-delims> set that appear in <reg-name> as data, not as delimitters? > >Dave >
Received on Thursday, 22 July 2004 02:40:41 UTC