Salamander 2.5 is not accepting my newly translated language SLG module as another language (Spanish) in Configuration.
I am using Resource Hacker 3.4.0.79 and have translated the menus and a bunch of dialogs to Spanish, as well as relevant portions in the "version info" section (SLGAuthor, SLGEmail, SLGComment, and SLGHelpDir).
Tried turning back to the original values in version info, but it does not help.
The translated file seems to be OK both when read by Resource Hacker and by checking the translated dialogs and menus.
Any suggestion? I would rather prefer not having to start again!
Translation problem
-
- ALTAP Staff
- Posts: 5231
- Joined: 08 Dec 2005, 06:34
- Location: Novy Bor, Czech Republic
- Contact:
Please send me your translated SLG file to jan.rysavy@altap.cz, I will try to look what went wrong.
-
- ALTAP Staff
- Posts: 5231
- Joined: 08 Dec 2005, 06:34
- Location: Novy Bor, Czech Republic
- Contact:
Thank you for taking your time!
I changed back 1033 to 0 (strange, since any change in version info puts back 1033 as resource type) and saved again, but still it does nor run as a new language.
Later, I recalled that the original, old file was still in the lang directory, so I told the configuration to use the spanish_original.slg file. Salamander replied that it should start again to recognize the new language file. When I did it, the error message came out saying something as file \program files\Altap Salamander 2.5\plugins\regedt\lang\spanish_original.slg was not found or not valid.. and it tries to find a valid slg file. Finally it can be started, but the spanish slg cannot be used (probably spanish_original.slg was also modified to not run, since the translation is being made in several runs from Resource Hacker).
I realized that in every plugin directory there is a lang subdirectory. I put a dummy spanish.slg copy of the corresponding english.slg, but still the same.
There should be some other differences.
Is editing the SLG files the only way to make translations?
I changed back 1033 to 0 (strange, since any change in version info puts back 1033 as resource type) and saved again, but still it does nor run as a new language.
Later, I recalled that the original, old file was still in the lang directory, so I told the configuration to use the spanish_original.slg file. Salamander replied that it should start again to recognize the new language file. When I did it, the error message came out saying something as file \program files\Altap Salamander 2.5\plugins\regedt\lang\spanish_original.slg was not found or not valid.. and it tries to find a valid slg file. Finally it can be started, but the spanish slg cannot be used (probably spanish_original.slg was also modified to not run, since the translation is being made in several runs from Resource Hacker).
I realized that in every plugin directory there is a lang subdirectory. I put a dummy spanish.slg copy of the corresponding english.slg, but still the same.
There should be some other differences.
Is editing the SLG files the only way to make translations?
-
- ALTAP Staff
- Posts: 5231
- Joined: 08 Dec 2005, 06:34
- Location: Novy Bor, Czech Republic
- Contact:
You probably changed also other structures in the SLG 
Editing of SLG files is definitely wrong way. Please wait for the Altap Translator.
Look at http://forum.altap.cz/viewtopic.php?t=2076

Editing of SLG files is definitely wrong way. Please wait for the Altap Translator.
Look at http://forum.altap.cz/viewtopic.php?t=2076