On Wed, 16 Apr 2008 10:04:19 +0200 John Mandereau <[EMAIL PROTECTED]> wrote:
> I leave fixing @lsrdir references in the manuals up to GDP > contributors. Since we haven't touched NR 2 yet, this isn't an issue. :) > 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? This is definitely Valentin's problem. My vote is for the first -- the only reason I stopped arguing about this a few months ago with him is that I discovered that we could rename tags. A lot of fine-tuning will be necessary, of course, but AFAIK we only have one of the NR 1 tags for the snippet list looking good (ie Pitches). That's an ongoing project. Valentin: as a special favor, tag something with "winds" (after you rename "bagpipes"). I don't care if it has anything to do with wind instruments; just get a tag in there so we can uncomment that item in makelsr.py. > 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 Camel-case tags are entirely Valentin's problem. As you say, they're not included in the docs, so he can do whatever he wants with them. :) Cheers, - Graham _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
