Re: how close are we to having an "addAt" or "insertAt" feature?

>> How much sense would it make for there to be a separate \mark-style >> command that functioned identically but didn't mess with the >> counter? I'm all for it! > Meh… I don’t really like the original suggestion (of a > RehearsalMark-relative \addAt parameter), so it makes little sense > to me

Re: how close are we to having an "addAt" or "insertAt" feature?

> For better or worse, I am currently focusing on speeding up "git > blame" which is braking down lots of people. Excellent! If you want a test case from the dark side, try http://repo.or.cz/w/wortliste.git For historical reasons, the `wortliste' is a single, large file instead of smaller on

Re: how close are we to having an "addAt" or "insertAt" feature?

>global = \repeat unfold 100 s1 >music = \addAt (4 3/8) \global \once \override >RehearsalMark.extra-offset #’(-1 . 0) > > where (4 3/8) means “in the fourth measure, at the moment of the 3rd > eighth note” I suggest that such a command allows for a third, optional parameter, which ma

Re: Survey: Git (G)UIs

> I'd like to make a survey on how you are working with Git. > > Do you use the command line exclusively, or a GUI (which one(s))? > Or a GUI for certain tasks and the command line for others? I use git on the command line only. However, I use the excellent `gitk' program for inspecting changes.

Re: Weirdness With Fonts and Font Tree Snippet

> Another way to do it is to create a lilypond file that contains > > #(ly:font-config-display-fonts) > > and typeset it. You will get a list of the fonts in the log window. Nice. The OP talked about `GUI'; I assume he means Frescobaldi. Maybe such a command could be added to its menu system,

Re: Weirdness With Fonts and Font Tree Snippet

> Indeed, I have found that on Mac OS X, the system is very picky > about what it sees and doesn't see. For instance, I use the > SkyFonts program to install fonts from the Google Fonts site. > Apparently, it doesn't install them as system fonts, so if I want to > use them in LilyPond (and PT San

Re: LilyPond 2.18.0 released

> ... mTeX ... musicTeX ... musixTeX ... Gesundheit! Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [Feature Request] \compressFullBarRests improvement(s)

> I think one of the things that bothers me about this thread is that > I don't understand why, if you want a four measure rest you would > write 2+2. For the vast majority of cases, if there are 48 bars > between two rehearsal marks I'm happy to see |=48=| between them. > So, why write anything

Re: [Feature Request] \compressFullBarRests improvement(s)

> I would like to echo Simon's concern as well. Furthermore, I don't > see why: > > R1*2 R1*2 > > ...producing two multimeasure rests of two measures duration is > troublesome. It is a fundamental problem of separating contents from layout. In many cases it is of great importance to structure

Re: [Feature Request] \compressFullBarRests improvement(s)

>> I also support this request. Another reason is that in many parts >> of percussion instruments, say, there is `tacet' for a very long >> time, e.g. from rehearsal number 20 to 76. A potential new >> implementation of \compressFullBarRests (or a variant as suggested >> by David K.) should allo

Re: [Feature Request] \compressFullBarRests improvement(s)

>> Here’s my request: I would love it if \compressFullBarRests actually did >> what it says it does… ;) > > FWIW, I agree with Kieren. If I saw a part with some multimeasure > rests broken for no obvious reason, e.g. > > { \compressFullBarRests \mark \default R1*2 R1*2 \mark \default R1*2 } > >

Re: promoting LilyPond

>> ... and I see a buglet in this image: The vertical line in the >> Soprano's ambitus must not degenerate to a dot. Either the line >> gets omitted completely, or it gets stretched a bit. > > However, http://code.google.com/p/lilypond/issues/detail?id=3525 and > thus :-) Hehe, thanks.

Re: A thought on Windows Experience

> Tim and Werner, I would love to, and have considered a few times in > the past. Unfortunately I do not have the time, have no experience > of texinfo, and would probably have to ditch it within the coming > year due to future plans anyway. It's not so much about texinfo but... > I don't know

Re: promoting LilyPond

> We need to figure out how we can provide "style sheets", similar to > how LaTeX makes it possible to define "document classes" (layout > definitions and tools) and "packages" (raw functionality packaged > into coherent interfaces). *This* is a very worthy project IMHO! It basically means a lot

Re: promoting LilyPond

> Just take a look at the simplicity this could give us: this > https://github.com/openlilylib/snippets/blob/master/templates/predefined-instruments/simple-example.ly > can produce the attached output. ... and I see a buglet in this image: The vertical line in the Soprano's ambitus must not d

Re: A thought on Windows Experience

> I also think lilypond's website is terrible. It looks like something > out of the eighties knocked up on a dos machine. By comparison, > take a look at the home pages of musescore, finale and sibelius. Actually, I don't see a very big difference between lilypond's and musescore's site. But im

Re: what do you use ragged-bottom for?

> If your variations are only one page long, you could achieve the > same effect with ragged-last-bottom. Keith is asking about > ragged-bottom, which applies to every page of the score. My concern is to compute a document where each page consists of a single large system in its `natural', uncom

Re: Ferneyhough-style Interruptive Polyphony

> A few weeks back I posted seeking a little help in implementing one > of the more peculiar notational devices of Brian Ferneyhough, namely > 'interruptive polyphony'. > > I've managed to find a way to implement these automatically and > wanted to share the code in case anyone in future is lookin

Re: Thoughts about creating Stack Exchange page?

> Maybe it is even better to send them directly to the posting!? > http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.general Probably. I don't use gmane at all, so I can't give a recommendation. However, as with StackExchange, people should *search* first before post something whethe

Re: Thoughts about creating Stack Exchange page?

> Then I suppose I should also post that answer to the meta question I > linked to previously!? I think this would be good, yes. > So, is this the link to give? > https://lists.gnu.org/mailman/listinfo/lilypond-user It depends. For casual users, the gmane interface is perhaps better suited, th

Re: Thoughts about creating Stack Exchange page?

> If it's community policy or at least a general agreement that we > should always refer to this list, I will of course do so the next > time! Yes, please do so. > But I hope we agree that it, as Ryan wrote, would be helpful for the > community if we found ways to deal with questions posted outs

Re: Thoughts about creating Stack Exchange page?

> Allow me to clarify that in no way did I intend for the Stack > Exchange page to replace this list. It would have been purely an > addition of resources. Well, you might answer all lilypond questions by simply pointing questioners to the list :) > For me, the purpose of the Stack Exchange pag

