Re: Noteheads slightly too large

On Sat 12 Dec 2015 at 09:47:18 (+0100), David Kastrup wrote: > David Wright writes: > > > Excuse my top-posting, but is there any context for this message? > > http://lists.gnu.org/archive/html/lilypond-user/2015-12/msg00296.html > > is no help either. It *might* be

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

Actually, coverting between the ratios and semitones has alread been done, as there's a simple set of log and mround functions that do it. Have a look in the OLL repository under notation-tools and you should find the .ily files. Cheers, A On Sun, Dec 13, 2015 at 7:51 AM,

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

On Sat, 12 Dec 2015, N. Andrew Walsh wrote: > accidentals as needed. I suppose, rather than having Lily/Scheme calculate > prime factors on the fly at runtime, it would be easier to have a lookup > table of the prime factorization for each integer up to a certain limit (but > that would end up

Re: November font

Hello All, In discussion with the developer and some checks we have done, it appears that the issue lies with Adobe Acrobat rendering on Mac OS X El Capitan. Using Preview on the Mac, everything is rendered nicely. It also renders fine on Document Viewer in Linux. I am pleased to report

Re: Noteheads slightly too large

Oh, so sorry - the original message I now see was on the lilypond bug list, not the lilypond user list to which I have incorrectly replied. Apologies for the mistake, Andrew ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Noteheads slightly too large

David Wright writes: > Excuse my top-posting, but is there any context for this message? > http://lists.gnu.org/archive/html/lilypond-user/2015-12/msg00296.html > is no help either. It *might* be helpful to be able to see the > Message-ID and In-Reply-To for the

Controlling hairpin length

Although I quite often find myself needing to use \override Voice.Hairpin.minimum-length = #2 or similar, I find that the results are unpredictable (to me!) Sometimes I have a very short hairpin, perhaps starting on a quaver and ending on the next quaver. In the output such a hairpin sometimes

Re: accidentals for just intonation

Hi Paul, thanks for getting back to me. To update the list: I'm working on making a set of stencils (using the various svg-to-path functions that Lily and the snippets repository have), which will then be used by the just-intonation toolset Urs is working on to build custom accidentals from

converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

Hi Andrew, > On Dec 12, 2015, at 10:38 AM, N. Andrew Walsh > wrote: > > I've been doing some background work on my just-intonation accidentals, and I > was hoping you could give me some advice on the svg-to-path translation. I > know what the stencils should look

Re: problem adding \epsfile to markup

Hi Harm, 2015-12-06 0:44 GMT+01:00 Thomas Morley : > 2015-12-05 21:49 GMT+01:00 Pierre Perol-Schneider > : > > Hi Ryan, > > The attached file seems to do the job. > > Cheers, > > Pierre > > @Pierre > How did you create the file? > If I

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

> Anyway, that’s how I’ve done this kind of thing. It’s not simple but it > works! If I understand the procedure correctly, wouldn't it be easier to use a tool like fontforge add/adjust font glyphs? -- Johan ___ lilypond-user mailing list

Re: Lower-case letter rehearsal marks

2015-12-13 0:16 GMT+01:00 David Kastrup : > Thomas Morley writes: > >> Though, I thought about some sort of macro, doing the job like: >> >> %% the macro: >> \simple-define-markup-command >> %% the args: >> % name: >> bold-red >> % body: >> \bold

Re: Lower-case letter rehearsal marks

Thomas Morley writes: > Though, I thought about some sort of macro, doing the job like: > > %% the macro: > \simple-define-markup-command > %% the args: > % name: > bold-red > % body: > \bold \with-color #red \etc > > I think it would prevent some confusions.

Re: Controlling hairpin length

2015-12-12 17:46 GMT+01:00 David Sumbler : > Although I quite often find myself needing to use > > \override Voice.Hairpin.minimum-length = #2 > > or similar, I find that the results are unpredictable (to me!) > > Sometimes I have a very short hairpin, perhaps starting on a

Extending staff lines through key change

I’m engraving a piece that ends with a D.C. al Fine. Also the key at the beginning of the piece is different from the key at the end of the piece. So, in order to cue the performer, a final key change is issued for the initial key: \version "2.19.32" { \relative c'' { \key g\major

Re: Extending staff lines through key change

Just add a "s8" after the key change. HTH, Abraham On Saturday, December 12, 2015, Cynthia Karl [via Lilypond] < ml-node+s1069038n184706...@n5.nabble.com> wrote: > I’m engraving a piece that ends with a *D.C. al Fine*. Also the key at > the beginning of the piece is different from the key at

Re: accidentals for just intonation

Am 12. Dezember 2015 16:38:13 MEZ, schrieb "N. Andrew Walsh" : >Hi Paul, > ... > >The system works like this: > >1) each accidental has a long thin vertical line: approximately 1 >staff-height, This triggers a question: *where* do you want the accidental to be

Re: problem adding \epsfile to markup

2015-12-12 21:41 GMT+01:00 Pierre Perol-Schneider : > Hi Harm, > > 2015-12-06 0:44 GMT+01:00 Thomas Morley : >> >> 2015-12-05 21:49 GMT+01:00 Pierre Perol-Schneider >> : >> > Hi Ryan, >> > The attached

Re: Controlling hairpin length

2015-12-12 22:35 GMT+01:00 Thomas Morley : > 2015-12-12 17:46 GMT+01:00 David Sumbler : >> Although I quite often find myself needing to use >> >> \override Voice.Hairpin.minimum-length = #2 >> >> or similar, I find that the results are unpredictable

Re: Lower-case letter rehearsal marks

2015-12-11 11:50 GMT+01:00 David Kastrup : >> Having >> \markup bold-red = <ẃhat-ever> >> ,i.e. a definition might lead to confusions. > > The compiler isn't confused. The question is more about the user. Yep, that was exactly my concern. >> Is it possible to create a

Re: Extending staff lines through key change

> > From: Cynthia Karl > > To: lilypond-user > > Subject: Extending staff lines through key change > > Date: Sat, 12 Dec 2015 15:41:32 -0600 > > > > I’m engraving a piece that ends with a D.C. al Fine. Also the key > > at the beginning of the piece is

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

Am 12. Dezember 2015 23:08:53 MEZ, schrieb Paul Morris : >> On Dec 12, 2015, at 3:34 PM, Johan Vromans >wrote: >> >> If I understand the procedure correctly, wouldn't it be easier to use >a >> tool like fontforge add/adjust font glyphs? > >Maybe so,

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

It would not, because the accidentals I use are in an open system of just intonation (not a fixed scale) in which *any* conceivable ratio can be represented (so long as I have the module for its respective prime factors). This is a serious limitation of a lot of systems, in that the moment you

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

> On Dec 12, 2015, at 3:34 PM, Johan Vromans wrote: > > If I understand the procedure correctly, wouldn't it be easier to use a > tool like fontforge add/adjust font glyphs? Maybe so, but the result is less portable because (if I understand correctly) you'd have to have a

Re: Extending staff lines through key change

Hi, see a recent conversation: http://lilypond.1069038.n5.nabble.com/WAS-Staff-ends-before-clef-time-and-key-td183976.html HTH, ~Pierre 2015-12-12 22:41 GMT+01:00 Cynthia Karl : > I’m engraving a piece that ends with a *D.C. al Fine*. Also the key at > the beginning of the