If you want machine translation, then you can use the free Google
Translation service for that. The quality of the translation can be
quite variable, naturally, since it’s simple algorithmic replacement,
not the work of a native speaker.
If you want to maintain multiple copies of the text yourself, then
you could make a simple replacement system using a lookup table –
essentially a large text file with all of the text from your site in
it. To make a new version of the site, you would translate this text
into a new language, and rename the file. Then on the server, you
could use some Clever Scripting™ to intercept all page requests,
slurp the requested page layout into a variable, and then interpret
the url to determine which version of the text to use as a substitute.
So you would point visitors to
http://example.com/es/index.html
or
http://example.com/fr/index.html
And the server would work out to use the es.php translation table or
the fr.php translation table.
I did some work on an Action to make this easier quite some time ago.
I’ll see if I can find it.
Walter
On May 7, 2008, at 10:34 AM, Keith Martin wrote:
Sometime around 7/5/08 (at 05:19 -0400) Heather Kavanagh said:
Remember I am a codeaphobic, so anything outwith Freeway will need
to be explained in very simple terms!
Interesting. Heather, do you have Scottish roots? The word “outwith”
is peculiarly Scottish in origin and usage. Although it isn’t hard to
figure out, it isn’t used by people from anywhere else in the world!
As far as your actual question goes (don’t you just hate it when
someone ignores what you say ang fixes on how you say it?), take a
good close look at Max’s WebYep actions. You probably need to store
the content externally and have the right stuff pulled into the
design on the fly, when pages are served.
k
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options