Re: Thoughts about creating Stack Exchange page?

>> I am also totally up for this idea as well. > > What's wrong with this list? Everybody wants to take his LilyPond > business to the web interface of his choice that takes a lot of > additional work over just reading and typing text and further > dilutes the LilyPond knowledge. I second that.

Re: specific dot configuration

>> But she also shows that – unless conditions are cramped – notes of >> different duration take a dot right beside each notehead... > > That's what the original edition does - but I find it very ugly in > that case. Not necessarily, cf. the image in https://code.google.com/p/lilypond/issues/d

Re: [WISH] about \super and \sub

> I don't understand Werner's remark : \sub is at the right height > even for chords. Not \sub, but \sup. > I've also compared with Sibelius, Finale, and some books I have > here; looks fairely good to me. Hmm. Look at the attached two images, extracted from https://code.google.com/p/lilypond/

SSCCE

Just found this link. *Very* useful for us, I think :-) http://sscce.org/ Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: NR 1.7.1: can't understand a sentence about scaling font size

> With the modern scalable fonts much of this size-adjusting has been > incorporated in hints and other techniques, I wished it were so, but alas, this is not true. Hinting is only useful to adapt glyphs to a given output device. It does *not* provide any optical scaling. Werner

Re: Petrucci clef/time signature spacing issue

>>> Entered as Issue 3598 >>> : Petrucci >>> clef/time sugnature space too large >>> and copied to the buglist for diligence. > > It seems kind of known: At least horizontal spacing is mentioned in > the docs: > http://lilypond.org/doc/v2.1

Re: Petrucci clef/time signature spacing issue

> Entered as Issue 3598 > : Petrucci > clef/time sugnature space too large > and copied to the buglist for diligence. Thanks! Werner ___ lilypond-user mailing list lilypond-user@gnu.org http

