The problem is that the output of the command may not be in terminal encoding either, it has to be selectable manually, --encoding=xxx maybe, but that is of course more effort for the "somebody" implementing this capability.

Or else we could just document that the input has to be in UTF-8 and the user must use iconv or similar tools to filter the pipe and do the conversion.

—
Reply to this email directly or view it on GitHub.