Bug 158967 - alt-numpad character input does not work
Summary: alt-numpad character input does not work
Status: RESOLVED DUPLICATE of bug 158112
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.6.4.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-02 10:14 UTC by staho
Modified: 2024-01-02 10:50 UTC (History)
0 users

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 staho 2024-01-02 10:14:22 UTC
Description:
In Windows one can type a character that is not present on the keyboard, using alt-numpad combination, e.g. Alt-0151 for &madsh; (—). It works in about everything, from notepad to Word. However, in Writer the numeric pad is regarded just like digits on the main keyboard part, in particular alt-1 is a shortcut for "properties" dock — thus using alt-numpad is no more possible. 

Moreover, the shortcuts alt-1, alt-2, alt-3 and alt-4 are NOT defined in the tools>>customise window, i.e. they appear unassigned or they have default assignments. 

A (kind of) workaround is to unassign anything from alt-0, alt-5..alt-9 AND assign "view 100%" to alt-1..alt-4. 

Steps to Reproduce:
1. open any document or create a new one
2. press and keep left Alt
3. type 0151 on the numeric key pad

Actual Results:
works like shortcuts alt-0, alt-1, alt-5, alt-1

Expected Results:
character “—”


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: pl-PL (pl_PL); UI: pl-PL
Calc: threaded

Windows 10 Pro	22H2
Compilation	19045.3803
Windows Feature Experience Pack 1000.19053.1000.0
Comment 1 Mike Kaganski 2024-01-02 10:50:57 UTC

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