Re: info documentation with images?

2008-01-14 Thread Graham Percival
On Tue, 15 Jan 2008 03:06:32 +0100 David Kastrup <[EMAIL PROTECTED]> wrote: > Graham Percival <[EMAIL PROTECTED]> writes: > > > Err, it is. We use lilypond-book to build the docs. > > And the info files don't contain images. > > What gives? Well, this is a quite different matter than us not u

Re: info documentation with images?

2008-01-14 Thread David Kastrup
Graham Percival <[EMAIL PROTECTED]> writes: > On Tue, 15 Jan 2008 02:04:37 +0100 > David Kastrup <[EMAIL PROTECTED]> wrote: > >> Graham Percival <[EMAIL PROTECTED]> writes: >> >> > On Mon, 14 Jan 2008 12:16:03 +0100 >> > David Kastrup <[EMAIL PROTECTED]> wrote: >> > >> >> I thought I remembered t

Re: info documentation with images?

2008-01-14 Thread Graham Percival
On Tue, 15 Jan 2008 02:04:37 +0100 David Kastrup <[EMAIL PROTECTED]> wrote: > Graham Percival <[EMAIL PROTECTED]> writes: > > > On Mon, 14 Jan 2008 12:16:03 +0100 > > David Kastrup <[EMAIL PROTECTED]> wrote: > > > >> I thought I remembered that Lilypond was supposed to be able to > >> generate in

Re: info documentation with images?

2008-01-14 Thread David Kastrup
Graham Percival <[EMAIL PROTECTED]> writes: > On Mon, 14 Jan 2008 12:16:03 +0100 > David Kastrup <[EMAIL PROTECTED]> wrote: > >> I thought I remembered that Lilypond was supposed to be able to >> generate info files with images (and that Emacs' CVS was able to >> display those images). > > Isn't t

Re: two issues on LSR

2008-01-14 Thread Valentin Villenave
2008/1/14, Till Rettig <[EMAIL PROTECTED]>: > Hi Valentin, > > I tried updating the snippet I posted (about ancient incipit), but I > can't edit it, I don't know what the mistake is. You cannot edit snippets once I approved them. You have to send a new snippet with the exact same title, and your c

two issues on LSR

2008-01-14 Thread Till Rettig
Hi Valentin, I tried updating the snippet I posted (about ancient incipit), but I can't edit it, I don't know what the mistake is. Then I have another thing here, a "workaround" from the list about one year ago. It is about marking the notes of spoken parts with a cross on the stem. It is no

Re: info documentation with images?

2008-01-14 Thread Graham Percival
On Mon, 14 Jan 2008 12:16:03 +0100 David Kastrup <[EMAIL PROTECTED]> wrote: > I thought I remembered that Lilypond was supposed to be able to > generate info files with images (and that Emacs' CVS was able to > display those images). Isn't this done with lilypond-book? It's in Application Usage.

Re: signs

2008-01-14 Thread Mats Bengtsson
Valentin Villenave wrote: Plus, it would be useful even for "normal" users; speaking of personal experience, it took me a while, for instance, to understand that the dot actually meant a thick line. I guess, the dot first appeared in "|.", where it means "end the piece", just like a dot is

Re: signs

2008-01-14 Thread Valentin Villenave
2008/1/14, Werner LEMBERG <[EMAIL PROTECTED]>: > You are greatly exaggerating. Graham? exagerating? N way... :) This question is tricky. When I first saw your forwarded mail about barlines thickness, I was about to add the explanations and description myself, and then I had a second thought.

info documentation with images?

2008-01-14 Thread David Kastrup
Hi, I thought I remembered that Lilypond was supposed to be able to generate info files with images (and that Emacs' CVS was able to display those images). But I can find nothing in the documentation about how to enable this, and not even a git branch with an obvious name. Have I been dreaming

Re: page breaks related to header size

2008-01-14 Thread Risto Vääräniemi
On Jan 14, 2008 12:35 PM, Mats Bengtsson wrote: > If you want to discuss issues with the latest development releases, I'd > recommend to use the lilypond-devel mailing list. I have forwarded > this email there. OK. Thanks for the tip. I thought the lilypond-devel list was just for the actual devel

Re: page breaks related to header size

2008-01-14 Thread Mats Bengtsson
If you want to discuss issues with the latest development releases, I'd recommend to use the lilypond-devel mailing list. I have forwarded this email there. /Mats Risto Vääräniemi wrote: Dear All, Risto Vääräniemi wrote: Has this issue taken some steps backwards? I compiled both of Paul's

Developer docs

2008-01-14 Thread Bertalan Fodor (LilyPondTool)
Valentin Villenave wrote: Hi David, hi everybody. David's feature request has been officially added as http://code.google.com/p/lilypond/issues/detail?id=559 I'm both happy and sad to admit this request: I am happy to see that people like David care about making LilyPond an even better program,

Re: signs

2008-01-14 Thread Werner LEMBERG
> > I think the solution is quite easy: just add those textual > > descriptions into the source file as comments; blind people will > > always look up those descriptions I think. > > Where do we draw the line? Quite easy: Wait for bug reports and/or suggestions from users who need this. > This w