Re: How do I shift notes in one voice w/o shifting the other?

On Wed, Nov 29, 2023 at 4:05 PM Knute Snortum wrote: > The original is odd. It has a half note where a quarter note should be. But > if you want to reproduce it exactly, see my code below. No need for > temporary voices. Another wrote to me privately suggesting that the original that I'm co

Re: How do I shift notes in one voice w/o shifting the other?

On Wed, Nov 29, 2023 at 11:54 AM Kevin Cole wrote: > On Wed, Nov 29, 2023 at 10:04 AM Knute Snortum wrote: > > Thanks. > > > I'm not sure what you want to do makes musical sense, that is, the d'>2 and the d'8 should be on the same beat, so why do you want the half > note to the right? > > I'm s

Re: How do I shift notes in one voice w/o shifting the other?

-- Knute Snortum On Tue, Nov 28, 2023 at 6:32 PM Kevin Cole wrote: > I searched for a way to shift notes horizontally but when I shift the > half-note chord in the first voice below, it shifts the second eighth-note > in the second voice, forcing it to stay to the right of the half-note. When

How do I shift notes in one voice w/o shifting the other?

I searched for a way to shift notes horizontally but when I shift the half-note chord in the first voice below, it shifts the second eighth-note in the second voice, forcing it to stay to the right of the half-note. When I tried adding something to shift the beamed eight-notes to the left, it shift

Re: O Canada with Ukrainian lyrics

el Gerdau > Cc: ericmcint...@mac.com, lilypond-user@gnu.org > Subject: Re: O Canada with Ukrainian lyrics > Message-ID: <87v8f9f2yu@fastmail.fm> > Content-Type: text/plain; charset="utf-8" > > > I attached a PDF of O Canada. > > **

Re: O Canada with Ukrainian lyrics

> Once upon a time this built. It might be a good starting point. The included file guitar.ly is missing. It might not be strictly required but I thought I’d mention it. Kind regards, Michael

Re: O Canada with Ukrainian lyrics

acing #'padding = #2 % spacing between title and staff bottom-margin = 0.75\in ragged-last-bottom = ##f tagline = ##f } % paper \layout { \override Score.ChordName #'font-size = #0 \override Score.LyricText #'font-size = #0 } % layout \header {

Re: O Canada with Ukrainian lyrics

ericmcint...@mac.com writes: > This gets me SO much closer!! Thank you so very much Jean and the rest > of the Lilypond community. I have been at this for hours now and I > think I might even be getting the hang of it. > > I’ll work with someone who speaks Ukrainian to help split the words > prope

Re: O Canada with Ukrainian lyrics

lly new to Lillypond and want to compile lyrics and music to O >> Canada for a Canada Day BBQ this Saturday with 50 newcomers from Ukraine. I >> downloaded a version of the song sheet from this wiki site >> <https://commons.wikimedia.org/wiki/File:O_Canada.pdf> and added U

Re: O Canada with Ukrainian lyrics

Le dimanche 25 juin 2023 à 23:30 -0600, ericmcint...@mac.com a écrit : > I am totally new to Lillypond and want to compile lyrics and music to O Canada > for a Canada Day BBQ this Saturday with 50 newcomers from Ukraine. I > downloaded a version of the song sheet from this wiki site 

O Canada with Ukrainian lyrics

Hello:I am totally new to Lillypond and want to compile lyrics and music to O Canada for a Canada Day BBQ this Saturday with 50 newcomers from Ukraine. I downloaded a version of the song sheet from this wiki site and added Ukrainian lyrics but I’m getting an error and don’t know how to interpret

Learning Materials in LilyPond (was: removing staff and clef w/o removing bar lines and brackets)

On 07/12/2017 08:50 AM, Karlin High wrote: Are you aware of this sight-singing textbook... http://www.lightandmatter.com/sight/sight.html ...made with Lilypond and LaTeX, with source code available and customization encouraged under CC-BY-SA license? Thanks for this link. That's a great resou

Re: Fwd: re: removing staff and clef w/o removing bar lines and brackets

It works! Issue resolved - thank you so much for your support. On Wed, Jul 12, 2017 at 5:50 AM, Karlin High wrote: > On 7/11/2017 11:11 AM, Reilly Farrell wrote: > > I'm creating some sight-singing examples for a class > > Are you aware of this sight-singing textbook... > http://www.lightandmat

