Blocked by #16 (which implements the --encoding command line argument.
You should also probably wait for #17 (so you can better see the resulting output).
If #16 is done, LIMA support utf-8 and utf-16. That's it. It's common that utf-8 will catch a string that won't be caught by utf-16. However, there are edge cases in which utf-16 is necessary (without the "remove null" strategy 4 implemented in #16 ): see PE files.
Implement support for an encoding of all. If all is received, then loop through all supported encodings for all files. Leave utf-8 as the default encoding.
Blocked by #16 (which implements the
--encodingcommand line argument. You should also probably wait for #17 (so you can better see the resulting output).If #16 is done, LIMA support
utf-8andutf-16. That's it. It's common thatutf-8will catch a string that won't be caught byutf-16. However, there are edge cases in whichutf-16is necessary (without the "remove null" strategy 4 implemented in #16 ): see PE files.Implement support for an encoding of
all. Ifallis received, then loop through all supported encodings for all files. Leaveutf-8as the default encoding.