<[EMAIL PROTECTED]> wrote:
> >>Using Unix line feeds works with most tools on most platforms.
>
> Well... except under Windows ;-)
Dreamweaver can easily be configured to use Unix line feeds - you all
use Dreamweaver, right? :)
> By the way, the _expression_ "Windows line feed" is not quite appropriate:
> One should rather say "ASCII line feed". It has always been that in ASCII, there
> is one character to get the cursor (actually the "cariage" from the time of good old TTYs)
> at the begining of the line, and another one to move the paper one line up.
Actually that's not strictly true. ASCII line feed is control J which
moves the paper one line up but does NOT move the cursor to the
beginning of the line. That requires an ASCII carriage return -
control M. Windows "line feeds" are control J control M - which is why
when you edit a Windows file on Unix you see a control M at the end of
every line or you see double-spaced lines.
Unix files use just the ASCII line feed characters and the convention
is that it represents a "newline" (hence the \n escape character in
C-based languages - carriage return is \r). Mac native line endings
are just control M (carriage return) but Mac editing tools are all
happy with control J instead.
> CP/M and Windows, which were supporting 8 bits, then 16 bits machines,
> were ASCII based system at the begining.
Both \n (control J) and \r (control M) are ASCII characters and even
on multibyte systems the lower character values are still technically
ASCII.
--
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
