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