Bug 149307 - incorrect >7bit filenames handling (Polish)
Summary: incorrect >7bit filenames handling (Polish)
Status: RESOLVED DUPLICATE of bug 297733
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Shie Erlich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-28 20:52 UTC by Maciej Pilichowski
Modified: 2012-08-17 00:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2007-08-28 20:52:31 UTC
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.
Comment 1 Maciej Pilichowski 2007-08-28 20:53:52 UTC
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.
Comment 2 Simos Xenitellis 2008-02-07 00:02:41 UTC
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.
Comment 3 Maciej Pilichowski 2008-02-07 10:13:47 UTC
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.
Comment 4 Maciej Pilichowski 2008-02-07 10:15:17 UTC
More problems:
when I try to delete file ”żółw" using Krusader it claims it does not exists (yet Krusader displays this filename).
Comment 5 Maciej Pilichowski 2009-01-18 16:06:07 UTC
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.
Comment 6 Jan Lepper 2012-08-16 12:40:58 UTC
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.
Comment 7 Maciej Pilichowski 2012-08-16 15:43:17 UTC
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.
Comment 8 Jan Lepper 2012-08-16 16:04:33 UTC
But your have set LANG=en_US.UTF-8 ?
Comment 9 Maciej Pilichowski 2012-08-16 20:00:22 UTC
This report is 5 years old -- NOW I have utf8, THEN (when reporting) I had iso-8859-2.
Comment 10 Jan Lepper 2012-08-16 20:56:45 UTC
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.
Comment 11 Maciej Pilichowski 2012-08-16 21:11:45 UTC
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 ***
Comment 12 Jan Lepper 2012-08-17 00:42:33 UTC
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