Re: Documentation typo?

2006-03-15 Thread Graham Percival
On 15-Mar-06, at 12:51 PM, Geoff Horton wrote: 2.7.38, section 10.1.2 (p. 234 of the PDF): "A number of \scores creates a single output file, where all movement are concatenated." should probably read "where all movements are" Thanks, fixed (and also re-worded). - Graham ___

Re: Documentation clarification?

2006-03-15 Thread Graham Percival
On 15-Mar-06, at 5:21 PM, Geoff Horton wrote: (Sorry to keep hammering on the docs--I'm working on a project that requires me to look at them closely and I keep finding stuff.) No, please keep these coming! They're great. :) BTW, I respond to each email individually so that somebody search

Re: Documentation bug?

2006-03-15 Thread Graham Percival
On 15-Mar-06, at 12:45 PM, Geoff Horton wrote: 2.7.38, section 9.2.7. The first thing discussed here in the 2.6 documentation ... point still begins "Another difficult adjustment . . . ", when no difficult adjustments have yet been mentioned. Thanks, fixed! - Graham

Documentation clarification?

2006-03-15 Thread Geoff Horton
(Sorry to keep hammering on the docs--I'm working on a project that requires me to look at them closely and I keep finding stuff.) 2.7.38, section 8.2.8, dealing with different editions and the \tag command: Toward the bottom of the section (p. 196 of the PDF), right above "See Also", it says: "T

Re: caps font shape not working

2006-03-15 Thread Han-Wen Nienhuys
Nicolas Sceaux wrote: Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: Mats Bengtsson wrote: Looks like a bug! I forward it to bug-lilypond. I fixed it on the Lily side, by adding 'caps shape to font.scm, but you also have to have a Small-caps font available to Pango. Probably the best option

Re: caps font shape not working

2006-03-15 Thread Nicolas Sceaux
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > Mats Bengtsson wrote: >> Looks like a bug! I forward it to bug-lilypond. > > I fixed it on the Lily side, by adding 'caps shape to font.scm, but > you also have to have a Small-caps font available to Pango. > > Probably the best option is to remove th

Re: 2.7.38 bug: proportional duration beaming of 32nds and greater

2006-03-15 Thread Trevor Bača
On 3/15/06, Trevor Bača <[EMAIL PROTECTED]> wrote: > On 3/15/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: > > Trevor Bača wrote: > > > On 3/15/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: > > > > > >>Trevor Bača wrote: > > >> > > >>>This is a weird one. If you have the following three conditi

Error in placement of rehearsal marks

2006-03-15 Thread Alan Stern
Later versions of Lilypond exhibit this same problem, but at the moment I can only test on 2.7.33. Rehearsal marks sometimes get placed incorrectly. Normally they are centered over the bar line or the clef symbol (at the beginning of a line), but sometimes they get placed farther to the left.

Documentation typo?

2006-03-15 Thread Geoff Horton
2.7.38, section 10.1.2 (p. 234 of the PDF): "A number of \scores creates a single output file, where all movement are concatenated." should probably read "where all movements are" ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org

Documentation bug?

2006-03-15 Thread Geoff Horton
2.7.38, section 9.2.7. The first thing discussed here in the 2.6 documentation was how to change one element in a group, a process made much easier by the introduction of the \tweak command (thanks!). The relevant material has been moved into a new section, but the material now promoted to the firs

Re: caps font shape not working

2006-03-15 Thread Graham Percival
On 15-Mar-06, at 4:48 AM, Han-Wen Nienhuys wrote: Mats Bengtsson wrote: Looks like a bug! I forward it to bug-lilypond. I fixed it on the Lily side, by adding 'caps shape to font.scm, but you also have to have a Small-caps font available to Pango. Probably the best option is to remove the

Re: 2.7.38 bug: proportional duration beaming of 32nds and greater

2006-03-15 Thread Trevor Bača
On 3/15/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: > Trevor Bača wrote: > > On 3/15/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: > > > >>Trevor Bača wrote: > >> > >>>This is a weird one. If you have the following three conditions ... > >>> > >> > >>yes, it's a build issue. Only MacOS has th

ragged-last-bottom not handled by convert-ly

2006-03-15 Thread Werner LEMBERG
[CVS 2006-03-14] convert-ly incorrectly converts `raggedlastbottom' to `ragged-lastbottom' instead of `ragged-last-bottom'. Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

collision of accents and ties

2006-03-15 Thread Werner LEMBERG
Another regression compared to the 2.6 series, caused by the new tie algorithm. Werner == % % [EMAIL PROTECTED] \version "2.7.38" \header { texidoc = " In dense layout, accents and ties collide. " } \relative c'' {

too short stems in \markup

2006-03-15 Thread Werner LEMBERG
IIRC, this is a regression compared to the 2.6 series. Werner == % % [EMAIL PROTECTED] \version "2.7.38" \header { texidoc = " Stems in \markup commands are too short if the font size gets reduced. " } \markup { \font

Re: 2.7.38 bug: proportional duration beaming of 32nds and greater

2006-03-15 Thread Han-Wen Nienhuys
Trevor Bača wrote: On 3/15/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Trevor Bača wrote: This is a weird one. If you have the following three conditions ... yes, it's a build issue. Only MacOS has this problem. Ah, yes. Sorry I didn't mention: I am, in fact, on OS X. can you see

Re: "uniform-stretching" messes up note-spacing around time-signature changes

2006-03-15 Thread Han-Wen Nienhuys
Marcus Macauley wrote: cases, with or without any tuplets. I left all these examples in the report thinking it might help the developers to narrow down the possible causes of the bug. If they don't need it, they can use your brief version instead. thanks for the report. Should be fixed in CVS.

Re: 2.7.38 bug: proportional duration beaming of 32nds and greater

2006-03-15 Thread Han-Wen Nienhuys
Trevor Bača wrote: This is a weird one. If you have the following three conditions ... yes, it's a build issue. Only MacOS has this problem. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design

Augmentation dots and ties collision

2006-03-15 Thread Nicolas Mayencourt
Hello, There is augmentation dots and ties collision in 2.7.38, not present in 2.6.4.3. Here is a small exemple. Note that the collision is not the same when the note is on a staff line or not. { \time 3/4 << { e''2. ~ | e''2. } \\ { e'2. ~ | e'2. } >> << { f''2. ~ | f''2. } \\ { f'2. ~

Re: caps font shape not working

2006-03-15 Thread Han-Wen Nienhuys
Mats Bengtsson wrote: Looks like a bug! I forward it to bug-lilypond. I fixed it on the Lily side, by adding 'caps shape to font.scm, but you also have to have a Small-caps font available to Pango. Probably the best option is to remove the reference caps from the documentation and/or reinst

Re: caps font shape not working

2006-03-15 Thread Mats Bengtsson
Looks like a bug! I forward it to bug-lilypond. /Mats Laurenz Goellmann wrote: In order to markup composers names in small caps font shape I tried different methods as recommended by the lilypond documentation and other user hints found in the internet - but nothing really worked. All other

convert-ly error w.r.t. `beamed-xxx'

2006-03-15 Thread Werner LEMBERG
[CVS 2006-03-13] In my old score for version 2.3.22 I have \override Stem #'beamed-lengths = ... \override Stem #'beamed-minimum-free-lengths = ... \override Stem #'beamed-extreme-minimum-free-lengths = ... which isn't converted to the new syntax form \override Stem #'details #'beamed-l