Re: Bravura svg font

On 2016-01-07 02:57, Paul Booker wrote: Thanks Nathan, Since posting, I've scanned the bug and devel groups, and it would appear I am not being fashionable in wanting to do this. The trend seems to be toward woff fonts for svg, is that the case? Yes and no. The openlilylib font project

Re: Bravura svg font

On 08.01.2016 00:31, Nathan Ho wrote: The least serious use is the recent Christmas font adaptation by Leigh Verlag :) In case others be interested: Nice and funny :-) Thanks, Abraham (and Mark)! Yours, Simon

Re: Strange beaming error

Am 07.01.2016 um 10:16 schrieb David Kastrup: > Urs Liska writes: > >> Do you also have subdivideBeams = ##t somewhere? >> If so please show the result with both 2.19.28 and .35.. >> >> And if that's the case you should maybe send me (privately?) the full >> piece so I

Fwd: Concerts in Berlin with LilyPond scores

Forwarding to the User group, as it's more appropriate there, and for wider distribution. All the best for the concerts, Aurélien, and thanks for letting us know. Cheers, Colin Forwarded Message Subject:Concerts in Berlin with LilyPond scores Date: Thu, 7 Jan

Re: Fwd: Concerts in Berlin with LilyPond scores

Am 07.01.2016 um 23:50 schrieb Colin Campbell: > Forwarding to the User group, as it's more appropriate there, and for > wider distribution. All the best for the concerts, Aurélien, and > thanks for letting us know. That's partially true. lilypond-user is the better place to let more people

Re: Bravura svg font

On 2016-01-06 11:23, Paul Booker wrote: Hi, I'm a new use of lilypond-windows on Win 8.1 64bit and Win 7. First of all, thanks for wonderful software; I'm generating many snippets for educational purposes. My main problem so far is getting the bravura alternative font to appear. I don't

Re: Strange beaming error

Urs Liska writes: > Before testing further I assume the current issue is due to *not* > using the latest state (which isn't in a release yet). Why are there different states? Did the original plan fail on paper or did it never reach paper? Or was it not correctly

Re: Strange beaming error

Am 7. Januar 2016 10:16:29 MEZ, schrieb David Kastrup : >Urs Liska writes: > >> Do you also have subdivideBeams = ##t somewhere? >> If so please show the result with both 2.19.28 and .35.. >> >> And if that's the case you should maybe send me (privately?) the

Re: Strange beaming error

Chris Yate writes: > On 7 January 2016 at 00:49, Thomas Morley wrote: > >> Btw, your images are inline _not_ attached. >> > > Are inlined images not OK here? ...or were you just being pedantic? > ;-) They were inlined into the HTML part only

Re: Strange beaming error

Urs Liska writes: > Do you also have subdivideBeams = ##t somewhere? > If so please show the result with both 2.19.28 and .35.. > > And if that's the case you should maybe send me (privately?) the full > piece so I could test with several builds before and after several >

list of thicknesses affected by changing StaffSymbol.thickness

Hello all, Is there a single list somewhere in the documentation, of all the grobs whose sizes are tied to StaffSymbol.thickness? (Optimally, that list would also include each grob’s default multiplier/thickness.) Thanks, Kieren. Kieren MacMillan, composer ‣

RE: Strange beaming error

On 7 Jan 2016 1:31 am, "Mark Stephen Mrotek" wrote: > > Chris: > > > What is the time signature? 6/8? > > Or is it 2/4 grouped as if in tuplets? > Mark Mark, Yes, it's 6/8. Although it changes to 4/4 for one movement - the one before this problem occurs (that may or may

Re: Include total page count in page number

Thank you! That will at least get me by for now. - Abraham On Thu, Jan 7, 2016 at 7:09 AM, Jan-Peter Voigt [via Lilypond] < ml-node+s1069038n185643...@n5.nabble.com> wrote: > Hi Abraham, > > I created a short sketch, how this might be realized. In this example, > the result counts one page high

Re: Bravura svg font

On 2016-01-07 15:49, Simon Albrecht wrote: In case others be interested: Nice and funny :-) Thanks, Abraham (and Mark)! Yours, Simon There aren't enough novelty music fonts out there. Once I was a kid and I entered "Take Me

Re: How to reproduce this?

Hi there,There's a few things wrong here... I'd start by getting the voices separated. So something like: << \quaver_triplet_stuff % this will be voice 1 and stems-up \\ \chord_notes % this will be voice 2, but you'll have to hide the stems. exercise for the reader ;-) >> Chord notation

Re: Strange beaming error

On 7 January 2016 at 17:12, Mark Stephen Mrotek wrote: > Chris, > > > > As I mentioned in a previous reply, make sure that identical “\set > Timining” instructions are in both the upper and lower staff. > > Once this is done, recompile and check for accuracy. > > > > Mark >

Re: How to reproduce this?

