EOL conventions (was: Re: UCD in XML or in CSV? (is: UCD in YAML))

Eli Zaretskii via Unicode unicode at unicode.org
Sat Sep 8 01:47:23 CDT 2018

> Date: Sat, 8 Sep 2018 02:29:12 +0200 (CEST)
> From: Marcel Schneider <charupdate at orange.fr>
> Cc: RebeccaBettencourt <beckiergb at gmail.com>, verdy_p at wanadoo.fr, 
> 	d3ck0r at gmail.com, doug at ewellic.org, unicode at unicode.org
> > > And it only took them 33 years. :) 
> > 
> > That's OK, because Unix tools cannot handle Windows end-of-line format
> > to this very day. About the only one I know of is Emacs (which
> > handles all 3 known EOL formats independently of the platform on which
> > it runs, since 20 years ago).
> What are you referring to when you say “Unix tools”?

Sed and Grep don't consider CRLF as end of line, so regexps with $
fail to work as intended; the shell and/or the kernel don't recognize
the shebang sequence if it ends in CRLF, system editors display those
pesky "^M" at the end of each line, etc.  And if you have bad luck of
using a Mac-style file, where a single CR ends a line, all bets are

> Another text editor—the built-in one of many Linux distributions—Gedit allows 
> to choose from “Unix/Linux”, “Mac OS Classic”, and “Windows”, in the Save dialog.

Gedit is not a valid example when you compare it with Notepad.  Please
compare with editors which come with the OS out of the box: ed, ex,
vi, etc.  Because Gedit and Emacs are also available on Windows, so
they make the point moot.

More information about the Unicode mailing list