As of VNC2Me Beta 0.2, Translations of ALL GUI items can be done through the INI file. All User Interface text labels including traytips and popup's "SHOULD" be read from the INI, anything not so, SHOULD BE IN CAPITALS.
VNC2Me Debug Output has not been translated, because it would make the translations too long, and your clients would have no benefit from it, as debugging should be turned off before it gets to them.
The translation system has been (re)written to allow translation to any language without touching any code (just editing the INI file).
This rewrite made setting up the INI for translation a little more difficult, but there are some examples in the INI, that should be enough for most people.
The Following table lists some examples of the settings needed in the INI for translation.
| Language | INI Section Name | INI Language Section settings |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I'm sure you can see the pattern emerging, if you have problems, follow the step-by-step below, or post your problems on the translations forum. where registered users can post their INI
Step by step translating
VNC2Me Translation steps:
- Open vnc2me_sc.ini in your favourite editor (mine is notepad++
). - Copy the whole [Lang_English] Section. (other language sections may not be up-to-date,
- Paste it into the bottom of the INI file.
- Rename the section name to the Appropriate "Prim. lang. symbol" (4th column) from the MSDN Language Identifiers Constants
table. (http://msdn.microsoft.com/en-au/library/ms776294.aspx) - Copy the "Locale identifier" for that language (and any sub languages) into a new LANG_IDENT_N="" parameter (where N is the next sequential number in the list.
- Increment "LANG_COUNT=X" so that X is the number used above (step 5) plus one (x=n+1)
NOTE: numbering MUST be sequential, the "LANG_COUNT" accurate and no spaces should be present anywhere in the language section, otherwise the locale / language will not be read properly. - Enable debugging and download the Debug Viewer
, save the INI changes and start VNC2Me. Check that your language is being read correctly from the INI, similar to the example below:
[11120] V2M - Language loopcount = 0 & 041d <> LANG_IDENT_0 [11120] V2M - Language loopcount = 0 & 041d <> LANG_IDENT_1 [11120] V2M - Language loopcount = 0 & 041d <> LANG_IDENT_2 [11120] V2M - Language loopcount = 0 & 041d <> LANG_IDENT_3 [11120] V2M - Language loopcount = 0 & 041d <> LANG_IDENT_4 [11120] V2M - Language loopcount = 0 & 041d <> LANG_IDENT_5 [11120] V2M - Language loopcount = 0 & 041d <> LANG_IDENT_6 [11120] V2M - Language loopcount = 0 & 041d <> LANG_IDENT_7 [11120] V2M - Language loopcount = 0 & 041d <> LANG_IDENT_8 [11120] V2M - Language loopcount = 0 & 041d <> LANG_IDENT_9 [11120] V2M - Language - Auto detected language: Swedish <@OSLang = 041d>
- If the windows locale cannot be found within any of the
LANG_IDENT
parameters in theLANGUAGES
section, English is selected as the default language. - Save the file (in the same directory as the VNC2Me.exe file)
Setting a Language
VNC2Me can also be "Forced" to use a specific language, thus overriding the automatic language selection which is based on locale.
This method was the original way to change languages (before locale was used), but remains today, as it may be of benefit in certain circumstances.
- Open VNC2Me_sc.ini in your favourite editor (mine is notepad++
). - In the "COMMON" Section, set "LANGUAGE" parameter to your choice of language (removing the preceding "Lang_" from the section name).
- Enable debugging and download the Debug Viewer
, save the INI changes and start VNC2Me. Check that your language is being read correctly from the INI, similar to the example below:
[14612] V2M - Language - Using language from INI file: Lang_English
- Save the file (in the same directory as the VNC2Me executable).
Many fields within the GUI are limited in size, should a translation require an increased field size, every avenue will be explored to find a resolution, please quote the INI data that relates to that field, and how much bigger (percent) you need it (the translated text for that field would also be of benefit).
All comments/questions about translation can be added to the comments of this article, or to the "Translation" section in the forum.











