[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1691 in lilypond: Ugly bars in PDF documents
From: |
Reinhold Kainhofer |
Subject: |
Re: Issue 1691 in lilypond: Ugly bars in PDF documents |
Date: |
Sat, 20 Aug 2011 13:18:23 +0200 |
User-agent: |
KMail/1.13.6 (Linux/2.6.38-10-generic; KDE/4.7.0; i686; ; ) |
Am Saturday, 20. August 2011, 06:25:26 schrieben Sie:
> Comment #41 on issue 1691 by percival.music.ca: Ugly bars in PDF documents
> http://code.google.com/p/lilypond/issues/detail?id=1691
>
> Trevor reminded us (by email) that lilypond automatically sets
> ragged-right=##t if the music is less than a full line. This might be the
> behavior Reinhold was seeing. If he was seeing it in a different context,
> then this sounds like another bug. There's no reason why relative=1 should
> imply ragged-right.
No, it was not the implicit ragged setting for one-line snippets. Rather, the
snippets' ly files have an exmplicit
ragged-right=##t
inserted.
The issue is that the relative snippet option implies the fragment option,
which seems to set the ragged-right=##t in all its snippets...
Attached is a simple example to show this, using three snippets with identical
contents, but different snippet options. The first snippet will not have
ragged-right, but the other two will get an explicit ragged-right=##t in the
snippet's .ly file. While this behavior is indirectly explained in the AU, it
does not really make sense from a user's standpoint that relative should
automatically imply ragged-right (having "fragment" imply ragged-right makes
sense to make it easier for documentation writers....)
This deserves a bug report on its own.
To be honest, the whole snippet option handling seems to be a real mess right
now. I'll probably take a look at the whole snippet options handling system in
lilypond-book during the next few days. Probably we can properly analyze each
option's effects and make them more predictable (and correct).
Cheers,
Reinhold
--
------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
* Financial & Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
lybook-relative-ragged.tely
Description: Text document
- Re: Issue 1691 in lilypond: Ugly bars in PDF documents, (continued)
- Message not available
- Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 2011/08/13
- Message not available
- Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 2011/08/13
- Message not available
- Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 2011/08/19
- Message not available
- Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 2011/08/19
- Message not available
- Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 2011/08/19
- Message not available
- Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 2011/08/19
- Message not available
- Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 2011/08/19
- Message not available
- Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 2011/08/20
- Re: Issue 1691 in lilypond: Ugly bars in PDF documents, Trevor Daniels, 2011/08/19
- Re: Issue 1691 in lilypond: Ugly bars in PDF documents, Reinhold Kainhofer, 2011/08/20
Re: Issue 1691 in lilypond: Ugly bars in PDF documents,
Reinhold Kainhofer <=