Version: (using KDE KDE 3.5.7) Installed from: SuSE RPMs Maybe such filenames are not valid, but then Krusader should show appropriate warning. Let's say I have file a.txt and I want to rename it to ą.txt ą is a Polish character. I hit enter and I get ?.txt no warning Bug in bug, if I rename it to ć.txt I get warning "file ?.txt already exist, do you want to replace it" -- obviously in such case it is nonsense. I can rename files in Konsole (bash) or MC just fine, they are displayed also fine.
PS. Just to clarify, the last note is just to show that renaming to ć.txt is possible at all, I didn't mean to suggest that file ć.txt named in MC should be read the same way in Krusader.
What I see here is that KDE has a bug with filenames in an encoding other than ASCII. If a letter in the filename is converted to ?, this means that we had data loss. If you can verify that any filename/directory name with non-ASCII letters are converted to ???, then this is a very important bug in KDE.
Why KDE has a bug? Kate works fine (for example), Krusader does not. I just verified: LANG=pl_PL or LANG=pl_PL.ISO-8859-2 each time I rename file to (for example) żółw in Krusader, I get ?ó?w ó occurs not only in Polish (ISO-8859-1, that is the reason there is no error here. But, when I save a file in Kate with filename żółw I get żółw And what's important. When I run Krusader again to see what Kate saved I see... żółw So Krusader can interpret correctly filenames, but it cannot translate correctly input from the user.
More problems: when I try to delete file ”żółw" using Krusader it claims it does not exists (yet Krusader displays this filename).
Still present in KDE4.1.3, LANG=en_US.UTF-8. Visual appearance: instead of each Polish character I see diamond letter with "?" inside. Rename: I can edit such filename, but when I press enter I get error saying the file does not exist.
Are you sure the file names are in UTF-8 encoding ? If the aren't, this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=297733.
I wrote they are NOT utf-8. And it is not duplicate of the mentioned report "Filenames with invalid encoding..." because I also wrote which encoding I use. ISO-8859-2 is absolutely valid encoding.
But your have set LANG=en_US.UTF-8 ?
This report is 5 years old -- NOW I have utf8, THEN (when reporting) I had iso-8859-2.
On Thu, 16 Aug 2012 20:00:22 +0000 Maciej Pilichowski <bluedzins@wp.pl> wrote: > https://bugs.kde.org/show_bug.cgi?id=149307 > > --- Comment #9 from Maciej Pilichowski <bluedzins@wp.pl> --- > This report is 5 years old -- NOW I have utf8, THEN (when reporting) > I had iso-8859-2. > So if I understand you correctly, your locale is set to utf8, but you still have non utf8-encoded filenames. AFAIK this is exactly what leads to bug https://bugs.kde.org/show_bug.cgi?id=297733. The issue that you originally reported is probably a different one, since it was still the kde/qt 3 version.
Jan, let's close it as a duplicate, and if anyone runs in the same problem, in such case she/he could ask for reopening with providing more details. Since I guess, you will concur with me on that, I am closing it now, ok? *** This bug has been marked as a duplicate of bug 297733 ***
On Thu, 16 Aug 2012 21:11:45 +0000 Maciej Pilichowski <bluedzins@wp.pl> wrote: > https://bugs.kde.org/show_bug.cgi?id=149307 > > Maciej Pilichowski <bluedzins@wp.pl> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution|--- |DUPLICATE > > --- Comment #11 from Maciej Pilichowski <bluedzins@wp.pl> --- > Jan, let's close it as a duplicate, and if anyone runs in the same > problem, in such case she/he could ask for reopening with providing > more details. > > Since I guess, you will concur with me on that, I am closing it now, > ok? > > *** This bug has been marked as a duplicate of bug 297733 *** > Ok