Feature request: function key buttons to change with Shift
Moderators: Hacker, petermad, Stefan2, white
- Garlin007
- Junior Member
- Posts: 20
- Joined: 2003-03-11, 22:47 UTC
- Location: Toronto, Ontario, Canada
- Contact:
Feature request: function key buttons to change with Shift
In the original NC, when you pressed Shift, Ctrl or Alt, the descriptions on the button bar changed accordingly. Could this be implemented? This would be of help to newbies who don't know what the function keys do, especially if there were a tool-tip that more fully explained the button when you hover over it.
Garlin007 wrote:In the original NC, when you pressed Shift, Ctrl or Alt, the descriptions on the button bar changed accordingly. Could this be implemented?
Hacker wrote:IIRC Christian said this would cause too much trouble for the translators.

- Wanderer -
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
Too much??? Just several more strings (seems 44 standard hotkeys related with function keys) in addition to existing 1160 items... 7 strings are already translated and probably all others also can be found in current wcmd_eng.lng.Hacker wrote:IIRC Christian said this would cause too much trouble for the translators.
- ghisler(Author)
- Site Admin
- Posts: 50475
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
The problem is that all cm_xxx commands would need translations too, because TC would have to show the redefined hotkeys. Currently the bottom buttons are all static.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
[face=courier]On 02-04-2003 11:26:23 +0000 ghisler(Author) wrote:
g> The problem is that all cm_xxx commands would need
g> translations too
Yeah, agree with Val, what's the problem? Translators should translate, aren't they?
BTW, all internal commands already translated into Russian. Several times, AFAIK...
[/face]
g> The problem is that all cm_xxx commands would need
g> translations too
Yeah, agree with Val, what's the problem? Translators should translate, aren't they?

BTW, all internal commands already translated into Russian. Several times, AFAIK...

[face=courier]The Protoss do NOT run from their enemies.
It is here, that we shall make our stand.[/face]
It is here, that we shall make our stand.[/face]
Translating and/or editing the nearly 50 language files does take a lot of work.
Maybe it's time for a poll
tra-la-la
yippieeee (click here)
Maybe it's time for a poll


...BRB...
-
- Junior Member
- Posts: 37
- Joined: 2003-02-08, 13:51 UTC
- Location: Moscow, Russia
Maxwish:
You should add: My own translation.
That's my case as i do not like official Rus translation. There are some translated strings that superpose internal combox, buttons, etc' dimensions. So i have to make them short. Moreover i like to change everything i can that fits my tastes (thanx to BD for explanations in old forum) as Alt-X instead of Alt + F4 for Exit in functional buttons or the trick described at you site with size and number of files
I support Val and BD, professional translators should translate everything, except Christian's trademarks and copyrights
You should add: My own translation.
That's my case as i do not like official Rus translation. There are some translated strings that superpose internal combox, buttons, etc' dimensions. So i have to make them short. Moreover i like to change everything i can that fits my tastes (thanx to BD for explanations in old forum) as Alt-X instead of Alt + F4 for Exit in functional buttons or the trick described at you site with size and number of files
I support Val and BD, professional translators should translate everything, except Christian's trademarks and copyrights
# 85814 Personal licence
-
- Junior Member
- Posts: 39
- Joined: 2003-02-27, 11:41 UTC
- Location: Catalunya
I agree with Valentino and others.
I use the Catalan translation for TC and I love the TC suport for all the languages.
I like the old NC style for bottom butons.
I know this is time and work for the translators, but I think Mr. Ghisler said that next release of TC will be in Autum 2003. It's enough time to tranlate the necessary strings.
And one wish for plugin developers:
Please, add multilanguage suport in your pluguins:!:
TC is multilanguage, IMHO the plugins must to be multilanguage too.
The developers can read the strings from the language file of TC or use their own language file.
I use the Catalan translation for TC and I love the TC suport for all the languages.

I like the old NC style for bottom butons.
I know this is time and work for the translators, but I think Mr. Ghisler said that next release of TC will be in Autum 2003. It's enough time to tranlate the necessary strings.

And one wish for plugin developers:
Please, add multilanguage suport in your pluguins:!:
TC is multilanguage, IMHO the plugins must to be multilanguage too.
The developers can read the strings from the language file of TC or use their own language file.
norfie wrote:Valentino and Black Dog want to translate and/or organize/coordinate this required translation. Christian, I suppose you will get all required translations in a short time.
Or I misunderstood somebody?![]()
![]()


Christian, please provide me and Black Dog with every translator's emails/addresses/phones, etc, and we'll care for the rest...

I think we'll find several sturdy guys on this forum to speed up things...

Yes, and I think it would be best if TC extended its plugin interface with necessary functions to get localized string for given identifier. IMHO, it's too much waste of efforts if every plugin author had to implement this functionality yourself (locating wincmd.ini file (in some cases it's even impossible without user intervention), getting selected language from it, locating lng file and getting desired string from it). TC already has this functionality, so it's only necessary to expose it to plugins.Unjoanqualsevol wrote:The developers can read the strings from the language file of TC or use their own language file.
- ghisler(Author)
- Site Admin
- Posts: 50475
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Not at all! But with so many translators, some will be on vacation, some others are just very busy with other stuff, and some have changed their e-mail address and didn't let me know. Yes, all this has happened! It usually takes more than a few months to get all translations together, sometimes from new translators.So, translators are lazy?
Please remember that these aren't professional translation services, these are all users who do it for fun. Professional translations to so many languages would be very expensive, and even less quality because the translators wouldn't know the program as the users who do the translations now.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
2ghisler(Author)
Yes, I understood these difficulties from the very beginning, just kidding...
To speed up translations you could ask for translations for new words/strings here on forum for languages whose translators didn't respond in several days. When original translators respond and ask you to change these strings (translated by someone else) you can always release corrections (original author's version) in the next TC version.
In the end, IMHO, it's better to leave new strings for such "problem" languages not translated (i.e. in English) than to leave all users from being happy having some new feature!
What about new interface function to get localized string from a plugin (see my prev post)?
Yes, I understood these difficulties from the very beginning, just kidding...

To speed up translations you could ask for translations for new words/strings here on forum for languages whose translators didn't respond in several days. When original translators respond and ask you to change these strings (translated by someone else) you can always release corrections (original author's version) in the next TC version.
In the end, IMHO, it's better to leave new strings for such "problem" languages not translated (i.e. in English) than to leave all users from being happy having some new feature!

What about new interface function to get localized string from a plugin (see my prev post)?