incubator-jspwiki-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Gao" <david...@gmail.com>
Subject Re: Questions about JSPWiki internationalization
Date Mon, 25 Feb 2008 15:45:58 GMT
I agree with Luca's suggestion. It would be better to have a kind-of
coordinator for each language translation. I would volunteer for Simplified
Chinese translation.

Simplified Chinese translation will be ready around next week with
verification passed.

David Gao (davidgjm@gmail.com)

2008/2/25, Luca Gilardoni <gil@quinary.com>:
>
> Hi all.
> I have italian localisation almost ready (almost means I need a final
> pass to check typos).
> Question:
> - you prefer I send it / attach to JIRA
> - or get svn write access (how) and directly upload?
>
> In the latter case it could be easier to maintain later on - and I would
> gladly accept to take it in charge on my side.
> Let me know.
>
> Luca
>
> Craig L Russell wrote:
> > Hi David,
> >
> > To become a committer in the JSPWiki project requires a commitment to
> > the project and the support of others on the jspwiki team.
> >
> > Your commitment to the project is based on continuing to contribute to
> > the project (usually this will be in the form of dialog on
> > jspwiki-dev, creating JIRA issues, and providing patches for them).
> > Subscribing to jspwiki-dev and engaging in dialog there is a good way
> > to become part of the community.
> >
> > We're always looking for new members.
> >
> > Best regards,
> >
> > Craig
>
> >
> > On Feb 20, 2008, at 6:20 PM, David Gao wrote:
> >
> >> Hi Craig,
> >>
> >> Thank you for your response.
> >>
> >> I'm able to submit issues in JIRA. However, how can I become a
> >> committer of JSPWiki? I did not find any guide information about this
> >> on JSPWiki site.
> >>
> >> David
> >>
> >> -------- Original Message --------
> >>> Hi David,
> >>>
> >>> On Feb 18, 2008, at 6:44 PM, David Gao wrote:
> >>>>
> >>>> Another stupid question is: how can I submit my files to JSPWiki,
> >>>> via JIRA or simply in CVS?
> >>>
> >>> We are now using Apache's svn repository, and I don't see you on the
> >>> committer list, so the best way is to create a JIRA and attach the
> >>> patch to it.
> >>>
> >>> If you are a committer and I simply missed you, you can directly
> >>> update the svn.
> >>>
> >>> Regards,
> >>>
> >>> Craig
> >>>>
> >>>>
> >>>> David Gao (davidgjm@gmail.com)
> >>>>
> >>>>
> >>>> -------- Original Message --------
> >>>>> Yes ... but it also took me a while to realize that what's inside
> >>>>> <JSPWiki-Home>/WEB-INF/i18n is useless
> >>>>> within Tomcat (unless moved under classes ...).
> >>>>> Maybe it would be better to move it away from there in the
> >>>>> standard distro.
> >>>>>
> >>>>> As for the 1/n jars ...  in similar situations I use to have a
> >>>>> separate jar for all 'standard supported'  languages
> >>>>> to avoid cluttering .... which does not prevent one to add a new
> >>>>> language just by adding under classes or,
> >>>>> if things should grow too much (hope so!) to simply substitute the
> >>>>> languages jar with what's really needed.
> >>>>> Choice to you but let me know as I will provide in a while an
> >>>>> Italian version :-) ..
> >>>>>
> >>>>> Luca
> >>>>>
> >>>>> Janne Jalkanen wrote:
> >>>>>>> My questions are:
> >>>>>>>        Does the folder "<JSPWiki-Home>/WEB-INF/i18n"
really work
> in
> >>>>>>> running environment in terms of internationalization support?
> >>>>>>>
> >>>>>> Nope!
> >>>>>>
> >>>>>>
> >>>>>>>        Do I have to add my localization resources to
> >>>>>>> "<JSPWiki-Home>/WEB-INF/classes/" directory in order
to have i18n
> feature?
> >>>>>>>        Is there any information about how i18n works in
current
> JSPWiki
> >>>>>>> design?
> >>>>>>>
> >>>>>> The easiest way is to create a JAR file of your property files,
and
> >>>>>> drop that into WEB-INF/lib.  Putting them in classes directory
is a
> >>>>>> bit suspect, as it creates clutter.
> >>>>>>
> >>>>>> It does not matter where you put the files, as long as they
are
> >>>>>> somewhere in the classpath.
> >>>>>>
> >>>>>> Though, this reminds me that we should probably create separate
JAR
> >>>>>> files for each localization (except for default English).  It
would
> be
> >>>>>> a bit cleaner, though it would add clutter, too.
> >>>>>>
> >>>>>> /Janne
> >>>>>>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message