Bug 139960 - Insert time hotkey does not work on non-english keyboard settings
Summary: Insert time hotkey does not work on non-english keyboard settings
Status: RESOLVED DUPLICATE of bug 129547
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.4.2 release
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Shortcuts-Locale
  Show dependency treegraph
 
Reported: 2021-01-28 08:03 UTC by Tomas Janco
Modified: 2022-05-12 10:30 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Janco 2021-01-28 08:03:30 UTC
Description:
The default hotkeys for inserting date and time are Ctrl+~ and Ctrl+Shift+~ on US keyboad layout.
However I use Slovak keyboad layout, where the ~ key actually writes semicolon (;). The Ctrl+~ hotkey is correctly localized to Ctrl+; and works as expected.
The Ctrl+Shift+~ is localized to Ctrl+Shift+; but Shift+; on Slovak keyboard is ° sign and it is a dead key. The Ctrl+Shift+; hotkey does not work and there is no option to set Ctrl+Shift+° hotkey in the list.

Steps to Reproduce:
1. Set keyboard layout to Slovak
2. In Calc, press Ctrl+~ (Ctrl+key below escape key) to insert date
3. Press Ctrl+Shift+~ to insert time

Actual Results:
Date is inserted in 2., Nothing happens in 3.

Expected Results:
Date is inserted in 2., Time is inserted in 3.


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: sk
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Linux (Gentoo)
OS is 64bit: yes
Comment 1 Ziyad 2021-01-31 19:16:32 UTC
I am in the same situation. I use an arabic keyboard layout. (Ctrl+'), (Ctrl+;), (Ctrl+[), (Ctrl+]) and even (Ctrl+Shift+ any of those keys) doestn't work.
That problem is old.
Comment 2 Buovjaga 2022-05-12 10:30:56 UTC

*** This bug has been marked as a duplicate of bug 129547 ***