lilypond-devel
[Top][All Lists]
Advanced

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

bad TeX patch


From: Han-Wen Nienhuys
Subject: bad TeX patch
Date: Sat, 21 Sep 2002 22:48:25 +0200

address@hidden writes:
> 
> This patch in tex.scm:
> 
> -    (string-append "%\n\\EndLilyPondOutput\n"
> +    (string-append "%\n\\endgroup\\EndLilyPondOutput\n"
> 
> -   "\\turnOnPostScript\n"))
> +   "\\turnOnPostScript\\begingroup\\parindent0pt\n"))
>  
> is really bad IMHO.  Setting indentation unconditionally in lilypond
> output makes it impossible to control \parindent one level higher
> (for example, to indent a multi-system example).
> 
> It seems that Han-Wen has added this patch for lazyness only to make
> `tex <lilypond output>' work better.  I can understand the wish to
> make lilypond output compile directly without writing a wrapper
> document, but the above change is the wrong way.  If you agree, I
> write some code so that `latex <lilypond output>' works out of the
> box.

I think that parindent is not the proper mechanism for indenting
musical examples, they're not paragraphs after all. The separate
first-line indent for music can not be controlled from (la)tex anyway,
and for indenting all pieces of music, there are other
options. (eg. plaintex \narrower, if memory serves me.).  OTOH, I'll
settle for latex <output>.  I had to do something, otherwise HTML
output is completely messed up.


--
Han-Wen Nienhuys   |   address@hidden   |   http://www.cs.uu.nl/~hanwen 




reply via email to

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