Re: Google-to-Allura port adds brackets around rests

[Trevor Daniels]

- Original Message - 
From: "Trevor Daniels" 
To: "Trevor Daniels" ; "Lily-Devel List" 
; "Simon Albrecht" 
Sent: Tuesday, September 08, 2015 11:04 PM
Subject: Re: Google-to-Allura port adds brackets around rests


> 
> Trevor Daniels wrote Tuesday, September 08, 2015 12:37 PM
>> 
>> Simon Albrecht wrote Monday, September 07, 2015 11:28 PM
>>>
>>>> Am 08.09.2015 um 00:23 schrieb Trevor Daniels:
>>>> Simon Albrecht wrote Monday, September 07, 2015 7:16 PM
>>>>> Am 07.09.2015 um 20:09 schrieb Dan Eble:
>>>>>> Compare
>>>>>>
>>>>>> https://code.google.com/p/lilypond/issues/detail?id=1677
>>>>>> https://sourceforge.net/p/testlilyissues/issues/1677/ 
>>>>>> <https://sourceforge.net/p/testlilyissues/issues/1677/>
>>>>>>
>>>>>> The latter has square brackets around rests, e.g. “[r4]” instead of “r4”.
>>>>>
> 
> Further to this, there are over 300 issues containing rests in square
> brackets, of which 77 are still active (i.e. they have a Status of Accepted
> Started or New.)  So we really ought to fix those if it is at all possible.

With help from Simon the square brackets around rests in those 77 issues
have now all been fixed by hand.  I'm afraid the remainder, none of which are
still active, will have to remain wrong, unless someone else wants to
practice editing Allura issues.

Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Google-to-Allura port adds brackets around rests

[Trevor Daniels]

Werner LEMBERG wrote Wednesday, September 09, 2015 5:37 AM
> 
>> Further to this, there are over 300 issues containing rests in
>> square brackets, of which 77 are still active (i.e. they have a
>> Status of Accepted Started or New.)  So we really ought to fix those
>> if it is at all possible.
> 
> Has someone written to the Allura team how to handle this?  Ideally,
> there should be a configuration option to disable this feature, which
> we definitely neither want nor need.

Well, we won't be not wanting or not needing it again, as
we shall not be doing any more imports from GC to Allura.

This is caused by an unfortunate coincidence between
LilyPond syntax and GoogleCode syntax.  It appears to be
a well-known problem with GC, starred 73 times:

https://code.google.com/p/support/issues/detail?id=996

It seems that the Allura import attempts to import these
links (the square brackets identify the enclosed text at
the text to display), but there is no follow-up url.  I
don't know if this is because GC doesn't supply one or
because it is suppressed as being broken.  I suspect the
former.  We clearly don't want to suppress the processing
of links in general, as attachments rely on them.

Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Google-to-Allura port adds brackets around rests

[Werner LEMBERG]

> Further to this, there are over 300 issues containing rests in
> square brackets, of which 77 are still active (i.e. they have a
> Status of Accepted Started or New.)  So we really ought to fix those
> if it is at all possible.

Has someone written to the Allura team how to handle this?  Ideally,
there should be a configuration option to disable this feature, which
we definitely neither want nor need.


Werner

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Google-to-Allura port adds brackets around rests

[Trevor Daniels]

Trevor Daniels wrote Tuesday, September 08, 2015 12:37 PM
> 
> Simon Albrecht wrote Monday, September 07, 2015 11:28 PM
>>
>>> Am 08.09.2015 um 00:23 schrieb Trevor Daniels:
>>> Simon Albrecht wrote Monday, September 07, 2015 7:16 PM
 Am 07.09.2015 um 20:09 schrieb Dan Eble:
> Compare
>
> https://code.google.com/p/lilypond/issues/detail?id=1677
> https://sourceforge.net/p/testlilyissues/issues/1677/ 
> 
>
> The latter has square brackets around rests, e.g. “[r4]” instead of “r4”.

 Oh shoot! That’s not a problem with the port, but it has been a problem
 with Google adding a link to
 , which in the
 source for Allura markdown reads
 "[r4]".
 But I imagine it shouldn’t be too complicated to make a script to
 convert [r4] into r4 and similar with different durations. One
 complication is that R1 has been converted into [r1]…
