Website structure + different languages

[Bramvg]

As you all know everything starts with a good folder structure
and site structure before realy going into the coding.

My problem: the site I will create will be available in different languages
and most likely in a short period of time also in different countries.
Of course I want to use the advantage of CF and create ONLY once the
scripts.

Now, the site is personalized [Hello David, on this page you can....] and that
is a part of the problem.
The Database structure as I see it will be like:

Database
-----------
- AutoID
- Country
- Language
- PageID
- Txt1
- Txt2
- Txt3
- ....

Sample:
----------
- 11
- US
- EN
- 13
- Hello
- , on this page you can....


In this way the authors (not me) can easyly translate content using an online updater.
Because when I code the page, I will first run a select query with: PageID (hard coded),
and select the fields: Txt1 + txt2 + ...

The code will look like:
-------------------------------

#txt1# #session.Firstname# #txt3#

The problem I have is that I'm afraid the site will be 'slow', any suggestions
how I should do this? I just think this is not the fasted way for outputting
information.


A possible sollution that I had, but I don't know how and if it's possible, is to
make a 'CFM Generator' that I run offline and generaters the site content and leaves
the #session.Firstname# and other dynamic things in it.

So, I would be able to generate CFM code for an EN (english) version, FR (French) version,...
without having to makes copies of CFM code.

Any help would be more than welcome!

With kind regards
bram

 

[iqof188]

Bram, let's take into account one of the basic rules of designing a database: give each entity its own table.
If you apply this "golden" rule ;-) on your design, you will see that certain things that need to be stored only once (such as the English phrase "Welcome #session.username#" or the French phrase "Bienvenue etc...&quot.
What I would suggest is that you design a relational database, since poor performance is mostly not caused by DB-interaction, but caused by poor database design.
Unless you use Access as your database (which IS slower than SQL Server and Oracle for instance), you should not worry about performance, especially not when you decide to do some query-caching for some db-content that will not change a lot (like "Welcome to my site" or stuff like that.
Hope this helps, good luck!


<webguru>iqof188</webguru>