On Thu, 2004-07-22 at 16:24, Han-Wen Nienhuys wrote:
> I would not base anything on the chord name itself (ie. the output
> string). Systems for chord names are highly non-standard, so they're
> not a good basis to interpret. I suppose that you would have to
> devise some kind of lookup structure
On Fri, 2004-07-23 at 10:06, [EMAIL PROTECTED] wrote:
> As I said before, I really do love the quality of Lilypond output. So I hope
> you'll take this in the spirit it's intended: observations from a domain
> expert
> that may or may not be useful to you in the future.
>
Thanks for the input. I'
* Han-Wen Nienhuys ([EMAIL PROTECTED]) wrote:
> It will require some hacking to get page layout done correctly within
> a Texinfo book format.
I actually meant to put just the code, without the result. I think
that it should be enough for this section. OTOH a page showing
graphically all page lay
[EMAIL PROTECTED] writes:
> * Han-Wen Nienhuys ([EMAIL PROTECTED]) wrote:
> > they should be renamed to bottommargin.
> >
> > or you can do
> >
> > #(define bottom-margin (* 2 cm))
>
> thanks! should/can I change the names in the manual?
yes.
> (and maybe put > and example)
It will require
* Han-Wen Nienhuys ([EMAIL PROTECTED]) wrote:
> they should be renamed to bottommargin.
>
> or you can do
>
> #(define bottom-margin (* 2 cm))
thanks! should/can I change the names in the manual? (and maybe put
and example)
Pedro
___
lilypond-dev
[EMAIL PROTECTED] writes:
> * Han-Wen Nienhuys ([EMAIL PROTECTED]) wrote:
> > > How about making top-margin and bottom-margin available as a variable
> > > to be defined in "\paper" as well? It would also be terrific to have
> > > things like left-margin and right-margin.
>
> actually I just saw t
* Han-Wen Nienhuys ([EMAIL PROTECTED]) wrote:
> > How about making top-margin and bottom-margin available as a variable
> > to be defined in "\paper" as well? It would also be terrific to have
> > things like left-margin and right-margin.
actually I just saw that the manual for 2.3.7 says that top
