Re: Natural marked with a sharp symbol (mensural notation)

Hi Lukas, On 25/07/2020 20:16, Lukas-Fabian Moser wrote: I stumbled upon a score in G minor where a E natural would be marked as a E note preceded by a sharp symbol. What would be a “clean” way to achieve that? I have thought of redefining the natural symbol by the sharp one, but:   1. I

Re: Natural marked with a sharp symbol (mensural notation)

Hi Niols, I stumbled upon a score in G minor where a E natural would be marked as a E note preceded by a sharp symbol. What would be a “clean” way to achieve that? I have thought of redefining the natural symbol by the sharp one, but:   1. I don't know how to do this.   2. This would

Natural marked with a sharp symbol (mensural notation)

Hello, I stumbled upon a score in G minor where a E natural would be marked as a E note preceded by a sharp symbol. What would be a “clean” way to achieve that? I have thought of redefining the natural symbol by the sharp one, but: 1. I don't know how to do this. 2. This would not work

RE: positioning a natural

To: lilypond-user@gnu.org Subject: Re: positioning a natural Am 03.01.20 um 06:55 schrieb Mark Stephen Mrotek: > Hello All, > > In the following the natural should be associated with the a4. > > Any suggestions/corrections welcome. How about this? \version "

Re: positioning a natural

