On 2009-10-22, David Kastrup wrote:
> Patrick McCarty writes:
>
> > On 2009-10-18, David Kastrup wrote:
> >>
> >> GNU LilyPond 2.13.4
> >> Processing `bad.ly'
> >> Parsing...
> >> bad.ly:4:16: error: syntax error, unexpected MUSIC_IDENTIFIER
> >> MÃÃÃ A\342\231
> >> \257 Bâ
Patrick McCarty writes:
> On 2009-10-18, David Kastrup wrote:
>>
>> GNU LilyPond 2.13.4
>> Processing `bad.ly'
>> Parsing...
>> bad.ly:4:16: error: syntax error, unexpected MUSIC_IDENTIFIER
>> MÃÃÃ A\342\231
>> \257 Bâ \break
>> error: failed files: "bad.ly"
>>
>> Apparentl
Patrick McCarty writes:
> On 2009-10-18, David Kastrup wrote:
>>
>> GNU LilyPond 2.13.4
>> Processing `bad.ly'
>> Parsing...
>> bad.ly:4:16: error: syntax error, unexpected MUSIC_IDENTIFIER
>> MÃÃÃ A\342\231
>> \257 Bâ \break
>> error: failed files: "bad.ly"
>>
>> Apparentl
On 2009-10-18, David Kastrup wrote:
>
> GNU LilyPond 2.13.4
> Processing `bad.ly'
> Parsing...
> bad.ly:4:16: error: syntax error, unexpected MUSIC_IDENTIFIER
> MÃÃÃ A\342\231
> \257 Bâ \break
> error: failed files: "bad.ly"
>
> Apparently, the error column is being tracked b
2009/10/19 David Kastrup :
> -Eluze writes:
>> however, with version 2.13.3 (under windows vista) i get the following error
>> message:
>>
>> Analysieren...
>> bad.ly:4:23: Fehler: syntax error, unexpected MUSIC_IDENTIFIER
>> Määä A♯ B♭
>> \break
>>
>> which to me looks
-Eluze writes:
> David Kastrup wrote:
>>
>> -Eluze writes:
>>
>>> now, if i comment the \break (or omit it), the file compiles quite well -
>>> did i miss something?
>>
>> The subject line and the problem description?
>>
>>
>
> ahhh! i see now - i thought you were looking for a solution…
>
David Kastrup wrote:
>
> -Eluze writes:
>
>> now, if i comment the \break (or omit it), the file compiles quite well -
>> did i miss something?
>
> The subject line and the problem description?
>
>
ahhh! i see now - i thought you were looking for a solution…
however, with version 2.13.3 (
-Eluze writes:
> David Kastrup wrote:
>>
>>
>> The following input file:
>>
> … which is a .bin file and should be a .ly file - but downloaded its content
> looks like
>
> \markup{
> Määä A♯ B♭ \break
> }
>
> now, if i comment the \break (or omit it), the file compiles quite well -
> did
David Kastrup wrote:
>
>
> The following input file:
>
… which is a .bin file and should be a .ly file - but downloaded its content
looks like
\markup{
Määä A♯ B♭ \break
}
now, if i comment the \break (or omit it), the file compiles quite well -
did i miss something?
--
View this m
> I am not topposting
I reported this bug once already, but its distribution was haphazard
(never got to gmane) and nobody entered it into the bug tracker.
The following input file:
bin2jX8eDNUTu.bin
Description: Binary data
leads to the following error output (which hacks an utf-8 character
> I'm not top-posting
The following input file:
bad.ly
Description: Binary data
leads to the following error output (which hacks an utf-8 character into
pieces, replaced by printable octal sequences to make this transfer
better via mail):
GNU LilyPond 2.13.4
Processing `bad.ly'
Parsing...
ba
11 matches
Mail list logo
