3 ms·

I think I can offer most reasonable compromise here. Decide upon on new UTF-8 code point. Have the use mandated and ignore and ban all end-points that do not us

by Ekaros 2y ago

I think I can offer most reasonable compromise here. Decide upon on new UTF-8 code point. Have the use mandated and ignore and ban all end-points that do not use this code-point instead of CRLF or just LF alone.

phkahler 2y ago
So break everything.
whizzter 2y ago
https://xkcd.com/927/ https://xkcd.com/927/
kps 2y ago
You mean U+2028 LINE SEPARATOR?
- Ekaros 2y ago
  Perfect. So now we just need to start filing bug reports to any tool that does not support it instead of CRLF or LF alone.
  - deleted 2y ago
    [deleted]
- bear8642 2y ago
  Oh, yet another option - first thought was U+0085 NEXT LINE as above
bear8642 2y ago
> Decide upon on new UTF-8 code point. Unicode have already done so - (NEL) https://www.compart.com/en/unicode/U+0085 https://www.compart.com/en/unicode/U+0085
deleted 2y ago
[deleted]
nycdotnet 2y ago
Which would need to be encoded in at least two bytes at which point, why not just use CRLF?