>>>>> "JA" == Eric Marsden <email@example.com> writes:
JA> The idea would be to create a file messages.FR, say, corresponding to a
JA> messages.EN, etc, and come up with some mechanism for extracting the
JA> appropriate messages according to the locale.
It seems you're not aware of the ongoing development of Majordomo2. This
version has all of the long responses moved out into files that can be
overridden by the list owner along with a way for the list owner to specify
a language preference. The short messages are still in the code though.
We've talked about a scheme to fix this (see the archives or the TODO file
in the current development snapshot) which basically entails having a
file containing all of the short messages translated into various
languages. We also worked out a scheme for users to specify their language
preference. I created a list (firstname.lastname@example.org, send majordomo
commands to email@example.com) for discussion but it has
been essentially dead (I don't have time to publicize it and those who were
interested basically disappeared) and as a result I have put
internationalization issues a bit further back on the list of things to do.
JA> Would the majordomo developers welcome such a move?
I would have to say that given current developments, I doubt there will be
any more releases of the Majordomo1 code base and thus any work done on it
will in all probability be lost. If you'd like to help with
internationalization of Majordomo2 I'd certainly welcome the effort and
help where I can. (My non-English language abilities only extend to poor
Spanish, deteriorating Japanese and laughable Norwegian leading to
hilarious Swedish and Danish. Hint: don't ask for 'leek' on your
1) Snapshots and such are available from http://www.hpc.uh.edu/majordomo/
2) I did receive a set of German translations but unfortunately they are
all done in ASCII. I asked for 8-bit versions (the code supports
serving it out and specifying preferred MIME encodings) but I never
received a response.