It will always use "," as output delimiter and I believe the correct behavior would be to either use the original delimiter or implement the -t output delimiter option.
This behavior can lead to unexpected/unwanted conversions:
Say, the original delimiter is ";" and the comma appears in fields as decimal seperator unquoted (such as in German formatting for floating point numbers), then xsv will quote the floating point numbers (as they contain a comma), thus force-converting the value to a string.
However, if I want to retain the floating point numbers and have a non-comma field seperator, then there appears to be no way to use fixlengths.
It will always use "," as output delimiter and I believe the correct behavior would be to either use the original delimiter or implement the -t output delimiter option.
This behavior can lead to unexpected/unwanted conversions:
Say, the original delimiter is ";" and the comma appears in fields as decimal seperator unquoted (such as in German formatting for floating point numbers), then xsv will quote the floating point numbers (as they contain a comma), thus force-converting the value to a string.
However, if I want to retain the floating point numbers and have a non-comma field seperator, then there appears to be no way to use fixlengths.