Nabble - Gnu - Lilypond - Bugs

Issue 937 in lilypond: Support for right-to-left music

2009-12-17T17:40:51Z

Status: Accepted
Owner: pnorcks
Labels: Type-Enhancement Priority-Low

New issue 937 by pnorcks: Support for right-to-left music
http://code.google.com/p/lilypond/issues/detail?id=937

We have received a request from Father Gilmary to implement right-to-left
music. For background information, see

http://lists.gnu.org/archive/html/lilypond-user/2009-02/msg00634.html

Right-to-left music would help facilitate reading right-to-left scripts in
lyrics, for example.

Attached is an image of the beginning of Father Gilmary's example, with
Syriac scripts that are set right-to-left for every syllable.

The second image is an Inkscape mockup of one possibility for right-to-left
music with right-to-left script direction.

Attachments:
left-to-right.png 6.2 KB
right-to-left.png 10.6 KB

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 771 in lilypond: Instrument names should be centered accordingly to StartSystem objects in other staves

2009-12-17T16:16:42Z

Comment #7 on issue 771 by paconet.org: Instrument names should be centered
accordingly to StartSystem objects in other staves
http://code.google.com/p/lilypond/issues/detail?id=771

I can not remember who fixed it; although it has a small glitch (need of a
trial-and
error override), I'd like to pay my 40 EUR as promised.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Build error installing INFO files

2009-12-17T14:00:51Z

On Mon, Dec 14, 2009 at 9:29 PM, Pietro Cerutti <gahr@...> wrote:
> On 2009-Dec-14, 19:46, Graham Percival wrote:
>> I've been planning on changing it (again, but for the last time)
>> to "web.tely". I'll try that tomorrow, and check the buildlog for
>> any such errors. It's possible that they only show up as warnings
>> on linux?
>
> If you provide a patch I can try it out.

This might be fixed in current git, but I'm not overly optimistic.
However, the error message that you see might help.

Could you try downloading it, do the make + make doc, then store the
log for "make install" in a file? I don't need to see the log for the
make+make doc.

Cheers,
- Graham

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Fixed MIME for images on tracker

2009-12-17T13:52:57Z

On Tue, Dec 15, 2009 at 12:57 PM, Reinhold Kainhofer
<reinhold@...> wrote:
> Am Dienstag, 15. Dezember 2009 21:41:01 schrieb Patrick McCarty:
>>
>> It appears to be the age of the example. None of the images posted in
>> 2006 display inline, for example.
>
> Yes, the cutoff date seems to be September 25 to 26, 2007. Images posted
> earlier are not displayed inline, later images are. I've posted a comment to
> that bug for the google support category, so maybe they can explain what is
> wrong or what we can do about it...

Someone requested to open a new issue, so I reported it here:

http://code.google.com/p/support/issues/detail?id=3425

Thanks,
Patrick

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

horizontal alignment of dynamics attached to skips

2009-12-17T13:14:48Z

With the new Dynamics context for PianoStaff, the recommended way is to attach
the dynamics to skips in the Dynamics context... Unfortunately, dynamics
attached to a skip and dynamics attached to actual notes are differently
aligned: s\p results in the \p being far further to the left than in c\p.

Attached is an example.

Is there any way to make lilypond use the same horizontal position for s\p and
c\p ???

Cheers,
Reinhold
--
------------------------------------------------------------------
Reinhold Kainhofer, reinhold@..., 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

[dynamics_alignment.ly]

\version "2.13.8" mm = \relative c'' { c2 c c c c} dd = \notemode { s2\f s s\p s s\f } md = \relative c'' {c2\f c c\p c c\f } \score { \new PianoStaff << % That's how the pp should be aligned horizontally: \new Staff \md % Unfortunately, attaching the dynamics to skips will position them too far to the left: \new Staff << \mm \dd >> % With the new Dynamics context, unfortunately, attaching dynamics to skips % is the default, resulting in ugly dynamics position (i.e. dynamics touching % the bar line!) \new Staff \mm \new Dynamics \dd >>}

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

dynamics_alignment.pdf (37K) Download Attachment

Re: #852 - stop google from indexing old docs

2009-12-17T12:55:03Z

On Wed, Dec 16, 2009 at 09:07:20PM -0800, Mark Polesky wrote:
> Should I add an item to the Major release checklist about
> this? See the attached patch.

Yes please. In general, feel free to dump anything that seems
potentially useful into the CG. If it's a section aimed at
newbies (like CG 1), then a bit more caution is appropriate, but
for the later stuff, add first and ask questions later. :)

