Summary: | Dolphin abbreviates filenames in a way that doesn't make clear it is an abbreviation | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Alex <allo> |
Component: | view-engine: icons mode | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | CC: | kfm-devel, nate |
Priority: | NOR | ||
Version First Reported In: | 22.04.3 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Other | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Alex
2022-08-22 15:00:31 UTC
This is the way all strings across the OS are elided, and it's how Windows and macOS elide strings too. I don't think this is really a source of confusion for anyone, and if it is, it's something they can easily get used to. Isn't windows using … (1 unicode character) instead of ...? Yes, which is a valid character in a filename. It's also visually indistinguishable to users with many fonts. That's why I suggested color. That would not be possible with a filename. You may also underline it, or use other indications. I would need to test how Windows does it in detail. The thing I noticed before thinking about the consequences is that file....txt looks pretty weird and I am rather sure that it doesn't look that weird on Windows. I need to test how it looks there and why it looks better, though. |