It apparently has to do with the new security model in CFMX (which has built in version control, btw).
Bradley S. Dardaganian Lead Application Developer MediTech Media Ltd (USA) [EMAIL PROTECTED] (404) 591-3247 -----Original Message----- From: John Jonathan Kopanas [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 22, 2002 3:46 PM To: [EMAIL PROTECTED] Subject: Re: Multinlingula Sites and Methodology why is that? I know it is off topic. ----- Original Message ----- From: "Brad Dardaganian" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 2:10 PM Subject: RE: Multinlingula Sites and Methodology > My understanding is that Site Minder is going away with the release of > CFMX. > > > > Bradley S. Dardaganian > Lead Application Developer > MediTech Media Ltd (USA) > [EMAIL PROTECTED] > (404) 591-3247 > > > -----Original Message----- > From: John Farrar [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, May 22, 2002 1:41 PM > To: [EMAIL PROTECTED] > Subject: Re: Multinlingula Sites and Methodology > > > Since you did not define "cheap"... have you looked at Site Minder by > MM? > > John > > >>> [EMAIL PROTECTED] 05/22/02 01:40PM >>> > I was always told that you can not use version control with graphics. > In theory from what I understand it is a waste considering a lot of > functions you have are for comparisons between different versions and > the such. Plus I am sure it will take up a lot of HD space. > > My graphic artist copies the project folder and appends a version > number to the end of it. > > Other then CVS on unix can you suggest a good and cheap versioning > system for windows? Thanks. > ----- Original Message ----- > From: Balazs Wellisch > To: [EMAIL PROTECTED] > Sent: Tuesday, May 21, 2002 11:48 PM > Subject: RE: Multinlingula Sites and Methodology > > > Well, I have to disagree with your graphic artist on this, but if > that doesn't work for him you could also name the images the same way > you name your display files. <img > src="images/yourImage_#attributes.language#.gif. That's a lot messier > if you ask me. > > Do you use version control to manage the files in your application? > If so, it's much easier to just branch off the existing images > directory in your project, create a copy of the whole thing, and > modify each file as needed. Anyway, this only makes sense if you're > using version control. > > (Let me guess your graphic artist has never heard of version > control, likes to rename files by appending a .old at the end of file > names, occasionally puts spaces and special characters inside file > names, and wonders who the idiot was that made Unix case sensitive. > Yeah, I've fought my own battles with the "artists" :)) > > B > > -----Original Message----- > From: John Jonathan Kopanas [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, May 21, 2002 8:29 PM > To: [EMAIL PROTECTED] > Subject: Re: Multinlingula Sites and Methodology > > > I just spoke to the graphic artist about having different > directories depending on language and he is totally against it. He > says it is very messy. Any other suggestions or arguments I can give to him? > ----- 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="#request.images#yourImage.gif"> > > 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.bWdkMd > 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: [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 ==^================================================================