Am 03.01.20 um 06:55 schrieb Mark Stephen Mrotek: Hello All, In the following the natural should be associated with the a4. Any suggestions/corrections welcome. How about this? \version "2.19.83" \relative c'' { << { ais8 ([b]) } \\ {

positioning a natural

Hello All, In the following the natural should be associated with the a4. Any suggestions/corrections welcome. Thank you for your kind attention. Mark \version "2.19.83" \relative c'' { <<{ais8 ([b])}\\ {\once \override NoteColumn #'force-hshift = #1 a!4}>> }

Re: removing automatically generated natural signs

On Sun, Dec 10, 2017 at 03:16:12PM EST, David Wright wrote: > On Fri 08 Dec 2017 at 16:21:41 (-0500), Chris Jones wrote: > > On Fri, Dec 08, 2017 at 02:22:32PM EST, Ben wrote: > > > ( > > > On 12/8/2017 2:09 PM, Chris Jones wrote: [..] > This response seems to invite a brief explanation. > >

Re: removing automatically generated natural signs

in it in more detail. > > > > LilyPond makes a clear distinction between musical content and layout. The > > alteration (flat, natural sign or sharp) of a note is part of the pitch, and > > is therefore musical content. Whether an accidental (a */printed/***flat, > >

Re: removing automatically generated natural signs

On 08.12.2017 23:18, Chris Jones wrote: As a matter of fact without being an expert I have great respect for quality typesetting, past and present... paper-oriented or digital. Quality typesetting requires some degree of understanding about what you are typesetting; so if you’re going to do

Re: removing automatically generated natural signs

On Fri, Dec 08, 2017 at 04:40:51PM EST, David Kastrup wrote: > Chris Jones writes: > [..] > > Don't underestinmate the anonymous grease monkeys in printers' shops. Far from my intention I can assure you. As a matter of fact without being an expert I have great respect for

Re: removing automatically generated natural signs

On Fri, Dec 08, 2017 at 03:30:00PM EST, Simon Albrecht wrote: > On 08.12.2017 20:09, Chris Jones wrote: > > Wouldn't this become rather painful/tedious if the gentleman who wrote > > this particular song had had the bright idea of transposing it to > > a fancier key like... G# major for instance?

Re: removing automatically generated natural signs

Chris Jones writes: > But that is precisely the documentation I have been reading over and > over without being able to quite understand the implications. > > And I think that my problem lies with the last word: "... hear". > > Since I am not a musician but a mere scribe

Re: removing automatically generated natural signs

On Fri, Dec 08, 2017 at 03:23:35PM EST, Noeck wrote: > Hi, > > this isa bad hack I would not recommend, but you *could* revert the key > back to c major without showing it: > > \relative { > \key g \major > c' > \once \omit Staff.KeyCancellation > \key c \major > d e f g a b c > } > >

Re: removing automatically generated natural signs

only affects the > */printed/***accidentals, not the note’s pitch! > > --> This is a feature that often causes confusion to newcomers, so let us > explain it in more detail. > > LilyPond makes a clear distinction between musical content and layout. The > alteration (flat,

Re: removing automatically generated natural signs

On 08.12.2017 20:58, Urs Liska wrote: I think this is a great way to explain this concept. And I also belong to the party of those who want to write down (encode) what it*is* and not what it looks like. However, sometimes in ancient music accidentals are _not_ part of the actual content,

Re: removing automatically generated natural signs

On 08.12.2017 20:09, Chris Jones wrote: Wouldn't this become rather painful/tedious if the gentleman who wrote this particular song had had the bright idea of transposing it to a fancier key like... G# major for instance? If that were the case I would have to add an "is" to just about every

Re: removing automatically generated natural signs

Hi, this isa bad hack I would not recommend, but you *could* revert the key back to c major without showing it: \relative { \key g \major c' \once \omit Staff.KeyCancellation \key c \major d e f g a b c } Midi, transposition etc. will be broken, of course. Cheers, Joram

Re: removing automatically generated natural signs

gt; pitches and the key signature. The key signature only affects the >>> */printed/***accidentals, not the note’s pitch! >>> >>> --> This is a feature that often causes confusion to newcomers, so >let >>> us explain it in more detail. >>> >>

Re: removing automatically generated natural signs

Urs, > But to be fair one should note that there are serious encoding systems out > there that work like the OP expects, for example the MEI encoding format or > the Amadeus notation software. > When I discussed the topic with an Amadeus power user he said that he would > go nuts with all the

Re: removing automatically generated natural signs

n causes confusion to newcomers, so let us explain it in more detail. LilyPond makes a clear distinction between musical content and layout. The alteration (flat, natural sign or sharp) of a note is part of the pitch, and is therefore musical content. Whether an accidental (a */printed/***flat, natural

Re: removing automatically generated natural signs

Am 8. Dezember 2017 20:22:32 MEZ schrieb Ben <soundsfromso...@gmail.com>: >( >On 12/8/2017 2:09 PM, Chris Jones wrote: >> I would need some help removing the autmatically generated natural >signs >> that I see in lilypond's output. >> >> |

Re: removing automatically generated natural signs

On Fri 08 Dec 2017 at 14:09:31 (-0500), Chris Jones wrote: > I would need some help removing the autmatically generated natural signs > that I see in lilypond's output. > > I coded this: > > | global = { > | \time 4/4 > | \key g \major > | \tempo \marku

Re: removing automatically generated natural signs

( On 12/8/2017 2:09 PM, Chris Jones wrote: I would need some help removing the autmatically generated natural signs that I see in lilypond's output. | melody = \relative c { | \global | \partial 16 d'16 \bar "||" | \set melismaBusy

Re: removing automatically generated natural signs

On 12/8/2017 2:09 PM, Chris Jones wrote: I would need some help removing the autmatically generated natural signs that I see in lilypond's output. I coded this: | global = { | \time 4/4 | \key g \major | \tempo \markup { \concat {Mouv. \super t} de Marche} | } | | #(set

Re: removing automatically generated natural signs

On 12/8/2017 2:09 PM, Chris Jones wrote: I would need some help removing the autmatically generated natural signs that I see in lilypond's output. I coded this: | global = { | \time 4/4 | \key g \major | \tempo \markup { \concat {Mouv. \super t} de Marche} | } | | #(set

removing automatically generated natural signs

I would need some help removing the autmatically generated natural signs that I see in lilypond's output. I coded this: | global = { | \time 4/4 | \key g \major | \tempo \markup { \concat {Mouv. \super t} de Marche} | } | | #(set-global-staff-size 16.5) | | melody

Re: How to fix bad overlap between normalsize and smaller note sharp, flat, natural?

Ben wrote: > Which accidentals did you want to show, the larger one? > You could just do a few overrides I think, like this: > (see attached) > > Is this what you meant? Yes exactly as i was looking for, thank you so much Ben and have a nice day! Peter

Re: How to fix bad overlap between normalsize and smaller note sharp, flat, natural?

On 10/21/2017 1:11 PM, Pieter Terpstra wrote: Dear lilypond users, How would you recommend to fix this? Most kindly, Peter Have an example here: \version "2.18.2" \relative c'' { \key gis \minor \time 2/4 << { % Voice "1" \teeny g16 ais b cis d e fis gis | eis, fis gis a

How to fix bad overlap between normalsize and smaller note sharp, flat, natural?

Dear lilypond users, How would you recommend to fix this? Most kindly, Peter Have an example here: \version "2.18.2" \relative c'' { \key gis \minor \time 2/4 << { % Voice "1" \teeny g16 ais b cis d e fis gis | eis, fis gis a eis!4 } \\ { % Voice "2" g4 d' | eis,4 eis!

Re: "natural width" of a measure

2017-04-11 22:34 GMT+02:00 David Nalesnik : > Here's how you can determine the widths of measures. Note that I've > put everything on one line, so that the \once \override of the > NoteHead gives access to every column in the score. You can adjust > what alignment

Re: "natural width" of a measure

e: >>>>> >>>>> >>>>> Am 11.04.2017 um 20:46 schrieb Malte Meyn: >>>>>> Am 11.04.2017 um 20:36 schrieb Urs Liska: >>>>>>> So, is there any moment in the compilation process where the >natural, >>>

Re: "natural width" of a measure

t;>> >>> >>> >>> On Tue, Apr 11, 2017 at 1:00 PM, Urs Liska [via Lilypond] <[hidden email]> >>> wrote: >>>> >>>> >>>> Am 11.04.2017 um 20:46 schrieb Malte Meyn: >>>>> Am 11.04.2017 um 20:36 schri

Re: "natural width" of a measure

mail]> >> wrote: >>> >>> >>> Am 11.04.2017 um 20:46 schrieb Malte Meyn: >>>> Am 11.04.2017 um 20:36 schrieb Urs Liska: >>>>> So, is there any moment in the compilation process where the natural, >>>>> unstretche

Re: "natural width" of a measure

m 20:46 schrieb Malte Meyn: >> > >> > Am 11.04.2017 um 20:36 schrieb Urs Liska: >> >> So, is there any moment in the compilation process where the natural, >> >> unstretched length of a measure can be calculated? It doesn't have to >> >> be

Re: "natural width" of a measure

>> So, is there any moment in the compilation process where the > natural, > >> unstretched length of a measure can be calculated? It doesn't > have to be > >> an easily-read property and can involve calculation, but > actually

Re: "natural width" of a measure

hrieb Malte Meyn: >>>> Am 11.04.2017 um 20:36 schrieb Urs Liska: >>>>> So, is there any moment in the compilation process where the natural, >>>>> unstretched length of a measure can be calculated? It doesn't have to be >>>>> an easily

Re: "natural width" of a measure

:36 schrieb Urs Liska: >>>> So, is there any moment in the compilation process where the natural, >>>> unstretched length of a measure can be calculated? It doesn't have to be >>>> an easily-read property and can involve calculation, but actually the x >

Re: "natural width" of a measure

On Tue, Apr 11, 2017 at 1:52 PM, Urs Liska <u...@openlilylib.org> wrote: > > > Am 11.04.2017 um 20:46 schrieb Malte Meyn: >> >> Am 11.04.2017 um 20:36 schrieb Urs Liska: >>> So, is there any moment in the compilation process where the natural, >>> unst

Re: "natural width" of a measure

On Tue, Apr 11, 2017 at 1:00 PM, Urs Liska [via Lilypond] < ml-node+s1069038n202184...@n5.nabble.com> wrote: > > > Am 11.04.2017 um 20:46 schrieb Malte Meyn: > > > > Am 11.04.2017 um 20:36 schrieb Urs Liska: > >> So, is there any moment in the c

Re: "natural width" of a measure

Am 11.04.2017 um 20:46 schrieb Malte Meyn: > > Am 11.04.2017 um 20:36 schrieb Urs Liska: >> So, is there any moment in the compilation process where the natural, >> unstretched length of a measure can be calculated? It doesn't have to be >> an easily-read property and

Re: "natural width" of a measure

Am 11.04.2017 um 20:36 schrieb Urs Liska: > So, is there any moment in the compilation process where the natural, > unstretched length of a measure can be calculated? It doesn't have to be > an easily-read property and can involve calculation, but actually the x > position of the ba

"natural width" of a measure

Hi, is there any chance to retrieve the "natural width" of a measure after typesetting but before the line is stretched to the full line width? This is a rather long-term question, but it would be terrific if - upon a compilation - I could retrieve a list of initial widths of each mea

Re: Accidental/natural on the same note in a polyphonic staff.

t; > *To:* lilypond-user <lilypond-user@gnu.org> > *Sent:* Monday, September 05, 2016 1:30 PM > *Subject:* Accidental/natural on the same note in a polyphonic staff. > > Hi All, > > This question comes from the French list: > http://lilypond-french-users.12989

Re: Accidental/natural on the same note in a polyphonic staff.

https://sourceforge.net/p/testlilyissues/issues/1134/ ? -- Phil Holmes - Original Message - From: Pierre Perol-Schneider To: lilypond-user Sent: Monday, September 05, 2016 1:30 PM Subject: Accidental/natural on the same note in a polyphonic staff. Hi All

Re: Accidental/natural on the same note in a polyphonic staff.

That's it!! Thanks for the reminder Robin. Cheers, Pierre 2016-09-05 20:47 GMT+02:00 Robin Bannister : > Pierre Perol-Schneider wrote: > >> Now I'm sure to have read something about this situation but I cannot find >> it... >> (A much simpler solution). >> > > > Well, the

Re: Accidental/natural on the same note in a polyphonic staff.

Pierre Perol-Schneider wrote: Now I'm sure to have read something about this situation but I cannot find it... (A much simpler solution). Well, the following technique might be considered _simpler_ but is it acceptable as a _solution_ ? \relative c' { \omit TupletBracket \omit

Accidental/natural on the same note in a polyphonic staff.

} \\ { \once\override NoteColumn.force-hshift = #2.1 <c, f> %% => j'imposerai le bécarre ici afin d'éviter %% l'espacement indésirable du silence : %% (natural sign placed here to avoid the rest misplacement) \once\

Re: Removing "cautionary" natural

er a b > this last b has a natural mark (like the previous one) because (I think) > it is in a different pitch. > > Nevertheless I would like to "remove" (hide) it. > > What is the easiest way? > > THank you > Alberto > >

Re: Removing "cautionary" natural

On 08/11/15 18:16, tisimst wrote: \once \omit Accidental Like a charm. Thank you! Alberto ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Removing "cautionary" natural

Hello I have a melody where, somewhere, there is a bes a little later, the is a bes' then a b' and later a b this last b has a natural mark (like the previous one) because (I think) it is in a different pitch. Nevertheless I would like to "remove" (hide) it. What is the easiest w

quarter tone - hide natural that appears to cancel key sig

Hi, So, I am in the key of B flat, and one melody line has in it a beh (B quarter-flat). When it renders, I get a natural sign followed by a quarter-flat sign - how can I have just the quarter flat? The natural seems redundant in this context. Thanks

Re: quarter tone - hide natural that appears to cancel key sig

Am 22.08.2015 um 00:35 schrieb Ian Rashkin: Hi, So, I am in the key of B flat, and one melody line has in it a beh (B quarter-flat). When it renders, I get a natural sign followed by a quarter-flat sign - how can I have just the quarter flat? The natural seems redundant in this context

how to prevent natural sign?

Hi there, I don't want the natural sign to be displayed. However, I don't find a way to do so. Many thanks! Regards, Jinsong \version 2.19.18 \relative c'' { \clef treble % \set Staff.extraNatural = ##f r4 g bes r g b } ___ lilypond

Re: how to prevent natural sign?

Hi, On Thu, Apr 9, 2015 at 9:10 AM, Jinsong Zhao jsz...@yeah.net wrote: Hi there, I don't want the natural sign to be displayed. However, I don't find a way to do so. Many thanks! Regards, Jinsong \version 2.19.18 \relative c'' { \clef treble % \set Staff.extraNatural = ##f r4

Re: how to prevent natural sign?

On Thu, Apr 9, 2015 at 9:21 AM, David Nalesnik david.nales...@gmail.com wrote: Hi, On Thu, Apr 9, 2015 at 9:10 AM, Jinsong Zhao jsz...@yeah.net wrote: Hi there, I don't want the natural sign to be displayed. However, I don't find a way to do so. Many thanks! Regards, Jinsong

Re: parts for natural horns and trumpets

On Wed, Apr 1, 2015 at 12:22 AM, Urs Liska u...@openlilylib.org wrote: You may have a look at https://github.com/openlilylib/openlilylib/tree/master/editorial-tools/auto-transpose That's pretty awesome. Unfortunately it doesn't behave like I'd expect by default. Here's an example: \version

Re: parts for natural horns and trumpets

Am 01.04.2015 um 04:48 schrieb Craig Dabelstein: Hi Lilyponders, Does anyone have a successful way of writing parts for natural horns and trumpets that would change crooks (and therefore transpositions) several times during a part. There would be a global file holding the many key

parts for natural horns and trumpets

Hi Lilyponders, Does anyone have a successful way of writing parts for natural horns and trumpets that would change crooks (and therefore transpositions) several times during a part. There would be a global file holding the many key and time signature changes and then I would need the part

Re: parts for natural horns and trumpets

On Tue, Mar 31, 2015 at 10:48 PM, Craig Dabelstein craig.dabelst...@gmail.com wrote: Hi Lilyponders, Does anyone have a successful way of writing parts for natural horns and trumpets that would change crooks (and therefore transpositions) several times during a part. There would

Putting a natural sign on a note

Hi all, The following two bars of code result in the music correctly written, however, I would like to place a natural symbol on the first note of the second bar, just to remind folks that it is different. I know this is not the convention, but I want to do it anyhow. Is there a way? Bill

Re: Putting a natural sign on a note

Thanks to you and Jan-Peter. Bill On 15-02-10 11:16 AM, Kevin Barry wrote: On Tue, Feb 10, 2015 at 3:13 PM, William Marchant wmarch...@eastlink.ca mailto:wmarch...@eastlink.ca wrote: I would like to place a natural symbol on the first note of the second bar, just to remind folks

Re: Putting a natural sign on a note

Hi William, you can use the exclamation or question mark: b! b? or you place a markup as a text script above the note: b^\markup \natural HTH Jan-Peter Am 10.02.2015 um 16:13 schrieb William Marchant: Hi all, The following two bars of code result in the music correctly written, however, I

Re: Putting a natural sign on a note

As an addition: If you want this behaviour as a general rule (reminder in the next bar), you can use the modern accidental style: \version 2.18.2 \language english { \accidentalStyle modern bf4 bf bf8 bf bf bf | b b b b d4 d | }

Re: Putting a natural sign on a note

On Tue, Feb 10, 2015 at 3:13 PM, William Marchant wmarch...@eastlink.ca wrote: I would like to place a natural symbol on the first note of the second bar, just to remind folks that it is different. I know this is not the convention, but I want to do it anyhow. Is there a way? Bill

Re: Putting a natural sign on a note

to you and Jan-Peter. Bill On 15-02-10 11:16 AM, Kevin Barry wrote: On Tue, Feb 10, 2015 at 3:13 PM, William Marchant wmarch...@eastlink.ca wrote: I would like to place a natural symbol on the first note of the second bar, just to remind folks that it is different. I know

Re: would 'gn' for G-natural be useful in \language english ?

The content of the file is also below just for good measure. Cheers, -Paul pitchnames = #`( (cff . ,(ly:make-pitch -1 0 DOUBLE-FLAT)) (cf . ,(ly:make-pitch -1 0 FLAT)) (c . ,(ly:make-pitch -1 0 NATURAL)) (cn . ,(ly:make-pitch -1 0 NATURAL)) (cs . ,(ly:make-pitch -1 0

Re: would 'gn' for G-natural be useful in \language english ?

distinction to 'b' that LilyPond does not preserve. Nevertheless, written English uses -natural in a systematic way https://archive.org/stream/wellknownpianoso00wilkrich/ wellknownpianoso00wilkrich_djvu.txt and I find that helpful in typing LilyPond, so I am taking Michael Ellis' suggestion to use

Re: would 'gn' for G-natural be useful in \language english ?

} is not as helpful for rearranging music as it could be. I'm proposing \languageabbreviated for people who want to use \displayLilyMusic to generate brief english, and/or want to type 'cn' for the same reasons that we sometimes pronounce 'natural' in English. lt;https://code.google.com/p/lilypond

Re: would 'gn' for G-natural be useful in \language english ?

Ralph Palmer palmer.r.violin at gmail.com writes: On Sun, Nov 16, 2014 at 11:31 PM, Keith OHara k-ohara5a5a at oco.net wrote:Dear list, In English, pronouncing the 'natural' in 'C-natural' is required if the note is out-of-key.  LilyPond does not consider the key when reading note- input

Re: would 'gn' for G-natural be useful in \language english ?

. -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/would-gn-for-G-natural-be-useful-in-language-english-tp165872p168834.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond

Re: would 'gn' for G-natural be useful in \language english ?

Another American here, but I don't have a very strong opinion on this. I can see arguments on both sides. -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/would-gn-for-G-natural-be-useful-in-language-english-tp165872p168834.html Sent from the User mailing list

Re: would 'gn' for G-natural be useful in \language english ?

On Sun, Nov 16, 2014 at 11:31 PM, Keith OHara k-ohara5...@oco.net wrote: Dear list, In English, pronouncing the 'natural' in 'C-natural' is required if the note is out-of-key. LilyPond does not consider the key when reading note-input, but could easily accept 'cn' as a name for the pitch C

Re: would 'gn' for G-natural be useful in \language english ?

the 'natural' in 'C-natural' is required if the note is out-of-key. LilyPond does not consider the key when reading note-input, but could easily accept 'cn' as a name for the pitch C-natural. There was a feature request on the bug-list, that LilyPond do so. Among those responding to the proposal

Re: would 'gn' for G-natural be useful in \language english ?

Dear list, In English, pronouncing the 'natural' in 'C-natural' is required if the note is out-of-key. LilyPond does not consider the key when reading note-input, but could easily accept 'cn' as a name for the pitch C-natural. There was a feature request on the bug-list, that LilyPond do so

How to prevent natural signs from being printed when the key signature changes

soprano \key c \major g a g f } } But I still get the natural sign printed. http://lilypond.1069038.n5.nabble.com/file/n168456/2014-11-06-170533_1024x600_scrot.png Am I doing something wrong or is this a bug? Thank you, A -- View this message in context: http://lilypond

Re: How to prevent natural signs from being printed when the keysignature changes

Jayaratna wrote Thursday, November 06, 2014 11:42 AM My code is: \version 2.18.2 \score { \relative c' { \key f \major c d e f \set Staff.printKeyCancellation = ##f \clef soprano \key c \major g a g f } } But I still get the natural sign printed. http

Re: How to prevent natural signs from being printed when the key signature changes

a g f } } But I still get the natural sign printed. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to prevent natural signs from being printed when the key signature changes

Just wait a minute! If you don't have the natural sign and the next key signature has neither sharp nor flat sign, how would you read the new key signature? I think the flat is necessary here. Helge ___ lilypond-user mailing list lilypond-user@gnu.org

Re: How to prevent natural signs from being printed when the key signature changes

.1069038.n5.nabble.com/file/n168461/2014-11-06-183422_1024x600_scrot.png Thank you, A -- View this message in context: http://lilypond.1069038.n5.nabble.com/How-to-prevent-natural-signs-from-being-printed-when-the-key-signature-changes-tp168456p168461.html Sent from the User mailing list

would 'gn' for G-natural be useful in \language english ?

completely distinct names from 'c'. I am not sure if something similar makes sense in fixed-do naming as used in French and Spanish. Would anyone else like to see 'fn' as a second way to express F-natural in English (in addition to the existing 'f') ? David Winfrey writes: A new accidental

Re: would 'gn' for G-natural be useful in \language english ?

- Original Message - From: Keith OHara k-ohara5...@oco.net To: lilypond-user@gnu.org Sent: Friday, August 29, 2014 7:41 AM Subject: would 'gn' for G-natural be useful in \language english ? Dear user list, The suggestion quoted below from the bug-lilypond list http://lists.gnu.org

Re: would 'gn' for G-natural be useful in \language english ?

, German Lilypond, and English Lilypond? Would anyone else like to see 'fn' as a second way to express F-natural in English (in addition to the existing 'f') ? No: please not. There are surely two ways of indicating pitches? One is the method used in musical notation itself, where a note on the C

Re: would 'gn' for G-natural be useful in \language english ?

English speakers (at least the ones in my part of America) will say cee or cee-natural for the note C. The latter is to emphasis that you are not speaking of another pitch like C-sharp. In the key of D, say, some people will say cee when they mean cee-sharp. cee-natural shows you haven't made

Re: would 'gn' for G-natural be useful in \language english ?

At 07:20 29/08/2014 -0700, Knute Snortum wrote: English speakers (at least the ones in my part of America) will say cee or cee-natural for the note C. The latter is to emphasis that you are not speaking of another pitch like C-sharp. Agreed. In the key of D, say, some people will say cee

Re: would 'gn' for G-natural be useful in \language english ?

and -double flat) have separate names in any language, including German, English, German Lilypond, and English Lilypond? In English the names use two parts, noun-adjective, which allows the construction C-natural. German has single words (ces c cis) for the pitches, and these are distinct from

Re: would 'gn' for G-natural be useful in \language english ?

is that used in Lilypond input, where c always represents C-natural, irrespective of the key signature in force. Similarly cis or cs and so on are interpreted literally, without reference to the key signature. +1 ___ lilypond-user mailing list

Re: would 'gn' for G-natural be useful in \language english ?

At 08:38 29/08/2014 -0700, Keith OHara wrote: In English the names use two parts, noun-adjective, which allows the construction C-natural. German has single words (ces c cis) for the pitches, and these are distinct from the names for the alterations (Be, AuflösungZeichen, Kreuz

Cautionary \natural

The composer would like me to place a cautionary natural symbol on several notes. He specifies a /parenthesized/ natural. Can anyone help me find a way to do this? Charlie ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org

Re: Cautionary \natural

{ c? } On 5. Juli 2014 21:06:52 MESZ, Charles Marshall marsh...@potsdam.edu wrote: The composer would like me to place a cautionary natural symbol on several notes. He specifies a /parenthesized/ natural. Can anyone help me find a way to do this? Charlie

Re: Cautionary \natural

{ c? } On 5. Juli 2014 21:06:52 MESZ, Charles Marshall marsh...@potsdam.edu wrote: The composer would like me to place a cautionary natural symbol on several notes. He specifies a /parenthesized/ natural. Can anyone help me find a way to do this? Charlie

Re: \fill-line while respecting natural widths

Hi all, I've posted an update to this on the issue tracker. I think the discussion should move there. https://code.google.com/p/lilypond/issues/detail?id=3860 Best, David ___ lilypond-user mailing list lilypond-user@gnu.org

Re: \fill-line while respecting natural widths

On 02/08/2014 11:22 PM, Kieren MacMillan wrote: Hi David, Hmm--do you think it should be added as an option to \fill-line? DEFINITELY! As just one example: I’m going to use it in the musical theatre scores I’m engraving right now, to [evenly] space two columns of dialogue above a system of

Re: \fill-line while respecting natural widths

2014-02-08 23:22 GMT+01:00 Kieren MacMillan kieren_macmil...@sympatico.ca: Hi David, Hmm--do you think it should be added as an option to \fill-line? DEFINITELY! +1000 - this is awesome! As for now, i have added it to the snippets

Re: \fill-line while respecting natural widths

Hi David, See the attached. (I just changed a line or two of the definition of \fill-line from scm/define-markup-commands.scm.) Hopefully this gives you what you want! --David That's interesting, see the result of the two markups: \version 2.18.0 \markup \fill-line { This line has

Re: \fill-line while respecting natural widths

On Feb 8, 2014, at 10:24 AM, Ed Gordijn ed.klari...@gmail.com wrote: Hi David, See the attached. (I just changed a line or two of the definition of \fill-line from scm/define-markup-commands.scm.) Hopefully this gives you what you want! --David That's interesting, see the result

Re: \fill-line while respecting natural widths

Hi Mike, It's a feature - \fill-line evenly distributes the centers of objects along a line irrespective of their widths. I see,so there wasn't enough room in the last column for the long word different? I created too many columns. Thanks, Ed ___

Re: \fill-line while respecting natural widths

David (et al.), OOO! This is wonderful. I can already see several places where I will use this. Thanks, Kieren. On Feb 8, 2014, at 2:20 AM, Mike Solomon m...@mikesolomon.org wrote: On Feb 8, 2014, at 1:18 AM, David Nalesnik david.nales...@gmail.com wrote: Hi Mike, See the

Re: \fill-line while respecting natural widths

Hi Mike, On Sat, Feb 8, 2014 at 1:20 AM, Mike Solomon m...@mikesolomon.org wrote: On Feb 8, 2014, at 1:18 AM, David Nalesnik david.nales...@gmail.com wrote: Hi Mike, See the attached. (I just changed a line or two of the definition of \fill-line from scm/define-markup-commands.scm.)

Re: \fill-line while respecting natural widths

Hi Kieren, On Sat, Feb 8, 2014 at 7:16 AM, Kieren MacMillan kieren_macmil...@sympatico.ca wrote: David (et al.), OOO! This is wonderful. I can already see several places where I will use this. Thanks, Kieren. Hmm--do you think it should be added as an option to \fill-line? (Well,

Re: \fill-line while respecting natural widths

Hi David, Hmm--do you think it should be added as an option to \fill-line? DEFINITELY! As just one example: I’m going to use it in the musical theatre scores I’m engraving right now, to [evenly] space two columns of dialogue above a system of underscore music. But maybe it should be its own

  1   2   >