RE: Multinlingula Sites and Methodology

[Erik Voldengen]

Nope, not really.  Off the top of my head, You'll rename index.cfm to fbx_switch in all your fuses, and strip out all that cfbodycontent stuff.  Then you'll create a new index.cfm in the root and cfinclude the core file.   You'll take your headers and footers, and combine them into layout files,   You'll have to create your fbx_layouts files for each circuit that needs one, but that's a one or two line file, so no problem   You'll also have to create fbx_circuits, which should be pretty simple.   You'll have to rename all those app_locals to fbx_settings, and remove includes of app_globals.   Like I said earlier, well thought out global search/replace can update all the fuseactions in your application to the "dot notation."   I just swapped a site over a couple of days ago.  I'd never update a FB2 app to FB3 unless I planned on adding some significant functionality, but it's worth it to me to not have to change the way I am thinking/coding.  Your case sounds quite valid, too.   Another issue that could come up is if you used a variable to store the relative directory to the root, ie attributes.fuse_root = "../../"  If you did that, I'd use more global search and replaces in your fuse files to get rid of those references, since everything is relative to the root in FB3.    I have did a little demo application to accompany my presentation at the Fusebox conference last year, and it's available at http://www.fusium.com under developer resources->example applications.  It's made up of a very simple application written in FB2, and again in FB3 for comparison purposes.  You might want to take a look, and also look at the powerpoint presentation I gave (also on www.fusium.com, developer resources -> presentations).   Best of luck, it's not that hard, really!   -Erik     -----Original Message----- From: John Jonathan Kopanas [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 21, 2002 8:26 PM To: [EMAIL PROTECTED] Subject: Re: Multinlingula Sites and Methodology That is not a bad idea.  Is there anything I should watch out when switching code from fb2 to fb3? ----- Original Message ----- From: Erik Voldengen To: [EMAIL PROTECTED] Sent: Tuesday, May 21, 2002 9:54 PM 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   -----Original Message----- From: John Jonathan Kopanas [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 21, 2002 6:18 PM To: [EMAIL PROTECTED] Subject: Re: Multinlingula Sites and Methodology 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 ----- From: Balazs Wellisch To: [EMAIL PROTECTED] 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.bVW5on 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 ==^================================================================ ==^================================================================ This email was sent to: archive@jab.org 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 ==^================================================================