Re: Petrucci clef/time signature spacing issue

>> I wonder why there is such a large gap between the clef and the >> time signature. Looks quite unnatural IMHO. > > Agreed. I think it's because the time sig is always placed in the > same location, and the clef is narrow, so it looks bad. See > attached annotated example. Thanks for that.

Petrucci clef/time signature spacing issue

If I say \override Score.TimeSignature.style = #'mensural \override NoteHead.style = #'petrucci \clef "petrucci-c3" \time 2/2 c'2 c'4 c'4 I wonder why there is such a large gap between the clef and the time signature. Looks quite unnatural IMHO. Werner <>___

Re: fixed vertical space

> Doesn't something like this do it? > > markup-system-spacing = [...] Yes, as Robin has suggested, too. However, this is a global setting, while I would like to have something local. Werner ___ lilypond-user mailing list lilypond-user@gnu.or

Re: fixed vertical space

>> However, I want a fixed space between \markup and \score that >> doesn't get stretched. > > How about mm-feed? > http://lists.gnu.org/archive/html/lilypond-user/2010-04/msg00057.html Nope: #(define-markup-command (mm-feed layout props amount) (number?) (let ((o-s (ly:output-def-lookup la

Re: fixed vertical space

>> I have >> >> \markup { ...} >> \score { ... } >> >> (at the top level) and I want some vertical space between the >> \markup and the \score which isn't stretchable. How can I achieve >> that? > > \markup { \vspace #10 } ? This would insert *at least* a 10-units vertical space (since lilypo

Re: forcing bar number events

> The property barNumberVisibility takes a function as its argument. > I forget what the function's arguments need to be, but if you can > figure that out, you can roll your own function that prints the > number at bar 10. The arguments are the bar number and the current timing position. It woul

Re: forcing bar number events

>> Is it possible to make bar number `10' visible automatically? >> Looking up the documentation, it seems that a bar number gets >> printed only if there is a bar line, and \compressFullBarRests >> prevents that... > > I don't think this is a good idea. How would the reader know at > which momen

fixed vertical space

I have \markup { ...} \score { ... } (at the top level) and I want some vertical space between the \markup and the \score which isn't stretchable. How can I achieve that? Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://

Re: forcing bar number events

>> It would be a great simplification if it would not be necessary to >> artificially break up `R1*4' into `R1 R1*3'. > > The multi-measure rests break on any event, tempo change, double > bar..., > > so you could put a repeating s1*5 in the 'conductor' part if you > want to prevent the rests fr

forcing bar number events

[2.17.26] Folks, consider this snippet \relative c'' { \compressFullBarRests \set Score.barNumberVisibility = #(every-nth-bar-number-visible 5) \override Score.BarNumber.break-visibility = #end-of-line-invisible c1 | c1 | c1 | c1 | c1 | c1 | c1 | c1 | R1*4 | c1 |

Re: Problem with hemiola notation

> After reading (tens of) thousands of LilyPond emails, we (or at > least I) have developed a habit (actually sort of a 'conditioned > response') of grabbing the code from an email, pasting it into an > editor and running lilypond on that file. if the compilation fails, > our brains say "no outpu

Re: Notehead of harmonic whole note too narrow

> This looks a better match for the other whole notes: > > \relative f'' { > \key e \minor > << > { > \tweak font-size #3 > \tweak style #'harmonic-mixed > b1 > [...] For my taste, the harmonic note head is too big. I think the original size is just fine if it gets ce

Re: Feta font modifications by Janek

> Alas, I found one: > http://www.fontfabrik.com/lucfuse.html > "FUSE 11 has pornography as theme. My contribution to this issue is > a MultipleMaster font. [...] Five characters are converted to small > FREE PORNO MOVIES. New versions use antialiasing and gif > compression." Actually, this is

Re: Feta font modifications by Janek

> I omitted to mention that OpenType does not support the > parameterization concept of MM, and so OT is not an evolution of MM. This is not correct. Earlier versions of the OpenType specification *did* support MM, but since Adobe stopped using them, those tables were removed from the OT specs t

Re: Feta font modifications by Janek

[wearing the FreeType maintainer hat] >> There are some uses for it in in-house font design - which to some >> extent could include lilypond - but MM fonts are not really offered >> any more, and nobody is developing along those lines. Basically, I don't see any technical difficulties in using M

Re: maintaining advanced power-user Scheme functions

> Well, one question may be whether git could be an alternate > interface into the LSR. In a limited manner, it already is > (snippets migrate back from LilyPond git repository into the LSR). Actually, I like the idea of using git for the LSR *as the storage*. Experienced cann access it directly,

Re: SMuFL

> I think "so poorly documented that in practice almost no one can > understand how it works" still can't qualify as "in effect > proprietary". It is not *that* badly documented. However, the number of people who understand Metafont are rather small today. > - Someone who doesn't really want to

Re: SMuFL

>> Unicode is a *character* standard, mainly to *exchange* >> information. It is *not* related to glyphs, or to fonts. The >> SMuFL team correctly maps the glyphs to the Private Area of >> Unicode, and they don't suggest the inclusion of any of those >> entities into the Unicode standard. > > T

Re: SMuFL

> The SMuFL standard is just a specification cooked up by Steinberg > for the new program. It's been possible for them to consider this > since they are architecting the program from scratch. But it's a > step away and outside of the hugely important work the Unicode > Consortium have been doing

Re: Pattern-generating Scheme function challenge

>> %% Why not public? > > Not public because it is trivial and not discoverable. People > looking through GUILE documentation will find and use > lset-difference. There is a lot of cruft in lily-library like that > which should really be thrown out. Making it public would be a step > in the wr

Re: LSR preview broken?

> Approved as > http://lsr.dsi.unimi.it/LSR/Item?id=883 Thanks! Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: LSR preview broken?

> Your snippet compiles fine with 2.14.2 (tested). Thanks. > There are some problems in the LSR concerning cropped images. Hmm, I don't think this affects my snippet. Maybe simply approving it solves the issue :-) Werner ___ lilypond-user mail

LSR preview broken?

I've just added a snippet to the LSR (`Percent repeat counters for piano music'), but I'm not able to preview it. Since I don't have a 1.14 lilypond binary, I can't check whether the problem is in the file (it compiles fine with 1.16 and the current development version). However, even adding a ve

Re: LilyPond blog has new home!

> So, how do you like the new location and graphic design? I saw a > lot of visitors after the announcement, but there were very few > comments... It looks nice, thanks! Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.

Re: Cut and paste from manual returns errors

> That's enormously useful. Shouldn't something like that be front and > center, along with a short (i.e. 1-2 page) guide on best practice > for searching it as suggested by others above? Unfortunately, only Acrobat can read that. There is no free tool yet which correctly interprets PDF portfoli

Re: Replacement suggestions for Century Schoolbook?

>> This typeface style is known as "Scotch". A high-quality, free Scotch >> type-family is "Old Standard". [...] > > Thanks for letting us know. > I've tried it (only on the screen, no time to visit print shop for a > high quality print :( ); it is in fact very similar in shape to > Century (exce

Re: Path to LilyPond 2.18

> I'd prefer to declare 2.17.next_increment as a release candidate; let > that stand and if it's OK, cut 17.95 as a final RC, then run 2.18.0. Well, in emacs the first release candidate has .95, and I think this is a good decision. And I vote against a `final' RC; this makes too much pressure.

Re: problem with \RemoveEmptyStaves

>> I want an option that staves are only removed if there are at least >> two systems on a page. A second pass over the full score should be >> quite cheap, if really necessary, since line breaks are already >> done. > > I think this could be done automatically, without a second pass, > [...] Th

Re: problem with \RemoveEmptyStaves

>> What prevents Lilypond to do this automatically? I want an option >> that staves are only removed if there are at least two systems on a >> page. > > I would phrase that there *would* be two systems after removing the > empty staves. No, I don't mean that. I mean the situation where Lilypond

Re: problem with \RemoveEmptyStaves

>> Thanks. *Very* kludgy. > > No, not at all. The RemoveEmptyStaves feature was intended to be > adjusted in that way, so the solution in that snippet is a safe and > direct way to avoid removing staves when you don't want them > removed. It will not break at the next LilyPond version or > int

Re: problem with \RemoveEmptyStaves

>> In a big score, it removes staves even if only a single system fits >> on a page, see the attached image. > > In some big scores (say, Mahler) you need to remove the empty staves > just to let the rest fit legibly on a page. OK. In other words, we would need a new value for property `remove-

problem with \RemoveEmptyStaves

Folks, the \RemoveEmptyStaves command apparently has a big drawback: In a big score, it removes staves even if only a single system fits on a page, see the attached image. How can I avoid this? Werner <>___ lilypond-user mailing list lilypond-us

Re: Does the optimal-page-breaker work?

>> I'm successfully using ly:page-turn-breaking with an organ piece, >> fitting about 200 bars on 11 pages. > > Good. Do you let LilyPond find page-turns at rests, or put in > \allowPageTurn at every potential turn? I'm inserting \allowPageTurn commands: In virtually all places where a turn cou

snare drum in MIDI

Folks, what must I do to assign a snare drum sound to a staff? According to the General MIDI standard, this is channel 10, slot 38. Looking into the code, however, I see no easy way to do that, given that percussion instruments are handled as sets only... Werner

Re: Does the optimal-page-breaker work?

> Does anyone let LilyPond choose page-turns for them? I'm successfully using ly:page-turn-breaking with an organ piece, fitting about 200 bars on 11 pages. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman

Re: OpenType support in Windows

>> We urgently need a developer working on Windows who is sufficiently >> familiar with GNU stuff, in particular with Pango and Harfbuzz. >> Behdad Esfahbod, the developer of Harfbuzz, is willing to help >> provided we have someone who can test and debug patches. > > I'd be happy to test patches o

Re: OpenType support in Windows

>> I recently tested LilyPond on Windows 8 (Enterprise Development >> Test version running on VirtualBox). It appears that LilyPond does >> not support any OpenType features on Windows 8 (at least as of >> version 2.16.2). > > We have issues > http://code.google.com/p/lilypond/issues/detail?id=26

Re: Problem with encoding unicode

> Not all unicode characters are being correctly realised in my score. > Something like \mark \markup { \char ##x03EE } will work but this > throws an error: > > \mark \markup { \char ##x1080B } > > [...] > > Thanks. Is there a solution to the problem? It's happening in > about 30% of the unicod

Re: mdash in markup?

> I can send a doc patch, if you like. Fixing is better than > complaining. Please do so! Usually, developers don't have a good sense for documentation :-) Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman

Re: cre - - sen - - do

> Even better, IMHO: > > cre = -\tweak #'text #"cre" \cresc > scen = -\tweak #'text #"scen" \cresc > do = -\tweak #'text #"do" -\tweak #'style #'none \cresc > > { > b2\cre b > b\scen b > b\do b > b1\f > } With the current development version, it's even more compact: cre = -\tweak tex

Re: accidentals and broken bars

>> \relative c'' { >> cis4 cis \bar"" \break >> cis cis >>} > > How about > > \relative c'' { > cis4 cis \bar"" \break > cis! cis > } Thanks, but this makes an additional accidental in case the bar doesn't get broken. I want a solution which is independent on the layout

full rests and broken bars

And here a variation of my previous e-mail: Has anyone written a macro to handle broken bars with full rests gracefully? \relative c'' { << { c c \bar"" \break c c } \\ { R1} >> } I can imagine to have a macro \ifBreak which gives the two alternatives: \ifB

accidentals and broken bars

Folks, if a bar gets broken, how can I make lilypond display additional accidents automatically after the break? \relative c'' { cis4 cis \bar"" \break cis cis } Werner <>___ lilypond-user mailing list lilypond-user@gnu.org https://l

Re: musicxml2ly enhancements

>%{ 5 %} a,4 ( a4 ) ( b4 ) d4 | I like that. It's tedious to type manually, but a computer program doesn't know that word :-) >>> >>> Indeed, but i find it unreadable, especially if it was placed at >>> every line. Really? It's like having a BASIC program which always sta

Re: Cropped output (à la -dpreview) possible in Finale and Sibelius

> As far as what can be controlled by Lilypond and it's developers, > making sure PNG files are generated well *is* something that should > be addressed, since that is completely within Lilypond's control. Does GhostScript's PNG backend produces satisfying results? Otherwise, what about creating

Re: Cropped output (à la -dpreview) possible in Finale and Sibelius

> It's a very hard problem and probably not solvable. Ah, I misread, sorry. Yes, it might be worth to test with line strokes. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Cropped output (à la -dpreview) possible in Finale and Sibelius

> Have you seen > http://code.google.com/p/lilypond/issues/detail?id=2658 ? *That's* > appalling - and it's how LilyPond output is rendered :( :( :( (image > attached) It's sad that there are no comments on this issue after 9 > months :( It's a very hard problem and probably not solvable. Essen

Re: musicxml2ly enhancements

> Putting the bar number at the start of the line would require > > %{ 5 %} a,4 ( a4 ) ( b4 ) d4 | > > instead. I like that. It's tedious to type manually, but a computer program doesn't know that word :-) Werner ___ lilypond-user mailing list

Re: shortening a stem

>> Indeed, very nice! Thanks for the link. Unfortunately, it doesn't >> work with Stem.length at all because this is not an `offset'. > > Really? It works perfectly for me, with 2.17.13: > \offset Stem #'length #2 % in positions, not ss! > see attached. Interesting. Compiling your file wit

Re: shortening a stem

> Have you tried using > > \once \override Stem.length-fraction = #(magstep -n) Yes. > Unfortunately the amount of shortening is not consistent across all > notes for a particular value of n. Exactly. This makes it quite inconvenient for applying a simple optical correction. Werner ___

Re: shortening a stem

> > what must I write to shorten an unbeamed stem by, say, one unit? > > A naive approach would be > > > > \once \override Stem.length #(- ly:stem::calc-length 1) > > > > which doesn't work of course... > > David Nalesnik wrote a very versatile function that makes such > things very easy. You ca

Re: Fingering not aligned in 2.17, ok in 2.16

> See below. In 2.16.2, the fingering indications are vertically > aligned. In 2.17.14, they aren't. > > \relative f'' { > \set fingeringOrientations = #'(left) > 4 > } Do you consider this a bug? Actually, I like the new behaviour better. What does the literature say? Werner _

