For those of you using the locale functions in CFMX beware of significant
issues when using SUN JRE 1.4.1
>From our testing of CFMX on JRE 1.4.1 we found that all of the following
functions returned unexpected results.
LSIsDate()
- Set Locale to "English (UK)"
- Pass LSIsDate() value of "13/12/02" which is Dec. 13 2002 a valid date.
- Returns error of "13/12/02" is an invalid date format.
LSDateFormat()
- Set Locale to "English (UK)"
- Pass LSIsDate() value of "13/12/02" which is Dec. 13 2002 a valid date.
- Returns error of "13/12/02" is an invalid date format.
LSParseDateTime()
- Set Locale to "English (UK)"
- Pass LSIsDate() value of "13/12/02" which is Dec. 13 2002 a valid date.
- Returns error of "13/12/02" is an invalid date format.
Note: Appears almost as though the setlocale() even though when you run
function getlocale() it returns the correct label. If you do enter in the
"English (US)" formatted date as "12/13/02" the functions work but the
LSDate functions do not show any of the localiezed values. ie. Deciembre
instead of December if Spanish etc.
LSCurrencyFormat(n,"none")
- Set Locale to "English (UK)"
- Pass LSCurrencyFormat() value of 123456.78
- Returns 123,456.78 (proper except that in locales with different
separators the separators do not change)
LSCurrencyFormat(n,"local")
- Set Locale to "English (UK)"
- Pass LSCurrencyFormat() value of 123456.78
- Returns GBP123,456.78 (Localized currency specifier does not work)
Note: Should return local currency specifier but does not.
LSCurrencyFormat(n,"international")
- Set Locale to "English (UK)"
- Pass LSCurrencyFormat() value of 123456.78
- Returns GBP123,456.78 (proper for some locales but shows EURO for many
locales that used to be specific to that locale).
Note: For all currencies the thousands separator and other separators do not
change regardless of the locale that has been set.
We have downgraded to JRE 1.4.0_02 as this seems to have fixed the problems
mentioned above. However, I point all this out as many on this list have
suggested that moving to JRE 1.4.1 has fixed your JDBC problems. This may
not be a good solution if you are using LS functions. If someone at
Macromedia would like to see this error in action please contact me offline
and we can make it available. What is the recommended JRE for CFMX? CFMX
ships with 1.3.0_03 but in the documentation Migrating ColdFusion 5
Applications page 9 it states the following for the CFHTTP tag. "The
timeout attribute requires the Java Development Kit (JDK) 1.4; otherwise,
ColdFusion MX ignores this attribute". Is JRE 1.4 the reccomended JRE?
Secondly, through this testing we have also noticed a difference in the way
CF 5.0 processes localized dates and the way that CFMX processes localized
dates. To be honest I think the way that CFMX processes the locale makes
more sense than previously, but it is still a difference you should be aware
of.
In CF 5 locale set to "English (UK)":
#LsDateFormat('12/13/02', 'mmmm dd yyyy')# - Cold Fusion returns no errors
and formats the date as "December 13 2002"
In CFMX locale set to "English (UK)":
#LsDateFormat('12/13/02', 'mmmm dd yyyy')# - Cold Fusion returns an error
of "12/13/02" is an invalid date format.
If you add the LSParseDateTime() to the equation in MX:
#LsDateFormat(LSParseDateTime('12/13/02'), 'mmmm dd yyyy')# - Cold Fusion
returns no errors and formats the date as "December 13 2002"
Enjoy! We have :(
Mark Johnson
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
