I came up with this list from looking at the download directory. Is
this correct? Does mingw mean "windows"? What's the deal with MacOS /
darwin-* ?
MacOS
darwin-ppc
darwin-x86
freebsd-64
freebsd-x86
linux-64
linux-arm
linux-ppc
linux-x86
mingw
_
Trevor Bača wrote:
Sure, I'd be happy to. (And if winds up being too complicated, then
that's certainly OK; just keep me in check!)
Go nuts. :) My only concern is the vertical space of the printed
music on the page. For the lilypond input, do whatever you want.
Overrides, scheme, Turing
On 8/30/07, Trevor Bača <[EMAIL PROTECTED]> wrote:
> On 8/30/07, Graham Percival <[EMAIL PROTECTED]> wrote:
> > Han-Wen Nienhuys wrote:
> > > Graham Percival escreveu:
> > >
> > >
> > >> ... hmm, I might see a use for that. We could have one really fancy
> > >> example, *without* input code, in th
On 8/30/07, Graham Percival <[EMAIL PROTECTED]> wrote:
> Han-Wen Nienhuys wrote:
> > Graham Percival escreveu:
> >
> >
> >> ... hmm, I might see a use for that. We could have one really fancy
> >> example, *without* input code, in the "root" node of each section.
> >>
> >
> > I concur with this. S
Han-Wen Nienhuys wrote:
Graham Percival escreveu:
... hmm, I might see a use for that. We could have one really fancy
example, *without* input code, in the "root" node of each section.
I concur with this. Some 'real' examples also help give users an idea what
some features (eg. fatTe
Graham Percival escreveu:
> ... hmm, I might see a use for that. We could have one really fancy
> example, *without* input code, in the "root" node of each section.
I concur with this. Some 'real' examples also help give users an idea what
some features (eg. fatText) could be used for.
--
Han-
On 8/30/07, Graham Percival <[EMAIL PROTECTED]> wrote:
> Trevor Bača wrote:
> > The second example was infinitely easier: we just needed something to
> > show a text script complicated enough to require a markup (which is
> > almost everything). The indication, is, of course, Debussy's famous
> > m
Valentin Villenave wrote:
About the reg tests:
allow me to quote my official mentor GP: when I became the new LSR
guy, the first assignment he gave me was to add to the LSR any of the
regression tests that might be useful.
From: Graham Perc
Trevor Bača wrote:
The second example was infinitely easier: we just needed something to
show a text script complicated enough to require a markup (which is
almost everything). The indication, is, of course, Debussy's famous
marking at the beginning of Des pas sur la neige.
Let's ignore the \f
Thanks, fixed in git.
Cheers,
- Graham
Jean-Charles Malahieude wrote:
Hi Graham,
According to the working example that comes just before, please apply:
@@ -2221,11 +2221,11 @@ can be used to adjust note durations.
}
@end lilypond
@refbugs
-The @code{\featherDuration} command only works w
> -Original Message-
> From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> 2007/8/30, Trevor Bača <[EMAIL PROTECTED]>:
>
> > The first example -- the one for \fatText -- was quite difficult to
> > come up with. I looked at the existing \fatText last night
> and thought
> > "what poss
Valentin Villenave wrote:
2007/8/31, Graham Percival <[EMAIL PROTECTED]>:
There's a few other places in the manual where they're used. Yes, they
could of course be used in more places. I'm sure that both of you know
why they aren't yet. :)
Let me guess... Everyone tried to help but
2007/8/31, Graham Percival <[EMAIL PROTECTED]>:
Great! I noticed the glissando link indeed, but never had the
curiosity to look at the source file.
> There's a few other places in the manual where they're used. Yes, they
> could of course be used in more places. I'm sure that both of you know
>
Valentin Villenave wrote:
Leaving the feature page aside, what I often tried to figure out was:
how to better integrate the LSR with the manual. I can't put links to
the manual in the snippets descriptions (since the links are likely to
be broken soon); neither can I put links to the LSR snippets
2007/8/30, Trevor Bača <[EMAIL PROTECTED]>:
> [I'm a little hesitant to speak on this issue because I think my
> opinions differ a bit from the rest of the team. So fair warning,
> subjective opinion coming up. I personally *love* and adore the
> manual. I use it every day. I read it more often t
On 8/30/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> 2007/8/30, Trevor Bača <[EMAIL PROTECTED]>:
>
> > The first example -- the one for \fatText -- was quite difficult to
> > come up with. I looked at the existing \fatText last night and thought
> > "what possible musical context is there for
2007/8/30, Trevor Bača <[EMAIL PROTECTED]>:
> The first example -- the one for \fatText -- was quite difficult to
> come up with. I looked at the existing \fatText last night and thought
> "what possible musical context is there for making text open up a gap
> in the middle of a score; where on ea
2007/8/30, Trevor Bača <[EMAIL PROTECTED]>:
> I tried to make the point visually this morning by mocking up 8.1.1
> "Text scripts" in LaTeX. I don't think I got all the settings right to
> match the docs, but at least here I can kinda give a little bit by
> contributing an example (instead of just
Hi Graham,
According to the working example that comes just before, please apply:
@@ -2221,11 +2221,11 @@ can be used to adjust note durations.
}
@end lilypond
@refbugs
-The @code{\featherDuration} command only works with very short
+The @code{\featherDurations} command only works with very
Good catch. Actually, we should rephrase the initial text (lines 1283
and 1284) to avoid naming a specific version, because convert-ly updates
the \version in the example but not in the intro text. And that intro
text is really awkward, anyway. I can't believe I wrote it.
Cheers,
- Graham
hello Mats,
thanks for your reply. I didn't know about m4 or cpp. Will take a look.
victor.
On 8/29/07, Mats Bengtsson <[EMAIL PROTECTED]> wrote:
>
> In any text editor, it's trivial to automatically replace all occurences
> of
> something like
> \lilystart
> by
> \begin[staffsize=12]{lilypond}
Hi,
I think we should change the version number in the tutorial text for
2.11 from 2.10.1 also to 2.11.23 as done in the example.
It is in line 1284.
After all this manual is for 2.11.x isn't it?
Greetings
Till
___
lilypond-devel mailing list
lilyp
John Mandereau wrote:
Le mardi 28 août 2007 à 22:52 +0300, Till Rettig a écrit :
I don't know all the
reasons, but there is clearly one: your patches don't include all the
changes you made to German translations, for example adding
"documentlanguage: de" to working.itely.
This is strange,
Hi Henrik,
this sounds really good! At the moment it is only me translating and I
was quite busy with other things lately so the process is somewhat
slowed down. That to say I am on my way on chapter 7, everything
afterwards is not touched yet. I have also elaborated a glossary with
German-En
Hi Graham,
Anybody feel like writing a wordy explanation about polyphony?
I think I can handle that. =)
Best,
Kieren.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Graham Percival wrote:
I'm not overly enthusiastic about adding color to the manual: I'm not
certain how it will look in a printed pdf (many people print the docs)
or in the info files. We obviously need to use color in the doc
section about color, and the red staff-lines in Ancient notation
I'm not overly enthusiastic about adding color to the manual: I'm not
certain how it will look in a printed pdf (many people print the docs)
or in the info files. We obviously need to use color in the doc section
about color, and the red staff-lines in Ancient notation will show up as
black an
27 matches
Mail list logo
