RE: reviewing draft-weber-iri-guidelines-00

   4.  Replace each entity references with its corresponding character.

This can't be done until after the fields of an IRI are parsed out. Example: in a path, you don't want an escaped / or # or ? to be transformed until after you've parsed out the path.

This is a catch-22 situation. Full normalization (which, as noted, we agree, should not be applied) would depend on unescaping the characters, whereas full unescaping, as you note, may break things. Perhaps this wants to be “unescape iunreserved characters”?

Addison


Addison Phillips
Globalization Architect (Lab126)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.

Received on Wednesday, 6 July 2011 00:33:43 UTC