Bug 263420 - Adding files with "strange" encoding fails.
Summary: Adding files with "strange" encoding fails.
Status: REPORTED
Alias: None
Product: k3b
Classification: Applications
Component: GUI/Usability (show other bugs)
Version: 2.0.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-17 14:21 UTC by Szokovacs Robert
Modified: 2022-12-04 21:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Szokovacs Robert 2011-01-17 14:21:09 UTC
Version:           2.0.1 (using KDE 4.5.5) 
OS:                Linux

The problem described in bug 165044 affects K3B as well.

Reproducible: Always

Steps to Reproduce:
(assuming UTF8 locale)
1, create file with accented characters in the name: touch áéüö.txt
2, convert the name to Latin2: convmv --notest -f utf8 -t latin2 áéüö.txt
3, drag the file into the burning area


Actual Results:  
Error message, file is unaccessible

Expected Results:  
the file should be added to the to-be-burned list
Comment 1 Andrew Crouthamel 2018-11-12 02:56:33 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Szokovacs Robert 2018-11-14 15:03:01 UTC
In Version 17.12.3 (KDE Frameworks 5.47.0) the bug still reproducible.
Comment 3 Justin Zobel 2022-12-03 09:01:36 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Szokovacs Robert 2022-12-04 19:49:45 UTC
Yes, in K3b Version 22.04.3, the behavior is still the same. Dolphin now thinks it invokes (for example) kate OK, but in reality kate opens a non-existing file...