Dolphin 2.0 in kde 4.8.2 create a folder with slashes / in it foo/bar/qux and dolphin tries to keep them in file name AND shows it! Reproducible: Always Steps to Reproduce: 1.right click 2.create new --> folder 3.foo/bar/qux Actual Results: see the impossible filename listed! (I think it is a look alike character... which is not a safe or good practice) Expected Results: create the path or give error message drwxr-xr-x 5 aaron aaron 4.0K 2012-04-30 01:07 . drwxr-xr-x 92 aaron aaron 12K 2012-04-30 01:07 .. drwxrwxr-x 2 aaron aaron 4.0K 2012-04-30 01:07 bar⁄baz⁄qux drwxrwxr-x 5 aaron aaron 4.0K 2012-04-27 20:19 etc -rw-rw-r-- 1 aaron aaron 29K 2012-04-27 23:25 liverootfs.tar.gz -rw-r--r-- 1 aaron aaron 8 2010-08-06 20:56 moocow.txt drwxrwxr-x 4 aaron aaron 4.0K 2012-04-27 19:21 usr aaron@chum:~/test$ cat bar⁄baz⁄qux/ cat: bar⁄baz⁄qux/: Is a directory aaron@chum:~/test$ This is impossible!!!! wtf!?! Please don't go find another character that looks like it, it's not right!
Created attachment 70772 [details] screenshot of the foo/bar/qux file
As far as I know this is a feature not a bug - however I'm reassigning it to kdelibs, where this has been implemented (btw: you've also commented on bug 296825 and as you see the expectations in this usecase what should happen differ from person to person). Personally I have no strong opinion here what should be done, but consider the current behavior fine: I've already watched enough people adding a '/' as part of the filename.
Swapping characters without confirmation is not ok! PERIOD. I don't know how to type that fake slash, or what to call it, and that means I can't handle it. If there is a language where there are slashes that are not our slashes... they need to type the ALT-whatever code or turn on a non-standard option. A non-modal interactive dialog would be the best thing for this, but I must inisist that it cannot swap characters by default. There are excuses for people who don't know a / cannot be in a filename... but there is no excuse for not educating them. That guy in the other bug now knows he can't do that with a /, and I don't even know how he got the idea that he could put a / in a filename to begin with.
> Swapping characters without confirmation is not ok! > PERIOD. It seems not to be OK at least for you, but we need to provide software also for other people out there ;-) > There are excuses for people who don't know a / cannot be in > a filename... but there is no excuse for not educating them. It depends on the target-user group KDE is aiming for: For users like you (and probably me) it is clear that '/' should not be part of a name and automatically creating sub-folders would be nice. On the other hand the majority of users out there is not aware about this. If you think with our < 1 % market share we are in a position to educate users about this - well, I guess we'll stay below 1 % forever ;-) But as said already above: I've not really a strong opinion about this topic and as it is not on me to decide about this I won't continue a lengthy discussion. To use your words: period :-)
I'm sorry for writing in an emotional style... this is a violation of trust with my computer... The issue is not the fake slash existing, it is the swapping of a slash for some other look alike. It is a problem for interopearability with other programs and people. I don't think I know anybody who knows how to type "fake slash" or even what to call it. I type slash, I expect to get a slash. It is like ordering a hamburger, and getting a chicken sandwitch. How does dolphin deal with non printable characters? Is there an option to have Dolphin show non ascii as an escaped sequence? This would be more appropriate. Look alike letters are also a security concern for websites.. I can go to google.com/ and it could be a different website than google.com I should not have a problem with having non-ascii in my filenames, (I do, but I'm trying to relax and get used to it) What else gets swapped? (somewhat rhretorical)
also, consistancy with other programs aaron@neptune:~/test$ touch cow/moo/flea touch: cannot touch `cow/moo/flea': No such file or directory aaron@neptune:~/test$
also, consistancy with other programs aaron@neptune:~/test$ touch cow/moo/flea touch: cannot touch `cow/moo/flea': No such file or directory aaron@neptune:~/test$ (create it in dolphin) aaron@neptune:~/test$ ls cow⁄moo⁄flea aaron@neptune:~/test$ cd cow/moo/flea bash: cd: cow/moo/flea: No such file or directory aaron@neptune:~/test$
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!
Dear Bug Submitter, This is a reminder that 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
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!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!