EOL
Fri, 11 May 2018 12:32:25 +0200
Introducing extended line endings support in Notepad
For many years, Windows Notepad only supported text documents containing Windows End of Line (EOL) characters - Carriage Return (CR) & Line Feed (LF). This means that Notepad was unable to correctly display the contents of text files created in Unix, Linux and macOS.
For example, here’s a screenshot of Notepad trying to display the contents of a Linux .bashrc text file, which only contains Unix LF EOL characters:
As you can see, Notepad is incorrectly displaying the file’s contents, making the file look garbled. This has been a major annoyance for developers, IT Pros, administrators, and end users throughout the community.
Today, we’re excited to announce that we have fixed this issue!
This has been a major annoyance for developers, IT Pros, administrators
Sat, 12 May 2018 04:10:44 +0200 last edited: Sat, 12 May 2018 04:25:35 +0200
lol
and wondering if we might see something similar or related come from the Mac world.
I remember back in the 90s seeing text files from a Mac which had line endings that were \r (by itself)
(different to both windows \r\n and unix \n)
Its possible that they might have changed that around the turn of the millenium with OSX but I'm not sure.
(Their OS became bsd-based from OSX onwards so they could now be using unix style line endings but I'm not sure
if there could still be some software in that world doing something different with text files)
If text files using \r only as line endings still turn up anywhere they might still be a problem for notepad users.
and what about situations that might still need to know about the differences in the way those two chars could be used?
(eg everyones probably seen commandline utilites use \r to go back to the start of the current line to rewrite the display of a running status in a terminal context)
actually thinking maybe also the Amiga used \r by itself for line endings in text files (not sure though)
and the fact that any of this still turns up as a problem decades later shows what can happen when theres a lack of agreement over standards!
and wondering if we might see something similar or related come from the Mac world.
I remember back in the 90s seeing text files from a Mac which had line endings that were \r (by itself)
(different to both windows \r\n and unix \n)
Its possible that they might have changed that around the turn of the millenium with OSX but I'm not sure.
(Their OS became bsd-based from OSX onwards so they could now be using unix style line endings but I'm not sure
if there could still be some software in that world doing something different with text files)
If text files using \r only as line endings still turn up anywhere they might still be a problem for notepad users.
and what about situations that might still need to know about the differences in the way those two chars could be used?
(eg everyones probably seen commandline utilites use \r to go back to the start of the current line to rewrite the display of a running status in a terminal context)
actually thinking maybe also the Amiga used \r by itself for line endings in text files (not sure though)
and the fact that any of this still turns up as a problem decades later shows what can happen when theres a lack of agreement over standards!
This website is tracked using the Piwik analytics tool. If you do not want that your visits are logged this way you can set a cookie to prevent Piwik from tracking further visits of the site (opt-out).