Re: User comments on R shorthand

> - Old: R2 == a full measure rest in 2/4 time > - New: R2 == *two* full measure rests in any time signature Actually, I like this. This would also help in situations like tacet al |--| > That breaks backward compatibility. convert-ly is your fr

Re: articulation simbols

>> \staccato >> \tenuto >> \accent > > Will give this a go. It's a glaring omission in the manual (and thus a severe obstacle for blind users) that most articulation symbols are not described verbally but only shown as images. http://lilypond.org/doc/v2.16/Documentation/notation/list-of-arti

Re: Aw: Re: Re: Pseudo-handwritten font

[please use plain text for your e-mails] > > What do you mean with `rigid'? > > Some things related to Feta/Emmentaler access are still being > handled deep inside non-public scheme coding or even C source code > and consequently very hard to tweak. Please open bug reports about those issues.

Re: Aw: Re: Pseudo-handwritten font

> In the first place: I've attached a zip file containing the current > (albeit unfinished) versions of the LilyJAZZ music and LilyJAZZ Text > font plus the corresponding LilyJAZZ.ily include. Very impressive! > The main obstacle is the rigid way Lilypond handles its (her, his?) > internal music

Re: \relative proposal: putting absolute pitches anywhere within \relative block using @-sign

>> However there is no fundamental need for the first pitch being an >> absolute pitch in the first place. > > It can be relative to f if we want to. That adds the least amount > of information to the first pitch. It seems to me that we should completely avoid the word `absolute' if we speak ab

