Re: Super and sub

Hi all, Please be so kind to attached objective examples including publishers' name. What you "imagine", what's "possible" or "seems like" won't help much here... Cheers, Pierre 2016-02-06 22:24 GMT+01:00 John Gourlay : > Joram, > > As you say, LaTeX is for producing

Re: Super and sub

Am 6. Februar 2016 22:24:41 MEZ, schrieb John Gourlay : >Joram, > >As you say, LaTeX is for producing beautiful mathematics and LilyPond >is for producing beautiful music. It’s possible that the conventions in >the two different kinds of typography differ in their

Super and sub

Dear all, in a recent question on this list [1] about \super in markup text, all three replies suggested to tweak the vertical position of superscripts by hand because the default is obviously too high. I compared the Lilypond result of \super and \sub to the equivalents in LaTeX (because who

Re: Super and sub

Kieren MacMillan wrote Saturday, February 06, 2016 8:03 PM >> - raise the superscript by 0.8 instead of 1.0 >> - lower the subscript by -0.4 instead of -0.75 > > In my opinion, these are both improvements on the current default. I agree. Trevor ___

Re: Super and sub

>> I compared the Lilypond result of \super and \sub to the >> equivalents in LaTeX (because who would doubt that LaTeX is wrong >> in such a question) Please have a look at other, non-CM fonts also, since CM is sometimes a bit peculiar :-) >> - raise the superscript by 0.8 instead of 1.0 >> -

Re: Grace notes and voices.

On 07.02.2016 01:13, Hwaen Ch'uqi wrote: Having searched rather thoroughly through the archives, I understand that the issue of grace notes within voice contexts is a perennial one. Unfortunately, the Known Issues and Warnings do not address my problem, and the example is, to my mind, incredibly

Re: Super and sub

Hi Joram, > I compared the Lilypond result of \super and \sub to the equivalents in > LaTeX (because who would doubt that LaTeX is wrong in such a question) =) > Of course LilyPond's emphasis is on beautiful music notation, > but I think also text parts of scores should look good. Agreed! > -

Re: Super and sub

+1 See the wish I had in 2013: http://lilypond.1069038.n5.nabble.com/WISH-about-super-and-sub-td152384.html Pierre 2016-02-06 21:34 GMT+01:00 Trevor Daniels : > > Kieren MacMillan wrote Saturday, February 06, 2016 8:03 PM > > >> - raise the superscript by 0.8 instead of

Re: Super and sub

Joram, As you say, LaTeX is for producing beautiful mathematics and LilyPond is for producing beautiful music. It’s possible that the conventions in the two different kinds of typography differ in their placement of sub and superscripts, and so LaTeX and LilyPond should differ in their

Grace notes and voices.

Greetings All, Having searched rather thoroughly through the archives, I understand that the issue of grace notes within voice contexts is a perenial one. Unfortunately, the Known Issues and Warnings does not address my problem, and the example is, to my mind, incredibly contrived. At the root of

Re: More ponderings on Chordmode

"Peter Gentry" writes: > Thanks Chris I guessed most of the format but the # Escaped me. To > # or not to # that is the question. > >> \chords { >> \set ChordNames.midiInstrument = #"acoustic guitar (steel)" >> \myChordsTransposed >> } I

RE: More ponderings on Chordmode

>-Original Message- >From: David Kastrup [mailto:d...@gnu.org] >Sent: Saturday, February 06, 2016 10:50 AM >To: Peter Gentry >Cc: lilypond-user@gnu.org; 'Christopher R. Maden' >Subject: Re: More ponderings on Chordmode > >"Peter Gentry" writes: > >>

Re: Super and sub

I was thinking that text produced by LilyPond would likely be about music, with references, for example, to chords with superscripts in their names. It would appear odd if the chord names in text appeared differently than in the music itself. John

RE: More ponderings on Chordmode

