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/ 
> > > <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
> > <https://code.google.com/p/lilypond/source/detail?r=4>, which in the
> > source for Allura markdown reads
> > "[r4]<https://code.google.com/p/lilypond/source/detail?r=4>".
> > 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