Show HN: Stamp turns a folder into a plain text file and a file into a folder

Re:Show HN: Stamp turns a folder into a plain text file and ... by hamburglar on Sunday February 07, 2021 @05:23PM (#26058798)

There are file names that can’t be expressed as UTF8? I’m intrigued.

[ Parent | on HN ]

Re:Show HN: Stamp turns a folder into a plain text file and ... by brianush1 on Sunday February 07, 2021 @06:00PM (#26059036)

Posix file names can be any sequence of bytes other than '/' and 0

[ Parent | on HN ]

Re:Show HN: Stamp turns a folder into a plain text file and ... by hamburglar on Sunday February 07, 2021 @06:23PM (#26059181)

I guess that's true. I suspect the support for non-UTF8 names in modern tooling is very, very spotty, given how many config files and file formats that refer to other files use UTF-8 themselves. E.g. can you refer to one of these names in an nginx config? (just an example; I have no idea if its config is UTF-8 or not)

[ Parent | on HN ]

Re:Show HN: Stamp turns a folder into a plain text file and ... by benibela on Sunday February 07, 2021 @06:55PM (#26059357)

I have a collection of non-utf8 and other problematic files to test such tools:

https://github.com/benibela/nasty-files

You probably cannot clone the repo on Windows. It works well on Linux. But in KDE you could not delete it after checkout

[ Parent | on HN ]

Re:Show HN: Stamp turns a folder into a plain text file and ... by tyingq on Sunday February 07, 2021 @10:06PM (#26060319)

Also, filenames with one or more newlines bork a lot of Linux software.

[ Parent | on HN ]

Re:Show HN: Stamp turns a folder into a plain text file and ... by masklinn on Monday February 08, 2021 @03:10AM (#26061931)

And Windows file names can include unpaired surrogates, which are not allowed in UTF8 (that’s why WTF8 exists).

[ Parent | on HN ]