Colleagues Navigators - in reference to the post [Only registered and activated users can see links. ] and answers -> [Only registered and activated users can see links. ] post1003214 A little note:

Is not a good practice to change the software iGO messages in the source files - as a suggested colleague - NyKy.
This can lead to a program bug, or at least it stops.
Changes to commands that are displayed in the form of messages on the screen, or heard and measured in the speaker (for TTS) should be made in the files dictionary.lang, or dictionary.voice.
It is these files have been created to ensure that the national languages are visible or audible.
The introduction of changes in the manner specified by Nyky - may in fact lead to a situation where the command contained in the tool and translated into the native language does not find a counterpart in the program - because there is a reference to a specific argument in English.

Dictionary.lang file is an archive lang.zip i18n folder.
Once you open it (without unpacking), we see a whole series of messages that have their own translation of the English language (native for the program) into a national - eg.

DEBUG ~ Animated Policeman = "Animowany Policjant"

here "Animowany Policjant" = Animated Policeman (in my - that is Polish)

All you have to insert the string to translate preceded by DEBUG ~
that is: DEBUG ~ .......... (message content) = "...... (j translation. domestic) ..."

Then save and when asked whether to change or save the contents of the archive.
I'ts all

It also described the costas3850 (thx) in the post -> [Only registered and activated users can see links. ]
and ready.



PS.And at the end of the request:
If the answer to the questions User's - it corresponds to the way it is correct.
Shortcut - understandable for stagers will not be good for beginners.

Regards wojpen