- From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
- Date: Tue, 09 Feb 2010 11:19:15 +0100
- To: Joseph Anthony Pasquale Holsten <joseph@josephholsten.com>
- Cc: uri-review@ietf.org, public-html <public-html@w3.org>, URI <uri@w3.org>
Joseph Anthony Pasquale Holsten wrote: > On Feb 8, 2010, at 3:40 PM, Lachlan Hunt wrote: >> http://www.ietf.org/id/draft-holsten-about-uri-scheme-03.txt > > A quick diff suggests this is the same as what had been up in github, with > - s/recognize/recognise/ > ... > All of which sounds great, and I've incorporated into the current > branch an http://github.com/josephholsten/about-uri-scheme. > > The current branch also includes > - s/Internationlized/Internationalized/ We should be consistent with the use of en-GB or en-US spellings. Normally, I would prefer to use en-GB, but in this case, since we have to deal with references to sections in RFC 3986 for "... Normalization", which uses the US spellings, and various other refernces that should use US spellings, it's easier and more consistent to use en-US for everything, than to carefully use en-GB for most things while leaving en-US where necessary. > And I'd love it if there was a way to make Encoding Considerations > and Normalization less awful to read. All I want to say is that > normal encoding and normalization procedures apply, we're not trying > to use any special cases. Instead I have 200 words of jargon. I think these are fine as is > Is that all that remains? I'm not aware of anything else. -- Lachlan Hunt - Opera Software http://lachy.id.au/ http://www.opera.com/
Received on Tuesday, 9 February 2010 10:19:49 UTC