I just tried viewing a text file with no CRs on Windows. It
worked with "type", but "more" couldn't handle it: it just
output a question mark for each line. Cygwin tools mask
that behavior.
So, this is sort of endemic of how we're cheating a bit.
Specifically, nmh uses Unix line conventions everywhere. There are two places
where it knows how to convert to canonical format: when sending via SMTP,
and retrieving via POP. This hasn't been an issue in the past, because
a) we've never needed the canonical message format ever, and b) at worst
text will be encoded using q-p and all of the right stuff will happen.
Unfortuntely (or hopefully, depending on your perspective), these things
are no longer guaranteed to be true. I am just thinking about the future.
Actually, here's a good test; the mailing list should convert this to
base64 if I include a character with the high bit set, so I'll do that
here and see what line endings are in the base64. 🗿
--Ken
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers