Kaiser

There's also troubles when pointing Unicode-containing filenames in CLI, I found no workaround here

Add BOM support

Sure thing! I'll open a request on BOM. Actually, we got different situations there. The issue with plain CMD is purely a matter of presentation (I suppose it has to do with font), but one can just copy/paste any Unicode output provided (using tools like RHash, eg). But in case of Jacksum, in CLI output it actually replaces unavailable chars with U+003f (question marks). I suppose there's a room for improvement.

Thanks! Workaround is very useful (maybe it would be great for incorporating it to FAQ). But CLI output (not file) continues to replace chars with '?'. Any way to fix that? I already know what BOM is. Some editors may be adding BOM sometimes, but it confuses the parser, unabling it to use hashlist file correctly. Read-only BOM support would be great, isn't it?

Thanks! Workaround is very useful (maybe it would be great for incorporating it to FAQ). But CLI output (not file) continues to replace chars with '?'. Any way to fix that? I already know what BOM is. Some editors may be adding BOM sometimes, but it confuses the parses, unabling it to use hashlist file correctly. Read-only BOM support would be great, isn't it?

Thanks! Workaround is very useful (maybe it would be great for incorporating it to FAQ). But CLI output (not file) continues to replace chars with '?'. Any way to fix that?

Show progress option

UTF-8 is necessary