(1) would the process of managing translations for a db be > that much different than managing translations for resource bundle > properties files?
I think the main difference during translation would be in what you provide the translator. Utilizing text based resource bundles you can provide two files, one the local version and the other the English version. The translator will translate directly into the new RB and return that to you. Utilizing a DB backed RB you have to either develop a UI for the RB editing, or export from the DB to a text file to send to the translator. >(2) I'm certainly not trying to re-invent the wheel, IMO there are a few key reasons to use text based RB's. First, using the tools to manipulate RBs make it easy to switch between bundles which would have to be custom developed with your solution (e.g. your 'locale' column that would have to be inserted into every table that contained rb's). A second reason (IMO) is the dependency that is needlessly created between the code and the DB server. Rich Kroll ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Enterprise web applications, build robust, secure scalable apps today - Try it now ColdFusion Today ColdFusion 8 beta - Build next generation apps Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:293583 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
