Hacker News new | past | comments | ask | show | jobs | submit login

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.



> Decide upon on new UTF-8 code point.

Unicode have already done so - (NEL) https://www.compart.com/en/unicode/U+0085


So break everything.


Which would need to be encoded in at least two bytes at which point, why not just use CRLF?


You mean U+2028 LINE SEPARATOR?


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.


Oh, yet another option - first thought was U+0085 NEXT LINE as above


https://xkcd.com/927/




Consider applying for YC's Summer 2025 batch! Applications are open till May 13

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: