Re: misplaced comment produces wrong HTML output. (issue 60880044)

[Francisco Vila]

2014-02-09 12:23 GMT+01:00 Phil Holmes <address@hidden>:
> ----- Original Message ----- From: "Francisco Vila" <address@hidden>
> To: "Phil Holmes" <address@hidden>
> Cc: "Graham Percival" <address@hidden>; "LilyPond-Devel list"
> <address@hidden>; <address@hidden>
> Sent: Sunday, February 09, 2014 10:45 AM
> Subject: Re: misplaced comment produces wrong HTML output. (issue 60880044)
>
>
>
>> 2014-02-09 11:23 GMT+01:00 Phil Holmes <address@hidden>:
>>>
>>> ----- Original Message ----- From: <address@hidden>
>>> To: <address@hidden>
>>> Cc: <address@hidden>; <address@hidden>
>>> Sent: Sunday, February 09, 2014 10:08 AM
>>> Subject: Doc: misplaced comment produces wrong HTML output. (issue
>>> 60880044)
>>>
>>>
>>>> Was this fix produced automatically by running import-lsr.py (or
>>>> whatever the script is called), or was it done manually?  Remember that
>>>> this file begins with
>>>> % DO NOT EDIT this file manually
>>>>
>>>> If there's a bug in the import script, then this bug will just re-appear
>>>> the next time somebody imports LSR.
>>>>
>>>> https://codereview.appspot.com/60880044/
>>>
>>>
>>>
>>>
>>> It looks like it's actually a spurious comment in
>>> Documentation/snippets/new/creating-a-delayed-turn.ly
>>
>>
>> What's strange is that creating-a-delayed-turn.ly in
>>
>>  Documentation/snippets/new
>>
>> does NOT have the spurious comment.
>>
>> Only creating-a-delayed-turn.ly in
>>
>>  Documentation/snippets/
>>
>> does.
>
>
> It does have it, but in a different place, and I presume this confuses
> makelsr:

Terminology issue here. The required comment is not the spurious comment.

-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com