RE: Mac OSX and Text Editors

[Stephan Moss]

So, Unix endings & utf-8 encoding is best?  That's what the built in
editor spits out? 

-----Original Message-----
From: Mats Bengtsson [mailto:address@hidden 
Sent: Friday, August 12, 2005 6:52 AM
To: Stephan Moss
Cc: address@hidden
Subject: Re: Mac OSX and Text Editors



Stephan Moss wrote:
> When Lilypond reads the .ly file, what is it looking for in terms of 
> format (line endings, etc)?

Line endings are treated like any other white space (spaces and tabs),
so you can write your input on a single line if you like.


> I took a file that worked from the built in editor to Text Wrangler 
> and then back again and it generated lots of errors (Unexpected #end, 
> if I remember right).  I wound up re-entering it in the built in 
> editor.  I'm assuming that Text Wrangler (from the people who make 
> Bbedit) mangled the file in such a way that the parser didn't like it
anymore.

My guess is that it didn't output a plain text file but added some extra
control characters somewhere. An alternative is that it didn't use UNIX
style line endings but the old-style Mac line endings or used the wrong
character encoding. I don't know anything about this particular editor,
but usually it's possible to specify what format the file is saved in.

   /Mats