Cheers,
- Graham

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 787 in lilypond: script stack order fails with 2 more notes

2009-12-17T11:47:56Z

Updates:
Status: Fixed
Labels: -Fixed_2_13_9 fixed_2_13_9

Comment #8 on issue 787 by pnorcks: script stack order fails with 2 more
notes
http://code.google.com/p/lilypond/issues/detail?id=787

(No comment was entered for this change.)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 771 in lilypond: Instrument names should be centered accordingly to StartSystem objects in other staves

2009-12-17T11:43:49Z

Comment #6 on issue 771 by pnorcks: Instrument names should be centered
accordingly to StartSystem objects in other staves
http://code.google.com/p/lilypond/issues/detail?id=771

Neil, is this fixed now?

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 846 in lilypond: copyright years for manuals

2009-12-17T07:25:14Z

Updates:
Status: Fixed

Comment #3 on issue 846 by markpolesky: copyright years for manuals
http://code.google.com/p/lilypond/issues/detail?id=846

(No comment was entered for this change.)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 909 in lilypond: Redundant \consists produce a segfault

2009-12-17T00:33:38Z

Updates:
Status: Fixed
Labels: fixed_2_13_10

Comment #4 on issue 909 by pnorcks: Redundant \consists produce a segfault
http://code.google.com/p/lilypond/issues/detail?id=909

(No comment was entered for this change.)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 909 in lilypond: Redundant \consists produce a segfault

2009-12-17T00:18:23Z

Updates:
Status: Started

Comment #3 on issue 909 by pnorcks: Redundant \consists produce a segfault
http://code.google.com/p/lilypond/issues/detail?id=909

(No comment was entered for this change.)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: #852 - stop google from indexing old docs

2009-12-16T21:07:20Z

Should I add an item to the Major release checklist about
this? See the attached patch. I'll apply it if you guys
think it's a good idea. The alternative is to write some
script that generates robots.txt, but that's beyond me.

Let me know.
- Mark

[0001-Doc-Add-robots.txt-item-to-Major-release-checklist.patch]

From d5f69c57e19af6085d071e581dbfa629c2e3a32a Mon Sep 17 00:00:00 2001 From: Mark Polesky <markpolesky@...> Date: Wed, 16 Dec 2009 20:59:48 -0800 Subject: [PATCH] Doc: Add robots.txt item to Major release checklist. --- Documentation/contributor/release-work.itexi | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/Documentation/contributor/release-work.itexi b/Documentation/contributor/release-work.itexi index 9340d5d..b1a957b 100644 --- a/Documentation/contributor/release-work.itexi +++ b/Documentation/contributor/release-work.itexi @@ -141,6 +141,13 @@ translation@@iro.umontreal.ca, mentioning lilypond-VERSION.pot - doc auto redirects to v2.LATEST-STABLE + - add these two lines to http://www.lilypond.org/robots.txt: + +@example +Disallow: /doc/v2.PREVIOUS-STABLE/ +Disallow: /doc/v2.CURRENT-DEVELOPMENT/ +@end example + News: comp.music.research -- 1.6.3.3

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 883 in lilypond: stems may collide with noteheads in tightly-spaced music

2009-12-16T16:26:07Z

Comment #2 on issue 883 by Carl.D.Sorensen: stems may collide with
noteheads in tightly-spaced music
http://code.google.com/p/lilypond/issues/detail?id=883

Further investigation causes me to believe that this behavior is caused by
the addition of skylines (see lily/note-
spacing.cc, lines 87ff).

Perhaps the stem should become part of the skyline? Or at least the stem
side of the note-column should be
identified?

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 883 in lilypond: stems may collide with noteheads in tightly-spaced music

2009-12-16T16:13:13Z

Comment #1 on issue 883 by Carl.D.Sorensen: stems may collide with
noteheads in tightly-spaced music
http://code.google.com/p/lilypond/issues/detail?id=883

It appears that the note heads are being spaced only to avoid the other
note-heads, i.e. that the stems are not
considered at all.

If the notes are close together vertically, collision avoidance kicks in;
if the notes are not close together
vertically, they're allowed to overlap, which causes the collisions with
the stems.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 697 in lilypond: Path problem on Windows

