Hi,Victor!
   i'm very glad to see the new 1.1.7 version of java console has added the language choosing menu, but there are only two languages --English and Russuan can be chosen,  so i want to add our mother language(Chinese) by myself,  would you tell me how can i start(for example, which source files or modules are the language swiching's core)? 
   thank you!
Best Regards
Billy
			
			
			
				Hi!
I start preparing Java console for translating to different languages. Actual translation is done by creating appropriate language files. You can try to locate existing messages.properties in projects (currently projects library, core, and alarm browser are prepared for translation), and create files messages_zh_CN.properties with Chinese translation. Then I will add appropriate language switch and include these translated files into main source tree.
Best regards,
Victor
			
			
			
				Thank you!
			
			
			
				Hi.
But, where I can locate messages.properties file?
Best regards.
			
			
			
				Hi!
You have to get current svn repository: https://svn.netxms.org/public/netxms/trunk (https://svn.netxms.org/public/netxms/trunk). Sources of Java console are under src/java/netxms-eclipse. Below that point there are various messages.properties in different plugins, like src\java\netxms-eclipse\core\src\org\netxms\ui\eclipse\console\messages.properties. There should be one message file per plugin, usually located in the root package of a plugin. PLease note that currently only few plugins are prepared for translation.
Best regards,
Victor
			
			
			
				Hi, Victor!
I send you plugins translated into Spanish.
Best regards.
			
			
			
				Hi!
Thanks for the translation! I have added language switch for Spanish and Chinese languages, and add files you have sent to the project. I also forgot to mention that there are additional files to translate - they are called bundle.properties, and located in <project_root>/OSGI-INF/l10n.
I'll post to this thread as I will prepare more plugins for translation.
Best regards,
Victor
			
			
			
				Also, the following line looks wrong to me:
AcknowledgeAlarm_ErrorMessage=No es posible puedo Cannot aceptar la alarma 
Best regards,
Victor
			
			
			
				QuoteAlso, the following line looks wrong to me:
AcknowledgeAlarm_ErrorMessage=No es posible puedo Cannot aceptar la alarma 
Yes, it's wrong. I re-send corrected and rechecked file.
QuoteI also forgot to mention that there are additional files to translate - they are called bundle.properties, and located in <project_root>/OSGI-INF/l10n.
I have also translated into Spanish and verified four bundle.properties files.
Best regards.
			
 
			
			
				Hi, Victor!
I send you plugins translated into Chinese,  please add them into the new version.  And i hope that you can put the completely international version in which most of the information of in user interface can be changed into the four languages(Chinese, English, Russian & Spanish).Thank you!!
Best regards.
			
			
			
				Hi.
QuoteI'll post to this thread as I will prepare more plugins for translation.
Any news about this theme.
Best regards.
			
				up  ;)
			
			
			
				Sorry for deley with that. I'll spend few evenings on this and next week and will convert most plugins to use messages files. Then you will be able to continue translation.
Best regards,
Victor
			
			
			
				Hi all!
Finally I've made some progress on this. Attached is an archive with latest message files. Please translate (in appropriate messages_lang.properties) and send back to me keeping same directory structure within archive. Archive includes existing translated files as well. Please note that there can be new entries in already translated files, so you have to compare existing translated files with English version for possible appearance of new messages!
Best regards,
Victor
			
			
			
				Good job!
			
			
			
				
Hi.
I send you message files translated into Spanish language. Sorry for delay  :-[
Best regards.
			
			
			
				Hi!
Thank you, I've integrated them into source code. I'll create more message files to translate soon. In the meantime, you can translate error messages from NetXMS API:
      "Request completed successfully",
      "Component locked",
      "Access denied",
      "Invalid request",
      "Request timed out",
      "Request is out of state",
      "Database failure",
      "Invalid object ID",
      "Object already exist",
      "Communication failure",
      "System failure",
      "Invalid user ID",
      "Invalid argument",
      "Duplicate DCI",
      "Invalid DCI ID",
      "Out of memory",
      "Input/Output error",
      "Incompatible operation",
      "Object creation failed",
      "Loop in object relationship detected",
      "Invalid object name",
      "Invalid alarm ID",
      "Invalid action ID",
      "Operation in progress",
      "Copy operation failed for one or more DCI(s)",
      "Invalid or unknown event code",
      "No interfaces suitable for sending magic packet",
      "No MAC address on interface",
      "Command not implemented",
      "Invalid trap configuration record ID",
      "Requested data collection item is not supported by agent",
      "Client and server versions mismatch",
      "Error parsing package information file",
      "Package with specified properties already installed on server",
      "Package file already exist on server",
      "Server resource busy",
      "Invalid package ID",
      "Invalid IP address",
      "Action is used in event processing policy",
      "Variable not found",
      "Server uses incompatible version of communication protocol",
      "Address already in use",
      "Unable to select cipher",
      "Invalid public key",
      "Invalid session key",
      "Encryption is not supported by peer",
      "Server internal error",
      "Execution of external command failed",
      "Invalid object tool ID",
      "SNMP protocol error",
      "Incorrect regular expression",
      "Parameter is not supported by agent",
      "File I/O operation failed",
      "MIB file is corrupted",
      "File transfer operation already in progress",
      "Invalid job ID",
      "Invalid script ID",
      "Invalid script name",
      "Unknown map name",
      "Invalid map ID",
      "Account disabled",
      "No more grace logins",
      "Server connection broken",
      "Invalid agent configuration ID",
      "Server has lost connection with backend database",
      "Alarm is still open in helpdesk system",
      "Alarm is not in \"outstanding\" state",
      "DCI data source is not a push agent",
      "Error parsing configuration import file",
      "Configuration cannot be imported because of validation errors",
      "Invalid graph ID",
      "Local cryptographic provider failure",
      "Unsupported authentication type",
      "Bad certificate",
      "Invalid certificate ID",
      "SNMP failure",
      "Node has no support for layer 2 topology discovery",
      "Invalid situation ID",
      "Named instance not found",
      "Invalid event ID",
      "Operation cannot be completed due to agent error",
      "Unknown variable",
      "Requested resource not available",
      "Job cannot be cancelled",
      "Invalid policy ID",
      "Unknown log name",
      "Invalid log handle",
      "New password is too weak",
      "Password was used before",
      "Invalid session handle",
      "Node already is a member of a cluster",
      "Job cannot be put on hold",
      "Job on hold cannot be resumed",
      "Zone ID is already in use",
      "Invalid zone ID",
      "Cannot delete non-empty zone object",
      "No physical component data",
      "Invalid alarm note ID",
      "Encryption error"
      "Bad MIB file header",
      "Bad MIB file data"
Best regards,
Victor
			
			
			
				Hi.
I attach text file with translations.
Best regards.