> -Original Message-
> From: Graham Percival [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 23, 2008 7:11 PM
> To: Carl D. Sorensen
> Cc: lily-devel
> Subject: Predefined command maintainer
>
>
> I'd like to get a volunteer for Predefined Commands
> Maintainer. I estimate it'll take 5 hou
> -Original Message-
> From: Graham Percival [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 23, 2008 7:11 PM
> To: Carl D. Sorensen
> Cc: lily-devel
> Subject: Predefined command maintainer
>
> On Fri, 23 May 2008 15:23:09 -0600
> "Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
>
> > > Are t
This looks right to me, and since nobody has come up with any
better names, let's go with bracketed/quoted/bare.
Unless we want to call the first one "curly text". ;)
Cheers,
- Graham
On Fri, 23 May 2008 21:19:56 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
>
> So, in summary, might we
On Fri, 23 May 2008 21:19:56 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> Other commands are more selective. For example, text for
> ottava brackets can only be entered as quoted text.
I consider this a bug. I can see the difficulties for lyric mode,
but IMO all other text should take \m
On Fri, 23 May 2008 15:23:09 -0600
"Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
> > Are these really so important to the notation that we need
> > predefined commands for them? How often do people want to
> > change the default Alterations/Plus placement? These might
> > be better just shown wi
On Fri, 23 May 2008 15:23:09 -0600
"Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
> > The other Up/Down commands use Neutral for the \revert.
> > Granted, in this case you generally don't have lilypond
> > choosing which direction to place these objects, but I think
> > it's still worth following t
What's the status of the texi2html output?
1) Are there any remaining bugs or missing features in texi2html
that we'd like to see? Patrick is planning on making a release
soon, and it would be silly if we discovered an important problem
right after a release:
http://lists.gnu.org/archive/html/te
> -Original Message-
> From: Trevor Daniels [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 23, 2008 2:42 PM
> To: Carl D. Sorensen; lily-devel
> Subject: Re: predefined commands for figured bass
>
>
> bassFigureStaffAlignmentUp = {
> \revert Staff.BassFigureAlignmentPositioning #'direction
> -Original Message-
> From: Graham Percival [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 23, 2008 3:00 PM
> To: Carl D. Sorensen
> Cc: lily-devel
> Subject: Re: predefined commands for figured bass
>
> On Fri, 23 May 2008 14:12:49 -0600
> "Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
>
On May 23, 2008, at 11:08 PM, Reinhold Kainhofer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There are several lilypond commands that contain a hyphen, but the LSR
currently does not allow searching for them. Apparently, "-" is not
allowed
in the search string:
http://lsr.dsi.unimi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There are several lilypond commands that contain a hyphen, but the LSR
currently does not allow searching for them. Apparently, "-" is not allowed
in the search string:
http://lsr.dsi.unimi.it/LSR/Search?q=on-the-fly
Would it be hard to allow also h
On Fri, 23 May 2008 14:12:49 -0600
"Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
> Here are some proposed predefined commands for Figured Bass:
>
> bassFigureStaffAlignmentDown = {
> \override Staff.BassFigureAlignmentPositioning #'direction = #DOWN
> }
>
> bassFigureStaffAlignmentUp = {
> \
Carl
bassFigureStaffAlignmentUp = {
\revert Staff.BassFigureAlignmentPositioning #'direction
}
I wonder if using \revert is better than setting
'direction to #UP? If the default value of 'direction
is ever changed this command would need to be changed
too. But if 'direction is explicitly set
So, in summary, might we have something like this?
Entering text
Text may be entered in three ways:
o delimited by curly brackets, let's call this "bracketed text"
o delimited by double quotes, let's call this "quoted text"
o delimited by spaces, let's call this "bare text"
but there are restr
Here are some proposed predefined commands for Figured Bass:
bassFigureStaffAlignmentDown = {
\override Staff.BassFigureAlignmentPositioning #'direction = #DOWN
}
bassFigureStaffAlignmentUp = {
\revert Staff.BassFigureAlignmentPositioning #'direction
}
bassFigureStackingUp = {
\override St
I would like to propose the following predefined commands for the ChordNames
context:
hideRepeatedChordNames = {
\set chordChanges = ##t
}
showRepeatedChordNames = {
\set chordChanges = ##f
}
Here is an example of their use.
hideRepeatedChordNames = { \set chordChanges = ##t }
showRepeated
2008/5/23 Graham Percival <[EMAIL PROTECTED]>:
>> You may want to discuss these modifications with other Spanish people,
>> like the original author of Spanish glossary David Gonz__lez, or on a
>> Spanish mailing list or forum; besides this, you may directly apply
>> modifications in Git to the Spa
On Fri, 23 May 2008 10:48:36 +0200
John Mandereau <[EMAIL PROTECTED]> wrote:
> On 2008/05/23, Graham Percival wrote:
> > But please don't modify the glossary yourself; that will make my job
> > harder when I merge the next update.
>
> Speaking of, do you mind if I go on applying technical changes
On 2008/05/23, Graham Percival wrote:
> But please don't modify the glossary yourself; that will make my job
> harder when I merge the next update.
Speaking of, do you mind if I go on applying technical changes to the
documentation directly in Git? I think this makes you less work, as Git
does a
On 2008/05/23, Mats Bengtsson wrote:
> Graham Percival wrote:
> >
> > *as far as I know*, anything in lilypond that accepts "blah blah"
> > also accepts \markup.
> >
> This is almost true. However, I seem to recall a few exceptions. For
> example, you
> cannot use a \markup expression as the va
2008/5/23 Graham Percival <[EMAIL PROTECTED]>:
> Yes, it's the grob that is created when you write
> c4-"foo" or c4-\markup{foo}
IIRC, a TextScript is also much more than that.
By the way, I'm unsure "script" is anywhere near more reassuring than
"string". Both look equally unfamiliar to me...
Graham Percival wrote:
*as far as I know*, anything in lilypond that accepts "blah blah"
also accepts \markup.
This is almost true. However, I seem to recall a few exceptions. For
example, you
cannot use a \markup expression as the value when you set a property in
\lyricmode.
/Mats
On Fri, 23 May 2008 09:40:21 +0200
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> 2008/5/23 Graham Percival <[EMAIL PROTECTED]>:
>
> >> or even textual annotation which
> >> can be applied to a note with either '-' or '\markup?
> >
> > In current GDP terminology, these are "Text scripts".
>
>
On Fri, 23 May 2008 09:32:25 +0200
John Mandereau <[EMAIL PROTECTED]> wrote:
> On 2008/05/21, Francisco Vila wrote:
> > Hello. I don't know who is responsible nowadays for the music
> > glossary; here is a list of proposed modifications for the Spanish
> > part of it. Thanks!
>
> You may want to
2008/5/23 Graham Percival <[EMAIL PROTECTED]>:
>> or even textual annotation which
>> can be applied to a note with either '-' or '\markup?
>
> In current GDP terminology, these are "Text scripts".
Which is not necessarily sensible, since TextScript is already a grob.
> Fundamentally, all text i
On 2008/05/21, Francisco Vila wrote:
> Hello. I don't know who is responsible nowadays for the music
> glossary; here is a list of proposed modifications for the Spanish
> part of it. Thanks!
You may want to discuss these modifications with other Spanish people,
like the original author of Spanish
On Fri, 23 May 2008 08:12:43 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> Graham Percival wrote May 22, 2008 11:39 AM
> > Failing all else, I suppose we /could/ use the terms "markup text"
> > and "quoted text". I mean, there are more uses for these terms
> > (whatever we end up calling th
Graham Percival wrote May 22, 2008 11:39 AM
On Thu, 22 May 2008 09:46:15 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
Valentin Villenave wrote May 22, 2008 9:03 AM
> "Markup expressions may also be enclosed in double quotes "...".
> Such expressions are treated as text strings and may not c
28 matches
Mail list logo