Re: \relative proposal: putting absolute pitches anywhere within \relative block using @-sign

>> But the first entry of a \relative block must be relative to >> something, right? So, simply consider that \relative { ... } is >> always relative to `c', and you get exactly the same. > > Well, the current proposal is to be relative to f rather than c' as > previously. Ah, yes :-) Wer

Re: \relative proposal: putting absolute pitches anywhere within \relative block using @-sign

>> I am *OPPOSED* to the proposal to change \relative syntax, as the >> proposal now stands. I think it is confusing to new users to have >> the first pitch in a \relative block be absolute and the rest be >> relative. But the first entry of a \relative block must be relative to something, right

Re: change barline type with time signature change

>> The contrast is not strong enough if you are viewing the image from >> a greater distance. As it is, it looks irritating to my eye. > > Agreed ― the "lighter" chosen here is insufficiently light. > However, the concept is one I'm interested in exploring. Mhmm. Your suggestion of handling on

Re: change barline type with time signature change

> This reminds me of an idea i had: make stafflines under rests grey, > to make it immediately obvious where an instrument is resting (see > attached - obviously a bigger example would demonstrate this idea > better, but i don' have one). How do you like it? Well, I don't like it. The contrast

Re: Bar lines

> To be absolutely clear: i want both an 'end-bar' property and the > thing mentioned above. OK. > Is my explanation clear? Yes, thanks. However, I still don't see the usefulness. Werner ___ lilypond-user mailing list lilypond-user@gnu.org htt

Re: Proposed new available and recommended behavior of \relative

>> Well... if you just don't emit the warning if the first pitch in a >> \relative {} block is incorrect, then it seems like you get exactly >> the current proposal except that you have to spell \relative { c'' >> } as \relative { c='' } instead. > > I like that idea! Indeed, this has some benef

Re: Bar lines

>> I really would not like to have to tell LilyPond for every single >> fragment to not use a final bar line. > > Could you explain what you didn't like in my suggestion that said "if > the music is more than 3 bars long, use a "|." barline; if it's 3 or > less use a "|" barline"? I think that i

Re: Proposed new available and recommended behavior of \relative

> One rationale is to stop the "distribution" of the information for > the first pitch to potentially quite separate places, like being > able to write > > \new Staff \relative { > \key aes \major > << % Voice one > { c''2 aes4. bes8 } > ... > > instead of the previous > > \new Staff

Re: Pseudo-handwritten font

>> Wow, very impressive! > > I hate to admit it, Hehe :-) > but it looks like a game changer of strategic importance to me. >> I hope that this extension will find its way into the official >> lilypond releases... > > What needs to be done for this? A good question. Do you have a contact e-

Re: Bar lines

> What does not make sense is to require the user to specify the > visual composition of a bar every time he wants to use it. That's > WYSIWYG without style sheets. Hmm. >> But if anyone wants to implement aliases, go ahead. > > I was of the impression that this was undesired. I can't remembe

Re: Chinese punctuation in Lyric mode

>> I've attached the output PDF. I hope it's possible to make the >> horizontal alignment of verses 2 and 3 to be the same as that of >> verse 1, i.e. treat ， and 、 the same as normal commas. > > the problem is that the *visible* width (i.e., the black stuff) is > not the same as the actual widt

Re: Single Whole Measure Rest vs compressed MMR

> IIRC I increased the horizontal space of compressed MMR in order to > prevent overlapping of tempo indications in a piece for an > instrument part with many MMR (similar to what Kieren is also > asking/fighting AFAIK). Aah, but this is a different problem (which can be very annoying, I know).

Re: Chinese punctuation in Lyric mode

> Hi, I'm trying to typeset a song with Chinese lyrics in Lilypond > 2.15.40-1 and I've ran into an issue with the horizontal alignment > of Chinese punctuation. While Chinese stops (U+3002 "。") and > full-width commas (U+FF0C "，") are correctly offset from the > centred syllables, the Chinese "d

Re: Figured bass help, please

> I know the standard figurings like 6, 6/4 etc., but could anyone who > understands give me a brief explanation of 6/5? Thanks. >From the bass note, add a 6th and a 5th (and a 3rd is to be added implicitly). In other words the chord is (from below to top): g bes des es Werner ___

<    7   8   9   10   11   12   13   14   15   16   >