2009-12-16T15:21:14Z

Updates:
Labels: Fixed_2.12.2

Comment #4 on issue 697 by Carl.D.Sorensen: Path problem on Windows
http://code.google.com/p/lilypond/issues/detail?id=697

Everything works properly on WinXP under parallels. Double-clicking
results in a correctly-produced .pdf

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: strange vertical formatting

2009-12-16T12:17:42Z

On Wed, Dec 16, 2009 at 8:06 PM, Werner LEMBERG <wl@...> wrote:
> Do you actually expect the vertical formatting of the snippet below as
> shown in the attached PDF?

Wow. CCing to bug- just in case.

Cheers,
Valentin

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 936 in lilypond: \tempo makes TextSpanner too long

2009-12-16T10:59:33Z

Updates:
Labels: Type-Defect Priority-Medium

Comment #1 on issue 936 by lemzwerg: \tempo makes TextSpanner too long
http://code.google.com/p/lilypond/issues/detail?id=936

(No comment was entered for this change.)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 936 in lilypond: \tempo makes TextSpanner too long

2009-12-16T10:55:20Z

Status: Accepted
Owner: lemzwerg

New issue 936 by lemzwerg: \tempo makes TextSpanner too long
http://code.google.com/p/lilypond/issues/detail?id=936

\version "2.13.10"

