Laura Conrad wrote:
Mats> You have to add the following to your file (it should
Mats> probably be there by default):
Mats> \layout{
Mats> ...
Mats> \context{
Mats>\PianoStaff
Mats>\accepts "FiguredBass"
Mats> }
Mats> }
Thanks, that works. I agree that it sho
> "Mats" == Mats Bengtsson <[EMAIL PROTECTED]> writes:
Mats> Laura Conrad wrote:
>>> "Mats" == Mats Bengtsson <[EMAIL PROTECTED]> writes:
>>>
>>>
>>
Mats> If you place the \figures{...} before the bass part in the
Mats> \score{...} block, it will be
Laura Conrad wrote:
"Mats" == Mats Bengtsson <[EMAIL PROTECTED]> writes:
Mats> If you place the \figures{...} before the bass part in the
Mats> \score{...} block, it will be printed above it.
This is true if you aren't using a \context PianoStaff. When I put
that in to ge
> "Mats" == Mats Bengtsson <[EMAIL PROTECTED]> writes:
Mats> If you place the \figures{...} before the bass part in the
Mats> \score{...} block, it will be printed above it.
This is true if you aren't using a \context PianoStaff. When I put
that in to get the curly brackets, it all
If you place the \figures{...} before the bass part in the \score{...}
block,
it will be printed above it. However, you may also want to use
\override BassFigureAlignment #'stacking-dir = #UP
/Mats
anders stenberg wrote:
Hi!
Any easy way to get figures on top of Bass part in figuredbass no
Hi!
Any easy way to get figures on top of Bass part in figuredbass not
below as seems to be default? using Lily 2.8.4
Anders Stenberg
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
On Tue, 07 Jun 2005 12:46:27 +0200
Mats wrote:
>
> I would claim that this idea clearly has influenced the design
> of LilyPond from the first version. You can set parameters to
> determine the layout in the \layout{...} block.
> However, there will always be special cases where the automatic
> l
Aaron Mehl wrote:
continued from preious email that yahoo sent
accidently before I finished :(
If a structural wish list was allowed however here
is
what I would want.
1. A real separation of content and formatting.
This means that a lilypond file would have no
formatting in it at
Aaron Mehl wrote:
Ok I am now getting both unconfused and confused.
But both paper and layout deal with layout.
Up to version 2.2, page layout and score layout was all
lumped together into \paper{...}. Now, there's more
structure to it. The intuitive notion is that \paper{...}
only deals wi
On 6-Jun-05, at 11:08 PM, Aaron Mehl wrote:
1. A real separation of content and formatting.
This means that a lilypond file would have no
formatting in it at all. A seperate style sheet would
be the place for this. The advantage is that if you
have style tweaks for multiple docs only one
Also, to get a nice overview of the changes from version 2.2 to 2.4,
please read the NEWS file for version 2.4:
http://lilypond.org/doc/v2.4/Documentation/topdocs/out-www/NEWS.html
Also, it may be worth to look at the printouts from
convert-ly -s
/Mats
Mats Bengtsson wrote:
On Sat, 4 Jun 2005
continued from preious email that yahoo sent
accidently before I finished :(
> If a structural wish list was allowed however here
> is
> what I would want.
>
> 1. A real separation of content and formatting.
This means that a lilypond file would have no
formatting in it at all. A seperat
Well,
I did some testing and lilypond doesn't like nesting
but it produces output in some instances.
What I get from this and the more pictures thread is
that some rules and I mean rules would help the
beginner.
ie this is how you build a vocal score, a piano score
etc.
would ease the entry to
Ok I am now getting both unconfused and confused.
But both paper and layout deal with layout.
I see that structure in lilypond is not a
documentation structure. ie a programmers structure.
If I were to build a document I would have formatting
for the page or the entire document and formatting
On Sat, 4 Jun 2005, Graham Percival wrote:
>
> On 4-Jun-05, at 4:31 PM, Aaron Mehl wrote:
>
> > So am I able to generalize from this that layout
> > replaces paper (you said not and the docs still say
> > that paper is still in?)
>
> There is currently a \paper{} and \layout{}. I really don't
> I don't know. I don't write music with lyrics.
> Let's look at the
> docs... Instrument-specific notation -> Vocal music.
Why not look a lyrics which is what I did and I got
the following: And I couldn't figure out where to put
it because I go an x =y situation again. Remember you
know where
On 4-Jun-05, at 4:31 PM, Aaron Mehl wrote:
So am I able to generalize from this that layout
replaces paper (you said not and the docs still say
that paper is still in?)
There is currently a \paper{} and \layout{}. I really don't
want to talk about anything that happened before 2.4, because
I
Hi Graham and list,
I did as you said and did a convert-ly on the file.
it basically replaced paper with layout and removed
the notes block but I see a second set of brackets.
--
\version "2.2.0"
\header{
title = "Zachrenu"
poet = "
On 4-Jun-05, at 12:47 PM, Aaron Mehl wrote:
So in the 2.4 series lilypond I was eventually able to
create my own template. Still I was never exactly sure
why it worked and others I tried didn't...
Why can't you use your 2.4 scores in 2.5? You might need
to update them with convert-ly, but the
Well this seems to imply: "forget being able to build
a lilypond file from scratch, you must start from a
template or all is lost."
Infact for the majority of my Lilypond experience I
relied on templates for creating scores.
What this did was limit my ability to make a score do
exactly what I wan
On Thursday 02 June 2005 05:56 pm, Erik Ronström wrote:
> | I see what you are saying but I still say a clearly defined
> | and enforced structure would make the entry into lilypond
> | much and mean much easier to the newbie.
>
> I agree completely! IMHO, this is the single most annoying thing ab
BTW,
for those late to this thread, my intention is not to
bash either lilypond or the docs.
Rather I am taking upon myself to write the section
file structure.
I however need to understand it. By that I mean not
from a programmers standpoint but the end user.
So that once I can setup from scr
| I see what you are saying but I still say a clearly defined
| and enforced structure would make the entry into lilypond
| much and mean much easier to the newbie.
I agree completely! IMHO, this is the single most annoying thing about
lilypond: the lack of a (obvious-to-the-user) uniform structur
| I see what you are saying but I still say a clearly defined
| and enforced structure would make the entry into lilypond
| much and mean much easier to the newbie.
I agree completely! IMHO, this is the single most annoying thing about
lilypond: the lack of a (obvious-to-the-user) uniform structur
--- Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> For me it's the opposite. I find it much harder to
> see
> the structure if you only have a long \score{...}
> where
> I have to scroll several pages from beginning to
> end.
Well if I take docbook as an example a book can have
multiple sections
Aaron Mehl wrote:
Ok here is where I am confused. There is a structure
for files which makes a file valid.
Then there is a grammar which must also be followed
for the lanuguage of lilypond.
I get the feeling after reading the docs that the
structure of lilypond is loose.
What I mean is that
Ok here is where I am confused. There is a structure
for files which makes a file valid.
Then there is a grammar which must also be followed
for the lanuguage of lilypond.
I get the feeling after reading the docs that the
structure of lilypond is loose.
What I mean is that it appear (if I am no
(Graham, or someone else, we should really try to make sure that
all commands and reserved words available in LilyPond are listed
in the Index. \layout is one of those missing. Doing such an exercise
would also help identifying what information is missing from the manual
today.)
Part of an answer
Hi all,
In a previous email I asked if layout replaced paper.
I was told to look at outputs, which I did. The paper
output section details \paper{}
but I see no mention of \layout {}
where in the docs is \layout discussed?
Thanks
Aaron
__
Do Yo
29 matches
Mail list logo
