Last thing on internationalization.

I was thinking that some of the parameters would be
internationalized.  For example table-headers.  In my
case I've used "Topic" "Created On" etc.  I wanted these
values to be flexible, but then also internationalized.
For each language and each parameter it becomes
increasing cumbersome.


----- Original Message -----
From: "Mark Orciuch" <[EMAIL PROTECTED]>
To: "Jetspeed Users List" <[EMAIL PROTECTED]>
Sent: Monday, March 10, 2003 11:50 AM
Subject: RE: NNTP Porlet


> Kevin,
>
> See Internationalization section of
> http://jakarta.apache.org/jetspeed/site/code-standards.html.
>
> Best regards,
>
> Mark Orciuch - [EMAIL PROTECTED]
> Jakarta Jetspeed - Enterprise Portal in Java
> http://jakarta.apache.org/jetspeed/
>
> > -----Original Message-----
> > From: Kevin McIntyre [mailto:[EMAIL PROTECTED]
> > Sent: Sunday, March 09, 2003 1:30 PM
> > To: Jetspeed Users List
> > Subject: Re: NNTP Porlet
> >
> >
> > Santiago -
> >
> > The NNTP Portlet can make use of and James to moderate discussion or
> > simple use another NNTP resource, without that feature.
> >
> > My question is how do I Internationalize a portlet?  Making entries in
> > each language file?
> >
> >
> >
> > ----- Original Message -----
> > From: "Santiago Gala" <[EMAIL PROTECTED]>
> > To: "Jetspeed Users List" <[EMAIL PROTECTED]>; "Jetspeed
> > Developers List" <[EMAIL PROTECTED]>
> > Sent: Sunday, March 09, 2003 6:33 AM
> > Subject: Re: NNTP Porlet
> >
> >
> > > Kevin McIntyre wrote:
> > > > Using NNTP I've created a "Threaded Discussion" Portlet.  I would
like
> > to
> > > > contribute.  It works with James, extending NNTPRepositoryImpl
> > > > to remove threads for moderated discussion.
> > > >
> > > > Is it necessary to Internationalize before contributing?
> > > >
> > >
> > > I would be nice :-)
> > >
> > > But I don't think a portlet which brings a James dependency should be
> > > inside jetspeed. (Maybe I understood it wrong).
> > >
> > > As a matter of fact, we are in the process of stabilizing Jetspeed 1
and
> > > planning a move to Jetspeed-2.
> > >
> > > My personal opinion (but I think most developers will agree) is that
> > > Jetspeed and portlets should be separate modules in the future.
> > >
> > > Jetspeed 2 will ship with functionality as a portal tool
> > > (administration), and a few key or simple demo portlets.
> > >
> > > Jetspeed will have separate modules for hosting development of
portlets
> > > like what you are proposing, shipping in different "portlet
> > > applications". The original proposal for the Portlet API included
> > > facilities for doing this. I don't think they will drop it, since it
is
> > > a highly desirable feature.
> > >
> > > So, while I think it will be worthwhile to look more into your
proposal,
> > > I suggest that you open a bugzilla issue (Request For Enhancement),
and
> > > discuss features and dependencies with interested people there. In
this
> > > way, you can proceed without bringing additional dependencies inside
> > > jetspeed.
> > >
> > > If it looks worthwhile, it could be put in the scratchpad to develop
> > > there until it can be released (in the Jetspeed-2 infrastructure) as a
> > > portlet application. Or people could build it separately from the
> > > scratchpad.
> > >
> > > Regards,
> > >       Santiago
> > >
> > > P.S.) I CC: dev, since it mostly belong to jetspeed development.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to