RE: i18n and packaging
Hi, OK. I'll tag and build around 2pm (my time, EDT) today. I'll send out a separate notice. Yoav Shapira Millennium Research Informatics >-Original Message- >From: Remy Maucherat [mailto:[EMAIL PROTECTED] >Sent: Tuesday, August 31, 2004 9:04 AM >To: Tomcat Developers List >Subject: Re: i18n and packaging > >Shapira, Yoav wrote: > >>Hi, >>I think it'd be nice to split the language resources out, not because of >their size but to make it easier for users to modify and enhance the i18n >bundles. I think we'll get more i18n-related contributions that way. >> >> >I suppose it could indeed encourage people. >I'll commit the change after your 5.5.0 tag, since I expect I'll forget >something somewhere and break a little the packaging ;) > >Rémy > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: i18n and packaging
Shapira, Yoav wrote: Hi, I think it'd be nice to split the language resources out, not because of their size but to make it easier for users to modify and enhance the i18n bundles. I think we'll get more i18n-related contributions that way. I suppose it could indeed encourage people. I'll commit the change after your 5.5.0 tag, since I expect I'll forget something somewhere and break a little the packaging ;) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: i18n and packaging
Hi,
I think it'd be nice to split the language resources out, not because of their size
but to make it easier for users to modify and enhance the i18n bundles. I think we'll
get more i18n-related contributions that way.
Yoav Shapira
Millennium Research Informatics
>-Original Message-
>From: Remy Maucherat [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, August 31, 2004 7:48 AM
>To: Tomcat Developers List
>Subject: i18n and packaging
>
>Hi,
>
>I have a problem with the packaging of resource strings. Each language
>is made of a lot of resources, and takes about 25K. So this doesn't
>scale that well (we have 4 incomplete languages today, but it would be
>good to have many more).
>
>I was considering adding ${catalina.home}/common/i18n/*.jar to the
>"common" loader repository list, with the JARs containing all the
>resource bundles. This would make it easy to add/remove a language.
>
>Or we could say we don't care, and put everything in the individual
>JARs, regardless of the size or management problems. This is simpler.
>
>Does someone have experience with this in other large Java applications
>? How do they do it ?
>
>Rémy
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary and/or privileged. This
e-mail is intended only for the individual(s) to whom it is addressed, and may not be
saved, copied, printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your computer system
and notify the sender. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
i18n and packaging
Hi,
I have a problem with the packaging of resource strings. Each language
is made of a lot of resources, and takes about 25K. So this doesn't
scale that well (we have 4 incomplete languages today, but it would be
good to have many more).
I was considering adding ${catalina.home}/common/i18n/*.jar to the
"common" loader repository list, with the JARs containing all the
resource bundles. This would make it easy to add/remove a language.
Or we could say we don't care, and put everything in the individual
JARs, regardless of the size or management problems. This is simpler.
Does someone have experience with this in other large Java applications
? How do they do it ?
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
