Alternative subtleties

Hello folks, I’ve always used \alternative with a list of bracketed elements, and just found that example in the Notation Reference: \version "2.19.44" forget = #(define-music-function (music) (ly:music?) #{ \accidentalStyle forget #music \accidentalStyle modern #}) { \acci

Re: Getting a new computer

Hi Vaughan, Despite one comment here on the list, using as SSD will make no virtually no noticeable difference to lilypond. It is not disk IO bound, and we are not talking about reading gigabytes of files. You may want an SSD for general reasons, but in terms of pure lilypond, having the fastest C

Re: Getting a new computer

On 17 November 2016 at 13:24, Vaughan McAlley wrote: > Greetings, > > My 2008 iMac is reaching the end of its useful life, and I would like to > replace it with some kind of desktop computer that runs Debian. Given that a > significant proportion of my time on this new computer will be compiling >

Re: Photoscore

Am 28. November 2016 01:58:07 MEZ, schrieb Chris Yate : >On 27 Nov 2016 23:49, "Urs Liska" wrote: >> >> >> >> Am 28.11.2016 um 00:41 schrieb Chris Yate: >>> >>> Hi Jacques, >>> >>> I don't know... It seems ridiculous that they have no common format >- >but it's a relatively tiny industry... But

Re: LSR - file information [0.24759]

Hi Harm, In your code, isn't it just slightly odd breaking scheme for a function across several calls to #define in lilypond? While that seems to be possible (although strangely I can't get your code to compile, with unhelpful error messages, but never mind that), would one not write a single fun

Re: Photoscore

On 27 Nov 2016 23:49, "Urs Liska" wrote: > > > > Am 28.11.2016 um 00:41 schrieb Chris Yate: >> >> Hi Jacques, >> >> I don't know... It seems ridiculous that they have no common format - but it's a relatively tiny industry... But I doubt the big houses like Peters and Barenreiter use either Sibeli

Re: LSR - file information [0.24759]

On Sun 27 Nov 2016 at 22:51:15 (+0100), Thomas Morley wrote: > 2016-11-27 19:48 GMT+01:00 Trevor Daniels : > > > > David Kastrup wrote Sunday, November 27, 2016 5:14 PM > > > >> File names are a tricky area in itself. I think that there is some > >> normalization process involved in some systems t

Re: Photoscore

Am 28.11.2016 um 00:41 schrieb Chris Yate: > Hi Jacques, > > I don't know... It seems ridiculous that they have no common format - > but it's a relatively tiny industry... But I doubt the big houses > like Peters and Barenreiter use either Sibelius or Finale... The big houses more or less *excl

Re: Photoscore

Hi Jacques, I don't know... It seems ridiculous that they have no common format - but it's a relatively tiny industry... But I doubt the big houses like Peters and Barenreiter use either Sibelius or Finale... In the larger world of office IT, Microsoft have dealt with the issue of everyone expec

Re: Photoscore

Am 28.11.2016 um 00:20 schrieb Jacques Menu Muzhic: > Hello Chris, > > How does Finale behave in the commercial publishing industry, compared > to Sibelius, in terms of market share? AFAICT they're about the same. Much more interesting IMHO is how Dorico will change the market - and how it will

Re: Photoscore

Hello Chris, How does Finale behave in the commercial publishing industry, compared to Sibelius, in terms of market share? > Le 28 nov. 2016 à 00:03, Chris Yate a écrit : > > Hi Andrew > > > Apologies in advance, I'm going to be *that guy*... ;-) > > > > For what it’s worth, I’m a huge

Re: Photoscore

Hi Andrew Apologies in advance, I'm going to be *that guy*... ;-) For what it’s worth, I’m a huge fan of Linux, Lilypond and Muse and all the other wonderful **free** tools that we have available BUT if I was in any sense interested in working with a commercial publisher – especially for p

Re: Photoscore

> "Jacques" == Jacques Menu Muzhic writes: Jacques> Oups, totally forgot I had tested it two years ago, my Jacques> fault. So use a different email to get another free trial. -- Laura (mailto:lcon...@laymusic.org) (617) 661-8097

Re: LSR - file information [0.24759]

2016-11-27 19:48 GMT+01:00 Trevor Daniels : > > David Kastrup wrote Sunday, November 27, 2016 5:14 PM > >> File names are a tricky area in itself. I think that there is some >> normalization process involved in some systems that tries to make sure >> that something like an ä will be recognized reg

Re: header in movements

