On May 9, 2007, at 12:51 PM, Paul Hastings wrote:

> Jon Clausen wrote:
>> 1) Sets the language locale variable which is cross referenced to the
>> #server.coldfusion.supportedlocales#.  This allows you to use
>> Coldfusion internationalization for dates/currency formatting.
>
> you have to be careful with this. cf relies on core java for it's  
> locale
> resource data which is often out-to-lunch (recent case in point,  
> core java up to
> version 6 flubs en_Au & en_NZ time formats, there are gobs & gobs  
> of other
> problems--the devil *is* in the details). you need to test your  
> supported
> locale's data in core java versus something more "standard" like  
> the CLDR
> project www.unicode.org/cldr/ then decide your approach (native cf  
> i18n bits
> which are easier to use & a bit faster vs something like icu4j  
> which runs off
> the CLDR data & has other goodies like non-gregorian calendars).

For the sake of brevity, I left out that this particular site  
bypasses any CF/Java locale information for dealing with currency.   
That's been an ongoing problem,  espeically with Asian and Middle  
Eastern currency symbols and formats.   A  good point on en_Au and  
en_NZ time formats, though.  I haven't run into that issue with any  
of the client's partners, though we have several from Australia.  I  
may have to look into a change there.

>> particular site has around 50 different international sites pointing
>
> which really argues for the more traditional approach of resource  
> bundles &
> their ecosystem. i would hate to manage something this complex w/ 
> notepad or it's
> equivalent.

Not meaning to sound defensive, however, I don't find this aspect  
particularly complex.  At the beginning, adding a new locale or   
Language posed new and interesting issues - Bangladesh, especially,  
was fun :) -  but one "trip around the world" so to speak and the  
best practices emerged.  Now dealing with adding new language/ 
currency to the application is a fairly straightforward affair.

Don't get me wrong: I'm not saying that  resource bundles aren't a  
more robust and inclusive method of handling internationalization,  
but also I think the needs of the Application may dictate whether  
it's a viable solution for a given project.

  In this case, the current structure allows a great deal of  
flexibility for the client and their partners and minimizes the  
development time required to maintain the application- providing a  
better ROI and speed-to-market for the client as they grow their  
business internationally.  Resource bundles might be an option if the  
percent of business being driven from those markets necessitates it,  
though, so I would never count that option out.

Warm regards,

Jon

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
ColdFusion MX7 by AdobeĀ®
Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. 
Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:277479
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to