Hi There.
I’ve created some commands in C# using RhinoCommon and they work perfectly well in multiple systems and users in US English. However, the DLL failed to load and find the commands in a German Rhino.
Do we have a document stating what needs to be done/enhanced to expose the commands to multiple cultures?
Thanks!
Hi @AxeManGa,
What one is the case? The DLL fails to load? or your commands are not found? Perhaps we need more details or perhaps a sample that isn’t working for you?
– Dale
Hi. Sorry for the delay. I found an answer to issue #1. When my co-worker copied the DLL, for some reason the policy set on his PC blocked the DLL. We had to right click on it and check the box for ‘unblock’ in the file properties in Windows.
The second issue remains. Since I am using a combination of C# code and Rhino script, it seems that certain commands (such as -Import) do not work on the German version. I was wondering if I am going to have to create overloaded methods and expressly write the command in each supported language for the Plug-In.
Hi @AxeManGa,
When scripting Rhino commands from a plug-in, always precede the command name with an underscore, or _ character. This runs command as English command name.
Rhino can be localized in many languages. The non-English versions will have commands, prompts, command options, dialog boxes, menus, etc., translated into their respective languages. English commands will not work in these versions.
For scripts written in English to work on all computers (regardless of the language of Rhino), the scripts need to force Rhino to interpret all commands as English command names.
For example: In the English version of Rhino, the following macro works:
Circle 3Point 0,0,0 1,1,0 0,3,0
But in the French version of Rhino, this won’t work. Instead you need one of these macros:
Cercle 3Point 0,0,0 1,1,0 0,3,0
_Circle _3Point 0,0,0 1,1,0 0,3,0
To make sure macros work worldwide, write them in English and put _ in front of all command names and options.
– Dale
Hi Dale!
_ThankYou!