Hi,

I'm looking at updating some of the aries code so messages could
potentially be translated. Looking at blueprint there are two
categories of things that I think need doing:

1. We need to resolve exception messages from ResourceBundles
2. Some of the messages output using SLF4J need to be translatable by
resolving from ResourceBundles

The first I can cope with easily enough, but I don't know SLF4J well
enough to know the best way to do the second. As I understand it SLF4J
does not itself do any localization. So we would need to pre-resolve
any messages before calling the relevant SLF4J method. One option
would be to use the SLF4J extension for localization, but the API
seems a little nasty to me. If I understand it you need to know up
front what languages you translate into, and you need to change an
enum to add a new language, which isn't exactly modular.

So I wondered what people thought should be done to translate messages
output via SLF4J? Incidentally I plan to translate message sent to
info, warn and error, but not debug or trace

Alasdair

-- 
Alasdair Nottingham
[email protected]

Reply via email to