lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: subsubsection lilypondfile


From: Mats Bengtsson
Subject: Re: subsubsection lilypondfile
Date: Fri, 22 Apr 2005 09:58:25 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414

This is really a LaTeX question that has nothing to do with
LilyPond per se. I'd recommend the book "The LaTeX Companion" by
Goossens et al. or some other book on advanced LaTeX issues.
There you will, for example, learn how to redefine the layout of
sections or subsubsections or whatever to continue on the same line
as the title instad of issuing a new line. As an alternative, I
have already mentioned the enumerate environment. If you use the
package called "enumerate", then you can easily modify the layout
of the enumerate numbering to fit any needs.

   /Mats

David Raleigh Arnold wrote:
On Thursday 21 April 2005 07:48 am, you wrote:

Bernard Hurley wrote:

You are right there are restrictions on what can go in a section

header

which is why I said in a previous e-mail that this \section and
\subsection etc macros might need to be re-defined.

Your solution does not work for a multi-line score because you don't
want all the lines in the same savebox. Also the section number

appears

in the "wrong place" in a multi-staff score - in line with the

bottom

staff.

On the other hand, why would you ever want a multi-line score
in a section title?


Might have fifty sight reading exercises.

One could have music as subsubsections below subsection headings, which would
be useful in docs of many kinds.  daveA


--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
        Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================




reply via email to

[Prev in Thread] Current Thread [Next in Thread]