[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to Debug Parse Errors

From: Richard Grubb
Subject: Re: How to Debug Parse Errors
Date: Tue, 3 Dec 2002 21:25:46 -0600

My problem has been resolved. The line endings were messed up. On my machine, I don't have dos2unix, but I do have dosunix which the man page said should do the same translation. Except in this case, it removed all line endings (plus some characters in column 1 and most of the ending '}'s ). I had to reinsert all of the line endings and missing characters with Nedit.

Then ly2dvi processed the file properly. LaTex barffed on the <8A> character, but I just replaced it with an 'a' and everything processed properly.

I guess I'll have to unzip and untar the source code to get good copies of example files instead of saving them from the web site through my browser.

On Tuesday, December 3, 2002, at 04:56 PM, Simon Bailey wrote:

On Tue, 2002-12-03 at 23:23, Richard Grubb wrote:
Running "less" shows the only "non-printable" characters
are a bunch of ^M (Which are end-of-line characters; Unix or Mac, I
would have to look up which it is) and one <8A> in the Mutopia header
for the title (an "a" with some accent mark in Standchen).

^M are end of line characters in dos. <8A> = รค, this one shouldnt be a
problem for lilypond. i don't know about the ^M's though. you might try
running the file through dos2unix ('man dos2unix' for more info), then
try ly2dvi on it.

Don't be irreplaceable, if you can't be replaced, you can't be promoted.

Lilypond-user mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]