Re: Fwd: re: removing staff and clef w/o removing bar lines and brackets

On 7/11/2017 11:11 AM, Reilly Farrell wrote: > I'm creating some sight-singing examples for a class Are you aware of this sight-singing textbook... http://www.lightandmatter.com/sight/sight.html ...made with Lilypond and LaTeX, with source code available and customization encouraged under CC-BY-S

Re: Fwd: re: removing staff and clef w/o removing bar lines and brackets

Am 11.07.2017 um 18:11 schrieb Reilly Farrell: Hi All, I'm creating some sight-singing examples for a class and would like to start with some examples with no staff,no clef,no key signature, though keeping bar lines and system brackets (for duet examples) (Solfege syllables are provided as l

Fwd: re: removing staff and clef w/o removing bar lines and brackets

Hi All, I'm creating some sight-singing examples for a class and would like to start with some examples with no staff,no clef,no key signature, though keeping bar lines and system brackets (for duet examples) (Solfege syllables are provided as lyrics.) Currently I am doing something like this

Re: best solution for book making with multiple scores and multiple titles but w/o page breaks between pieces

Here's an explanation how to modify the score's header: http://lilypond.org/doc/v2.19/Documentation/notation/custom-titles-headers-and-footers You should probably also leave the book-level header block empty because it will put in its variable values when you don't set one of the same name in the

Re: best solution for book making with multiple scores and multiple titles but w/o page breaks between pieces

Just override the scoreTitleMarkup variable to look like bookTitleMarkup and then you can put everything in the score's \header. Best, Abraham On Monday, January 11, 2016, Mike Solomon wrote: > Hey all! > > \bookpart forces a page break between pieces in a suite, which I don’t > want, but other

best solution for book making with multiple scores and multiple titles but w/o page breaks between pieces

Hey all! \bookpart forces a page break between pieces in a suite, which I don’t want, but otherwise I like how it prints robust titles for each work. Is there a way to do everything that \bookpart does minus the page breaks? I can create top-level markups instead of using the \header, but it’d

lilypond-book: clean up w/o --output?

Hi all, Trying to establish a workflow for lilypond-book and LaTeX, I am caught up in a conflict between wanting to clean up the small files that lilypond-book creates, but not wanting to use its --output flag. I usually encapsulate my LaTeX-only projects in a single directory containing: - p

Re: Suppressing the o in fret diagrams

On 3/2/10 1:59 AM, "keith Luke" wrote: > Is it possible to suppress the open string indicator in fret diagrams? > > Instead of \fret-diagram #"4-2-2;3-1-1;2-o;1-o;" I would like the equivalent > of \fret-diagram #"4-2-2;3-1-1;2- ;1- ;" where the o doe

Re: Suppressing the o in fret diagrams

Leaving the open strings out works for most fret diagrams, but when I generate an F chord for ukulele, #"2-2;o;1-1;o;" becomes #"2-2;1-1;" and the wrong fret diagram results. Is there a way to put a "null" spacer for the open strings? Thanks, Keith On Mon, M

Re: Suppressing the o in fret diagrams

Original-Nachricht Is it possible to suppress the open string indicator in fret diagrams? Instead of \fret-diagram #"4-2-2;3-1-1;2-o;1-o;" I would like the equivalent of \fret-diagram #"4-2-2;3-1-1;2- ;1- ;" where the o does not appear on strings

Suppressing the o in fret diagrams

Is it possible to suppress the open string indicator in fret diagrams? Instead of \fret-diagram #"4-2-2;3-1-1;2-o;1-o;" I would like the equivalent of \fret-diagram #"4-2-2;3-1-1;2- ;1- ;" where the o does not appear on strings 2 and three.

Re: Quit [now definitely O/T]

Jan-Peter Voigt wrote Thursday, November 12, 2009 3:58 PM So my question would be, is there a guide to the sources? Are there key principals in the architecture? If there is a chance to get into this next to my job, I would really like to give Lily somthing! Thanks for the offer! You will

Re: Quit [now definitely O/T]

Jesús Guillermo Andrade writes: > El 12/11/2009, a las 02:17 p.m., David Kastrup escribió: >> And that's the main point: does the job. The one thing Emacs Lisp has >> going over Common Lisp that it is a reasonably limited language to >> learn >> in comparison. Which is a nuisance to seasoned Li

Re:Quit [now definitely O/T]

