ChangeLog number
> On Friday March 26 2004 01:03, David Bobroff wrote: > > It looks just a docs thing but 'make all' with CVS ChangeLog 1.1954 > > exits thusly: > > How can I find the ChangeLog number? > Getting the same error for some time irritated me too; My patch > worked for > me. I report the ChangeLog number so the developers know exactly what revision I'm using/having problems with. I normally get that number here: http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/ Your question prompted me to poke around a bit thinking it should be available somewhere within the source tree. I found it here: lilypond/CVS/Entries At the bottom of the file. -David ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make all' error on CVS (docs?)
On Friday March 26 2004 01:03, David Bobroff wrote: > It looks just a docs thing but 'make all' with CVS ChangeLog 1.1954 > exits thusly: How can I find the ChangeLog number? Getting the same error for some time irritated me too; My patch worked for me. The patch does the following: 1. Adds 2.2's preface node to the menu (which was the error). 2. Removes the colon prior to the list of major changes; if you still want the colon, it should be preceded by an object (thats grammar talk, not programming talk). An example of using that would be "Major areas of change are the following: orchestral notation, lyrics formatting and font size handling." or "Major areas of change: orchestral notation, lyrics formatting and font size handling." 3. Changed 2.2's preface to be for this year (2004). Index: Documentation/user/preface.itely === RCS file: /cvsroot/lilypond/lilypond/Documentation/user/preface.itely,v retrieving revision 1.37 diff -u -3 -p -r1.37 preface.itely --- Documentation/user/preface.itely25 Mar 2004 23:24:45 - 1.37 +++ Documentation/user/preface.itely27 Mar 2004 03:25:42 - @@ -5,6 +5,7 @@ @unnumbered Preface @menu +* Preface to version 2.2:: * Preface to version 2.0:: * Preface to version 1.8:: * Preface to version 1.6:: @@ -15,12 +16,12 @@ @unnumberedsec Preface to version 2.2 During the 2.1 development cycle, the cleanup of the existing features -has continued unabated. Major areas of change are: orchestral +has continued unabated. Major areas of change are orchestral notation, lyrics formatting and font size handling. Han-Wen and Jan -Utrecht/Eindhoven, The Netherlands, March 2003. +Utrecht/Eindhoven, The Netherlands, March 2004. @node Preface to version 2.0 ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Dynamic questions
http://lilypond.org/doc/v2.1/input/regression/out-www/lily-1175767955.ly
mentions that something like /ff/> will appear on the same horizontal level.
Should other markings, such as cresc, do it too? My guess is that
\set crescendoText = \markup { \italic "cresc. poco" }
a'2\< a a a\!\mf
from the dynamics section of the manual works, but that something like
a\f\cresc a a\!\ff
would not follow that the same way.
Should a consistency between the space between the crescendoSpanner being
adjacent to the preceding crescendoTextand and the space between
crescendoSpanner and where it ends (particularly, for example, when ending
next to another dynamic). Sometimes it seems to work like
cresc.- - - f
and othertimes its like
cresc.- - -f
depending on spacing. In the manual, there is an example even showing the last
dash shrunk down; it almost seems to be a dot.
If the current working is preferred, or others are not implemented for some
reason, that works for me too; I didn't find any mailings I could notice to
be relevant, and the manual doesn't mention a word one way or the other which
lead me to assume that it either works as desired or hadn't been looked at
like this yet.
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: minor slur problem
On Wednesday March 24 2004 16:20, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > % > > % This file shows a problem with broken slurs in staves having different > > % sizes in lilypond CVS 2004-03-23 21:42 MET. > > % > > % . The starting point of the continuation of a broken slur is offset > > % too far to the left in the smaller staff. > > Why? where do you think it should start? I know some other things are restricted to an imaginary line that they cannot pass (or so I have heard), such as a resumed melisma should start at the end of the key signature. Does something like this apply to slurs? One starts before the end of the clef, and the other does not start until sometime after the right edge of the clef. If I (or these ideas) are wrong for typesetting, I'd like to know that too. ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Documentation of Architecture / Design?
On Monday March 22 2004 06:53, Bertalan Fodor wrote: > I think advanced users often use this reference, so what about calling > it Advanced Reference or a similar name, which is from a user's point of > view. > > > I have also misinterpreted the name "Program Reference" as > > "Programming > > > Reference". I don't really have any better suggestion, though. > > A long name could be "Full documentation of all contexts, objects, > > properties, ..." but we need something shorter. Well, what about the program is described in the reference; is it about advanced useage, is it trying to be an entire syntax reference? A suitable name can probably describe what it is all about. ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: barline problem
> The following works fine over here. Thanks. Something like this should be put into the regression suite, since it is not trivial IMHO. Werner ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: severe gs 8.14 problems with lilypond [xefitra]
On Wed, Mar 24, 2004 at 11:28:18PM +0100, Werner LEMBERG wrote: > > > ./src/gxccman.c:576: > > > gx_add_cached_char: Assertion `cc->pair == pair' failed. Thanks for the example file. I've reproduced with HEAD. The issue had been reported separately in the meantime; I've attached your example as well and assigned to the responsible engineer. You can follow the bug at http://bugs.ghostscript.com/show_bug.cgi?id=687391 This and several other issues with 8.14 are motivating us to schedule an 8.15 release. No timeline as of yet. Thanks for the report, -r ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: barline problem
The following works fine over here.
/Mats
\score {
\new PianoStaff
<<
\override Score.BarLine #'transparent = ##t
\override Score.SpanBar #'transparent = ##t
\new Staff \notes {
s1 | \break
}
\new Staff \notes {
s1 |
}
>>
\paper {
raggedright = ##t
}
}
Werner LEMBERG wrote:
Try to make also the SpanBar object transparent!
Example, please. I tried but I wasn't successful.
Werner
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
--
=
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: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
'make all' error on CVS (docs?)
It looks just a docs thing but 'make all' with CVS ChangeLog 1.1954 exits thusly: All snippets are up to date... Compiling ./out/fdl.texi... mv ./out/lilypond.texinfo out/lilypond.nexi 2>/dev/null || mv ./out/lilypond.texi out/lilypond.nexi if [ 4006000 -le 4006000 ]; then \ (cd ./out && \ ls -1 lily-*.ly | sed 's/.ly$/.txt/' | xargs touch) || true; \ fi chmod -w out/lilypond.nexi LANG= makeinfo -I ./out --output=./out/lilypond.info out/lilypond.nexi ./out/preface.texi:14: `Preface to version 2.2' has no Up field (perhaps incorrect sectioning?). ./out/preface.texi:14: warning: unreferenced node `Preface to version 2.2'. makeinfo: Removing output file `./out/lilypond.info' due to errors; use --force to preserve. make[2]: *** [out/lilypond.info] Error 1 make[2]: Leaving directory `/usr/src/lilypond/Documentation/user' make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/src/lilypond/Documentation' make: *** [all] Error 2 [EMAIL PROTECTED] lilypond]# -David ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
