Multilingual support for localization

# 5 years ago
balics	There might be requirement of native language for Tango applications, so I am wondering if Tango has the abilities of multilingual support. Thanks!

# 5 years ago
Reynald	balics There might be requirement of native language for Tango applications, so I am wondering if Tango has the abilities of multilingual support. Thanks! Hi, All the Tango attributes have a label attribute configuration property which is meant to be used by Tango applications when displaying attributes (For instance, atkpanel is using this label) so you can use this label to display the name you want for any attribute. You could use that to translate the attribute name in the language you want. Honestly, I never tried it with Chinese characters for instance and I don't know if atkpanel for instance supports it. I think the commonly used Tango applications like jive, atkpanel, pogo, astor… are not currently supporting multilingual support (all the menus and dialogs are in English). Kind regards, Reynald Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 5 years ago

Reynald

balics
There might be requirement of native language for Tango applications, so I am wondering if Tango has the abilities of multilingual support. Thanks!

Hi,

All the Tango attributes have a label attribute configuration property which is meant to be used by Tango applications when displaying attributes (For instance, atkpanel is using this label) so you can use this label to display the name you want for any attribute. You could use that to translate the attribute name in the language you want.
Honestly, I never tried it with Chinese characters for instance and I don't know if atkpanel for instance supports it.

I think the commonly used Tango applications like jive, atkpanel, pogo, astor… are not currently supporting multilingual support (all the menus and dialogs are in English).

Kind regards,
Reynald

Rosenberg's Law: Software is easy to make, except when you want it to do something new.
Corollary: The only software that's worth making is software that does something new.

# 5 years ago
Reynald	It looks like there is currently another limitation: the State and Status attributes labels cannot be changed. Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 5 years ago
Reynald	Please note that you can configure the Character code set used by omnniORB for the string attributes for instance. This is the encoding which will also be used in the Tango events containing string values. You can configure omniORB configuration by adding the following line in /etc/omniORB.cfg file, or you can use a custom file and use OMNIORB_CONFIG environment variable so it points to your custom file. Then, in this file, you would need to have a line like: `nativeCharCodeSet=UTF-8` Default omniORB codeset is ISO-8859-1 (latin-1). On the Java side, JacORB tries to use the codeset defined in your locale settings. On Linux, you can see that by executing the following command: `locale` which will return something like that: LANG=en_US.UTF-8 and many other values. In this example, UTF-8 will be used by JacORB to encode the Tango strings. You can also configure your Tango database to use a custom charset. Latest MySQL versions are using utf8mb4 character set by default. Please refer to omniORB and jacORB documentation if you want to get more details about codesets: http://omniorb.sourceforge.net/omni42/omniORB.pdf http://omniorb.sourceforge.net/omni42/omniORB/omniORB008.html https://www.jacorb.org/releases/3.9/ProgrammingGuide.pdf Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 5 years ago

Reynald

Please note that you can configure the Character code set used by omnniORB for the string attributes for instance.
This is the encoding which will also be used in the Tango events containing string values.

You can configure omniORB configuration by adding the following line in /etc/omniORB.cfg file, or you can use a custom file and use OMNIORB_CONFIG environment variable so it points to your custom file.
Then, in this file, you would need to have a line like:

nativeCharCodeSet=UTF-8

Default omniORB codeset is ISO-8859-1 (latin-1).

On the Java side, JacORB tries to use the codeset defined in your locale settings.

On Linux, you can see that by executing the following command:

locale

which will return something like that:
LANG=en_US.UTF-8
and many other values.

In this example, UTF-8 will be used by JacORB to encode the Tango strings.

You can also configure your Tango database to use a custom charset.
Latest MySQL versions are using utf8mb4 character set by default.

Please refer to omniORB and jacORB documentation if you want to get more details about codesets:
http://omniorb.sourceforge.net/omni42/omniORB.pdf
http://omniorb.sourceforge.net/omni42/omniORB/omniORB008.html
https://www.jacorb.org/releases/3.9/ProgrammingGuide.pdf

Rosenberg's Law: Software is easy to make, except when you want it to do something new.
Corollary: The only software that's worth making is software that does something new.