Description: As in the title Language A of protected cell can be changed to Language B. Steps to Reproduce: 1.Create at least 2 (Y and X) cells one with Language A (Y) the other wit Language B (X) 2. Protect Y placing the cursor in it and clickig on the table plus locked lock symbol. 3. Click on Tools/language/For all text/Language B or C but not A. Actual Results: Cell Y has changed to Language B or C Expected Results: It should keep Lanuage A Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.4.2 (AARCH64) / LibreOffice Community Build ID: 51a6219feb6075d9a4c46691dcfe0cd9c4fff3c2 CPU threads: 8; OS: macOS 14.5; UI render: Skia/Metal; VCL: osx Locale: en-US (en.UTF-8); UI: en-US Calc: threaded
Created attachment 195279 [details] Test file
I confirm it with Version: 24.8.0.3 (X86_64) / LibreOffice Community Build ID: 0bdf1299c94fe897b119f97f3c613e9dca6be583 CPU threads: 4; OS: Windows 10 X86_64 (10.0 build 19045); UI render: default; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: CL threaded Additional observation If you select table, entries in Tools -> Language are greyed out But perhaps result should be, that a dialog pops up wih a message like: Do you want to change language also for protected cells? (Yes / No) But reading bug 120726 I've learned that there's already a warning message. But it doesn't appear if I try to change a protected cell. => Design-Team
Confirmed by comment2
I would balance convenience versus protection. Do you experience a data-integrity issue or something similar, Daniele?
Hi Heiko, Thank you for asking. I suppose that you mean whether I lost data. No I did not. The reason why I posted this in the first place is that something happens which, according to the behaviour of protected cells, should not. In my case it was my mistake to change the language for all text, and still I was surprised that the protected cells were affected. But imagine different people working on the same document and the cells having been protected to avoid accidental changes in them. The fact that the changes cann accidentally be applied is annoying. Moreover this results in non functioning of spelling or grammar checker tools. I would be in favour of a warning for consistency sake with the behaviour of the blocking. I hope that I answered your question, kind regards, Daniele
[Automated Action] NeedInfo-To-Unconfirmed
The topic was on the agenda of the design meeting. With no further input I suggest to keep the ticket with low importance. If a volunteer wants to show this information it would be welcome. This should likely be Calc as Writer tables have no option for content protection.