>> add information about windows, utf-16 & copyright to man page

This commit is contained in:
Thomas Lindop 2025-05-24 10:55:25 +01:00
parent 2a536d4a3f
commit e8f7c9b411

21
man.md
View file

@ -36,7 +36,7 @@ Show a small help message.
## Edge Cases & Other Tidbits
## What doesn't FAT allow?
### What doesn't FAT allow?
Mainly `*<>\|/:?'`
### What about whitespace?
@ -47,15 +47,26 @@ If a sequence of invalid characters surrounded by spaces is in one of the
file names, and the `remove` strategy is being used, then you will be left
with multiple whitespace characters in a row. For example,
```
Really questionable ?? filename
"Really questionable ?? filename"
```
will become
```
Really questionable filename
"Really questionable filename"
```
with a double space before `filename`.
with a double space before "filename".
### What about invalid UTF-8/UTF-16?
### What about invalid UTF-8?
This is removed and replaced with "\_INVALID_". This replacement is done
before anything else.
### What about UTF-16/Windows?
Owl has only been tested so far on Linux with a UTF-8 locale. UTF-16 support
on Windows is likely possible, but has not been tested. Please contact me if
you would like Windows support (see below).
## AUTHORS & COPYRIGHT
Written by user SixteenThousand of github.com (email
thomsixteenthousand@gmail.com) and licensed under the GNU General Public
License version 3 (GPL v3). See <https://www.gnu.org/licenses/> for more
information.