Re: LSR inconsistencies

2019-10-13 Thread Wols Lists
On 11/10/19 10:13, Thomas Morley wrote: > According to wikipedia "etc", i.e. without full stop, is valid as > well. Full stop removed. Valid in common usage, maybe. If you're being a grammar pedant, it is an abbreviation of "et cetera", so the full stop is required to indicate the abbreviation

Re: LSR inconsistencies

2019-10-12 Thread Sebastiano Vigna
> On 12 Oct 2019, at 12:08, Werner LEMBERG wrote: > >> Template: integrating \startTextSpan and \stopTextSpan in a customized >> TextSpanner >> >> then click "Enable filter". Nothing returns. > > Indeed. Here, the *second* backslash in the title prevents results in > the filter. This

Re: LSR inconsistencies

2019-10-12 Thread Thomas Morley
Am Sa., 12. Okt. 2019 um 12:08 Uhr schrieb Werner LEMBERG : > > >> > Though the title contains backslashes, thus it's not searchable > >> > in LSR. Not sure what to do!? > >> > >> Hmm. I just entered `\mark' in the LSR search box, and it *does* > >> return snippets with backslashes in the title.

Re: LSR inconsistencies

2019-10-12 Thread Werner LEMBERG
>> > Though the title contains backslashes, thus it's not searchable >> > in LSR. Not sure what to do!? >> >> Hmm. I just entered `\mark' in the LSR search box, and it *does* >> return snippets with backslashes in the title. What exactly is the >> problem? > > From here: > >

Re: LSR inconsistencies

2019-10-12 Thread Thomas Morley
Am Sa., 12. Okt. 2019 um 07:22 Uhr schrieb Werner LEMBERG : > > > Done. > > Thanks! > > >> http://lsr.di.unimi.it/LSR/Item?id=857 > > > > Done. > > > > Though the title contains backslashes, thus it's not searchable in > > LSR. Not sure what to do!? > > Hmm. I just entered `\mark' in the LSR

Re: LSR inconsistencies

2019-10-11 Thread Werner LEMBERG
> Done. Thanks! >> http://lsr.di.unimi.it/LSR/Item?id=857 > > Done. > > Though the title contains backslashes, thus it's not searchable in > LSR. Not sure what to do!? Hmm. I just entered `\mark' in the LSR search box, and it *does* return snippets with backslashes in the title. What

Re: LSR inconsistencies

2019-10-11 Thread Thomas Morley
Am Mo., 7. Okt. 2019 um 09:16 Uhr schrieb Werner LEMBERG : > Another minor issue: There are some snippets that have a full stop at > the end of the title. IMHO, a title should never have that. > > http://lsr.di.unimi.it/LSR/Item?id=310 Done > http://lsr.di.unimi.it/LSR/Item?id=336 Title

Re: LSR inconsistencies

2019-10-09 Thread Werner LEMBERG
>> I don't see a corrected title in today's sqldump file. [And in the >> text body the word is written incorrectly, too.] > > Maybe I forgot to actually _store_ it :(( Hopefully it'll works now. It does, thanks! >> Another minor issue: There are some snippets that have a full stop >> at the

Re: LSR inconsistencies

2019-10-08 Thread Thomas Morley
Am Mo., 7. Okt. 2019 um 09:16 Uhr schrieb Werner LEMBERG : > > > > #1033 can be found in the 2.19.83-snippets, but not in master. No > > clue. > > #1069 was approved Thursday or Friday, can't be in the source until > > someone does a lsr-import > > #1071 same as for #1069 > > OK.

Re: LSR inconsistencies

2019-10-07 Thread Werner LEMBERG
> #1033 can be found in the 2.19.83-snippets, but not in master. No > clue. > #1069 was approved Thursday or Friday, can't be in the source until > someone does a lsr-import > #1071 same as for #1069 OK. Thanks for checking. > #1083 title corrected, no clue why it's missing in

Re: LSR inconsistencies

2019-10-05 Thread Thomas Morley
Am Sa., 5. Okt. 2019 um 10:11 Uhr schrieb Werner LEMBERG : > > > I've found some LSR inconsistencies. All of the following snippets > are tagged as `docs' and approved but missing in the lilypond git > repository (while present in the LSR bundle). > > #1033 >