>>>
>>> I don't understand what the url links in GC were supposed to do, but
>>> whatever it was they are broken now.  I've never seen links attached
>>> to rests before, so I think this is a one-off, probably caused by pasting
>>> text from elsewhere.  In which case it's probably easiest to simply
>>> edit this issue manually.
>>
>> Unfortunately no: Every single instance in the Google code DB of "r" or 
>> "R" followed by a number is equipped with such a link – which has always 
>> been taken as an oddity and ignored. That’s why I talked about scripts… 
>> – though I’m not quite sure how and when such a script might be applied; 
>> probably upon migrating to the Savannah server.
> 
> Ah, I see.  I guess I'd not noticed this before.
> 
> It would be relatively easy to remove the square brackets by editing the
> JSON file, but restoring the R's which have been changed to r's is harder.
> It would mean comparing the text with the original GC issue.  Maybe
> doable, but free text and Lily code is not trivial to parse.  In the JSON
> file downloaded from GC the text that appears as urls is not in any way
> annotated  -  they are just plain r's and R's.  So there is nothing easy to 
> search for.

Further to this, there are over 300 issues containing rests in square
brackets, of which 77 are still active (i.e. they have a Status of Accepted
Started or New.)  So we really ought to fix those if it is at all possible.

Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Google-to-Allura port adds brackets around rests

[Trevor Daniels]

Simon Albrecht wrote Monday, September 07, 2015 11:28 PM
>
>> Am 08.09.2015 um 00:23 schrieb Trevor Daniels:
>> Simon Albrecht wrote Monday, September 07, 2015 7:16 PM
>>> Am 07.09.2015 um 20:09 schrieb Dan Eble:
 Compare

 https://code.google.com/p/lilypond/issues/detail?id=1677
 https://sourceforge.net/p/testlilyissues/issues/1677/ 
 

 The latter has square brackets around rests, e.g. “[r4]” instead of “r4”.
>>>
>>> Oh shoot! That’s not a problem with the port, but it has been a problem
>>> with Google adding a link to
>>> , which in the
>>> source for Allura markdown reads
>>> "[r4]".
>>> But I imagine it shouldn’t be too complicated to make a script to
>>> convert [r4] into r4 and similar with different durations. One
>>> complication is that R1 has been converted into [r1]…
>>
>> I don't understand what the url links in GC were supposed to do, but
>> whatever it was they are broken now.  I've never seen links attached
>> to rests before, so I think this is a one-off, probably caused by pasting
>> text from elsewhere.  In which case it's probably easiest to simply
>> edit this issue manually.
>
> Unfortunately no: Every single instance in the Google code DB of "r" or 
> "R" followed by a number is equipped with such a link – which has always 
> been taken as an oddity and ignored. That’s why I talked about scripts… 
> – though I’m not quite sure how and when such a script might be applied; 
> probably upon migrating to the Savannah server.

Ah, I see.  I guess I'd not noticed this before.

It would be relatively easy to remove the square brackets by editing the
JSON file, but restoring the R's which have been changed to r's is harder.
It would mean comparing the text with the original GC issue.  Maybe
doable, but free text and Lily code is not trivial to parse.  In the JSON
file downloaded from GC the text that appears as urls is not in any way
annotated  -  they are just plain r's and R's.  So there is nothing easy to 
search for.

Trevor




___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Google-to-Allura port adds brackets around rests

[David Kastrup]

"Trevor Daniels"  writes:

> Simon Albrecht wrote Monday, September 07, 2015 7:16 PM
>>
>
>> Am 07.09.2015 um 20:09 schrieb Dan Eble:
>>> Compare
>>>
>>> https://code.google.com/p/lilypond/issues/detail?id=1677
>>> https://sourceforge.net/p/testlilyissues/issues/1677/
>>> 
>>>
>>> The latter has square brackets around rests, e.g. “[r4]” instead of “r4”.
>> 
>> Oh shoot! That’s not a problem with the port, but it has been a problem 
>> with Google adding a link to 
>> , which in the 
>> source for Allura markdown reads 
>> "[r4]".
>> But I imagine it shouldn’t be too complicated to make a script to 
>> convert [r4] into r4 and similar with different durations. One 
>> complication is that R1 has been converted into [r1]…
>
> I don't understand what the url links in GC were supposed to do, but
> whatever it was they are broken now.  I've never seen links attached
> to rests before, so I think this is a one-off, probably caused by pasting
> text from elsewhere.  In which case it's probably easiest to simply
> edit this issue manually.

