https://bugs.documentfoundation.org/show_bug.cgi?id=143540

Marco Menardi <mme...@mail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|NOTOURBUG                   |---
             Status|RESOLVED                    |REOPENED

--- Comment #35 from Marco Menardi <mme...@mail.com> ---
I think is LibreOffice bug, because the regular, old, "has always be this way"
behavior, also in Windows, is that the numeric decimal separator produces
exactly what is printed on that key and specialized programs that heavily relay
on numeric decimal input do the conversion, so is not a KDE problem but that
part that is broken when integrating libreoffice with KDE-Wayoand.
I.e. Italian keyboard has a "." (dot) printed in the numeric keypad, but our
decimal separator is "," (coma).
Wherever I press that key a dot is produced, but i.e. Excel or KCalc (KDE
calculator) or LibreOffice calc (under X11), has always converted "on the fly"
to a decimal separator.
Another example: on Windows in Notepad we obtain a dot, in Calculator we get
the decimal separator.
So current KDE behavior is correct, it Libreoffice that does not behave
correctly with Wayland KF integration (worked fine in X11).
Is just recently with KDE moving to Wayland that things have changed for me
with LibreOffice, i.e. KCalc works instead just fine as with X11.
(btw, I've had this but when moving to KDE 6.1 and Wayland, from 5.27 and X11,
so I tested only  KF5 and KF6 on QT6)
If I remove the libreoffice-kf5/6 package, being still in KDE, the keypad works
fine.

Test results:
NO Bug with
KDE 5.27.11
KdeFramework 5.115
QT 5.15.13
LibreOffice 24.2.5
X11

YES Bug present with
same as above, but with Wayland!
(installed plasma-workplace-wayland and switched to it at login)

YES Bug present with
KDE 6.1.4
KdeFramework 6.6.2
QT 6.6.2
LibreOffice 24.8.0
Wayland
(tested both with libreoffice-kf5/6 and libreoffice-qt5/6)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to