\header { texidoc = "
A @code{\tempo} mark must not influence a @code{TextSpanner} object
within another context.

Below is a counterexample: On the right side, the spanner extends far too
much into the second bar (it should stop actually before the first note).
You get correct behaviour if you comment out the @code{\tempo} line.
" }

\score {
<< \new Staff \relative {
f4 f f f |
\tempo "Tempo I"
f4 f f f |
}

\new Dynamics {
\override TextSpanner #'(bound-details left text) = "rit."
s1\startTextSpan |
s1\stopTextSpan |
}
>>
}

% EOF

Attachments:
tempo-spanner.png 3.1 KB

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 712 in lilypond: alignment of multiple \tempo marks over `church rests'

2009-12-16T10:51:03Z

Updates:
Labels: -Priority-Low Priority-Medium

Comment #2 on issue 712 by lemzwerg: alignment of multiple \tempo marks
over `church rests'
http://code.google.com/p/lilypond/issues/detail?id=712

(No comment was entered for this change.)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: notation rhythm issue

2009-12-16T08:54:09Z

2009/12/16 isaac <thehuan@...>:
> i think this is not in the list of known bugs because i looked through it and
> didnt find it. and im not top posting (i dont know what top posting means)
>
> the problem is the length of the full bar notes. in theory, 3/4 time can have a
> semibreve as a full bar note that takes all 3 beats. lilypond correctly input my
> chord with the 3 crotchet beats into semibreves but it then interpreted the
> semibreves as 4 beats.

A 3/4 bar is filled with a dotted half, not a semibreve.

Duration for dotted half notes is two-dot as in "c2."

Full bar rests (not notes) in 3/4 or any other time signature is
always printed like a centered semibreve rest, for this write R2. in
3/4 or R1 in 4/4

--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
No le des el mando a distancia a Microsoft. No utilices Windows 7.
http://windows7sins.org

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: #852 - stop google from indexing old docs

2009-12-16T08:05:30Z

Han-Wen Nienhuys wrote:

> On Wed, Dec 16, 2009 at 6:59 AM, Graham Percival
> <graham@...> wrote:
>
>
>>> Disallow: /doc/v1.9/
>>>
>> Huh, I didn't reliaze we kept the old unstable directories around;
>> they're not listed on
>> http://lilypond.org/documentation
>> anybody mind if I delete the unstable doc dirs?
>>
>
> IIRC it is a symlink to the 2.0 documentation. We dont remove it to
> not break other people's links gratuitiously.
>

That's a good point. There are probably many links to the old unstable
docs in the mailing list archives and even though the information often
is not fully appropriate for the current versions, looking at the
corresponding page in the old manual will provide a useful link on where
to look in the current docs.

/Mats

--
=============================================
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: mats.bengtsson@...
WWW: http://www.s3.kth.se/~mabe
=============================================

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: #852 - stop google from indexing old docs

2009-12-16T07:30:53Z

Graham Percival wrote:
> True, although it would be simple to have
> doc/stable/
> doc/devel/
> doc/archive/

That's better.

> Oh, we'll keep the stable docs. I just don't think the
> old *unstable* docs are worth having online.

Is it really such a burden to keep the old docs on the
lilypond.org server? Why the desire to remove them? It's
really not a huge thing to me, so I don't want to argue too
much about it. Just curious.

Also, I looked at the new robots.txt and I have one comment.
These lines are all unnecessary (redundant):

Disallow: /doc/v2.0/Documentation/user/out-www/lilypond/source
Disallow: /doc/v2.0/Documentation/user/out-www/source
Disallow: /doc/v2.2/Documentation/user/out-www/lilypond/source
Disallow: /doc/v2.2/Documentation/user/out-www/source
Disallow: /doc/v2.4/Documentation/user/out-www/lilypond/source
Disallow: /doc/v2.4/Documentation/user/out-www/source
Disallow: /doc/v2.5/Documentation/user/out-www/lilypond/source
Disallow: /doc/v2.5/Documentation/user/out-www/source
Disallow: /doc/v2.5/Documentation/user/out-www/music-glossary/source

...as long as the following lines are there:

Disallow: /doc/v2.0/
Disallow: /doc/v2.2/
Disallow: /doc/v2.4/
Disallow: /doc/v2.5/

- Mark

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Some "Cheat cheet" nitpicks

2009-12-16T07:25:08Z

> If the makefile sets it to 0mm, then what happens for longer
> examples with bar numbers? Presumably somebody needs to go through
> all the docs to find multi-line examples, then add
> [left-padding=3mm]
> to those examples.

Exactly. However, in most multi-line examples of the lilypond
documentation the right thing to do IMHO is to remove bar numbers,
too.

> This is too much work for not enough payoff. Especially since (I
> think) a one-line patch to the C file that Sven identified would
> render this work unnecessary.

Regardless of the difficulty or (simplicity) to implement this in the
lilypond binary, I'm not sure whether this is a good idea at all. The
left padding is a kind of metadata since you need some context to
align to. In other words, a call to the lilypond binary can't find
the right left padding value of a snippet.

Werner

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: #852 - stop google from indexing old docs

2009-12-16T07:12:50Z

On Wed, Dec 16, 2009 at 6:59 AM, Graham Percival
<graham@...> wrote:

>> Disallow: /doc/v1.9/
>
> Huh, I didn't reliaze we kept the old unstable directories around;
> they're not listed on
> http://lilypond.org/documentation
> anybody mind if I delete the unstable doc dirs?

IIRC it is a symlink to the 2.0 documentation. We dont remove it to
not break other people's links gratuitiously.

--
Han-Wen Nienhuys - hanwen@... - http://www.xs4all.nl/~hanwen

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Some "Cheat cheet" nitpicks

2009-12-16T07:06:48Z

Graham Percival <graham@...> writes:

> On Wed, Dec 16, 2009 at 2:02 PM, Werner LEMBERG <wl@...> wrote:
>>>> The best solution is probably to add a new command line option
>>>> `--default-left-padding' to lilypond-book (which is then used in
>>>> the Makefile with value 0mm to override the default setting of
>>>> 3mm), and adding a snippet option `left-padding' to the lilypond
>>>> environments (within lilypond-book) to override the default left
>>>> padding if necessary.
>>>
>>> No. We're not adding that option to 90% of the snippets in the
>>> docs. It can't be done automatically, and it's way too much work to
>>> do it manually.
>>
>> ??? I've just suggested the `--default-left-padding' option to
>> exactly avoid that! Ideally, we would simply change the default value
>> of lilypond-book's `--left-padding' option to 0mm, but this breaks
>> backwards compatibility. Thus my suggestion to have a means to
>> control the default value instead.
>
> If the makefile sets it to 0mm, then what happens for longer examples
> with bar numbers? Presumably somebody needs to go through all the
> docs to find multi-line examples, then add
> [left-padding=3mm]
> to those examples.
>
> This is too much work for not enough payoff. Especially since (I
> think) a one-line patch to the C file that Sven identified would
> render this work unnecessary.

It is common to have the first line of multiple lines indented and
adjusted (they look like paragraphs essentially), but it makes little
sense to indent single lines. In particular if you interchange single
lines with text, or treat them as inline material.

So it might be nice to be able to specify special padding/adjustment for
single-line formatting. If there was a way to find out post-fact what
kind of formatting was actually employed for any snippet, this might
also be nice. But one can probably guess somewhat reliably by checking
the width of the result.

--
David Kastrup

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Some "Cheat cheet" nitpicks

2009-12-16T06:21:50Z

On Wed, Dec 16, 2009 at 2:02 PM, Werner LEMBERG <wl@...> wrote:

>>> The best solution is probably to add a new command line option
>>> `--default-left-padding' to lilypond-book (which is then used in
>>> the Makefile with value 0mm to override the default setting of
>>> 3mm), and adding a snippet option `left-padding' to the lilypond
>>> environments (within lilypond-book) to override the default left
>>> padding if necessary.
>>
>> No. We're not adding that option to 90% of the snippets in the
>> docs. It can't be done automatically, and it's way too much work to
>> do it manually.
>
> ??? I've just suggested the `--default-left-padding' option to
> exactly avoid that! Ideally, we would simply change the default value
> of lilypond-book's `--left-padding' option to 0mm, but this breaks
> backwards compatibility. Thus my suggestion to have a means to
> control the default value instead.

If the makefile sets it to 0mm, then what happens for longer examples
with bar numbers? Presumably somebody needs to go through all the
docs to find multi-line examples, then add
[left-padding=3mm]
to those examples.

This is too much work for not enough payoff. Especially since (I
think) a one-line patch to the C file that Sven identified would
render this work unnecessary.

Cheers,
- Graham

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: notation rhythm issue

2009-12-16T06:05:49Z

Please read again in the Learning Manual on how to specify durations. In
your example, you ask LilyPond to let each chord have a duration that
equals 4/3 of a crotchet (since 1 means whole note = 4/1 crotchets, 2
means halft note = 4/2 crotchets, 8 means minim = 4/8 crotchets, and so
on. Just replace "3" by "2." and you get what I think you want.

/Mats

isaac wrote:

> i think this is not in the list of known bugs because i looked through it and
> didnt find it. and im not top posting (i dont know what top posting means)
>
> the problem is the length of the full bar notes. in theory, 3/4 time can have a
> semibreve as a full bar note that takes all 3 beats. lilypond correctly input my
> chord with the 3 crotchet beats into semibreves but it then interpreted the
> semibreves as 4 beats.
>
> version "2.12.0"
> { \clef bass \key f\major \time 3/4
> < f,, f, >3~
> < f,, f, >3~
> < f,, f, >3~
> < f,, f, >3~
> < f,, f, >3~
> }
>
> hope this helps you and me :)
>
> thanks
>
> isaac
>
>
>
> _______________________________________________
> bug-lilypond mailing list
> bug-lilypond@...
> http://lists.gnu.org/mailman/listinfo/bug-lilypond
>

--
=============================================
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: mats.bengtsson@...
WWW: http://www.s3.kth.se/~mabe
=============================================

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Some "Cheat cheet" nitpicks

2009-12-16T06:02:00Z

> It's part of the lilypond binary (or scheme functions) itself, not
> lilypond-book.

OK.

>> The best solution is probably to add a new command line option
>> `--default-left-padding' to lilypond-book (which is then used in
>> the Makefile with value 0mm to override the default setting of
>> 3mm), and adding a snippet option `left-padding' to the lilypond
>> environments (within lilypond-book) to override the default left
>> padding if necessary.
>
> No. We're not adding that option to 90% of the snippets in the
> docs. It can't be done automatically, and it's way too much work to
> do it manually.

??? I've just suggested the `--default-left-padding' option to
exactly avoid that! Ideally, we would simply change the default value
of lilypond-book's `--left-padding' option to 0mm, but this breaks
backwards compatibility. Thus my suggestion to have a means to
control the default value instead.

Werner

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 854 in lilypond: lilycontrib.tcl

2009-12-16T05:50:22Z

Comment #7 on issue 854 by percival.music.ca: lilycontrib.tcl
http://code.google.com/p/lilypond/issues/detail?id=854

BTW, does anybody other than Carl feel like taking it over? Mark,
maybe? :)

