If I were attempting this, I would personally tend towards extending the core types as a way of providing multi-lingual content.
The simplest way to select a language would be to add eg lang=en to the url. Somewhere in index.cfm check for that url value and store it in client or cookie scope (to provide persistance). Then the webskins would detect which language to use. Or if you were taking the multi-branch approach, give each branch the alias of the language acronym, and index.cfm would then set application.navid.home = application.navid[client.lang].
Blair
On 9/19/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
Nobody wants to take the risk here? How much would it cost me to hire
someone to make such a website?
Orlando
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/farcry-dev
-~----------~----~----~----~------~----~------~--~---
