Articles

Translations revisited ...

VNC2Me now allows translation to ANY language supported by MS Windows.

These things happen if you wake up in the middle of the night with a head full of code (yep, THAT IS how much of a geek I am), and can't go back to sleep until its working.

Everything that needs to be changed for translation into currently (and future) supported languages, can be done from the INI, by setting up the locale(s) and language in the INI file (as well as the translating everything).

This means that most of what I said in the the earlier "Translate VNC2Me" How-to article, has been rewritten.

Now anyone can translate vnc2me, but will they help us help others ???

if you want to help, let us know, as we can always use a new translator (or twenty).

---

Add this page to your favorite Social Bookmarking websites

Getting the latest source code (SVN Checkout)

NOTE: the code you get from the SVN may not even work, let alone be stable

VNC2Me uses the Sourceforge SVN, to ensure source is available well into the future.

Windows users need to install some software, please follow these steps to begin:

1. Download Tortoise SVN and follow the prompts to install (default settings have always worked for me)
2. create a new directory in which to store the files.
3. Right mouse click on the new directory and select "SVN Checkout"
4. enter the address https://vnc2me.svn.sourceforge.net/svnroot/vnc2me into the "URL of repository" field.
5. Make sure "HEAD Revision" is selected, and click "OK"
6. Wait till all files are received (may take some time).

Further assistance with Tortoise SVN can be found on SF.net

---

Add this page to your favorite Social Bookmarking websites

Debugging VNC2Me SC Problems (Beta 0.2 and above)

User Rating: / 1
PoorBest 

VNC2Me comes with large amounts of debugging abilities built into the program, but debugging needs to be enabled in the INI file first.

Open the vnc2me_sc.ini file in your favourite editor (mine is notepad++) within the [V2M_GUI] section of the INI (near the top) is the option "MAIN_ENABLE_DEBUG=0", this should be set to "MAIN_ENABLE_DEBUG=1". This will enable the Debug checkbox near to the "Exit" button on the Main window, and a "Debug" option in the "Show" Menu of the Tray icon.

Two possible uses for debugging are:

1. Setup on NEW custom SSH server.
2. One / Some clients are having connection problems.

Basic Debugging

Type 2 above is the easiest to describe, as you have already eliminated possible SSH server problems due to most clients ability to connect successfully.
so lets start there:

1. Enable debugging using above method
2. Test and copy debug output to a text file (or other document such as spreadsheet)
3. Package this using your preferred method (setup scripts are provided in SVN or "Roll-your-Own" package), and send to the client.
4. Have the client open the application and tick the box (or use tray menu) to show the debug window.
5. Initiate the client connection (using the normal buttons on the main window).
6. Upon connection failure, press the "Debug > Clipboard" button on the debug window to copy all debug output to clipboard.
7. Instruct client to paste into email (or other).
8. Compare unsuccessful client connection with successful to find where application stops

This is the simplest way of debugging the application, as minimal data is collected.

Advanced Debugging

For more advanced troubleshooting, we have enabled the standard windows debugging system used by many applications, so applications like "sysinternals debugview" can be used to view all actions (well most) of the application. This allows pausing of debug output, large amounts of history to be viewed easily (its not unlimited), and many other features. Follow Step 1 of the above instructions to enable debugging, then:

1. Download and run a debugging program like "sysinternals debugview"
2. Close all running application that may be using this debugging system (best to close as much as you can)
3. Start VNC2Me with debugging enabled (described above)
4. View debugging output and troubleshoot problem.

If problem appears to be related to the SSH connection, try opening a command prompt in the VNC2Me directory, then open v2mplink using the following arguments: " your.host -v -ssh" (include a space between v2mplink and you host name)

You may also want to include any of the following:

• -P port# (connect to specified port - if different from 22)
• -l username (connect with specified username - otherwise plink asks)
• -pw password (login with specified password - otherwise plink asks)
• -2 (force use of SSH protocol Version 2) (NOTE: SSH Version 2 should be used in 99.9% of cases)

This should give you a successful connection, and allow you to run commands like "ls" on Linux or "dir" on windows. If you are unsuccessful with connecting using plink, then the problem is outside of the scope of our help, and you should lookup the problem in Google, or contact your hosting provider.

---

Add this page to your favorite Social Bookmarking websites

Translate VNC2Me

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.

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:

1. Open vnc2me_sc.ini in your favourite editor (mine is notepad++).
2. Copy the whole [Lang_English] Section. (other language sections may not be up-to-date,
3. Paste it into the bottom of the INI file.
4. 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)
5. 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.
6. 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.
   
7. 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>

8. If the windows locale cannot be found within any of the

   LANG_IDENT

   parameters in the

   LANGUAGES

   section, English is selected as the default language.
9. 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.

1. Open VNC2Me_sc.ini in your favourite editor (mine is notepad++).
2. In the "COMMON" Section, set "LANGUAGE" parameter to your choice of language (removing the preceding "Lang_" from the section name).
3. 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

4. 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.

---

Add this page to your favorite Social Bookmarking websites