W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2005

[Bug 1829] New: clarify whether URI escaping is affected by the normalization-form

From: <bugzilla@wiggum.w3.org>
Date: Tue, 02 Aug 2005 18:02:05 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1E015Z-0000M0-Sr@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1829

           Summary: clarify whether URI escaping is affected by the
                    normalization-form
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Serialization
        AssignedTo: joannet@ca.ibm.com
        ReportedBy: joannet@ca.ibm.com
         QAContact: public-qt-comments@w3.org


Original comment raised by Bjoern Hoehrmann 
[http://lists.w3.org/Archives/Public/public-qt-comments/2005Aug/0002.html]

It's not clear to me
that normalization-form has no impact on resource identifier escaping
... For example, with 

  escape-uri-attributes = no
  normalization-form = NFC

input such as

  <a href='Bjo&#x308;rn' ...

would yield in

  <a href='Bj&#xf6;rn' ...

With 

  escape-uri-attributes = yes
  normalization-form = NFC

however it would yield in, as I understand it,

  <a href='Bjo%CC%88rn' ...

which is not in NFC even though that has been requested. Also note that
RFC 3987 requires the result to be NFC-normalized under some circum-
stances, so I think this needs to be clarified in the draft.
Received on Tuesday, 2 August 2005 18:02:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:39 GMT