Hi Buschmann, How about : \version "2.18.2" %\language "german" \layout { \context { \ChordNames \override ChordName.font-family = #'serif \override ChordName.font-size = #0 } } << \chords { f2 gis4 dis b } << \relative c'' { \numericTimeSignature

Re: How to reproduce this?

Hello Abraham, Thanks, that works fine! JM > Le 7 janv. 2016 à 19:47, Abraham Lee a écrit : > > Jacques, > > > > On Thu, Jan 7, 2016 at 11:42 AM, Jacques Menu > wrote: > Hello Pierre, > > This doesn’t

Variable names

I assume there have been discussions on extending the syntax for LP identifiers to include dashes and underscores. My personal opinion is that a non-alpha separator is good to have, but two different separators may quickly become confusing. Is it 'set_variable' or 'set-variable'? Given the

How to reproduce this?

Hi, I'm a Lilypond newbie switching over from Sibelius. As part of my self tutoring I have tried my hand at reproducing a example (written in Sib) i used in my thesis: http://i.imgur.com/SboviWR.png I'm a bit stuck and i hope you guys can give me a nudge. This is my feeble attempt: \version

Re: Variable names

On Thu, Jan 07, 2016 at 08:59:22PM +0100, Johan Vromans wrote: > I assume there have been discussions on extending the syntax for LP > identifiers to include dashes and underscores. My personal opinion is > that a non-alpha separator is good to have, but two different > separators may quickly

Rewriting an expression that uses ly:make-simple-closure

Hi all, Here’s a tricky one… I’m working on updating a piece from the Mutopia Project[1] (from LilyPond 2.16.1 to 2.19.35) and it uses the following: centermarkup = { \once \override TextScript.self-alignment-X = #CENTER \once \override TextScript.X-offset =#(ly:make-simple-closure

Re: How to reproduce this?

Thank you, much obliged! 1) I didnt get... \addlyrics \lyricsto "Chords" { V2 \markup\concat { \raise #.4 \small\flat VII } \markup\center-column { \concat { \raise #.7 \small\sharp III } IV } I } ...to work though: http://i.imgur.com/aVeeG1V.png 2) How

Re: How to reproduce this?

Thats it! Thank you, this was inspiring. Buschmann ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to reproduce this?

Jacques, On Thu, Jan 7, 2016 at 11:42 AM, Jacques Menu wrote: > Hello Pierre, > > This doesn’t compile on 2.19.33 though. > > Thanks for all the help you provide to the rest of us! > Try this out: %<--- \version "2.19.31" \layout { \context {

Re: Strange beaming error

Am 07.01.2016 um 18:24 schrieb Chris Yate: > On 7 January 2016 at 17:12, Mark Stephen Mrotek > wrote: > > Chris, > > > > As I mentioned in a previous reply, make sure that identical “\set > Timining” instructions are in both

Re: How to reproduce this?

Hello Pierre, This doesn’t compile on 2.19.33 though. Thanks for all the help you provide to the rest of us! JM Starting lilypond 2.19.33 [Untitled]... Processing `/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T/frescobaldi-mmxLK7/tmpXWfERQ/document.ly' Parsing...

Re: How to reproduce this?

Am 07.01.2016 um 21:59 schrieb Simon Albrecht: > \offset positions #'(.5 . .5) Beam I’ve never seen that function before and I don’t find it in the documentation. Since when does this exist? (it’s defined in music-functions-init.ly) ___

Re: How to reproduce this?

Am 07.01.2016 um 22:53 schrieb Malte Meyn: > > > Am 07.01.2016 um 21:59 schrieb Simon Albrecht: >> \offset positions #'(.5 . .5) Beam > > I’ve never seen that function before and I don’t find it in the > documentation. Since when does this exist? (it’s defined in >

Re: How to reproduce this?

On 07.01.2016 23:00, Malte Meyn wrote: Am 07.01.2016 um 22:53 schrieb Malte Meyn: Am 07.01.2016 um 21:59 schrieb Simon Albrecht: \offset positions #'(.5 . .5) Beam I’ve never seen that function before and I don’t find it in the documentation. Since when does this exist? (it’s

Re: How to reproduce this?

On 07.01.2016 19:23, Pierre Perol-Schneider wrote: Oops, my fault, I forgot about the slur. So here it goes, \version "2.18.2" %\language "german" \layout { \context { \ChordNames \override ChordName.font-family = #'serif \override ChordName.font-size = #0 } } << \chords {

Re: Include total page count in page number

2016-01-07 16:55 GMT+01:00 Jan-Peter Voigt : > Ah, yes > To use \page-ref is another option. You just need a label at the end of the > last score. > > Chefredakteur > Jan-Peter > > Am 7. Januar 2016 15:43:26 MEZ, schrieb Robin Bannister : >> >> tisimst wrote:

Re: Strange beaming error

Hi Chris, OK, I've now compiled your score (thanks for the gist, looks nice BTW) and went through the beaming issues I could see. First of all I must say that the new subdivision logic (introduced in 2.19.35) seems to do what I wanted and is actually an improvement: Compare 01.png to 02.png and