Feature Request: International Language Support

One of the major gaps that this client has is support for languages other than English - so that the client output is more understandable and meaningful to non-native English speakers.

I would like to gauge interest in whether it is worth pursuing an "internationalisation" patch to the client, most likely configured as a parameter detected / passed in at compile time + a value switch in the configuration file.

Obviously, to support languages would require a consistent approach to logging messages, have these stored in a specific file, where, depending on the language selected, the right message used.

The only way though to support languages other than English (US, UK, AU etc) would be from the wider folk using the client to contribute a translation and submit a PR, then have this PR reviewed by at least one or two other folk who are that language native speakers.

Initial support that I can think of which might be required:

* English (EN-US)
* English (EN-GB, EN-AU, EN-NZ etc)
* French
* German
* Spanish
* Japanese
* Chinese (Simplified)
* Russian

Thoughts?

The issue describes adding internationalization to a CLI client. First, examine the codebase for logging and output messages to understand the current structure. Look for a configuration system to add a language parameter. The work involves designing a translation file format, extracting all user-facing strings, and creating a mechanism to load the correct language file at compile-time or runtime. 'Done' means the client can output messages in different languages based on a config setting, with an initial set of translations provided.

Written by the indexing model from the issue text.