W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2004

Re: Fw: [XSLT2.0]

From: Igor Hersht <igorh@ca.ibm.com>
Date: Thu, 1 Apr 2004 17:11:10 -0500
To: Henry Zongaro <zongaro@ca.ibm.com>
Cc: public-qt-comments@w3.org
Message-ID: <OF520E5EAD.C2F201FC-ON85256E69.007915B5-85256E69.0079DE44@ca.ibm.com>

I agree,  but I think it could be good idea to mention that string after
second tag-separator
could be used in implementation defined way.
 I guess that at least Java processors would use the sting  the same way
which is to
 map to the variant.

Igor Hersht
XSLT Development
IBM Canada Ltd., 8200 Warden Avenue, Markham, Ontario L6G 1C7
Office D2-260, Phone (905)413-3240 ; FAX  (905)413-4839

             BM                                                         To 
                                       Igor Hersht/Toronto/IBM             
             04/01/2004 01:41                                           cc 
             PM                        public-qt-comments@w3.org           
                                       Fw: [XSLT2.0]                       


     In [1] you submitted the following comment:

Igor Hersht wrote on 2004-01-11 05:01:13 PM:
> lang attribute used in xsl:number(12 Numbering)
> and xsl:sort (13.1 The xsl:sort Element) language argument used in
> date formatting functions (16.5 Formatting Dates and Times)
> format-dateTime, format-date, format-time
> The attribute and arguments have common rules "The effective
> value of the attribute must be a value that would be valid for
> the xml:lang attribute"
> (http://www.w3.org/TR/1998/REC-xml-19980210#sec-lang-tag).
> The specs define precisely mapping from value of the attribute to ISO 639
> language
> and ISO 3166 country codes.
> Problem Mapping from a value of the attribute to a variant code is not
> specified.
>  Solution
> A variant code should be constructed from the substring after the second
> tag separator
> by converting the substring to upper case and replacing all '-'
> with '_'.
> The variant code is ignored, if implementation cannot find a resources
> the variant code
> with given ISO-639 language and ISO-3166 country code. A warning message
> should be issued
> in this case. Changes in behavior caused by the variant are
> defined.

     Thank you for submitting your comment.

     The XSL Working Group discussed your comment.  The working group
decide not to make any change to XSLT 2.0. The working group felt that this
sort of information about variants wouldn't be appropriate in XSLT 2.0, but
would be more appropriate in a specification that is a successor to RFC

     May I ask you to confirm that this is an acceptable response to your


Henry Zongaro      Xalan development
IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
Received on Thursday, 1 April 2004 17:13:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:56:56 UTC