I think version 0.5 is actually a step back from the previous one (where it
just had
a check-box for 'translator or not'). I propose:

- have a variable at the top of the script; IS_TRANSLATOR = 0 / 1 (or
true/false,
or whatever the format of this language is).

- we distribute two versions of the script; one for translators, one for
normal
contributors. The only difference between the two scripts is that single
global
variable at the top of the script. Yes, this means that we "waste" 6.7 Kb
of web
hosting space. Cry me a river.

- inside the script, instead of having:
button .buttons.patch -text "Make patch from origin" -command
patch_from_origin
button .buttons.patch_translation -text "Make translation patch from
origin" -co
we have:
if (IS_TRANSLATOR)
button .buttons.patch_translation -text "Make translation patch from
origin" -co
else
button .buttons.patch -text "Make patch from origin" -command
patch_from_origin
endif

(or whatever the syntax is)

Now some nitpicks:
- can the commit/abort/etc buttons be greyed-out if the user hasn't
initialized yet?

- if/when the split between normal+translation is done, could the update
button just
be "initalize code" or "update code" ? I think short+sweet is better.

- generally, catch errors: for example, clicking "locally commit changes"
when no
changes are done will pop up a window saying "git aborted: child process
exited
abnormally".

- after a few random clicks, attempting to "abort changes - revert to
origin" (the
panic button" produces:
abort_dir: ./aborted_edits
fatal: unable to create '/home/gperciva/lilypond/.git/index.lock': File
exists
fatal: Could not reset index file to revision 'origin/master'.
Repository reset.
that's highly sub-optimal; the "nuke them all from orbit, it's the only
way to be
sure" button should always work.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: #852 - stop google from indexing old docs

