Re: id's for svg elements

2013-10-27 Thread Henning Hraban Ramm
Am 2013-10-27 um 19:46 schrieb David Kastrup : > Henning Hraban Ramm writes: > >> Am 2013-10-27 um 16:11 schrieb David Kastrup : > At any rate, the user lists are rather helpful resources as well. This user list must be in the top 99 percentile in terms of quickness, thoroug

Re: id's for svg elements

2013-10-27 Thread David Kastrup
Henning Hraban Ramm writes: > Am 2013-10-27 um 16:11 schrieb David Kastrup : At any rate, the user lists are rather helpful resources as well. >>> >>> This user list must be in the top 99 percentile in terms of quickness, >>> thoroughness, and effectiveness of response. >> >> It's definite

Re: id's for svg elements

2013-10-27 Thread Henning Hraban Ramm
Am 2013-10-27 um 16:11 schrieb David Kastrup : >>> At any rate, the user lists are rather helpful resources as well. >> >> This user list must be in the top 99 percentile in terms of quickness, >> thoroughness, and effectiveness of response. > > It's definitely one of LilyPond's assets. Oh yes!

Re: latest source (was Re: id's for svg elements)

2013-10-27 Thread David Kastrup
Bric writes: > On 10/27/2013 03:07 AM, Mike Solomon wrote: >> (PS: how is it that you have 2.17.30, when the latest version is >> 2.17.29 ? http://download.linuxaudio.org/lilypond/source/v2.17/ ) >> >> >> I build LilyPond from source, and the current version in current >> master is 2.17.30. > >

Re: id's for svg elements

2013-10-27 Thread David Kastrup
Bric writes: > On 10/27/2013 03:29 AM, David Kastrup wrote: > >> I sometimes have difficulty distinguishing sarcasm from enthusiasm. At >> any rate, the manuals should by now contain a number of good leads. How >> far you get with them without additional help really depends on your >> general p

Re: latest source (was Re: id's for svg elements)

2013-10-27 Thread Urs Liska
What you're seeing is the latest _released_ source tarball. They are referring to the latest state of the development Git repository at savannah.org Bric schrieb: >On 10/27/2013 03:07 AM, Mike Solomon wrote: >> (PS: how is it that you have 2.17.30, when the latest version is >2.17.29 ? http:

latest source (was Re: id's for svg elements)

2013-10-27 Thread Bric
On 10/27/2013 03:07 AM, Mike Solomon wrote: (PS: how is it that you have 2.17.30, when the latest version is 2.17.29 ? http://download.linuxaudio.org/lilypond/source/v2.17/ ) I build LilyPond from source, and the current version in current master is 2.17.30. uuuh... so did /I/, from 2.17.2

Re: id's for svg elements

2013-10-27 Thread Bric
On 10/27/2013 03:29 AM, David Kastrup wrote: Mike Solomon writes: On Oct 27, 2013, at 12:57 AM, Bric wrote: Hi! I see it. And I can see that you're doing some sort of awesome magic here, but it remains a total mystery... looking at the code, and looking at the result, alike. (what's a "gro

Re: id's for svg elements

2013-10-27 Thread David Kastrup
Mike Solomon writes: > On Oct 27, 2013, at 12:57 AM, Bric wrote: > >> Hi! I see it. And I can see that you're doing some sort of awesome >> magic here, but it remains a total mystery... looking at the code, >> and looking at the result, alike. >> >> (what's a "grob property"? I guess it's time

Re: id's for svg elements

2013-10-27 Thread Mike Solomon
On Oct 27, 2013, at 12:57 AM, Bric wrote: > On 10/26/2013 04:15 AM, Mike Solomon wrote: >> On Oct 26, 2013, at 10:51 AM, Bric wrote: >> >> For example… >> >> \version "2.17.30" >> >> #(define (note-number grob) >> (string-concatenate >> (list >> "NoteHead/" >> (number->stri

Re: id's for svg elements

2013-10-26 Thread Bric
On 10/26/2013 04:15 AM, Mike Solomon wrote: On Oct 26, 2013, at 10:51 AM, Bric wrote: can someone help scope out the task of adding semantically sound unique identifiers to the svg elements? Such that the id bears info on, at least, the staff, (maybe bar), and note/chord index (consecutive

Re: id's for svg elements

2013-10-26 Thread Mike Solomon
On Oct 26, 2013, at 10:51 AM, Bric wrote: > can someone help scope out the task of adding semantically sound unique > identifiers to the svg elements? > > Such that the id bears info on, at least, the staff, (maybe bar), and > note/chord index (consecutive integer index, for instance) > > the