Re: GUB: patch for linux_kernel_headers
Pedro Kröger wrote: Hi, You may want to apply the attached patch. It updates linux_kernel_headers to 2.6.13+0rc3-2.1. I couldn't find 2.6.13+0rc3-2 from any mirror. Pedro It was a few weeks ago, so I assume that debian throws away old versions quickly. I expect that this will break in the near future as well; can we figure out a mechanism that doesn't rely on Debian source archives? Or one that takes it from a stable version of ubuntu/debian? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond-book fails; python 2.3 used instead of 2.4
Graham Percival wrote:
lilypond-book produces pdfs with incorrect margins, and displays this
error message:
---
Traceback (most recent call last):
File
/Users/gperciva/Apps//LilyPond.app/Contents/Resources/bin/lilypond-book,
line 1754, in ?
main ()
File
/Users/gperciva/Apps//LilyPond.app/Contents/Resources/bin/lilypond-book,
line 1732, in main
psfonts_file = os.path.join (global_options.output_name, basename +
'.psfonts')
File
/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/posixpath.py,
line 62, in join
elif path == '' or path.endswith('/'):
AttributeError: 'NoneType' object has no attribute 'endswith'
---
(although it keeps on processing the document)
I have python2.4 installed via fink, but it's still finding the system
2.3 (at /usr/bin/python). Any hints?
it's barfing because global_options.output_name is None. I've changed
the default to '' in CVS, but you might want to submit a full bugreport.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Tremolo positioning
Joe Neeman wrote: + Real height_of_my_trem = 0.0; + Grob *trem = unsmob_grob (me-get_object (tremolo-flag)); + if (trem) + height_of_my_trem = ly_scm2interval (trem-get_property (Y-extent)).length () +/* hack a bit of space around the trem. */ ++ beam_translation - beam_thickness; the proper procedure is to call Grob::extent(refp, Y_AXIS) instead. Stencil a (Lookup::beam (slope, width, thick, blot)); - a.translate (Offset (-width * 0.5, width * 0.5 * slope)); + Interval a_ext = a.extent (Y_AXIS); + a.translate (Offset (-width * 0.5, a_ext.length () / 2 - a_ext[UP])); I think you want Stencil::align_to (CENTER, Y_AXIS) - mol.align_to (Y_AXIS, -stemdir); - mol.translate_axis (chord_start_y + 0.5 * stemdir, Y_AXIS); + Real down_off = mol_ext.length () / 2 + mol_ext[DOWN]; + mol.translate_axis (-down_off * 2, Y_AXIS); } idem. Can you resend the patch using more idiomatic code? Thanks! -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Tremolo positioning
Han-Wen Nienhuys wrote: Can you resend the patch using more idiomatic code? Thanks! Also, can you include a small regression test sample, so it's obvious when we break something? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Improvements to Postscript backend (patches included)
David Feuer wrote:
I sent this some hours ago, but haven't seen it yet. Is the mailing list
broken, or just really slow?
The list is a bit slow, and I have been away.
Original message:
I made some changes to the Postscript backend, making the output more readable
(especially for text), around 10% shorter, and, at least in theory, also faster
to interpret. These changes are just a start, but I hope they help. I'd like
to know if it might be possible to make the backend work at a slightly higher
level, which should allow much smaller files (e.g., Postscript could easily
understand the concept of filled dotted quarter note in current note font with
upward stem 3 staff spaces long).
That's very unlikely. The internal representation is not strictly
hierarchical, so it's difficult to group different objects (eg. note and
stem) so they will be output together, and still be sure that all of
them are processed.
I'm not a master of diff, so let me know if the following aren't done right.
Diffs (made with -u) against the 2.8.0 source:
I'm missing a Changelog entry.
--- ../Installation
Programs/lilypond-2.8.0-src/lilypond-2.8.0/scm/framework-ps.scm 2006-03-20
19:45:18.0 -0500
+++ framework-ps.scm2006-03-25 18:25:43.875475200 -0500
@@ -42,8 +42,10 @@
(define font-list (ly:paper-fonts paper))
(define (define-font command fontname scaling)
(string-append
- / command { / fontname findfont
- (ly:number-string scaling) output-scale div scalefont } bind def\n))
+ / command { / fontname (ly:number-string scaling)
output-scale div selectfont } bind def\n))
+;(string-append
+; / command { / fontname findfont
+; (ly:number-string scaling) output-scale div scalefont } bind def\n))
Hi,
thanks for you patch. CAn you have a second look; there are some style
issues,
+/printletter {
+ currentpoint
+ 3 2 roll
+ glyphshow
+ moveto
+} bind def
+/printglyphs {
+ -1 1
+ {
+ 3 mul -3 roll
+ printletter
+ rmoveto
+ }for
+}bind def
can you add some comment explaining in more detail that this is for
kerning? Also, can you follow the naming convention, which is
word_word iso. wordword for PS files.
(I'd like to change this to word-word, some time)
+(define (round2 num)
+ (/ (round (* 100 num)) 100))
+
+(define (round4 num)
+ (/ (round (* 1 num)) 1))
+
+(define (str4 num)
+ (format #f ~f (round4 num)))
can you rename this to something more comprehensible?
+;; s/\.\([0-9]\{-}\)0* /\1 /g
+
?
(format #f gsave
- /~a ~a ~a output-scale div scalefont setfont\n~a grestore
+ /~a ~a output-scale div selectfont\n~a grestore
postscript-font-name
- (if cid?
- /CIDFont findresource
- findfont)
I don't understand this? How are CID resources supposed to be loaded now?
(define (named-glyph font glyph)
(string-append
- (ps-font-command font) setfont
+ (ps-font-command font)
/ glyph glyphshow ))
While you're at it, I think it would improve readability of the SCM file
when you try to replace string-append in cases like these.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB: patch for linux_kernel_headers
Jan Nieuwenhuizen wrote: Han-Wen Nienhuys writes: It was a few weeks ago, so I assume that debian throws away old versions quickly. I expect that this will break in the near future as well; can we figure out a mechanism that doesn't rely on Debian source archives? Or one that takes it from a stable version of ubuntu/debian? Yes, we could, but then it would not be debian_unstable.py. We may want to disable downloading of debian-unstable stuff by default (esp. because we do not build debian anyway) or make a switch to debian_stable.py. I think the linux_kernel_headers are used for the linux build, not the debian one. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB: patch for linux_kernel_headers
Han-Wen Nienhuys [EMAIL PROTECTED] writes: I think the linux_kernel_headers are used for the linux build, not the debian one. Hum, I was going to recommend to download directly from linux-libc-headers [1] (linux from scratch and DIY-linux use it) but I just learned the project is kind of dead [2] I suppose we could use stable like Jan suggested or maybe testing. It tend to change less frequently than unstable. Pedro Footnotes: [1] http://ep09.pld-linux.org/~mmazur/linux-libc-headers/ [2] http://lists.pld-linux.org/mailman/pipermail/llh-announce/2006-March/02.html ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Tremolo positioning
The tremolo bars should be thinner than beams, Urgh. Never seen that in normal scores from German publishers. On beamed notes, the tremolo bars usually slant sightly more than the beams Note that the tremolo bars always slant upward, regardless of beam- slant Hmmm. Mostly, you want to avoid them looking like beams that didn't print correctly... so, avoiding tremolos parallel to the beams is of importance. I really would like to see a situation where I can misinterpret a tremolo under a beam... I can scan the page tonight if that would help. In case there is a music example, please do so. But this is just a theoretical book, I assume. Can you provide a real-world example also? Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Tremolo positioning
Werner LEMBERG writes: The tremolo bars should be thinner than beams, Urgh. Never seen that in normal scores from German publishers. I think that I have seen thicker than beams, in some publications. On beamed notes, the tremolo bars usually slant sightly more than the beams Note that the tremolo bars always slant upward, regardless of beam- slant Hmmm. Here also are different styles, but I guess that using the beam slant looks best. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Addition to manual
On 24-Mar-06, at 6:54 PM, Cameron Horsburgh wrote: Text style dynamic changes (such as cresc. and dim.) are printed with a dashed line showing their extent. If you don't want to print this line you can use \override DynamicTextSpanner #'dash-period = #-1.0 Thanks, added. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Another thing for the manual
On 26-Mar-06, at 12:00 AM, Cameron Horsburgh wrote: Section 8.1.8 New dynamic marks/end of the first paragraph Note that the dynamic font only contains the characters f,m,p,r,s and z. Thanks, applied. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: time signature in ancient notation
On 27-Mar-06, at 2:08 PM, Juergen Reuter wrote: Graham, what do you think, could we put attached template into the docu instead of that currently in 3.7.2? By the way, we have now 3.5.1 Transcription of mensural music and 3.7.2 Gregorian transcription template. Maybe, these should be put together into a single section (and maybe the two titles harmonized)? Thanks, added. Let me know what you think of the titles when 2.8.1 comes out. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Tremolo positioning
On Tue, 28 Mar 2006 14:39, Joshua Parmenter wrote: This is described in Matt Stone's book Music Notation in the 20th Century (not just 20th century music notation, but the practices of notation in the 20th century): The tremolo bars should be thinner than beams, and as long or a little longer than the width of a note-head On beamed notes, the tremolo bars usually slant sightly more than the beams Note that the tremolo bars always slant upward, regardless of beam- slant Mostly, you want to avoid them looking like beams that didn't print correctly... so, avoiding tremolos parallel to the beams is of importance. When the beams are at the same angle that the tremolos would be, then the tremolos are adjusted slightly to avoid this. I can scan the page tonight if that would help. I think it would be most helpful if you could find a printed example of music that shows this -- regardless of what Matt Stone says, I don't think I have ever seen a tremolo slanted in the opposite direction of a beam. He must cite some references -- maybe you can find an example there. One of my previous examples was the Bartok solo violin sonata (which couldn't have been typeset before 1947) and it has downward slanting tremolos on downward slanting beams (parallel to the beam). I just picked up a Kalmus edition of Ravel Introduction and Allegro (Violin 2), typeset at the beginning of the 20th century, and it also has tremolos parallel to beams even when beams slant downward. Slightly unrelated, but now that you have me peering closely at tremolo flags... all the examples I have on hand have rectangular tremolo flags on beamed notes and parallelogram tremolo flags (what we do now) on unbeamed notes. Also the flags on beamed notes are much shorter than on unbeamed notes (about 60-70% the width). Joe ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond ./ChangeLog Documentation/user/advance... [lilypond_2_8]
On 28-Mar-06, at 1:22 PM, Graham Percival wrote: CVSROOT:/sources/lilypond Module name:lilypond Branch: lilypond_2_8 Changes by: Graham Percival [EMAIL PROTECTED] 06/03/28 21:22:09 Modified files: . : ChangeLog Documentation/user: advanced-notation.itely Log message: Backport doc material. (mostly a test) As everybody subscribing to lilypond-cvs knows by now, backporting this 20-line patch (or so) simply sent the entire new file to the -cvs list. I reported this bug to savannah back when 2.6 was branched, and Derek Robert Price had two suggestions to fix this problem. I don't understand the answers, but perhaps somebody else might? http://savannah.gnu.org/support/?func=detailitemitem_id=104373 It's not a serious issue, since this only happens the first time we change a file, but it would still be nice to avoid all the wasted bandwidth. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Tremolo positioning
On Tue, 28 Mar 2006 21:26, Joshua Parmenter wrote: I'll do this tonight (when I'm home with my scanner). Looking over some older scores, I definitely see examples like the one sent earlier... but over 10 years of typesetting, most current style sheets (if memory serves me correctly) specify slanted tremolos. I'll actually see if I can dig up the Durand style sheet (the one I've seen most recently) and see if ti specifies. While you're looking this up, could you also check the behaviour of tremolo flags on notes with flags (eg. unbeamed 8th notes)? I only have one example of this on hand and the behaviour is Tremolos on stem-up notes with flags are shortened and rectangular (same as beamed flags). Tremolos on stem-down notes with flags are the normal length, but more sloped than normal to help them avoid the flag. This behaviour seems to make sense, but I only have one example so it would be nice to have either confirmation or a counter-example/alternate behaviour. Cheers, Joe ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Tremolo positioning
On Tue, 28 Mar 2006 23:41, Joshua Parmenter wrote: Ignoring modern style sheets means not being able to type-set for those companies. Which also means using Finale or Sibelius. Or, perhaps this can be configurable. Maybe a stylesheet could be loaded? If you're new here, you may not realise that almost everything in lilypond is configurable. As things stand, you can do \override StemTremolo #'beam-slope = #0.3 at the beginning of your score and all tremolos will be sloped at 30 degrees. They can also be overridden individually. (And the same applies to tremolo width). So what we are discussing here is only the default behaviour. And I tend to agree with Han-Wen that the default should be to follow classical behaviour. Cheers, Joe And I apologize for not introducing myself and my situation. I was directed here from a MANTIS thread with Denemo. Basically, I'm a composer that does quite a bit of open-source development (mostly with SuperCollider). I've been using Finale forever, and am tired of paying for upgrade after upgrade. Also, since I have acquired some coding skills, and have just finished graduate school, I am looking for: a) an alternative b) a project I can expand personally to meet my needs (in my own copy... if need be) c) possibly a project that wants so assistance with development. I spent a good 5 years learning how to make Finale do what I wanted. I'm ready to invest time like that again if that kind of assistance is wanted. So, that's where I am coming from. Most of my notational needs are with extended 20th century technique... something no typesetting program does well... the ability for lilipond to use TeX obviously opens up many possibilities... I find this exciting. Look forward to learning the program, and, if it is wanted, possibly helping with development. Best, Josh On Mar 28, 2006, at 3:31 PM, Han-Wen Nienhuys wrote: Joshua Parmenter wrote: I'll do this tonight (when I'm home with my scanner). Looking over some older scores, I definitely see examples like the one sent earlier... but over 10 years of typesetting, most current style sheets (if memory serves me correctly) specify slanted tremolos. I'll actually see if I can dig up the Durand style sheet (the one I've seen most recently) and see if ti specifies. I would be most interested in a xerox/scan of this document. Schirmer's style guide shows slanted tremolo beams on horizontal beams, but I admit that it looks rather disconcerting. Let's do what the classics do, and ignore modern style sheets. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ** Joshua Parmenter [EMAIL PROTECTED] Post-Doctoral Research Associate - Center for Digital Arts and Experimental Media Raitt Hall - University of Washington Seattle, Washington 98195 http://www.dxarts.washington.edu http://www.realizedsound.net/josh/ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Tremolo positioning
On Tue, 28 Mar 2006 23:41, Joshua Parmenter wrote: Ignoring modern style sheets means not being able to type-set for those companies. Which also means using Finale or Sibelius. Or, perhaps this can be configurable. Maybe a stylesheet could be loaded? If you're new here, you may not realise that almost everything in lilypond is configurable. As things stand, you can do \override StemTremolo #'beam-slope = #0.3 at the beginning of your score and all tremolos will be sloped at 30 degrees. They can also be overridden individually. (And the same applies to tremolo width). Of course... I have only started working through the tutorial... so perhaps I should just keep a little quiet until I know what is going on! Thanks, Josh So what we are discussing here is only the default behaviour. And I tend to agree with Han-Wen that the default should be to follow classical behaviour. Cheers, Joe And I apologize for not introducing myself and my situation. I was directed here from a MANTIS thread with Denemo. Basically, I'm a composer that does quite a bit of open-source development (mostly with SuperCollider). I've been using Finale forever, and am tired of paying for upgrade after upgrade. Also, since I have acquired some coding skills, and have just finished graduate school, I am looking for: a) an alternative b) a project I can expand personally to meet my needs (in my own copy... if need be) c) possibly a project that wants so assistance with development. I spent a good 5 years learning how to make Finale do what I wanted. I'm ready to invest time like that again if that kind of assistance is wanted. So, that's where I am coming from. Most of my notational needs are with extended 20th century technique... something no typesetting program does well... the ability for lilipond to use TeX obviously opens up many possibilities... I find this exciting. Look forward to learning the program, and, if it is wanted, possibly helping with development. Best, Josh On Mar 28, 2006, at 3:31 PM, Han-Wen Nienhuys wrote: Joshua Parmenter wrote: I'll do this tonight (when I'm home with my scanner). Looking over some older scores, I definitely see examples like the one sent earlier... but over 10 years of typesetting, most current style sheets (if memory serves me correctly) specify slanted tremolos. I'll actually see if I can dig up the Durand style sheet (the one I've seen most recently) and see if ti specifies. I would be most interested in a xerox/scan of this document. Schirmer's style guide shows slanted tremolo beams on horizontal beams, but I admit that it looks rather disconcerting. Let's do what the classics do, and ignore modern style sheets. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/ ~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ** Joshua Parmenter [EMAIL PROTECTED] Post-Doctoral Research Associate - Center for Digital Arts and Experimental Media Raitt Hall - University of Washington Seattle, Washington 98195 http://www.dxarts.washington.edu http://www.realizedsound.net/josh/ ** Joshua Parmenter [EMAIL PROTECTED] Post-Doctoral Research Associate - Center for Digital Arts and Experimental Media Raitt Hall - University of Washington Seattle, Washington 98195 http://www.dxarts.washington.edu http://www.realizedsound.net/josh/ ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Improvements to Postscript backend (patches included)
On 3/28/06, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
David Feuer wrote:
thanks for you patch. CAn you have a second look; there are some style
issues
Sure. I can't deal with them right now, but I'll try to fix them up
this evening.
I'd like
to know if it might be possible to make the backend work at a slightly
higher
level, which should allow much smaller files (e.g., Postscript could easily
understand the concept of filled dotted quarter note in current note font
with
upward stem 3 staff spaces long).
That's very unlikely. The internal representation is not strictly
hierarchical, so it's difficult to group different objects (eg. note and
stem) so they will be output together, and still be sure that all of
them are processed.
I've searched and searched, but I can't seem to figure out where notes
and text turn into primitive objects sent to the backends. Could you
point me in the right direction? Is there an explanation somewhere of
the general process through which parsed Lilypond becomes printed
music? You say the internal representation is not strictly
hierarchical. What _is_ the internal representation? When objects
get broken up for separate processing, might it be reasonable for the
component pieces to point back to their parents? In any case,
whatever structure the internal representation actually has would most
likely be useful in the backend code. The image in my mind is an
intermediate program of sorts that is compiled to create Postscript or
TeX output and interpreted to create SVG output.
can you add some comment explaining in more detail that this is for
kerning?
Actually, I was rather curious where those numbers were coming from.
It might be a good idea to use separate routines for placing text, for
placing noteheads, and for whatever else, rather than using just one
glyph placer for all, as they really are rather different. Text tends
to have a lot of letters on horizontal lines. Notes tend to be on
lines or spaces in staves.
Also, can you follow the naming convention, which is
word_word iso. wordword for PS files.
Sure.
+(define (str4 num)
+ (format #f ~f (round4 num)))
can you rename this to something more comprehensible?
num-str4prec? I couldn't think of anything really good.
+;; s/\.\([0-9]\{-}\)0* /\1 /g
+
?
Sorry. That's junk.
(format #f gsave
- /~a ~a ~a output-scale div scalefont setfont\n~a grestore
+ /~a ~a output-scale div selectfont\n~a grestore
postscript-font-name
- (if cid?
- /CIDFont findresource
- findfont)
I don't understand this? How are CID resources supposed to be loaded now?
According to the Postscript reference, selectfont can be used with CID
resources as well as regular fonts. Unfortunately, I can't make the
utf-8 regression test work either with or without my changes, so I
can't be sure I got this right.
(define (named-glyph font glyph)
(string-append
- (ps-font-command font) setfont
+ (ps-font-command font)
/ glyph glyphshow ))
While you're at it, I think it would improve readability of the SCM file
when you try to replace string-append in cases like these.
Sure.
David Feuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Page and line penalties
Joe Neeman wrote: As far as I can tell, page and line penalties are used _only_ for forbidding and forcing page breaks. correct Is there much chance they will ever be used for anything else? If not, they could be replaced by booleans - this would make hopefully, we can use inverse durations of rests as penalties to provide a somewhat sensible automatic line/page breaking. One problem that needs to be solved is that the penalties are actually forces, but they does not translate to a scale that is sensible for users (or it does, but I don't know what scale) -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Improvements to Postscript backend (patches included)
- (if cid? - /CIDFont findresource - findfont) I don't understand this? How are CID resources supposed to be loaded now? According to the Postscript reference, selectfont can be used with CID resources as well as regular fonts. But a CID resource is completely useless for us since we don't get the corresponding CID value, AFAIK. In case Pango does the CMap resource handling (this is, we send a Unicode value and Pango returns the CID) we can enable this again. Werner, do we still need /CIDFont findresource ? It really depends on Pango... Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Tremolo positioning
This is great to know.
While I am still learning syntax, etc. of lilypond, perhaps the first
thing I can volunteer to do in the near future is program some of the
more common (or attainable) house style sheets. Like I said, I
believe I have the Durand sheet somewhere. If anyone else out there
has some current ones laying around, please contact me off list, and
I'll use this as one of my first goals.
Thanks everyone, and apologies again for jumping in mid thread.
Also, my scanner doesn't seem to like my new MacBook at the
moment I'll scan a few things in the near future and post them if
there is still interest.
Best,
Josh
On Mar 28, 2006, at 6:20 PM, Graham Percival wrote:
On 28-Mar-06, at 3:56 PM, Joshua Parmenter wrote:
If you're new here, you may not realise that almost everything in
lilypond is
configurable. As things stand, you can do
Of course... I have only started working through the tutorial...
so perhaps I should just keep a little quiet until I know what is
going on!
Due to your programming background, this is probably obvious, but
just in case... you can make stylesheets of your own, from
standard .ly files, and include them in every work.
For example, I have half a dozen files with my own definitions. I
include a single file, tutti.ly in every real music file.
tutti.ly in turn simply contains
\version 2.7.40
#(ly:set-option 'point-and-click #f)
\include ../init/init-defs.ly
\include ../init/init-layout.ly
\include ../init/init-paper.ly
Part of init-layout.ly is this:
\layout{
\context{ \Staff
\override TimeSignature #'style = #'numbered
}
\context { \Voice
\override TextScript #'padding = #1.0
\override Glissando #'thickness = #3
\override Glissando #'gap = #0.1
\override Glissando #'breakable = ##f
}
}
(to everybody else)
Yeah, I'll add an example of this to the docs in a few weeks.
Cheers,
- Graham
**
Joshua Parmenter
[EMAIL PROTECTED]
Post-Doctoral Research Associate - Center for Digital Arts and
Experimental Media
Raitt Hall - University of Washington
Seattle, Washington 98195
http://www.dxarts.washington.edu
http://www.realizedsound.net/josh/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
