SUMMARY Dolphin abbreviates long filenames like "thisisalongfilname.txt" as "thisisalongfilna....txt" which itself would be a valid filename. Indeed one can create the file "thisisalongfilna....txt" and dolphin displays two files which seem to have the same name next to each other. I would suggest coloring the three dots in a different color than the rest of the filename or a similar indication what is part of the filename and what is a replacement for a too long part of the filename. STEPS TO REPRODUCE 1. Create a file with a long filename 2. List the file in dolphin OBSERVED RESULT The filename is abbreviated to a string that could also be a valid filename. EXPECTED RESULT There should be some indication that it is abbreviated.
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.