2009-12-16T05:29:10Z

On Wed, Dec 16, 2009 at 1:24 PM, Mats Bengtsson
<mats.bengtsson@...> wrote:
>
> Graham Percival wrote:
>>
>> Note that if anybody wants to do serious archeological work, they
>> can just grab git
>
> Yes!

Is this a vote in favor of removing the v1.9 docs from the website,
and leaving v1.8 and v2.0 online?

>> and compile whatever version they want.
>>
>
> Probably not, because of incompatibilities with current versions of Python,
> Guile, GCC, ...

If somebody is *serious* about the archeology of open-source projects,
they'll have a bunch of boxes with cira-1994, 1995, 1996, 1997, etc.
development tools installed. :)

No, I haven't heard of anybody doing such work yet, but I could
imagine that within the next 50 years some sociologist or historian or
whatever might be digging through old mailist archives and tracking
changes to git and whatnot. I've seen weirder PhD thesis projects.

Cheers,
- Graham

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: #852 - stop google from indexing old docs

2009-12-16T05:24:23Z

Graham Percival wrote:
>
> Note that if anybody wants to do serious archeological work, they
> can just grab git
Yes!
> and compile whatever version they want.
>
Probably not, because of incompatibilities with current versions of
Python, Guile, GCC, ...

/Mats

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 845 in lilypond: AUTHORS / THANKS should be integrated into new website

2009-12-16T04:05:55Z

Updates:
Status: Fixed

Comment #3 on issue 845 by percival.music.ca: AUTHORS / THANKS should be
integrated into new website
http://code.google.com/p/lilypond/issues/detail?id=845

... and now finished it. I've changed the topdocs AUTHORS to use the new
file.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 846 in lilypond: copyright years for manuals

2009-12-16T04:00:38Z

Updates:
Labels: -Type-Other Type-Documentation

Comment #2 on issue 846 by percival.music.ca: copyright years for manuals
http://code.google.com/p/lilypond/issues/detail?id=846

Mark started this.

I'm (re)defining Type-Documentation as "anything that can be done by editing
texi/tely files".

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 815 in lilypond: Enhancement: AJAX-powered search auto-completion for the online documentation

2009-12-16T03:56:31Z

Updates:
Labels: -Type-Documentation Type-Other

Comment #2 on issue 815 by percival.music.ca: Enhancement: AJAX-powered
search auto-completion for the online documentation
http://code.google.com/p/lilypond/issues/detail?id=815

Lining this up with the other webpage-related stuff.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 869 in lilypond: input/regression/ renaming to regression/

2009-12-16T03:52:30Z

Updates:
Labels: -Type-Defect Type-Other

Comment #1 on issue 869 by percival.music.ca: input/regression/ renaming to
regression/
http://code.google.com/p/lilypond/issues/detail?id=869

(No comment was entered for this change.)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond