[kdewebdev-site] Localisation

[D.Reddish]

I have been wanting to mail about this since yesterday.

When I came to this. I was specificaly asked for something that would
keep the server load down. So that is what I did. And made it as simple
as possible for anyone looking at it to understand as I could.

Chris Hornbakers proposal seems to me from reading the posts to be being
met with some degree of missunderstanding.
Essentialy it is very simple.
Inside your conventional web page you have your text which is flagged
for translation. 
_(here is the cod to be translated)
This text is extracted to a file for translation.
If your in the default language you just get the text as is
_(here is the orriginal cod again)
 if another language is flagged you get a check to see if the
translation is avaliable and if it is then its loaded
_(heir ist die cod translation)
 in place of the orriginal language.


His proposal (bearing in mind that I have not actualy seen his code) is
a valid one. It results in a very clean structure to the site and makes
use of some excelent managment tools.

In a nutshell the position as I see it is this.....

Chris's proposal is technicaly sound. Uses excelent tools for the
purpose. Results in an uncomplicated file structure. But encounters
significant server overhead. Translations centralised.(One big file per
language, plus a machine file to telling what goes where and belongs to
what and replaces what)

The type of proposal I put forward uses very basic code that is easily
understood. Uses the minimum server resources, but at the cost of more
complexity in the file structure. (One file per translated page)

So here is the tradeoff.
	If server overhead isn't an issue. Then Chris's style of proposal is
technicaly the better.
	If server overhead is an issue. Then a more basic approach is the one
to go for.

Please bear in mind that there are several facts that I am currently
ignorant of. 
a, what server resources are in fact avaliable.
b, the likley usage that it will be subject to.


I don't know what the situation with these facts are so I won't attempt
to make any kind of a call on this.
But I will say that server resources permitting I personaly would
support Chris's style of approach, it is certainly a more technicaly
elegant solution.
And that always appeals to me.

Dave Reddish
-- 
D.Reddish
D_Reddish at jabber.org
wykd at jabber.org
ie_stinks at yahoo.com
dave_r at jabber.kdewebdev.org