Jan wrote: > Quitting with LilyPond seems to cost him nothing. Well, the obvious solution for that is to start charging for Lilypond, so they have a disincentive to quit. ;-) Tim Reeves ___ lilypond-user mailing list lilypond-user@gnu.org http://li

Re: Quit [now definitely O/T]

Dear David: Thank you very much for your reply. If I was not that clear, please accept my apologies. I was not trying to seem pretentious or arrogant (far from it since I went into the thread as a newbie). My first language was COBOL, then Pascal, Perl and C. I barely have some notions of

Re: Quit [now definitely O/T]

Tim McNamara writes: > On Nov 12, 2009, at 2:11 AM, Jan Nieuwenhuizen wrote: > >> Op donderdag 12-11-2009 om 08:41 uur [tijdzone +0100], schreef David >> Kastrup: >> >>> Carl Sorensen writes: >>> >> >> >>> _Addressing_ the actual problems is definitely more suitably done >>> on the >>> developer

Re: Quit [now definitely O/T]

Sorry, I initially just sent this to Jan and meant to send it to the group. On Nov 12, 2009, at 2:11 AM, Jan Nieuwenhuizen wrote: Op donderdag 12-11-2009 om 08:41 uur [tijdzone +0100], schreef David Kastrup: Carl Sorensen writes: _Addressing_ the actual problems is definitely more sui

Re: Quit [now definitely O/T]

Jesús Guillermo Andrade writes: > El 12/11/2009, a las 04:11 a.m., David Kastrup escribió: > > Jan Nieuwenhuizen writes: > > > As a new contributor/developer, by using a different, and a particular > > unfriendly platform for free software development, you are faced with > >

Re: Quit [now definitely O/T]

Hello there!... El 12/11/2009, a las 04:11 a.m., David Kastrup escribió: Continued on developer list. Jan Nieuwenhuizen writes: As a new contributor/developer, by using a different, and a particular unfriendly platform for free software development, you are faced with tackling several diff

Re: Quit [now definitely O/T]

Hello Kieren, hello David, hello out there, I followed this conversation a little bit. Well I have been a quite good C++ coder, but that was about 10 years ago. Right now I am one of those million java developers. For my Job I had to turn to Java, wich I didn't really love. With Java5 it go

Re: Quit [now definitely O/T]

Kieren MacMillan writes: > Hi David, > >> The best programmers are often programmers that are into programming >> for the sake of programming. Ask such a person for help with >> typesetting music, and Lilypond will be one of the points of >> attraction for him, and obstacles are disproving his g

Music Publishing Blog [slightly O/T]

Hello everyone, I've set up a blog dedicated to issues in Music Publishing, and specifically, the use of Open-Source tools in the print side of things. I've just put up two posts, aimed at Educators, dealing with the use of LilyPond, OpenOffice.org and the OOoLilyPond extension. The posts c

Re: Quit [now definitely O/T]

