Description: On Windows, the default shortcut for ZWNJ is ctrl+shift+2. To use that, one should activate Persian keyboard layout, and then press this key combination. Zero-width non-joiner https://en.wikipedia.org/wiki/ZWNJ This does not work on LibreOffice Calc. At the same time, typing ZWNJ using this key combination is possible in Notepad. Steps to Reproduce: 1. Open Calc 2. Activate Persian keyboard layout 2. Type می then ctrl+shift+2 and then شود Actual Results: After pressing ctrl+shift+2, the selected cell comes out of the editing mode, and the rest of the word that is typed is overwritten on the previous text. Expected Results: ZWNJ should be inserted in the document. For example, if you type می then ZWNJ and then شود you should get میشود, but you will get شود because the previous part is overwritten. Reproducible: Always User Profile Reset: No Additional Info: Additional Info: Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: f505d8fee149f089090b208db99a7b4107af76e9 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: fa-IR (fa_IR); UI: en-US Calc: threaded
All shortcuts for ZWNJ, including the ones I made using AutoHotkey are now broken, also broken in LibreOffice Write. Not only that, but also no character can now be inserted into a text using and Alt+xxxx combination. For instance, it used to be possible to insert “, ”, ‘, and ’ by using Alt+0147, Alt+0148, Alt+0145, and Alt+0146 respectively. Now, as soon as the Alt key is pressed, other actions hijack the event and either parts of the UI switches on or off or something else happens. Disabling the shortcuts in the Customization menu does not seem to disable the hijacking of the Alt key, so that is also broken. I believe for this latter issue a new bug report must be opened. Therefor, the only way to insert a ZWNJ character now is to go through the Special Characters menu, find the character, and then insert it into the text.
I think I might have a hypothesis why this is happening: 1- Go to Tools -> Customize... -> Keyboard 2- Scroll down to where the keyboard shortcut for Ctr+Shift+2 is 3- Assign the shortcut you need to use 4- Before you leave, look at what is on the side of the top right corner of the Shortcut Keys list: You will see a radio selector that might be defaulted to Calc, Write, or any other app you are inside 5- Now switch to the top radio item, i.e. LibreOffice (in my case LibreOfficeDev because I am using a development version) 6- Repeat steps 2 and 3 above 7- Click on OK The software should correctly behave as you asked it to behave. I went through the same steps (missed step 4 the first 100 times that I was trying to find a reason why this is happening). Once done, my AutoHotkey script is now working fine (it inserts everything I wanted it to insert, including the ZWNJ character. Please let us know if these steps fixed the issue.
Created attachment 191673 [details] Aa screenshot of the keyboard shortcut key menu This is a screenshot of the menu for Customization of the keyboard shortcut keys. In this image, the section that has caused me confusion and wasted hours of my time trying to troubleshoot the issue is indicated by a red rectangle on the top right corner.
@Eric, you are mixing different reports. Bug 158112 is about the [ALT]+[numpad] shortcuts. Bug 150512 is about a specific character under specific conditions. There is a chance that these two reports are actually about the same thing, and so resolving one would resolve the other too. Please, until then, let's keep each of these reports on-topic.
The shortcut to insert ZWNJ into Writer is still broken (as of 2025-02-15). It makes no difference if I assign it to [Ctrl]+[Shift]+2 or I use my own AutoHotkey to alter it. It simply does not work any longer. I even used 25.8.0.0 alpha0+ (https://git.libreoffice.org/core/+log/1be7c7a3f200cab41cb718399e39e7e13e45aa2e) and got exactly the same broken behaviour as before. It is noteworthy that it got working some time ago, certainly long after when this bug was reported, till a few months ago. However, I cannot pinpoint when it broke again. I will try to narrow it down and if I could find any build that was working in the past few months, I will make a comment here.