Batch has virtually no unicode support.
I'd phrase it more like "batch has half-baked and very finicky unicode support"
- unicode input in the interactive console, for example pasting unicode text at the prompt;
- unicode console output, both at the default prompt, and "cmd /u";
- environment and loop path variables are unicode;
- internal commands (dir, copy etc) take unicode command lines.
Does not support:
- batch files encoded as unicode text;
- unicode input other than the interactive console, for example redirection from file, or "for /f" reading of a unicode encoded text file;
- piping unicode is inconsistent, for example "more" doesn't take unicode input even in a "cmd /u" console.
I never found a way to create unicode file names
That's correct in the sense of not being able to hardcode unicode names in a batch file. And I know that's what you meant, but just to nitpick anyway
it's still possible to create unicode filenames if the name itself comes from elsewhere, for example from an environment variable, or the name of a file or path that already exists on disk.
P.S. The title of this thread is slightly misleading. Issue here was not about unicode characters at large, but rather about "special" characters missing from certain codepages. My code "happens" to work with "▒", but would not work with, for example, CJK (Asian) characters.