This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The following formatting functions all accept the empty sequence for the $language argument. fn:format-dateTime($value as xs:dateTime?, $picture as xs:string, $language as xs:string?, $calendar as xs:string?, $place as xs:string?) as xs:string? fn:format-date($value as xs:date?, $picture as xs:string, $language as xs:string?, $calendar as xs:string?, $place as xs:string?) as xs:string? fn:format-time($value as xs:time?, $picture as xs:string, $language as xs:string?, $calendar as xs:string?, $place as xs:string?) as xs:string? and have consistent handling of the $language argument. However fn:format-integer does not permit the empty sequence and has inconsistent handling of invalid values. fn:format-integer($value as xs:integer?, $picture as xs:string, $language as xs:string) as xs:string Could this not be made consistent with the other formatting functions, so that 1. a call to the two-argument function is equivalent to a call to the three-argument version with the third argument set to the empty sequence. 2. If the $language argument is omitted or is set to an empty sequence, or if it is set to an invalid value or a value that the implementation does not recognize, then the processor uses an
Discussed by the WG on 15 Nov 2011, agreed that the specs should be aligned and that when format-integer is given any of: (an empty sequence; nothing; an invalid value; a value not supported by the implementation), it should in each case fall back to a default language.
Thanks.