>-Original Message- >From: lilyp...@andis59.se [mailto:lilyp...@andis59.se] >Sent: Saturday, February 06, 2016 11:24 AM >To: Peter Gentry; lilypond-user@gnu.org >Subject: Re: More ponderings on Chord // Anders wrote >I'm just using the in Windows built in synthesizer so it >doesn't sound

Re: More ponderings on Chordmode

Just to be sure. You removed the \chordnames part and added the \chords. When I did this I got a guitar (well, it didn't sound like a guitar, but it was not a piano) both for the melody and the chords. I think it would be beneficial if you attached the .ly file so we can see what you have

RE: More ponderings on Chordmode

Thanks Chris I guessed most of the format but the # Escaped me. To # or not to # that is the question. >Date: Fri, 5 Feb 2016 14:33:22 -0600 >From: "Christopher R. Maden" >To: lilypond-user@gnu.org >On 02/05/2016 02:31 PM, Peter Gentry wrote: >> I cannot discover a

RE: More ponderings on Chordmode

I must be a tad slow. However I incorporate your suggestion still no guitar sounds when the chords play (only for the melody notes). The snippet does compile without error but seems to have zero effect. Thanks Chris I guessed most of the format but the # Escaped me. To # or not to # that

Re: Superscript in \markup environment

Hi Harm, Thank you very much for your help. Ref.: "You could have added what exactly you tried already.” : It did not work, probably because I just inserted it into the text instead of placing it outside the pair of quotation marks. I was not aware of that condition. I'm glad you also pointed

Re: Superscript in \markup environment

Dear Joram, Thank you for your help. I had already tried \concat { "5" \super "ths" } but it did not work. I see now that this code must be outside the pair of quotemarks containing the "normal" text, a condition I wasn't aware of. I'm glad you also pointed out the possibilities to fine-tune

Re: Superscript in \markup environment

Dear Abraham, Thank you for your advice, which did help. I had already tried \concat { a \super b }, but it did not work because, as I see now, I had just inserted it into the text instead of placing it outside the pair of quotation marks. I'm glad you also pointed out the possibilities to

Re: More ponderings on Chordmode

Message: 5 Date: Sat, 6 Feb 2016 11:27:16 +0100 From: "lilyp...@andis59.se" To: lilypond-user@gnu.org Subject: Re: More ponderings on Chordmode Message-ID: <56b5ca84.8050...@andis59.se> Content-Type: text/plain; charset=windows-1252; format=flowed Just to be sure. You

RE: More ponderings on Chordmode

Hello Colin Yes the melody notes on the staff play as a "guitar" but the chords sound as the default piano. >-Original Message- >From: Colin Campbell [mailto:c...@shaw.ca] >Sent: Saturday, February 06, 2016 1:02 AM >To: Peter Gentry; lilypond-user@gnu.org >Subject: Re: More ponderings

Re: More ponderings on Chordmode

On 2016-02-06 12:05, Peter Gentry wrote: I have tried a couple of different instrument names. The chord sound does vary but still very much piano like. \score { << \chords { \set ChordNames.midiInstrument = #"banjo" \myChordsTransposed } \new FretBoards { \set

RE: More ponderings on Chordmode

>-Original Message- >From: Steve Downes [mailto:st...@kingswayelec.co.uk] >Sent: Saturday, February 06, 2016 11:48 AM >To: lilyp...@andis59.se >Cc: Peter Gentry; lilypond-user@gnu.org >Subject: Re: More ponderings on Chordmode > >It may or may not be relevant but I find if I do what

Re: More ponderings on Chordmode

It may or may not be relevant but I find if I do what have you done I can get it change to sample to a guitar sound. However it doesn't sound like a guitar to me unless I sort out the chord voicing to a guitar inversion as well. This is quite a bit of work so I usually silence the chord names so

Re: More ponderings on Chordmode

"Peter Gentry" writes: > > >>-Original Message- >>From: David Kastrup [mailto:d...@gnu.org] >>Sent: Saturday, February 06, 2016 10:50 AM >>To: Peter Gentry >>Cc: lilypond-user@gnu.org; 'Christopher R. Maden' >>Subject: Re: More ponderings on Chordmode >>