Skip to main content
MerlinDE
Inspiring
December 30, 2019

P: Keyboard shortcuts for German broken

  • December 30, 2019
  • 17 replies
  • 1309 views

Again, the shortcuts for German language translation and keyboards is broken.  

Examples for develop module (references taken from Adobe's documentation at https://helpx.adobe.com/de/lightroom-classic/help/keyboard-shortcuts.html) :

  • Cycle through base settings: . / , -> these are mapped to increase/decrease picture rating
  • Brush size: ö / # -> # increases current slide in base settings; ö seems to do nothing
  • Anything using [ / ] -> this doesn't work on German keyboards; no exceptions!

 

This list continues endlessly. 

 

@Adobe: Can you please finally implement QA for all languages you deliver your product for? 

 

Cross post from https://community.adobe.com/t5/lightroom-classic/keyboard-shortcuts-for-german-broken-in-lightroom-c...

This topic has been closed for replies.

17 replies

johnrellis
Legend
April 19, 2020
Here are the lines in TranslatedStrings_Lr_de_DE.txt that specify the shortcuts for selecting the next and previous sliders in the Basic panel and incrementing and decrementing the slider values:

"$$$/AgDevelop/KBSC/decrementTargetAdjustmentValue=-"
"$$$/AgDevelop/KBSC/decrementTargetAdjustmentValueAlt=_"
"$$$/AgDevelop/KBSC/incrementTargetAdjustmentValue=#"
"$$$/AgDevelop/KBSC/incrementTargetAdjustmentValueAlt='"
"$$$/AgDevelop/KBSC/resetTargetAdjustment=;"
"$$$/AgDevelop/KBSC/targetNextAdjustment=+"
"$$$/AgDevelop/KBSC/targetPreviousAdjustment="

cryangel
Participant
April 19, 2020


There's a ton of different Articles relating to Keyboard Shortcuts, is that so difficult to get Fixed ?
On my Germany Keyboard lots of the Shortcuts are totaly Different to what the helpfile says, and some i cannot figure out at all.
Shortcuts for speedy developing in the main developing-tools-window   #/- ( indrease/decrease) are only accesible via + (scrooling through the tools) in one Direction ( downwards)? is there no Shortcut to go the other direction (upwards) as well ?  so if i want to togle betwen contrast and brightness, i allways have to go through ALL the tools till i get there again??
johnrellis
Legend
March 5, 2020
"Will my adjustments in the file (“transletedstrings”) remain even after an update?"

No, the TranslatedStrings file gets overwritten by each update, so you'll have to save away your edits in a separate file in your home directory. The Keyboard Tamer plugin remembers your shortcut edits, so you can just rerun the plugin after each new release.
Inspiring
March 5, 2020
Thank you very much for the answer john!

Are the shortcuts in the file "transletedstrings" hardcoded?

Now one more question: Will my adjustments in the file (“transletedstrings”) remain even after an update? Or do I have to insert them again? Have you already gained experience with this?


johnrellis
Legend
March 4, 2020
LR doesn't offer a convenient user interface for defining shortcuts. You can change many shortcuts (inconveniently) by editing the TranslatedStrings.txt file:
https://www.lightroomqueen.com/custom-keyboard-shortcuts/

The Keyboard Tamer plugin makes it easier for you to do that editing.

Unfortunately, many LR shortcuts are (unbelievably) hardwired into the code, including the ones the original post in this topic complains about.

Users have been asking to customize keyboard shortcuts since LR 1, and it's one of the most popular feature requests here. In that feature request I made a detailed proposal for how Adobe could incrementally improve the situation at low cost:
https://feedback.photoshop.com/photoshop_family/topics/custom_keyboard_shortcuts_in_lightroom?topic-...

You might add your constructive opinion to that feature request and add your Vote.
Inspiring
March 4, 2020
is there any news about this issue?
Is it possible to define the shortcuts yourself?

Edit: Found a solution: In the file "translatedstrings*" I can edit the shortcuts. Is there a possibility that they will be kept during an update? Otherwise they are always gone 😞
Inspiring
December 30, 2019
I read about problems with non-English keyboards all the time. I don't know if it's gotten worse over the years, or has always been this bad, but it's one of the key reasons I believe it's well past time that kbsc weren't hard-wired. That's SO back in the day of typewriters, not computers.

Give us a default set, fine. But nothing hard-wired. Let us change any of it to suit ourselves, our own workflows, our own languages. And give us an interface like you see in PP to see what is in use, what is available, depending upon whatever workspace (if there are multiple workspaces) we're in. I think we're past the point of "fixing" it by tinkering with bits and pieces of it—because every new kbsc they come up with for some new feature is going to break in some localized version, or break someone's workflow.