PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3154 *** shadow/3154 Fri Aug 17 07:00:54 2001 --- shadow/3154.tmp.18634 Fri Aug 17 07:00:54 2001 *************** *** 0 **** --- 1,31 ---- + +============================================================================+ + | format-number usage on international platform | + +----------------------------------------------------------------------------+ + | Bug #: 3154 Product: XalanJ2 | + | Status: NEW Version: 2.1.0 | + | Resolution: Platform: PC | + | Severity: Major OS/Version: Windows NT/2K | + | Priority: Other Component: Xalan | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + Using format-number on international platform throws: + + javax.xml.transform.TransformerException: ElemTemplateElement error: Malformed + format string + at org.apache.xpath.XPath.execute(XPath.java:283) + + <xsl:value-of select="format-number(AMT,'#,##0')"/> + + I know the regional settings for WinNT4.0 are set to Turkish and the thousands + separator is a '.' (period) and I have tested the format as: + + <xsl:value-of select="format-number(AMT,'#.##0')"/> + + and it works. BUT I know on Xalan 1.2.2 the comma worked correctly in that it + meant to use the thousands separator of the platform and not literal meaning.
