[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Updating LSR tags [was Re: make loop in input/lsr]
From: |
John Mandereau |
Subject: |
Updating LSR tags [was Re: make loop in input/lsr] |
Date: |
Wed, 16 Apr 2008 10:04:19 +0200 |
Trevor Daniels wrote:
> Commit bf5fc592ed4ffc6bae4e97d60c52d044554e6872 changed the section headings
> in specialist.itely and renamed four files to correspond, as follows:
>
> bagpipes.itely -> wind.itely
> guitar.itely -> fretted-strings.itely
> piano.itely -> keyboards.itely
> strings.itely -> unfretted-strings.itely
You're right to raise this issue, although this has little to do with
'make loop' problem (the empty bagpipes.snippet-list used to be there
for a long time).
I updated input/lsr '*.*tely' files, makelsr.py and input/new/*.ly with
the new tags:
bagpipes -> winds (commented out, for there is currently no snippets)
guitar -> fretted-strings Fretted strings
piano -> keyboards.itely Keyboards
strings -> unfretted-strings Unfretted strings
I leave fixing @lsrdir references in the manuals up to GDP contributors.
Please DO NOT run makelsr.py until tags have been renamed in LSR
database. I've not updated tags in LSR database because I don't know
exactly how to handle renaming: should we simply rename tags, or should
we clone tags and edit old tags such as guitar and piano so they only
include snippets specific to these particular instruments? I vote for
the second solution, even if it requires a bit more work. As I still
have a lot to do for translated docs with texi2html, could Valentin or
somebody who has write access to LSR database tackle this?
Speaking of LSR database, I renamed there some old camel-cased tags
(that are not included in docs today):
Preparing Parts -> Preparing parts
SchemeLanguage -> Scheme language
SymbolsAndGlyphs -> Symbols and glyphs
ConnectingNotes -> Connecting notes
AutomaticNotation -> Automatic notation
ContemporaryNotation -> Contemporary notation
> (Investigating this has screwed up my git with the same
> input/regression/musicxml file not up-to-date, 17f-AllChordTypes.xml, again.
> Is anyone else having trouble with this? Last time I had to rebuild the
> repository to get rid of it, and here it is back again :(
Which Git version do you have? On which OS? What Git commands did you
use exactly? Did you play with 'git checkout'?
Cheers,
John