> Finally, I would recommend against using any cgi variables or geographic lookup data as the sole determination of language. Great to use this to initiate the language on the first visit, but store a language id in a session or client variable and reference that to drive the actual content so you can provide links to alternate languages. If your system provides (or enforces) a means of associating pages, you can even provide links to the same page in all available languages (Tapestry does this), i.e. product information for product x in Spanish, English, German and French. :)
no, its generally considered best practice to transparently try to sniff a users language/locale preferences & fall back on some default language if you can't accomplish this. and your app should *always* offer users the chance to manually swap preferences--and lets not use any of those childish language flags, you'll end up insulting somebody--since you should be using unicode, its best to offer language choices in each language (french in french. thai in thai, etc.). it goes without saying that once sniffed or manually determined you should stock that preference away somehow & use that info on subsequent visits. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. http://www.cfhosting.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
