Windows Notepad -- Text Formatting [Archive] - ForumsHQ

[syntax53]

Anyone know what it is that makes notepad not process linefeed control characters (the usually invisible characters in a document that signal a new line)? some documents notepad opens are fine, but others i have to open with wordpad. .nfo files frequently seem to have this problem. i've tried differnt font settings, usually leaving it on terminal-9. anyone?

[syntax53]

nice, multiple pics in one post ... go vb3 :)

[Reckless]

Anyone know what it is that makes notepad not process linefeed control characters (the usually invisible characters in a document that signal a new line)? some documents notepad opens are fine, but others i have to open with wordpad. .nfo files frequently seem to have this problem. i've tried differnt font settings, usually leaving it on terminal-9. anyone?

I think it has something to do with the fact that you can't use ascii in notepad. It's more of a piece of paper than a word processor.

[Aragon]

it's usually a problem with transferring a text file as binary... how did you dl the file?



That's the conclusion I came up with a few years ago ... shrug.

[syntax53]

it's usually a problem with transferring a text file as binary... how did you dl the file?



That's the conclusion I came up with a few years ago ... shrug.



hmm, i d/l'd it last from an email off a webmail app (like hotmail).

[Aragon]

shrug u can use wordpad, save as text file again and open in notepad and it will look fine.. that's the only way I know of to "fix" it.

[Locke Cole]

Anyone know what it is that makes notepad not process linefeed control characters (the usually invisible characters in a document that signal a new line)? some documents notepad opens are fine, but others i have to open with wordpad. .nfo files frequently seem to have this problem. i've tried differnt font settings, usually leaving it on terminal-9. anyone?

It's the difference between Linux/Unix line feeds and MS-DOS style line feeds. In *nix, a single LF is the end of line (EOL), but in DOS/Windows, CR + LF are required to make EOL.



I usually "fix" this by opening the file via a CMD prompt and using EDIT-- EDIT is smart enough to recognize the *nix-style EOL terminators and correct for them, just press space then backspace (so you've effectively changed the file as far as EDIT is concerned), then Save the file and you'll be able to open it in Notepad as normal.