How can you be fooled by the U+202E trick? (2013)

Re:How can you be fooled by the U+202E trick? (2013) by dgrunwald on Wednesday February 16, 2022 @04:46AM (#30358015)

We don't need to store the metadata differently. The on-disk format is still unambiguous: the part after the last dot is the extension. It's only the graphical display that is ambiguous, because the last dot is not necessarily the rightmost dot. This is easily solved with a UI change, e.g. move the file extension from the "file name" column to a separately rendered "file extension" column.

One could even translate the file extension into something more user-friendly (e.g. .exe -> Application), making it a "file type" column. Which is of course what Windows Explorer has been doing for decades already. Of course, that results in everyone turning the classic file extension back on...

[ Parent | on HN ]

Re:How can you be fooled by the U+202E trick? (2013) by samwillis on Wednesday February 16, 2022 @06:35AM (#30358721)

I think one of the troubles here is the difference between a GUI and a command line type app. Very true on a GUI you can hide the extension and display file type in a column, which is what Windows and MacOS both increasingly do. However on the command line its still fundamentally part of the filename, to fix that is a larger job and my suggestion is that it should not be part of he filename, but metadata on the file/filesystem.

The other problem with hiding the extension is that you then have "file name" collisions, two files will appear to have the same name but only differentiate by the "type". I think that's wrong.

[ Parent | on HN ]