| Summary: | Dolphin allows you to safely place slashes in file names, but for folder names, doing this creates a folder hierarchy | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | alex |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | alexh.public+kde, bugseforuns, cfeck, dev-laptander, elvis.angelaccio, hr.denzler, john.kde, nate |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=296825 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
alex
2010-09-20 16:22:37 UTC
mkdir foo/bar mkdir: kann Verzeichnis „foo/bar“ nicht anlegen: Datei oder Verzeichnis nicht gefunden mkdir -p foo/bar Are you sure the '/' character isn't replaced with '⁄'? Note that these are different Unicode characters, and it may depend on the font whether you actually see a difference. You are right. 2 different chars: If I copy "foo⁄bar" from dolphin to gvim and search for '/' only the '/' I entered in gvim directly is found. So dolphin and konsole are consistent. Yes it is a different char, however Konsole displays it as the normal '/' char here. Either way, it causes confusion since it's creating a directory named something I didn't want. Personally I feel it would be best to allow a name such as 'foo/bar' to create the 'foo' directory and then 'bar' within that. Konsole with Monospace 12: /: 0x2F (input dolphin) ⁄: 0xE2 0x81 0x84 (output dolphin/Konsole) Using Okteta you can see that the slopes of the UTF-8 slashes are different. KCharSelect > SOLIDUS '/' alias slash > FRACTION SLASH '⁄' alias solidus Have fun with confusion When the user creates a folder named "Holiday 2009/2010" he surely does not want "2010" to be a subdirectory. There could be a message stating that '/' characters are not allowed in names, and giving the user the option * to revert and enter a different name * to replace that char with the similar looking '⁄' or a non-similar '_' char. * to ask if he really wants to create a two-level directory hierarchy. IMHO silently replacing the character is not nice. Are there any other characters which are not valid in file/directory names? How do other applications handle that? *** Bug 358567 has been marked as a duplicate of this bug. *** At the moment there is an inconsistency in Dolphin. Attempting to create a folder called "aaa/bbb" will bring up info text:
Using slashes in folder names will create sub-folders, like so:
aaa/
bbb/
But attempting to create a new text file called "aaa/bbb.txt" will actually create "aaa⁄bbb.txt", silently replacing the slash character with a near lookalike.
I don't like the inconsistency between the two procedures, and I particularly don't like the silent replacement of the current Create New Text File procedure.
I suggest that the Create New Text File (etc.) procedure should work the same as Create New Folder, i.e. if the user enters a "/" in the new file name, it would show the info text and make a folder hierarchy if the user continues.
I suppose there *might* be some people who regularly create new files with "/" in the name and like the fact that it automatically changes to "⁄" rather than creating a hierarchy, but I doubt there's many. They can always manually type in "⁄" if necessary. (https://unicodeplus.com/U+2044).
|