Executing test.sh on MacOS shows several test fail.
This ist most likely in all cases the situation that MacOS uses UTF16BE while Linux systems I used for testing use UTF16LE as default UTF16 encoding.
Is behavior is totally fine because there is a byte order mark (BOM) included with each text.
See also #29
Test results should be valid for both cases.
A solution will be to compare the outcoming file of a test run with two check sums. One expected for UTF16LE encoded data and one for UTF16BE encoded data. Simular as is has been done in the encoding test application (See #29 )
Executing
test.shon MacOS shows several test fail. This ist most likely in all cases the situation that MacOS uses UTF16BE while Linux systems I used for testing use UTF16LE as default UTF16 encoding. Is behavior is totally fine because there is a byte order mark (BOM) included with each text. See also #29Test results should be valid for both cases. A solution will be to compare the outcoming file of a test run with two check sums. One expected for UTF16LE encoded data and one for UTF16BE encoded data. Simular as is has been done in the encoding test application (See #29 )