Is there a way to create footnotes? I.e. a command to add a footnote
(containing markup) to the bottom of the current page, without stopping a
\score and writing a toplevel \markup ?
tia,
Wilbert Berendsen
--
http://www.wilbertberendsen.nl/
You must be the change you wish to see in the world.
I should be able to help with some of the trivial to easy sections,
and possibly some medium.
Thanks for your work on the documentation. It is one of the best of
any project I have seen.
Regards,
Joe
___
lilypond-user mailing list
Hi,
Briefly: Has anyone created the font descriptor (*.fd) and style
(*.sty) files that would enable Lilypond's fonts to be used in LaTeX?
I'd like to use Lilypond's fonts in the body of a Latex document as well
as using lilpond-book for the musical examples. Searching the
lilypond-user archives
Rune Zedeler wrote:
Well, in its current state I find the each subsection has its own page version
of the manual unusable, and therefore always uses the one big page manual.
I suggest that we gives each section its own page containing section and all
subsections. Ofcourse each section should
Tim Litwiller wrote:
In email setting
under your account
Composition Addressing - do you have it set to Compose message in HTML
format
and then if you have preferred to recieve message format as plaintext in
the addressbook.
if they are different thunderbird will try to convert
Thank you!
Trevor Bača wrote:
~ subsection 8.4.3 Proportional notation can be removed completely
in favor of subsection 11.6.5 Proportional notation
I'd rather not remove subsections yet; we'll do that when we GDPify that
particular chapter.
~ subsections 8.4.4 Clusters and 8.4.5 Special noteheads
Rune Zedeler wrote:
Very first I comment on the stuff I wrote below: When I wrote it I
didn't really notice / think about the fact the the first five sections
are left out. Probably some of my comments are not totally valid. Well,
I will think some more, and post another message about the
Eyolf Østrem wrote:
I would also say -- although this may exceed the limits of what kind
of suggestions were allowed -- that one thing that is missing is a
comprehensive survey of the syntax of Lilypond.
Like Appendix E Cheat sheet ? It's quite limited at the moment, but is
that what you're
Just a question...
(by the way, is it really relevant to cross post this entire
discussion to -devel?)
I'm finishing translating the current chapter #9 (changing-defaults)
and here's what I see:
9.3.2
Suppose we want to move the fingering indication in the fragment below:
=== but it actually
Graham Percival wrote:
+ 6.6.2 Stems
Currently, this subsection has nothing to do with polyphony.
Furthermore it is layout specific, and should therefore be postponed.
I have _always_ hated this section. I remember trying -- and failing
-- to find a home for it when I
Valentin Villenave wrote:
Just a question...
(by the way, is it really relevant to cross post this entire
discussion to -devel?)
We're talking about some major lilypond development work here.
Documentation is still development. A better question is is it really
relevant to cross post this
On 10.09.2007 (05:22), Graham Percival wrote:
Rune Zedeler wrote:
And in all cases, it is way too early. The user has not even learned what
the 4 in c4 means.
Tutorial. If a user hasn't read the LM, they're on their own and I have
*no* sympathy for them.
That's definitely the right
Yes, I guess my main point was the on-line manual, where the splitting into
separate HTML pages is a problem in some cases, like Valentin just
illustrated. As far as I understand, it's the texinfo - HTML conversion
that
imposes the constraint that each subsection ends up in a separate HTML.
It
2007/9/10, Graham Percival [EMAIL PROTECTED]:
+ 6.2.1 Clef
+ 6.2.2 Key signature
Hmm, neither clefs nor key signatures affect pitches. They only affect
how they are displayed.
Yes, true. Rename section?
Hell yes!
What about :
Pitches notation or
On 10.09.2007 (05:28), Graham Percival wrote:
Eyolf Østrem wrote:
I would also say -- although this may exceed the limits of what kind
of suggestions were allowed -- that one thing that is missing is a
comprehensive survey of the syntax of Lilypond.
Like Appendix E Cheat sheet ? It's quite
2007/9/10, Graham Percival [EMAIL PROTECTED]:
Err.. we're talking about Changing defaults, a chapter which hasn't been
significantly changed in the past three years, and which you've
_already_ complained as being a pile of garbage... and using this as an
argument for changing the way the rest
Hi Valentin,
I doubt we have enough stuff to make a whole Page layout chapter.
I disagree...
There's *more* than enough for a Page Layout chapter: even if some
(much?) of the material is referenced elsewhere/earlier, it would be
beneficial to have a single coherent section in which all
On 10.09.2007 (09:06), Kieren MacMillan wrote:
Hi Valentin,
I doubt we have enough stuff to make a whole Page layout chapter.
I disagree...
There's *more* than enough for a Page Layout chapter: even if some (much?)
of the material is referenced elsewhere/earlier, it would be beneficial to
Am Montag, 10. September 2007 schrieb Graham Percival:
Rune Zedeler wrote:
Well, in its current state I find the each subsection has its own page
version of the manual unusable, and therefore always uses the one big
page manual. I suggest that we gives each section its own page containing
Le lundi 10 septembre 2007 à 14:46 +0200, Mats Bengtsson a écrit :
Yes, I guess my main point was the on-line manual, where the splitting into
separate HTML pages is a problem in some cases, like Valentin just
illustrated. As far as I understand, it's the texinfo - HTML conversion
that
Briefly: Has anyone created the font descriptor (*.fd) and style
(*.sty) files that would enable Lilypond's fonts to be used in
LaTeX?
No.
1. Use lilypond-book - Seems to create a large amount of whitespace
around the character.
The surrounding whitespace can be suppressed; however, it is
Le lundi 10 septembre 2007 à 15:31 +0200, Reinhold Kainhofer a écrit :
Am Montag, 10. September 2007 schrieb Graham Percival:
Rune Zedeler wrote:
Well, in its current state I find the each subsection has its own page
version of the manual unusable, and therefore always uses the one big
To summarize some discussions:
- there seems to be considerable dislike for the current
one-short-subsection-per-HTML-page layout of the manual. That
surprises me, since I've never had a problem with it, but of course I'm
intimately familiar with the layout of the manual, so I'm happy to
Hi Graham (et al.):
Does anybody _like_ the current layout?
In some ways, my opinion won't matter, because I don't use (nor do I
really understand why anyone else uses) the HTML manual -- the PDF
documentation is all I ever use because:
1. It's perfect for printing;
2. Full-text
Le lundi 10 septembre 2007 à 08:00 -0700, Graham Percival a écrit :
To summarize some discussions:
- there seems to be considerable dislike for the current
one-short-subsection-per-HTML-page layout of the manual. That
surprises me, since I've never had a problem with it, but of course I'm
John Mandereau wrote:
We could use @anchor to get links (@ref's in Info) on the same page, but
I'm not sure *Menu items can redirect to an @anchor.
@menu items direct to @section items. This is no problem.
We will decide about having larger HTML pages (and thus larger Info
nodes) in a
On 10.09.2007 (11:09), Kieren MacMillan wrote:
Hi Graham (et al.):
Does anybody _like_ the current layout?
That being said... ;-)
My preference is for 2
Me 2.
Me 3.
--
paak, n:A stadium or inclosed playing field. To put or leave (a
a vehicle) for a
Le lundi 10 septembre 2007 à 14:37 +0200, Mats Bengtsson a écrit :
Graham Percival wrote:
+ 6.6.2 Stems
Currently, this subsection has nothing to do with polyphony.
Furthermore it is layout specific, and should therefore be postponed.
I have _always_ hated this
. The LaTeX encoding of the lilypond font(s) is clearly `U'; it
makes no sense to create a new encoding for it.
Could you explain what you mean by `U'?
Please consult the `fontenc' guide of the LaTeX base distribution.
`U' means `unspecified'.
The example in the tutorial above
Le lundi 10 septembre 2007 à 05:22 -0700, Graham Percival a écrit :
Rune Zedeler wrote:
Very first I comment on the stuff I wrote below: When I wrote it I
didn't really notice / think about the fact the the first five sections
are left out. Probably some of my comments are not totally
Am 2007-09-10 um 13:08 schrieb Stuart Pullinger:
Briefly: Has anyone created the font descriptor (*.fd) and style
(*.sty) files that would enable Lilypond's fonts to be used in LaTeX?
I'd like to use Lilypond's fonts in the body of a Latex document as
well
as using lilpond-book for the
Hi Tim,
Could you mail the file to me as an attachment, I can't seem to access
the file from gnu.org?
Sounds like things are moving on for you :D
Cheers,
Ralph
___
lilypond-user mailing list
lilypond-user@gnu.org
Am 2007-09-10 um 18:29 schrieb John Mandereau:
11 Page layout (new chapter)
11.1 Paper and pages (moved from Spacing issues)
11.2 Titles and headers
11.3 Breaks (moved from Spacing issues)
The problem is, this breaks the unity of Spacing stuff in a single
chapter, and if we do this,
Am 2007-09-10 um 17:00 schrieb Graham Percival:
- Does anybody _like_ the current layout? If so, speak up now or
forever hold your peace. :)
No. I always use the online manual in several tabs (the fewer single
pages, the fewer tabs!) and a Google tab with site:lilypond.org/
doc/...,
2007/9/10, fiëé visuëlle [EMAIL PROTECTED]:
No. I always use the online manual in several tabs (the fewer single
pages, the fewer tabs!) and a Google tab with site:lilypond.org/
doc/..., because it also finds the commands in samples (in contrary
to the PDF), and often I only need a working
Citat Valentin Villenave [EMAIL PROTECTED]:
Rune: I think it's possible with some JScript tweaking (at least, some
buzzword-compliant technologies allow to do this without frames).
Maybe. I have just never seen it.
Javadoc still uses frames, and about everything else I have encountered reloads
Juergen Reuter wrote:
Furthermore, I would like to see entries like
\displayLilyMusic: Displaying LilyPond notation
\displayLilyMusic: Displaying music expressions
rather being structured as follows:
\displayLilyMusic:
Displaying LilyPond notation
Displaying music
Tim Litwiller wrote:
Yeh, I'm moving along trying different suggested methods as I go,
keeping notes as to what works. and what doesn't.
Hi Tim,
Could you mail the file to me as an attachment, I can't seem to
access the file from gnu.org?
Sounds like things are moving on for you :D
Thanks so much for that, another thing to add to my watch for this list.
Ralph Little wrote:
Tim Litwiller wrote:
Yeh, I'm moving along trying different suggested methods as I go,
keeping notes as to what works. and what doesn't.
Hi Tim,
Could you mail the file to me as an attachment, I
John Mandereau wrote:
Tu sum up your suggestion, which I like quite much, I propose the
following section (inside chapter 7 Decorating musical notation, and
replacing Special use):
7.6 Note heads and stems
7.6.1 Stems
7.6.2 Special noteheads
7.6.3 Improvisation
7.6.4 Selecting
fiëé visuëlle wrote:
samples (in contrary to the PDF), and often I only need a working sample
of usage (the in-text samples are often too short or not on topic as I
understand it or too cluttered - or too simple).
Hmm. Samples are too sort, too cluttered, or too simple. That will be
hard
BTW I'd like to see an forever-working URL like
http://lilypond.org/doc/current/Documentation/ (instead of the version;
should need only one symlink; maybe current-stable and current-dev).
Well,
http://lilypond.org/doc/v2.11/Documentation/
gives you the current-dev. Yes, you need to
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Wilbert Berendsen [EMAIL PROTECTED] writes:
Is there a way to create footnotes? I.e. a command to add a footnote
(containing markup) to the bottom of the current page, without stopping a
\score and writing a toplevel \markup ?
No. However, adding numbered notes to the end of the book or of
Hi
I have a little issue with pitched trills:
http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Trills#Trills
I'm trying to do this but with multiple trills. So the code looks kind
of like the following:
RH = \relative c'' {
\clef treble
\time 4/4
\key d \minor
a d16
\pitchedTrill
Hi Stefan,
So now the first TrillSpan collides with the second. Is there a
possibility to decimate the length of the trill span somehow?
See http://lists.gnu.org/archive/html/lilypond-user/2007-09/
msg00070.html.
Cheers,
Kieren.
___
Am 2007-09-10 um 20:45 schrieb Graham Percival:
fiëé visuëlle wrote:
samples (in contrary to the PDF), and often I only need a working
sample of usage (the in-text samples are often too short or not on
topic as I understand it or too cluttered - or too simple).
Hmm. Samples are too sort,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I know we're now drifting away from the goal of restructuring the
documentation into sections. Instead, this thread seems to be turning into
improving the general documentation system, which I regard as a step that
should be done before going into
Hi Graham,
I'm willing to help in any of the trivial, easy or medium categories.
Regards,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
fiëé visuëlle wrote:
How about collecting the page layout with other print related stuff like
lilypond-book, graphics formats etc.?
As collecting the sound output related (everything else than MIDI?)
No, lilypond-book is in the Program Usage now. The manual deals with
lilypond input format.
Hi everybody,
A short while back, I was under the misapprehension that there was something
wrong with the spacing in piano staves when using version 2.11. Having
erroneously submitted a bug report to this effect, I found out that thanks
to the new spacing engine, the fixed distance workaround
To anybody involved in the GDP discussion, please take a few minutes to
look at the documentation for 2.11. There have been a few significant
changes since 2.10; please look at those changes so we avoid reinventing
the wheel. Specifically,
- Manual is only for lilypond input format.
-
Le lundi 10 septembre 2007 à 11:06 -0700, Graham Percival a écrit :
Juergen Reuter wrote:
Furthermore, I would like to see entries like
\displayLilyMusic: Displaying LilyPond notation
\displayLilyMusic: Displaying music expressions
rather being structured as follows:
Le lundi 10 septembre 2007 à 20:49 +0200, Eyolf Østrem a écrit :
BTW I'd like to see an forever-working URL like
http://lilypond.org/doc/current/Documentation/ (instead of the version;
should need only one symlink; maybe current-stable and current-dev).
Well,
I'd like to be able to damp TupletBrackets the way you can damp
Beams to force horizontal TupletBrackets. I can't seem to find a
similar method in the docs (I'm using 2.11.32).
It seems that there was a delta-y argument for bracket slope in a
much much older version of Lily . . .
Is there a way
On 9/10/07, Neil Puttock [EMAIL PROTECTED] wrote:
Hi everybody,
A short while back, I was under the misapprehension that there was something
wrong with the spacing in piano staves when using version 2.11. Having
erroneously submitted a bug report to this effect, I found out that thanks
to
On 9/10/07, Adam James Wilson [EMAIL PROTECTED] wrote:
I'd like to be able to damp TupletBrackets the way you can damp
Beams to force horizontal TupletBrackets. I can't seem to find a
similar method in the docs (I'm using 2.11.32).
It seems that there was a delta-y argument for bracket slope
Hi Adam,
I'd like to be able to damp TupletBrackets the way you can damp
Beams to force horizontal TupletBrackets. I can't seem to find a
similar method in the docs (I'm using 2.11.32).
%%% BEGIN SNIPPET %%%
\version 2.11.32
triplets = \relative c'''
{
\tupletUp
\times 2/3
I use LilyPond 2.10.29 on Windows 2000.
I've long noticed that installing the GTK separately from LilyPond (as it is
needed for other programs) sometimes causes problems (and so does installing
LilyPond after installing the separate GTK).
Is it possible to get a distribution of LilyPond that
Are they hymns you're dealing with? If so, I might recommend using a template
of mine and looking at the source of some full songs, comparing it (the source)
with the music while looking for how to do certain things.
All of the articles linked from the following URL have hymns/songs made with
60 matches
Mail list logo
