Todd, Although I see you point, my preference is to leave as many feature enabled and tell user, via documentation, how to turn them off. In addition Jetspeed is used, and developed, by people in many countries, so what should the default language be? (This is a rhetorical question)
Paul Spencer Todd Kuebler wrote: > I believe you can modify the overall language behavior in the > WEB-INF/conf/JetspeedResources.properties file if you don't want > multiple language support. The nice side effect is that I think it > speeds things up incrementally since the language search doesn't occur. > I actually would like to see Jetspeed boxed with this feature turned off > by default and a separate FAQ around configuring and using multiple > language support. That would be much friendlier to the average user. > > # Use language? > services.Profiler.language=false > > > -tk > > > At 12:28 PM 5/1/2002 -0700, Shultz, Kevin wrote: > >> Amen brother :o). That worked. I assumed the language directories were >> there in the event you wanted to overwrite the default in the parent >> directory with your specified language. That being said is it >> required that >> I modify both, or just the one residing in the language. If the >> default.psml in the parent is not used then should it be removed or >> does it >> serve as something more in the grand scheme of things? >> >> Thank you again for the good information. Makes me feel kinda dumb >> that I >> didn't think to try the language psml sooner. I suppose hind-sight is >> truly >> 50-50. >> >> Very Respectfully, >> >> Kevin >> >> -----Original Message----- >> From: Todd Kuebler [mailto:[EMAIL PROTECTED]] >> Sent: Wednesday, May 01, 2002 12:22 PM >> To: Jetspeed Users List >> Subject: Re: Default portal content look-and-feel changes not taking >> effect >> >> >> >> The thing that I wasted a good portion of my time on initially was the >> language directories. I would edit the template/psml file at the right >> point, but forget about the language specific file. My understanding is >> that if the language directory exists it is used. >> >> Have you edited psml/anon/html/en/default.psml? Have you verified >> that the >> psml you edited is the one being displayed by adding a portlet entry and >> verifying that it shows up? >> >> -tk >> >> >> At 12:15 PM 5/1/2002 -0700, Shultz, Kevin wrote: >> >I realize that this question has been versed in many ways and at many >> times >> >within these archives but to my defense I have traversed them in their >> >entirety and am either misunderstanding or simply not finding the >> >information I am looking for. >> > >> >I have added a new skin-entry within skins.xreg, I have modified >> >services.PortalToolkit.default.skin to equal the new skin entry, I have >> >modified the psml/anon/html/default.psml to reflect the skin name tag >> (as >> >the same new skin) and still my default portal page reflects a color >> scheme >> >based on the original install default orange-gray. I had hoped to >> isolate >> >where this setting resides with my own endeavors but have exhausted far >> more >> >man-hours in being unsuccessful that I care to count. >> > >> >If anyone can provide some much needed advice on what I seem to be >> missing >> I >> >would be most grateful. Thank you in advance >> > >> >Very Respectfully, >> > >> >Kevin >> > >> >-- >> >To unsubscribe, >> >e-mail: <mailto:[EMAIL PROTECTED]> >> >For additional commands, e-mail: >> ><mailto:[EMAIL PROTECTED]> >> >> >> -- >> To unsubscribe, e-mail: >> <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: >> <mailto:[EMAIL PROTECTED]> >> >> -- >> To unsubscribe, e-mail: >> <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: >> <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
