`--rs`/`--ors` not being respected with `--csv`/`--ocsv`?

[manselmi]

Issue

Miller doesn't seem to be respecting the --rs or --ors options in conjunction with the --csv or --ocsv flags.

More specifically, if I provide Miller a CSV with \r\n record terminators, request CSV output format with either --csv or --ocsv and request the output have \r\n record terminators with either --rs '\r\n' or --ors '\r\n', then Miller should output a CSV with \r\n record terminators. On macOS the output has \n record terminators.

I feel like I'm missing something obvious.

Expected output

% printf '%s\r\n' data | mlr --csv --rs '\r\n' --hi --ho cat | od -v -A d -t cx1
0000000    d   a   t   a  \r  \n
           64  61  74  61  0d  0a
0000006

Actual output

% printf '%s\r\n' data | mlr --csv --rs '\r\n' --hi --ho cat | od -v -A d -t cx1
0000000    d   a   t   a  \n
           64  61  74  61  0a
0000005

Environment details

Miller version:

% mlr --version
mlr 6.13.0

macOS version:

% sw_vers
ProductName:            macOS
ProductVersion:         15.5
BuildVersion:           24F74

CPU architecture:

% uname -p
arm

[johnkerl]

@manselmi this is known.

I could have sworn I'd documented this in the Miller-6 notes:
https://miller.readthedocs.io/en/6.13.0/new-in-miller-6/

Regardless, neither you nor I have found the place in the docs where I discuss this, so it needs to be made more clear, including here:
https://miller.readthedocs.io/en/6.13.0/file-formats/#csvtsvasvusvetc

The underlying story is that in Miller <= 5 I had a hand-written CSV parser in C wherein I could do what I wanted. For the Go port (Miller 6) I switched to using the Go CSV library. It does allow parameterization of the Comma (Miller FS) but not parameterization of the line ending (Miller RS). It turns out I've come to regret, since then, having used the Go CSV library rather than porting my own C-language CSV parser from C to Go -- for other reasons, in addition to the one you're reporting here.

So two action items for me;

• Document the status quo more clearly -- a quick change
• Longer term -- it would be great to port my old C-language CSV parser to Go and jettison the Go CSV library

[manselmi]

@johnkerl Thanks, I appreciate your detailed and thoughtful reply (as always). Updating the docs would be great!