Hi David, The best programmers are often programmers that are into programming for the sake of programming. Ask such a person for help with typesetting music, and Lilypond will be one of the points of attraction for him, and obstacles are disproving his geek state (or the state of what he

Re: Quit [now definitely O/T]

Kieren MacMillan writes: > Possibly, but again irrelevant (or at least orthogonal) to the > discussion: I think that 100% of the new developer base will have > started as part of the user base, since it seems unlikely to the point > of impossibility that a random non-Lilypond-using developer > (L

Re: Quit [now definitely O/T]

Hi David, It's not as bad as the numbers suggest. The ratio of serious developers who will balk at getting their development environment up and running will not be all that large. That may be true, but irrelevant to my point: the vast majority of the potential/actual "serious [new] develo

Re: Quit [now definitely O/T]

On Thu, Nov 12, 2009 at 02:50:08PM +0100, Jan Nieuwenhuizen wrote: > > Put another way, the difficulty of setting up a > > development system on anything but Linux is a significant obstacle to > > Lilypond's potential. > > It would surprise me if you could find many developers that want > to v

Re: Quit [now definitely O/T]

Hi Jan, Well, that's the question, isn't it? It depends on the percentage of users on each platform that are able and willing to contribute. Absolutely. It would surprise me if you could find many developers that want to volunteer their time working on free software, yet continue to do so u

Re: Quit [now definitely O/T]

Kieren MacMillan writes: > Hi Jan, > >> I'm just pointing out that choosing something different will >> --currently still -- cost you. > > Absolutely... and, as we've witnessed, this is almost certainly > materially affecting the number of developers that can/will work on > Lilypond. > > Like it

Re: Quit [now definitely O/T]

Op donderdag 12-11-2009 om 08:36 uur [tijdzone -0500], schreef Kieren MacMillan: Hi Kieren, > Absolutely... and, as we've witnessed, this is almost certainly > materially affecting the number of developers that can/will work on > Lilypond. Of course. > Like it or not, >95% of the computer w

Re: Quit [now definitely O/T]

Hi Jan, I'm just pointing out that choosing something different will --currently still -- cost you. Absolutely... and, as we've witnessed, this is almost certainly materially affecting the number of developers that can/will work on Lilypond. Like it or not, >95% of the computer world is

Re: Quit [now definitely O/T]

On 11/11/09 4:23 PM, "Jonathan Wilkes" wrote: >> >> spannerText = >> #(define-music-function (parser location span-text) >> (string?) >>   #{ >>       \override TextSpanner #'(bound-details >> left text) = #$span-text >>   #") >> >> which would allow above example to be coded much more >> ea

Re: Quit [now definitely O/T]

Op donderdag 12-11-2009 om 05:49 uur [tijdzone -0500], schreef Kieren MacMillan: Hi Kieren, > > There is nothing to learn. Have you seen a file? Adding plain > > text is more intuitive than using Apple's finder. Really. > > Well, since I don't even have a build system that works yet, this is

Re: Quit [now definitely O/T]

Hi Jan, There is nothing to learn. Have you seen a file? Adding plain text is more intuitive than using Apple's finder. Really. Well, since I don't even have a build system that works yet, this is all totally moot at the moment... Chances are problems are fixed before you encounter the

Re: Quit [now definitely O/T]

Jan Nieuwenhuizen writes: > Op donderdag 12-11-2009 om 08:41 uur [tijdzone +0100], schreef David > Kastrup: >> Carl Sorensen writes: > >> _Addressing_ the actual problems is definitely more suitably done on the >> developer list. > > So what are the actual problems? The actual problem is the pa

Re: Quit [now definitely O/T]

Continued on developer list. Jan Nieuwenhuizen writes: > As a new contributor/developer, by using a different, and a particular > unfriendly platform for free software development, you are faced with > tackling several difficult problems at once. > > This is only meant as an observation and an

Re: Quit [now definitely O/T]

Op donderdag 12-11-2009 om 08:41 uur [tijdzone +0100], schreef David Kastrup: > Carl Sorensen writes: > _Addressing_ the actual problems is definitely more suitably done on the > developer list. So what are the actual problems? Is LilyPond really too difficult? Do we rely too much on crufty inp

Re: Quit [now definitely O/T]

Op woensdag 11-11-2009 om 17:47 uur [tijdzone -0500], schreef Kieren MacMillan: > I've got to learn yet another markup language There is nothing to learn. Have you seen a file? Adding plain text is more intuitive than using Apple's finder. Really. > and install a bunch of apps (still in prog

Re: Quit [now definitely O/T]

Carl Sorensen writes: > David, > > I appreciate your persistence in this. I think that you are having part of > the difficulty in this conversation because it's on -user, not on -devel. > > The modifications to anything except input files (which use lilypond code > and embedded scheme) really in

Re: Quit [now definitely O/T]

David, I appreciate your persistence in this. I think that you are having part of the difficulty in this conversation because it's on -user, not on -devel. The modifications to anything except input files (which use lilypond code and embedded scheme) really involve knowledge that's primarily dis

Re:Quit [now definitely O/T]

> > > > Things like "ritardando" can't be found in the > notation index and are > > programmed something like > > > >     Some performance indications, > e.g., rallentando or accelerando, are > >     written as text and are > extended over multiple notes with dotted lines. > >     Such objects, c

Re: Quit [now definitely O/T]

On Nov 11, 2009, at 11:29 AM, David Kastrup wrote: For me, this situation is awkward, impeding and dissatisfactory. For others, it is reason to go away. I don't see that anything is gained for chastising me for my impression. That is merely shooting the messenger. Actually, more than the me

Re: Quit [now definitely O/T]

On Wed, 2009-11-11 at 22:33 +0100, David Kastrup wrote: > Carl Sorensen writes: > > The code to establish a ritardando could be easily written, and may (or may > > not) be done as part of the forthcoming GLISS (Grand LilyPond Input Syntax > > Stabilization) project. There's currently some disagre

Re: Quit [now definitely O/T]

Werner, What's the problem here? The problem is that I come to Lilypond with a skill set — specifically, many years of Java+Javascript+(X)HTML+XSL(T)+CSS+(La) TeX experience — which should be more than adequate for any modern documentation project involving a WWW component. I want to he

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 9:33 PM, David Kastrup wrote: >> \spannerText "rit." >> b1\startTextSpan >> e,\stopTextSpan > > What is wrong with > b1\startSpan "rit." > e,\stopSpan > > ?  Why force meddling with an internal variable in the first place?  You > need the text anyway, why not make it part o

Re: Quit [now definitely O/T]

>> @node Alternate input > > I have to mao-ing learn TEXI now? What's the problem here? If you don't want to do nifty things it's just a quite simple markup language. And since there has already been written a lot of TEXI documentation for lilypond I'm quite sure that you find examples for almo

Re: Quit [now definitely O/T]

Carl Sorensen writes: > David, > > Thanks for your willingness to articulate some concerns. I think that > your careful thinking can be of real help to the LilyPond community, > expecially if you can help us make things better. Thanks for putting up with me. > On 11/11/09 7:21 AM, "David Kastr

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 04:05:59PM -0500, Kieren MacMillan wrote: >> The first thing that comes to mind is Alternate input. >> Documentation/general/introduction.texi >> @node Alternate input > > I have to mao-ing learn TEXI now? > So much for your "2-5 hours" estimate... I stand by my "2-5 hours

Re: Quit [now definitely O/T]

Graham, The first thing that comes to mind is Alternate input. Documentation/general/introduction.texi @node Alternate input I have to mao-ing learn TEXI now? So much for your "2-5 hours" estimate... Still-doing-it-but-thinking-there's-almost-definitely-a-better-way, Kieren. ___

Re: Quit [now definitely O/T]

David, Thanks for your willingness to articulate some concerns. I think that your careful thinking can be of real help to the LilyPond community, expecially if you can help us make things better. On 11/11/09 7:21 AM, "David Kastrup" wrote: > Kieren MacMillan writes: > >> Hi Craig (et al.),

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 03:53:11PM -0500, Kieren MacMillan wrote: >> It does not tell you what language/classes/operations to use to >> implement what kind of task. > > OK, then submit a feature request — rant on -user does not count — and > maybe someone in the know will help out. No, please d

Re: Quit [now definitely O/T]

Jonathan Kulp writes: > On Wed, Nov 11, 2009 at 2:01 PM, Kieren MacMillan < > kieren_macmil...@sympatico.ca> wrote: > > Hi David (and anyone else who makes it here, wondering how to find the > "CG"), > > > > The manuals don't tell anything about "CG", where it is, what it does. >

Re: Quit [now definitely O/T]

Hi David, Where does the GDP document the meaning of the acronym "GDP"? Here's one place (of many): It does not say what kind of code to put where for what reason.

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 03:19:37PM -0500, Kieren MacMillan wrote: > Hi Graham, > >> - 2-5 hours of texinfo file editing > > I just pulled a new origin/master from git. > Today, I've got upwards of 3 hours to code: what do you want me to work > on? The first thing that comes to mind is Alternate i

Re: Quit [now definitely O/T]

On 11/11/09 12:12 PM, "Graham Percival" wrote: > On Wed, Nov 11, 2009 at 06:11:26PM +0100, David Kastrup wrote: > >> But if there is roadmap, design and vision, I have not yet been able to >> find it in the obvious places I have been looking for. > > The information for developers is the CG.

Re: Quit [now definitely O/T]

Kieren MacMillan writes: > Hi David, > > [By the way, since it's apparently open season on posting style > criticism: your consistent lack of salutation and valediction in your > posts makes you seem rude, curt, and above all patronizing.] Perfectly accurate. >> "Reasonable" entails a collectiv

Re: Quit [now definitely O/T]

Hi Graham, the "more available/obvious" choice would be to make the new website the main one. Currently, that's waiting on: - 2-5 hours of texinfo file editing I just pulled a new origin/master from git. Today, I've got upwards of 3 hours to code: what do you want me to work on? Cheers, K

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 2:01 PM, Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hi David (and anyone else who makes it here, wondering how to find the > "CG"), > > > The manuals don't tell anything about "CG", where it is, what it does. >> http://lilypond.org/web/devel/participating/>

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 03:01:33PM -0500, Kieren MacMillan wrote: > Step 3: Click on "Documentation for LilyPond 2.13 (latest development)" > [since you're going to be helping with development, this is the logical > choice]. > Location: >> Not the

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 08:47:33PM +0100, David Kastrup wrote: > > Graham Percival writes: > > > The information for developers is the CG. > > The manuals don't tell anything about "CG", where it is, what it does. > http://lilypond.org/web/devel/participating/> does not tell. There > is no dir

Re: Quit [now definitely O/T]

Hi David (and anyone else who makes it here, wondering how to find the "CG"), The manuals don't tell anything about "CG", where it is, what it does. http://lilypond.org/web/devel/participating/> does not tell. There is no directory of that name in the distribution. Step 1: Go to home page.

Re: Quit [now definitely O/T]

Graham Percival writes: > On Wed, Nov 11, 2009 at 06:11:26PM +0100, David Kastrup wrote: > >> But if there is roadmap, design and vision, I have not yet been able >> to find it in the obvious places I have been looking for. > > The information for developers is the CG. The manuals don't tell an

Re: Quit [now definitely O/T]

Hi David, [By the way, since it's apparently open season on posting style criticism: your consistent lack of salutation and valediction in your posts makes you seem rude, curt, and above all patronizing.] "Reasonable" entails a collective effort not to repeat avoidable work and frustratio

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 07:12:44PM +, Graham Percival wrote: > Other than kidnap + torture, of course. I might vote for this, > but it strikes me that it might cause long-term problems... Addendum: I don't know the details that you want, so torturing me won't help. I'd *like* to know those d

Re: Quit [now definitely O/T]

On Wed, Nov 11, 2009 at 06:11:26PM +0100, David Kastrup wrote: > > Kieren MacMillan writes: > > > I couldn't agree more! [See Steps 1&2, above.] > > I think that sums up very well why somebody would prefer not working > with Lilypond. Not only do you have to rely on expert advice, but the > ma

Re: Quit [now definitely O/T]

Sorry for the post in triplicate. Gmane's response time confused me. Kieren MacMillan writes: > Hi David, > >> I think that sums up very well why somebody would prefer not working >> with Lilypond. Not only do you have to rely on expert advice, but the >> main advice is "please do what an exp

Re: Quit [now definitely O/T]

Hi David, I think that sums up very well why somebody would prefer not working with Lilypond. Not only do you have to rely on expert advice, but the main advice is "please do what an expert would do, or shut up". Please show me where I said anything resembling "shut up"...? I'm sorry if you i

Re: Quit [now definitely O/T]

> I'm not topposting Third attempt because of topposting automoderation -- this _is_ a nuisance. Kieren MacMillan writes: [...] I don't see the "now definitely O/T" you put in the subject line. The subject was that somebody quit, and we are talking about the reason

Re: Quit [now definitely O/T]

Kieren MacMillan writes: [...] I don't see the "now definitely O/T" you put in the subject line. The subject was that somebody quit, and we are talking about the reasons. [...] >> It is too cheap to put this down to "faster". The problem is not >> t

Re: Quit [now definitely O/T]

I don't see the "now definitely O/T" you put in the subject line. The subject was that somebody quit, and we are talking about the reasons. Kieren MacMillan writes: >> It is too cheap to put this down to "faster". The problem is not >> that you need l

Re: Quit [now definitely O/T]

Hi David, It is too cheap to put this down to "faster". The problem is not that you need longer to do some things with Lilypond initially. The problem is that there is a large number of things for which there is no proper way to do them at all, and you have to take out the crowbar. As is

Re: Quit [now definitely O/T]

Kieren MacMillan writes: > Hi Craig (et al.), > >> I must say that the "faster" thing is a typical United States >> behavior. > > Whether or not it started in the USA, it's a worldwide phenomenon now. > =) > [Disclosure: I'm Canadian.] It is too cheap to put this down to "faster". The problem i

Re: Quit [now definitely O/T]

Hi Craig (et al.), I must say that the "faster" thing is a typical United States behavior. Whether or not it started in the USA, it's a worldwide phenomenon now. =) [Disclosure: I'm Canadian.] Our markets and media constantly barrage us with "time" issues. I think maybe "convenience"

change "o" with "dim" in diminished chords

Hi, I need to replace "o" symbol with "dim" for diminished chord names. I can achieve that by overriding a definition in chord-modifiers-init.ly. Is there any elegant way ? The optimal solution would be somewhere in \context { \Cho

Re: ||o||

> > It's probably best to submit a bug report, together with a > > high-resolution scan of such a note head. Werner > > Here it is: > > http://www.nabble.com/file/p18178776/Rondes%2Bdouble%2Bbarr%25C3%25A9es.bmp This is now registered as issue #648. Werner _

Re: ||o||

Werner LEMBERG wrote: > > >> Is this a notehead for ancient music? > > Not really. > >> You'll find it in NR 2.8.1.1 or NR appendix B.5. > > He won't find it since we don't have a glyph for it. It's probably > best to submit a bug report, together with a high-resolution scan of > such a not

Re: ||o||

> > > ||O|| > > > > > > a whole note, with two short vertical lines on both sides. > > > > Is this a notehead for ancient music? You'll find it in NR > > 2.8.1.1 or NR appendix B.5. > > Nope, that's typically used for the breve: &

Re: ||o||

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Sonntag, 29. Juni 2008 schrieb Graham Percival: > sdfgsdhdshd <[EMAIL PROTECTED]> wrote: > > In the new documentation, after looking carefully, i was not able to > > find the section related to the symbol > > > >

Re: ||o||

> Is this a notehead for ancient music? Not really. > You'll find it in NR 2.8.1.1 or NR appendix B.5. He won't find it since we don't have a glyph for it. It's probably best to submit a bug report, together with a high-resolution scan of such a note head. Werner __

O Magnum Mysterium

I think that I've sent a copy of my .ly file to everyone that requested one. If I missed you let me know. It's de Victoria's O Magnum Mysterium. The file generates choir, individual parts, choir with piano reduction, and midi files for choir and for each

Re: ||o||

ction related to the symbol > ||O|| > a whole note, with two short vertical lines on both sides. > > In section 1.2.1.1 there is the whole note with one short vertical > lines on both sides, but not 2. > > Thanks. > > -- > View this message in context: > http://

||o||

In the new documentation, after looking carefully, i was not able to find the section related to the symbol ||O|| a whole note, with two short vertical lines on both sides. In section 1.2.1.1 there is the whole note with one short vertical lines on both sides, but not 2. Thanks. -- View this

Re: O Magnum Mysterium is done

2008/6/24 Patrick Horgan <[EMAIL PROTECTED]>: > If anyone would like a copy of the .ly pond for O Magnum Mysterium drop me a > note and I'll email you a copy. Perhaps you should consider sending your updated code to the Mutopia project, using the e-mail address

O Magnum Mysterium is done

If anyone would like a copy of the .ly pond for O Magnum Mysterium drop me a note and I'll email you a copy. But--if you get a copy and print it please check for problems and if you see anything that could be improved, let me know:) It prints a choral score in one pdf, another pdf wit

Re: Semicircle (or fermata w/o dot)

> It is also too small. OK. > However, I anyway feel need for more symbols in the Feta font and/or > a ps symbol repository. No problem. Just send me (and Jürgen Reuter) a scan from the symbol which shows its typical usage. Werner ___ lilypond

Re: Semicircle (or fermata w/o dot)

2007/7/14, Bertalan Fodor <[EMAIL PROTECTED]>: It is also too small. I find it much easier to include explicit postscript. However, I anyway feel need for more symbols in the Feta font and/or a ps symbol repository. If in some time I have enough Postscript-related snippets, I'll ask Sebastiano

Re: Semicircle (or fermata w/o dot)

It is also too small. I find it much easier to include explicit postscript. However, I anyway feel need for more symbols in the Feta font and/or a ps symbol repository. Bert Valentin Villenave írta: 2007/7/13, Werner LEMBERG <[EMAIL PROTECTED]>: Why not using the `semicirculus' glyph from t

Re: Semicircle (or fermata w/o dot)

2007/7/13, Werner LEMBERG <[EMAIL PROTECTED]>: Why not using the `semicirculus' glyph from the parmesan font? I think this is better than using explicit PS code... AFAIK, the \semicirculus is upside down compared to what Bert's looking for; so in that case one would have to rotate it by 180°

  1   2   >