Either way you'll want to cache all (or at least the majority of the) the strings in memory on application load.
If you're making an admin tool to edit the strings, whether it writes to a flat file or to the DB wouldn't really matter that much. The resource bundle pattern is pretty well used these days. On 10/2/12 2:01 AM, Edward Chanter wrote: > We're about to embark on a project for which locallisation is a requirement > and it's the first time I've done this. I understand the basic concepts > about having data containing the words and phrases needed on a website > stored with versions for each language but I'm trying to figure something > out: what's the best way to store the data? > > I see a lot of sites using flat JSON/XML/Whatever files with the different > translations but is this something that would work well coming from a > database? Is it more efficient to use a flat file or simply have a database > store the words and phrases in columns with a new row for each language? > One advantage I can see with a database option is that it makes adding new > languages a little easier for people with no access to the file system on > the server. It could also be managed with web forms which seems easier than > having a massive flat file with loads of XML or JSON data structures. > > The purpose of this question is to see how you all do it and whether there > are any pit-falls I should watch out for? > > Thanks ;-) > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:352796 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
