Index: xdocs/subcomponents/drlvm/DeveloperGuide.html
===================================================================
--- xdocs/subcomponents/drlvm/DeveloperGuide.html (revision 540071)
+++ xdocs/subcomponents/drlvm/DeveloperGuide.html (working copy)
@@ -1553,6 +1553,32 @@
maximum use of its capabilities. See help message ij
-X for details on the logger command-line options.
The current VM logging system supports internationalization,
+ so that VM can print messages in the language of the customer system.
+ To use the internationalization feature, initialize one of the LC_ALL,
+ LC_MESSAGES or LANG system environment variables
+ in the <Lang>_<Region>.<Variant> locale format.
+ You can find a list of localized messages for a certain locale in the
+ <drlvm_trunk>/vm/vmcore/src/init/harmony_<locale_name>.properties.
+ message catalogue. For a convenient set of macros for printing internationalized
+ messages, refer to the cxxlog.h header file.
+
A record from the message catalogue has the following structure:
+ <XXXX><YYY>=<localized_message>
+ Where: br>
+
<XXXX> - a set of four letters; the current implementation contains
+ <ECHO>, <LDIE> and <WARN> sets;<YYY> - the localized message number, for example <005>;<localized_message> - the message written in the native language
+ (may be UTF8 coded), which can contain some substitution parameters,
+ for example <message with two parameters {0} and {1}>.Example
+Here is the example of using the <ECHO030=Unknown option {0}>
+ record from the message catalogue in VM code:
LECHO(30, "Unknown option {0}" << option);
+
@@ -2115,8 +2141,8 @@ Note
- The vm.other_natives_dlls property defines the list
- of libraries to be loaded.
+ The private vm.other_natives_dlls property defines
+ the list of libraries to be loaded.