> Absolutely. Were should it go? How about a bullet point
> outlining the
> config parameter and template location in the configuration
> guide plus a
> more comprehensive one in the components section? Of course I have
> to figure it all out first so give me a couple of days. :)
>
I
At 04:19 PM 5/1/2002 -0700, you wrote:
>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.
>-0
>I prefer to have it off in some cases, on in others.
>What I woul
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.
-0
I prefer to have it off in some cases, on in others.
What I would like to do is optimize the code so that stor
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 Spen
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
nformation
[EMAIL PROTECTED] 734-615-1419
> -Original Message-
> From: Shultz, Kevin [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 01, 2002 3:28 PM
> To: 'Jetspeed Users List'
> Subject: RE: Default port
