NVil Forum

General Category => NVILL Discussion => Topic started by: dixi on March 02, 2014, 09:43:46 am

Title: NVil localization
Post by: dixi on March 02, 2014, 09:43:46 am

Sorry for my english, I translate with the help of Google.

How can we translate the interface to another language, such as Russian? Is it possible to make a separate file for localization?

Thank you.

Title: Re: NVil localization
Post by: IStonia on March 02, 2014, 09:54:37 am

You can change the tool names to Russian. Edit > Customize > Radial Menus. Also, when you set up your user tool windows, you can use Russian text.

Title: Re: NVil localization
Post by: dixi on March 02, 2014, 10:27:25 am

I understood it, thank you! But how to translate tooltips and InstantHelp?

Title: Re: NVil localization
Post by: IStonia on March 02, 2014, 10:47:17 am

Currently you can't. I will see if I can expose them for modification.

Title: Re: NVil localization
Post by: Vaquero on March 02, 2014, 02:17:58 pm

That'll be great! It would also open up the possibility to write own help texts, for example, if one is missing.

Title: Re: NVil localization
Post by: IStonia on March 08, 2014, 08:17:30 am

Try this one
http://www.digitalfossils.com/Download/NVil-Mar-06-14.rar

"Create User Tool Text" is added to "Tool Search" window context menu. It can be used to create custom tool names, tooltips and related menu text.

The information is saved in this file
C:\Users\UserName\AppData\Roaming\DigitalFossils\NVil\User Settings\UserToolText.xml

Title: Re: NVil localization
Post by: Vaquero on March 18, 2014, 06:56:26 pm

I'm wondering why you didn't go for a full localization file. At the moment all the text is hardcoded, and for some tools, if a user version is present, the text gets replaced.
Why not replace all text in the code with keys, which content is then loaded according to the chosen language? Additionally I always used a parsing function to determine if the key contains text or a reference to another key in another section or the default if there is none in the selected language. It's a good thing you've already written a frontend to manipulate XML data. But with the current implementation one can't localize menu items for example.
I know at this point it is a huge workload to replace all hardcoded text, which is why I do this stuff early on in a project. I still wish, you would consider it.
For some unknown reason I can't copy the helptext from the tool search, but from the tools customization.  But the "User Tool Text" just works in the tool search and not in the tool customization...