Open Shooter3k opened 2 years ago
Workaround: normalize the record separator beforehand.
Spitballing ... one way to expand functionality to hande this use case this might be to allow the user to specify which terminator(s) to use on input (and maybe also on output?) For the wordlist management use cases, being able to "normalize" record separators would be a pretty powerful feature.
I haven't looked at the source yet, but it looks like rling currently treats 0x0d0a and 0x0a as alternate separators, and will deduplicate two strings terminated with each into a single output string (which is good!)
I had this discussion with waffle, it seems macs no longer use 0xD as delimiter well not since OS 9. It was designed to purposely see 0xD as in line and not a delimiter
If you take a file with a line ending of just as 0x0d as the field separator (class Mac), rling sees this file as a single line and does not remove duplicates/process the file as it should.