Tony Weeg wrote: > :) yeah, no sh*t so why not prepare for that? or at least maybe use this small app to learn some new i18n techniques?
> come on man... of course they do, and ive already got a dd/mm/yyyy > switch based on locale :) you should be using something more i18n than that. simple enough to use setLocale (en_US/en_GB/en_AU/en_CA/es_ES) and lsDateFormat w/one of the standard formats (full,long,medium,short, that way you can more easily parse the dates back to datetime objects). the new i18n stuff in mx is simply fantastic. > true... but, as long as the xml is there, and i can see what i've been down that road w/some jsp from one large GIS company. nobody easily knew what was what. always have to run back to the original text to figure things out. it was a mess to extend, a mess to debug. it's just not a good idea. > to the web page, then im good, right? i get that it would be EASIER from > the code view to manipulate that... no doubt, but other than that, im > not sure it has any merit? right, or am i missing something here? obviously you are missing something if you think easier code maintainence alone hasn't any merit. what if a toilet seat de-orbits onto your head & knocks you into hamburger? want "#textlabel44#" on your headstone? > :) yes, dad! jk. true, true, all true! yes, but it's i18n, i get all excited about i18n stuff. if you want to be sloppy about plain cf, go ahead. if you get sloppy about i18n stuff, i can't help but comment. > so you are suggesting, having a variable called > application.adminBundle, that has 2 structures (or three or however in this case, i guess that's one structure with a bunch of keys. for complex apps we normally breakdown rb's into logical chunks (structs) & then into groups within the rb itself (rb tool handles that we don't use these in app code but it makes things much easier to manage). in some cases we don't 100% normalize these as we've found it's easier on developers to deal with stuff in homogeneous chunks (thisRb, thisRb, thisRB, etc.) rather swapping back & forth (thisRb, commonRB, thisRb, etc). in your case one rb with whatever logical groups your app needs is enough. and my last word on this, if you're dealing with currency symbols, use unicode rather than latin-1. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:199641 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
