|
thats more or
less the method i've used, but made simpler (or do i mean more complicated?) by,
for example in dsp_hello.cfm:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<cfinclude
template="#whattemplate()#">
<cfoutput>
#dsp_hello.say_hello#
</cfoutput>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The
whattemplate() udf returns a file name to include, based on "global" vars (eg
company, language) and the calling template name, and the included file creates
a structure with the same name as the included file, with the relevant keys, in
this case "say_hello"
One of
the advantages of calling a udf to invoke the content structure is that the
code can track what content is used when, and if the user is admin, create links
to manage the content.
There were other
reasons, but the escape me - its still yesterday over here.
Or the day
before.
Bert
One
thing I've seen in a lot of forum apps with language packs, is one separate
page that sets all the display text values. A visitor to the site would select
the language in which they wish to view the site.
For
Example:
cfg_lang_english.cfm:
<cfscript>
variables.imageroot = "images/english/";
variables.helloimage = "hello.gif";
variables.goodbyeimage =
"goodbye.gif";
variables.hello = "Hello, Sir or Madam";
variables.goodbye = "Goodbye and Have a Nice Day.";
variables.register= "Please
Register!";
.....
</cfscript>
cfg_lang_slang.cfm:
<cfscript>
variables.imageroot = "images/slang/";
variables.helloimage = "hey.gif";
variables.goodbyeimage = "seeya.gif";
variables.hello = "hey
dude..";
variables.goodbye = "see ya...";
variables.register= "Yo.. sign
up!!!";
.....
</cfscript>
dsp_welcome.cfm:
<img
src="javascript:void(0);">#variables.hello#
etc. etc. etc.
This
way when you need to add a language, you change one page only. The variables
are all static to the language definition page. This would require a rework of
the site into FB3 and making all the text into separate variables, but in the
long run, the site would be infinitely scalable as far as languages are
concerned.
Bob
Krieger
The
FuseBox Tutor
-----Original Message-----
From: Erik
Voldengen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 21, 2002
7:55 PM
To: [EMAIL PROTECTED]
Subject: RE: Multinlingula
Sites and Methodology
John,
FB2 is not all that hard to swap up to FB3. The nasty part
is
renaming all your fuseactions, but you can do that with
some
well tought out global search and replaces.
Maybe you can do it if the time spent is
justified.
-Erik
Good ideas thanks a lot. The only
problem with the layout file is that when I did the English side of this
site I used FB2 :-(. Good Idea for the images though. Any more
suggestions? :-)
----- Original Message -----
Sent: Tuesday, May 21, 2002 8:55
PM
Subject: RE: Multinlingula Sites
and Methodology
Personally I would do it the second way. You'd have a lot
more files to modify using the first method if you wanted to ad a third
language.
But instead of using attributes.language I'd simply put the
language preference into a client variable. So instead
of
<cfinclude
template="dsp_display#attrubutes.language#.cfm">
it would read
<cfinclude
template="dsp_display#clients.language#.cfm">.
That way you don't have to pass the language
variable to every single script. (Although, you could also avoid that
hassle by appending attributes.language to #self# in
fbx_settings.cfm)
You could also put the same logic in your layout file like
so:
<cfswitch
expression="#client.language#">
<cfcase value="fr">
<cfset fusebox.layoutFile =
"frenchLayout.cfm">
</cfcase>
<cfdefaultcase>
<cfset fusebox.layoutFile =
"englishLayout.cfm">
</cfdefaultcase>
</cfswitch>
That way you could have a different layout for each
language.
You could also set up a variable to reference the correct images
in fbx_settings.cfm:
<cfswitch
expression="#client.language#">
<cfcase value="fr">
<cfset request.images =
"path/to/french/images/">
</cfcase>
<cfdefaultcase>
<cfset request.images =
"path/to/english/images/">
</cfdefaultcase>
</cfswitch>
Then in your display files you put
<img src="javascript:void(0);">
Of course you could still use
attributes.language instead of client.language if you
prefer...
Hope this helps,
Balazs
-----Original Message-----
From:
John Jonathan Kopanas [mailto:[EMAIL PROTECTED]]
Sent: Tuesday,
May 21, 2002 5:38 PM
To: Fusebox List
Cc: Denis
Doyle
Subject: Multinlingula Sites and
Methodology
As a programmer from Quebec, a lot of the
sites I have to work on have to be bilingual. Just as a
clarification, they only have to be in French but most people want
them in English because they do business outside of Quebec. Do
not let me get started with the politics here in Quebec, if it was not
for the women I would be long gone :-). Ok, where was I, oh yes
multilingual sites. I was wondering if anyone has come up with
their own personal methodologies on using Fusebox and creating
multilingual sites to fulfill the following requirements:
- it is easy to add a new language to the
site
- the logic is not
duplicated
- Images might have to change for each
language
What I don't want to do:
- I don't want to have to create a new
directory for every language and copy over the site and just change
the text and the tables I reference.
Some possible solutions:
- have the display pages in the different
languages and keep the action pages the same and just add language
conditions to the actions pages. Therefore the amount of switch
cases would increase.
ex)
<cfwitch
case="example">
<cfinclude
template="act_process.cfm">
<cfinclude
template="dsp_display.cfm">
</cfswitch>
<cfwitch
case="example_fr">
<cfinclude
template="act_process.cfm">
<cfinclude
template="dsp_display_fr.cfm">
</cfswitch>
- another way to go would be is to pass
language in query string and append it onto the file name in swtich so
it chooses file according to language
<cfwitch
case="example">
<cfinclude
template="act_process.cfm">
<cfinclude
template="dsp_display#attrubutes.language#.cfm">
</cfswitch>
Any other suggestions? Thanks for
your help.
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================
| 