https://bugs.kde.org/show_bug.cgi?id=364372
Thiago Sueto <herzensch...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
CC| |herzensch...@gmail.com
Ever confirmed|0 |1
--- Comment #9 from Thiago Sueto <herzensch...@gmail.com> ---
I can reproduce this issue with Kate 20.08.03 and, huh, kio 5.20.2 (that's what
kioclient5 --version states).
The tarball contains four files that can be opened with Kate and five with what
I assume are japanese characters (they're rendered as squares) plus (elona) or
(elonaplus) in their name, those are the ones that do not open on Kate. Dolphin
displays a chainlock on the bottom right of their icons.
Opening them by clicking makes Kate state the file does not exist.
Opening the embedded terminal and opening a file with Kate (like with fish
autocompletion) leads to Kate creating a new empty file with the same name.
Neither vi or nano seem to render japanese characters correctly (but it might
be because I didn't specifically install japanese fonts).
Renaming any of those files using the default encoding allows the file to be
opened by Kate, and after opening, the text inside shows up in proper japanese.
--
You are receiving this mail because:
You are watching all bug changes.
