- From: Ashok Malhotra <ashokma@microsoft.com>
- Date: Fri, 28 Nov 2003 12:25:21 -0800
- To: "Alberto Massari" <amassari@progress.com>, <public-qt-comments@w3.org>
Fixed! Thanks! All the best, Ashok -----Original Message----- From: public-qt-comments-request@w3.org [mailto:public-qt-comments-request@w3.org] On Behalf Of Alberto Massari Sent: Monday, November 17, 2003 8:51 AM To: public-qt-comments@w3.org Subject: [F&O] normalize-unicode The new definition for normalize-unicode has replaced the "W3C" normalization form with the string "fully-normalized". However, the description states: "The effective value of the $normalizationForm is computed by removing leading and trailing blanks, if present, and converting to upper case. [..] - If the effective value of $normalizationForm is "fully-normalized", then the value returned by the function is the value of $arg is the fully normalized form." Now, the effective value of $normalizationForm can never be "fully-normalized"; while it can be "FULLY-NORMALIZED", as the string is made upper-case. Alberto
Received on Friday, 28 November 2003 15:26:48 UTC