Le 2016-01-06, Tony Houghton <h...@realh.co.uk> a écrit : > On 05/01/16 18:32, François Gannaz wrote: > > Removing the locale with `LANG=C roxterm --separate` does fix it. > > > > And just as you suggested, the problem lies within the matching of > > action names. The strange part is that only part of it is > > translated: > > > > File/New Tab=<Shift><Control>t > > File/Nouvel Onglet=<Shift><Control>t > > > > "File" is translated into "Fichier" in roxterm's menu, but > > "Fichier/Nouvel Onglet" was ignored. > > So the submenu strings have to be translated, but not the top-level > menus? Strange. I might be able to at least correct that for > consistency, but I don't know what the ultimate solution would be. It > doesn't help that it's years since I worked on the relevant parts of > the code! If I make it so that the shortcuts are English then the > standard ones will work no matter what the language, but that will > make it harder for non-English users to configure their own. Is it > normal for the keystrokes to stay the same no matter what language is > used, or for those to be changed to match the words in other > languages? For example, would you expect to use <Shift><Control>t to > match the English version, or <Shift><Control>o for "onglet".
I'm very reluctant to a localized configuration, with keyboard shortcuts would vary with the locale. When I switch to another system, I expect an application to behave similarly: I've used Ctrl-Shift-t with several terminal emulators, and I did not care much which locale was declared, it was always the same shortcuts in every terminal. I would also get very confused if my config file were to break when the locale changes. I suspect some people pay more attention to menus and consistency between labels and shortcuts, but probably not that much for something as technical as a terminal emulator. That's my opinion, you decide. -- François
