> > Similarly, if the template processor relies on user input, it > should be > subjected to NFC per RFC 3987, while if it's a machine value, the > NFC > form should have been used in the first place. ... which effectively means that the template processor does not apply any form of normalization. NFC should have been used early; if it wasn’t, for some reason, IRI doesn't impose it. Note the point, though, about include-normalization. Consider: http://example.org/{boo}{moo} Let 'boo' = 'e' Let 'moo' = '\u0301' (a combining mark) The resulting URI is not NFC, even though each of the parts is. AddisonReceived on Wednesday, 17 September 2008 02:17:52 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 17 September 2008 02:17:53 GMT