lilypond-user
[Top][All Lists]
Advanced

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

RE: lilypond-book and DIN A4 ?!?


From: Georg Dummer
Subject: RE: lilypond-book and DIN A4 ?!?
Date: Tue, 2 Aug 2005 09:27:16 +0200

Here is an example that demonstrates the problem. Commenting out the
linewidth in the *.ly-file only places the last systems the right way.
Because this problem was already discussed here I abstained from sending the
code.
But maybe there is a better solution.

Georg

-----Original Message-----
From: Mats Bengtsson [mailto:address@hidden 
Sent: Monday, August 01, 2005 4:18 PM
To: Georg Dummer
Cc: lilypond-user
Subject: Re: lilypond-book and DIN A4 ?!?

As far as I can see, the \begin{flushright} doesn't solve anything as long
as you let lilypond-book determine the line width of the scores, since they
will be rather too long then too short (see my email to bug-lilypond a few
minutes ago).
However, if you explicitly set the line width of the music examples to be
shorter than the line width of the remaining LaTeX document, then it makes
sense to use something like what you propose to work around these bugs.

Since you haven't provided any complete example including both LaTeX and
LilyPond code, it's a bit hard to realize exactly what problems you try to
solve.

    /Mats

Georg Dummer wrote:
> This is my newest achievement:
> 
> \newcommand{\preLilyPondExample}{\begin{flushright}}
> \newcommand{\betweenLilyPondSystem}[1]{\hfill} % maybe not needed     
> \newcommand{\postLilyPondExample}{\end{flushright}}
> 
> This also gives acceptable results if you have set the instrument 
> name. In this case the first system (eps-picture) normaly has a 
> different width than the onthers.
> 
> Georg
> 
> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden 
> On Behalf Of Mats Bengtsson
> Sent: Monday, August 01, 2005 10:01 AM
> To: Martin Brodbeck
> Cc: address@hidden
> Subject: Re: lilypond-book and DIN A4 ?!?
> 
> As has been stated before: As long as you don't specify the line width 
> (or paper size) within the actual .ly code, there should be no need to 
> use this workaround.
> 
>     /Mats
> 
> Martin Brodbeck wrote:
> 
>>Graham Percival schrieb:
>>
>>
>>>Known issue; please search the lilypond-user and bug-lilypond mailist 
>>>archives for discussion and workarounds.
>>>(it was probably discussed on lilypond-devel as well)
>>
>>
>>After a third watch at lilypond-user I found a workaround:
>>"\newcommand{\betweenLilyPondSystem}[1]{\linebreak}" in the preamble 
>>of the LaTeX document fixes the issue.
>>
>>Thanks,
>>Martin
>>
>>
>>_______________________________________________
>>lilypond-user mailing list
>>address@hidden
>>http://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> --
> =============================================
>       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
> =============================================
> 
> 
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> 
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-user

--
=============================================
        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
=============================================

Attachment: test.lytex
Description: Binary data

Attachment: MeineEngenGrenzen.ly
Description: Text Data


reply via email to

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