Y
Hacker News
new
|
ask
|
show
|
jobs
by
Ekaros
621 days 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.
5 comments
bear8642
621 days ago
> Decide upon on new UTF-8 code point.
Unicode have already done so - (NEL)
https://www.compart.com/en/unicode/U+0085
link
phkahler
621 days ago
So break
everything
.
link
nycdotnet
621 days ago
Which would need to be encoded in at least two bytes at which point, why not just use CRLF?
link
kps
621 days ago
You mean U+2028 LINE SEPARATOR?
link
Ekaros
621 days 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.
link
bear8642
621 days ago
Oh, yet another option - first thought was U+0085 NEXT LINE as above
link
whizzter
621 days ago
https://xkcd.com/927/
link
Unicode have already done so - (NEL) https://www.compart.com/en/unicode/U+0085