I guess they link to (non-existent) SVN revisions, just like a full SHA
links to a (non-existent) Git revision.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Google-to-Allura port adds brackets around rests

[Federico Bruni]

Il giorno mar 8 set 2015 alle 0:23, Trevor Daniels 
 ha scritto:

I don't understand what the url links in GC were supposed to do, but
whatever it was they are broken now.  I've never seen links attached
to rests before, so I think this is a one-off, probably caused by 
pasting

text from elsewhere.  In which case it's probably easiest to simply
edit this issue manually.


They are automatic links to (svn|git) revisions.


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Google-to-Allura port adds brackets around rests

[Simon Albrecht]

Am 08.09.2015 um 00:23 schrieb Trevor Daniels:

Simon Albrecht wrote Monday, September 07, 2015 7:16 PM

Am 07.09.2015 um 20:09 schrieb Dan Eble:

Compare

https://code.google.com/p/lilypond/issues/detail?id=1677
https://sourceforge.net/p/testlilyissues/issues/1677/ 


The latter has square brackets around rests, e.g. “[r4]” instead of “r4”.

Oh shoot! That’s not a problem with the port, but it has been a problem
with Google adding a link to
, which in the
source for Allura markdown reads
"[r4]".
But I imagine it shouldn’t be too complicated to make a script to
convert [r4] into r4 and similar with different durations. One
complication is that R1 has been converted into [r1]…

I don't understand what the url links in GC were supposed to do, but
whatever it was they are broken now.  I've never seen links attached
to rests before, so I think this is a one-off, probably caused by pasting
text from elsewhere.  In which case it's probably easiest to simply
edit this issue manually.


Unfortunately no: Every single instance in the Google code DB of "r" or 
"R" followed by a number is equipped with such a link – which has always 
been taken as an oddity and ignored. That’s why I talked about scripts… 
– though I’m not quite sure how and when such a script might be applied; 
probably upon migrating to the Savannah server.


Yours, Simon

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Google-to-Allura port adds brackets around rests

[Trevor Daniels]

Simon Albrecht wrote Monday, September 07, 2015 7:16 PM
>

> Am 07.09.2015 um 20:09 schrieb Dan Eble:
>> Compare
>>
>> https://code.google.com/p/lilypond/issues/detail?id=1677
>> https://sourceforge.net/p/testlilyissues/issues/1677/ 
>> 
>>
>> The latter has square brackets around rests, e.g. “[r4]” instead of “r4”.
> 
> Oh shoot! That’s not a problem with the port, but it has been a problem 
> with Google adding a link to 
> , which in the 
> source for Allura markdown reads 
> "[r4]".
> But I imagine it shouldn’t be too complicated to make a script to 
> convert [r4] into r4 and similar with different durations. One 
> complication is that R1 has been converted into [r1]…

I don't understand what the url links in GC were supposed to do, but
whatever it was they are broken now.  I've never seen links attached
to rests before, so I think this is a one-off, probably caused by pasting
text from elsewhere.  In which case it's probably easiest to simply
edit this issue manually.

Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Google-to-Allura port adds brackets around rests

[Simon Albrecht]

Am 07.09.2015 um 20:09 schrieb Dan Eble:

Compare

https://code.google.com/p/lilypond/issues/detail?id=1677
https://sourceforge.net/p/testlilyissues/issues/1677/ 


The latter has square brackets around rests, e.g. “[r4]” instead of “r4”.


Oh shoot! That’s not a problem with the port, but it has been a problem 
with Google adding a link to 
, which in the 
source for Allura markdown reads 
"[r4]".
But I imagine it shouldn’t be too complicated to make a script to 
convert [r4] into r4 and similar with different durations. One 
complication is that R1 has been converted into [r1]…


Yours, Simon

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel