-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

All,

I'm finishing-up my (minor) work on separating SSI into a separate JAR
file and I noticed that while this file ends up in my catalina-ssi.jar
file:

   org/apache/catalina/ssi/LocalStrings.properties

This file (and others like it) do not:

   org/apache/catalina/ssi/LocalStrings_ko.properties

Instead, it ends up in this file:

lib/tomcat-i18n-ko.jar

... along with all the translations of all the other modules as well.

So, for example, if you want to take the tribes module somewhere (and
not have it in the default locale), you need both catalina-tribes.jar
and tomcat-i18n-*.jar.

This isn't really much of an issue for tribes,since I'm guessing it
doesn't work very well outside of Tomcat, but the SSI module could
theoretically be used in another container, so it might be nice to
bundle all of the translations with it.

Is there a particular reason (a) the translations are in a separate
JAR file - i.e. not in catalina.jar and (b) they are separated by
language? Perhaps the thought was that, knowing that you don't need
e.g. Korean means you can remove the JAR file from some kind of
bare-ones distribution.

For SSI, at least, I think it makes sense to bundle all the i18n files
together in the same JAR file. I'm using the <jarIt> macro to build my
JAR file which explicitly <excludes> LocalStrings_*.properties from
whatever JAR file is being built. I'd need to change the way that the
SSI JAR file is built in order to achieve this. But before doing so, I
wanted to get consensus on what to do with these files.

- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl3QFQAACgkQHPApP6U8
pFiaKw/6Ax3LEhmzMZS80ubdH0SWOkcud5PrjI4kC/LUxQfUSYqrKHLMKxFok0JL
SAgEq1v1qW8mAvj9Aejbk6nHv4R+PP+M4bxvXBv80OsHJ+8RaChtwctnYCykJD6O
fa878ugO84qgjqxP4ot+NH1AbbShdcu14uTYdTliXJolC6bXLZFGnLW8l2EelocE
tM3++uix9mS7uOVdNqJwjBP6Gfq97/Tp3KDjQv6KQqTQAiqOeJtPnKtCvlw807NM
LsG17TkO2FSHwkAwrf9K6N4Fvu2CsAEwjLlzlqi7RVuRv9FOiBNQ4IB/r+75YQAi
0ftVpjtB3LPKs3XJ1n8MH6CBk8E3symA7iY+jHnTuUha7OxgXSBs6KIqXgVPgVaz
wYR+E/u89BawwfdXQrxvuU3DtEJvqCauQJinqAexxGWUZ/w7qP0isNnAfemXOT4C
CtQxkcRHNXsi6meAl3bVgjLPIvNLeVaoDjKQ5Sl+NsSoWWhqlqZVmdfQQViHfr/C
Mj781gcctkFWuwgRENBq7i+P5mGzZ50EycxyrxOkq2xKaEf9dEY5x/QBJ4kKmLzQ
/tnIvqB1lsthYrN++Rrfhb92IZ0bCEBNtio8s5DW0I6qA5ywJMnsAAzMg6R3R76N
Io/NWFfHRu9pIyzGoMe0OA+fpO4wdByqw6wI3vQpt6K5hLSNh48=
=CQWx
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to