Tim Dawson wrote:
> I looked for some good internationalization tags on the web and haven't been
> able to find any that would work for what I'm trying to do: namely autosense
> the user's browser language, pick up the appropriate bundle (based on their
> prefernece order) and allow automatic formatting using
> java.text.MessageFormat.
>
While I'm in favor of having alternative solutions to the same problem available
(one size does *not* always fit all), you might want to take a look at the
internationalization support in the Struts framework project -- the framework
includes auto-sense (based on the user's Accept-Language header), a
<bean:message> tag that pulls message strings from a resources object and
applies MessageFormat translations, and a whole bunch more. Plus you get a nice
framework for the business logic of your app as well.
http://jakarta.apache.org/struts
>
> So we wrote our own, and decided it was in our best interest to submit these
> to the taglibs project, so that others wouldn't have to dupliate this effort
> and so that (assuming these tags are adopted) we'd be using the standard
> rather than something we have to continue to maintain ourselves. The whole
> maintenance argument is what really won this over with mgmt. :-) At the
> bottom of this message is a high level description of the library.
>
> Please advise on how I might submit this to the appropriate channels.
>
I think you just did :-)
If you're willing to license this code under the Apache license, and organize
the source as described on the Taglibs web site, this proposal can be voted on.
You've got my +1.
>
> Thanks,
>
> Tim Dawson
> Chief Architect
> WAM!NET Inc.
>
Craig McClanahan
