We use a similar approach (I live in Switzerland, using four languages is quite common for website). Since we are poor guys and often work on small projects, we define the variables using <cfscript> inside a bunch of dedicated files for each language. Then we include the relevant file on the fly based on the user's preference (usually stored inside a session var)
-- ---------------------------- Massimo Foti [EMAIL PROTECTED] Team Macromedia Volunteer for Dreamweaver www.macromedia.com/support/forums/team_macromedia ---------------------------- "Pete Ruckelshaus" <[EMAIL PROTECTED]> wrote in message news:010a01c19abd$88d54820 > The approach we took was to set all text on all pages as variables; using > includes or custom tags for the "common" (i.e. header, footer, navigation) > will make this task easier. All of the values for those variables were then > stored in a database. The default language is set to the native language of > the audience, which can be set as a cookie or a session variable (and which > the user can change by selecting a new language), which you can then use to > query against the database to grab the text values. For performance, you > either want to cache the query output, OR you want to set the language > variable in the URL and then you can use cfcache. > > We also provided our own content management interface to allow the > translators to easily translate the text from native language (English) to > the other languages. > > Obviously, it's more complex than this, but that's the general idea. > > Pete ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation · $99/Month · Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
