Re: \apply nest-props Re: constructive criticism

2004-01-13 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > (def-grob-description Accidental > "Perhaps a documentation for that here" > ;; first, the (meta (interface . (...))) field: > (item-interface accidental-interface font-interface) > ;; then, other field definitions: > (molecule-callback Accidental_interface::b

Re: more on octavation lines

2004-01-13 Thread Werner LEMBERG
> > . The final `delimiter' (the small vertical bar) must have a > > greater horizontal offset. I suggest to move it one notehead > > width to the right. > > Hmm, maybe a half notehead width is better... And the `8va' string should be slight offset to the left also. Attached are images and

specifying vertical rest position fails

2004-01-13 Thread Werner LEMBERG
Look at this input and the attached image: \context Staff \notes \relative c' { r16 e\rest c[( d r e]) c[( d e\rest e]) } The second `e\rest' doesn't work to change the vertical position. I've already reported this a more than a year ago... Werner <>

Re: \apply nest-props Re: constructive criticism

2004-01-13 Thread Nicolas Sceaux
Tue, 13 Jan 2004 13:58:44 +0100, Han-Wen a dit : > [...] > However, a newbie like me finds it a little confusing when functions > and macros follow similar naming conventions. I would propose some > kind of naming scheme, such that you can tell whether a symbol > represents a macro or a func

Tuplet formatting

2004-01-13 Thread Baron Schwartz
Hello list. Is it possible to specify where the 3 on a triplet should go? I have a triplet with the stems pointing up and a slur below. The number 3 should also go below the noteheads, but above the slur, to duplicate the original. I cannot find a way to set this property on a tuplet. Thank

input/bugs/

2004-01-13 Thread Han-Wen Nienhuys
To all those with CVS access: the input/bugs/ directory is deprecated. Do not put any stuff in that directory. Bugs should either be * fixed or * documented in the manual input/bugs/ falls under neither category. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~han

octavation problems

2004-01-13 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > > While the +8va and +15ma octavation works OK, it fails for 8va bassa > (15ma bassa is nonsense; this doesn't exist). It must be always below > the staff and never above. This is fixed. I'm leaving the 15ma bassa for the freaks. :-) > Secondly, a (global) parameter

Re: \apply nest-props Re: constructive criticism

2004-01-13 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > I don't know much about scheme coding style and habits. However, in, > say, Common Lisp, it is not bad style to have both macros and > functions, as they achieve different purposes. > [..] > which is less eleguant. You can *always* do without macros (eh, very > few lang

more on octavation lines

2004-01-13 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > > . Octavation lines must have a minimum distance from the staff lines; > I suggest to use 1.2 times the distance between two lines in a > staff. Fixed. > . Another problem is that currently we get the following for > octavation lines broken across systems: > >

Re: buggy cmbxti10.pfb

2004-01-13 Thread Han-Wen Nienhuys
thx, fixed mftrace CVS. [EMAIL PROTECTED] writes: > > > Using mftrace 1.0.19, pfaedit CVS from 2004-01-11 08:28, the slant in > > > cmbxti10.pfb has the wrong sign. It must be -14 degrees, not +14. > > > > Huh? Your letters are slanted in the wrong direction? > > No. The `/ItalicAngle' entry

Re: more on octavation lines

2004-01-13 Thread Werner LEMBERG
> . The final `delimiter' (the small vertical bar) must have a greater > horizontal offset. I suggest to move it one notehead width to the > right. Hmm, maybe a half notehead width is better... Werner ___ Lilypond-devel mailing list [EMAIL