2016-11-27 20:39 GMT+01:00 Mark Stephen Mrotek : > Abraham, > > > > Thank you for your response. > > Yet the “Title” and “Composer” do not migrate. > > Should each movement has its own header? Hi Mark, From NR 3.2.1 Creating titles headers and footers: A Score Title is derived from fields set a

RE: header in movements

Abraham, Thank you for your response. Yet the “Title” and “Composer” do not migrate. Should each movement has its own header? Mark From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of tisimst Sent: Sunday, November 27, 2016 10:23 AM To: lilypon

Re: LSR - file information [0.24759]

David Kastrup wrote Sunday, November 27, 2016 5:14 PM > File names are a tricky area in itself. I think that there is some > normalization process involved in some systems that tries to make sure > that something like an ä will be recognized regardless of whether it is > written as a single cha

Re: header in movements

That's because you put it in the global header block. By default, any properties set there will trickle down to any other header unless set to another value(including ##f). HTH, Abraham On Sun, Nov 27, 2016 at 10:56 AM Mark Stephen Mrotek [via Lilypond] < ml-node+s1069038n197139...@n5.nabble.com>

Unfolding percents in score only

As far as I can tell, short of writing tagged sections, there's no way to easily unfold only percents, while leaving voltas intact. Would this be a desirable behavior for Lilypond to have? My particular use case is transcribing band music. The inner parts of marches often use percent repeats in th

header in movements

Hello, When using the construction \version "2.18.2" \header { opus = "Hob. XVI :27" } \include "XVI27-1.ly" \pageBreak \include "XVI27-2.ly" \pageBreak \include "XVI27-3.ly" The opus appears not only before the first movement but also with the second and third. Thank you

Re: LSR - file information [0.24759]

2016-11-27 18:14 GMT+01:00 David Kastrup : > Thomas Morley writes: > >> I tracked it down to a guile problem. >> >> I stored in a file called filename_名字.scm nothing else then: >> >> ; >> >> (newline) >> (write (command-line)) >> >> (newline) >> (write (map string->symbol (

Re: LSR - file information [0.24759]

Thomas Morley writes: > I tracked it down to a guile problem. > > I stored in a file called filename_名字.scm nothing else then: > > ; > > (newline) > (write (command-line)) > > (newline) > (write (map string->symbol (command-line))) > > ; > > Navigat

Re: Automatic lyric colouring

Wonderful! Works perfectly. Thank you very much. On 27 November 2016 at 13:26, Thomas Morley wrote: > 2016-11-27 2:40 GMT+01:00 Jack Mackenzie : > > I'm trying to put together an engraver for educational purposes, with > > noteheads coloured according to a particular scheme, and lyrics following

Re: LSR - file information [0.24759]

Adnrew and Harm Thank you for helping. It is not mandatory to use UTF-8 characters for file name, but it will be a bonus. Since file system (window 10) support utf-8 for file name, the file name with UTF-8 be pass through lilypond as in header, lyrics do. I did some test UTF-8 can also be used a

Re: Automatic lyric colouring

2016-11-27 2:40 GMT+01:00 Jack Mackenzie : > I'm trying to put together an engraver for educational purposes, with > noteheads coloured according to a particular scheme, and lyrics following > this colouring. > > I've used the snippet for notehead colouring successfully > (http://lsr.di.unimi.it/LS

Re: Automatic lyric colouring

Am 27.11.2016 um 12:00 schrieb Urs Liska: > I *think* what is necessary here is an "engraver". This will process > the stuff in a second run-through and can determine what happens in > other contexts at the same time. > > Probably too complicated if you're not already familiar with Scheme, > but

Re: Automatic lyric colouring

Just to pipe in, although no idea: very interesting question! Looking forward to an answer! Jo' On Sun, Nov 27, 2016 at 12:01 PM +0100, "Urs Liska" mailto:u...@openlilylib.org>> wrote: I *think* what is necessary here is an "engraver". This will process the stuff in a second run-through and

Re: Automatic lyric colouring

I *think* what is necessary here is an "engraver". This will process the stuff in a second run-through and can determine what happens in other contexts at the same time. Probably too complicated if you're not already familiar with Scheme, but worth the effort for your use case, I think. There

Re: LSR - file information [0.24759]

2016-11-27 5:49 GMT+01:00 Andrew Bernard : > Hi Ming, > > > Indeed yes that fails, using a filename with Chinese characters. As as > aside, I myself have been learning to read and write and speak Chinese for a > long time. However, I have never had the need to do it in Lilypond. I am not > sure tha