handle text encodings besides ASCII and UTF-8

[jtmoon79]

Problem

Only ASCII encoded and UTF-8 encoded files can be processed. Log files with different encodings are processed but no text is found by s4.

For example, on a Windows 11 host, among .log files under C:\Windows, 28 of 128 files were not printed. A spot check of a few of those non-printed files showed they were UTF-16 encoded.

PS> Get-ChildItem -Filter '*.log' -File -Path "C:\Windows" -Recurse -ErrorAction SilentlyContinue `
   | Select-Object -ExpandProperty FullName `
   | s4.exe - --summary

Solution

Handle other text encodings.

Handling UTF-16 and UTF-32 would be satisfactory.

[jtmoon79]

File ./logs/Windows10Pro/SoftwareDistribution/ReportingEvents.log is UTF-16 encoded.
Many ad-hoc Windows log files are encoded something not ASCII or UTF-8.

[jtmoon79]

See design suggestion in #285 (comment)