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

            Bug ID: 152667
           Summary: Wrong text encoding for file names and clip board
                    under KDE x11
           Product: LibreOffice
           Version: 7.4.3.2 release
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: LibreOffice
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: tianer2...@outlook.com

Description:
When opening a file with Chinese characters in its name, the file name
displayed on the title bar becomes some random codes.

When pasting Chinese characters from the clipboard, it becomes random codes.


Steps to Reproduce:
1. Open LibreOffice Write, save the file as "test 测试 123.odt"
2. The title bar displays "test æµè¯ 123.odt"


3. Now, copy the string "test 测试 123" to KWrite first so it becomes pure text
without any html formatting
4. Copy the string again from KWrite to LibreOffice Write, it becomes some
random codes.

Actual Results:
Strings with Chinese characters become random codes.

Expected Results:
The pasted string should be the same.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
- This only happens under KDE X11. KDE Wayland works as expected.
- Copy & paste from browsers or from LibreOffice itself works as expected, but
any pure strings from text editor or file browser goes wrong.
- Looks like LibreOffice is not using the correct encoding for pasting those
strings.


System Info:

Operating System: Fedora Linux 37
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Kernel Version: 6.0.14-300.fc37.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-9300HF CPU @ 2.40GHz
Memory: 7.7 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2
Manufacturer: LENOVO
Product Name: 81T0
System Version: Legion Y7000 2019 PG0

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

Reply via email to