Re: Is GridLY the future?

>>> Sometimes people are scared by a maybe too rough tone, though. >> >> It *is* a problem, and not only about code quality. More than once >> I abandoned a patch before the quality of the code was even >> considered but because of fruitless discussions about use cases, >> when for example using L

Re: E-mail management question

> Subscribing to this e-mail list is overwhelming me with e-mail posts > that are beyond me and outside of my scope of interest. Is it > possible to throttle the e-mail so I don't receive 70 e-mails a day? You should activate `thread view' in your e-mail reader. Then you can simply ignore all e

Re: Jianpu Notation

>>Ok, the problem was that your music file was for LilyPond 2.19 and >>jianpu3.ly only works with 2.18. > > Have you proposed adding this to LilyPond? It seems like this would > be a promising thing to add to the core, since it's another standard > notation. But it's still *far* away from the l

Re: Do we really offer the future?

> The current workaround, of course, is to use \tag around the > section(s) in question. In particular, that method [relatively] > easily solves “hide these 16 measures” types of situations (like my > Example #2) and “depending on the version/edition, use either THIS > or THIS” (like my Example #1

Re: Abbreviations

> Don't do it. Redefining standard commands just to save typing is a > terrible idea. It depends. Especially \tuplet is awfully long, and it makes scores with a lot of triplets extremely hard to read. > Apropos outsmarting tools: with LilyPond source code in particular, > you risk doing that to

Re: divisi staves and notehead merge (issue 3518 revisited)

> I've just found out that adding > > \override NoteColumn.ignore-collision = ##t > > does exactly the right thing, at least for the given example. I > guess that this is just a work-around, since no real merging does > happen... ...nd a much simpler solution is as follows, just for refe

Re: divisi staves and notehead merge (issue 3518 revisited)

> Please have a look at the `divisi-staves.ly' regression test, which > is the solution to > > https://code.google.com/p/lilypond/issues/detail?id=3518 > > [Actually, this file contains undocumented features that deserves > documentation due to its importance for orchestral music...] > > I wa

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

> assume that the Savane installation on Savannah will eventuall > move to FusionForge). > > There are no such plans at present. Hmm. How does the development of Savannah's bug tracking system work, then? > I would be glad if we could use Savannah > > Ok, I'll look into the image

Re: Google Code will be no more at 2016-01-25

> Looks like google can export all issue data to a JSON file, so > that's encouraging: > http://code.google.com/p/support-tools/wiki/IssueExporterTool Indeed! > Just thinking out loud in terms of images, I wonder if GNU > MediaGoblin might help? > > http://mediagoblin.org/ Well, we need a dedic

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

> How many of those issues are the sort that affect users every second > Tuesday after a a blue moon versus critical bugs? I don't understand what you are trying to ask. Please have a look at https://code.google.com/p/lilypond/issues/list to see how we are collecting reports. Note that we

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

> Patches are always welcomed, but I do not know if anyone is > interested in hacking on the current php code to add such a > feature. > > Right, I'm not exactly "interested", but if that single feature > makes the difference between lilypond moving to savannah or > , I'd at least try

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

>> However, one extremely important feature is sorely missing from >> Savannah's bug tracker: the ability to directly display images, >> [...] Are there plans to implement image support? > > Realistically, no. Hmm. Perhaps it's time to open an issue in FusionForge (at least I assume that the Sa

Re: [savannah-help-public] Google Code will be no more at 2016-01-25

> Issues: > Savannah supports web-based 'trackers' (for bugs, supports, tasks, > etc.), for example: > https://savannah.nongnu.org/bugs/?group=lwip > and also using a DebBugs server, for example: > http://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs However, one extremely important feature

Re: divisi staves and notehead merge (issue 3518 revisited)

Any takers? Werner == > Please have a look at the `divisi-staves.ly' regression test, which is > the solution to > > https://code.google.com/p/lilypond/issues/detail?id=3518 > > [Actually, this file contains undocume

divisi staves and notehead merge (issue 3518 revisited)

Please have a look at the `divisi-staves.ly' regression test, which is the solution to https://code.google.com/p/lilypond/issues/detail?id=3518 [Actually, this file contains undocumented features that deserves documentation due to its importance for orchestral music...] I want a variation of

Re: Help requested from LilyPond users

> You may notice that, after almost 6 months, I've just uploaded a new > version of LilyPond. Congrats to you and Masamichi-san for your hard work to make this important release possible! Werner ___ lilypond-user mailing list lilypond-user@gnu.or

Re: ugly default output

>> There's *lots* of "short" music that would benefit greatly from >> beautiful typesetting. > > "Short" music, per se, isn't the problem. Well, it is in case it leads to very tight typesetting. The out-of-the-box settings of LilyPond aren't suited to that. Have a look at code issues 2141 to 2

Re: lengthening broken ties

>> In bar 2 you can see the effect of `minimum-length-after-break'. > > You mean bar 4--bar 2 is the default. Of course. Typo. >> Any chance to fix this? BTW, if you compare bar 2 with bar 6, you >> see exactly the opposite effect w.r.t. the default tie length: with >> a time signature the ti

Re: lengthening broken ties

>> If it's convenient, have a look at the attached patch/sketch. It >> adds a property, minimum-length-left-broken, which lets you adjust >> broken bits that start a line. > > Excellent! What an improvement with just a few lines of code! > Thanks a lot. Now that the change is in the repository

Re: Levelling hairpins

> It's probably a language thing... Indeed. I should have looked up the phrase before writing. Sorry. > The link you included is very interesting - although I won't hold my > breath, because I see that the discussion has been going on for 4½ > years so far. The very issue is that we only have

Re: Levelling hairpins

> It's a shame that Lilypond does not (so far as I know) have any way > to > (a) associate one mark with another for positioning purposes > (b) associate dynamics with two staves, and use some sensible > algorithm for vertically spacing the dynamics between the two > staves and their conte

Re: Broken ligatures in recent LilyPond versions

> So do I understand you correctly, that if a font contains a ligature > for a given sequence of characters, then Lilypond will always > typeset that character sequence using the ligature, It is more complicated than that. Here is the ideal model for OpenType ligature handling. 1. Get the cur

Re: Broken ligatures in recent LilyPond versions

>> Unfortunately, this is currently beyond our control. What you see >> is the default rendering with the pango library. Right now, >> lilypond lacks a font interface to control OpenType features. > > And why did it work before? I don't know. > Because the old pango library did it differently

Re: Broken ligatures in recent LilyPond versions

> LilyPond used to do ligatures correctly in 2.16.2 (see image). In > 2.18.2 and 2.19 versions, the ligatures are broken. Why? Unfortunately, this is currently beyond our control. What you see is the default rendering with the pango library. Right now, lilypond lacks a font interface to control

Re: absolute font size issues

[Reviving an old thread] From: Werner LEMBERG Subject: Re: absolute font size issues Date: Fri, 14 Nov 2014 06:25:20 +0100 (CET) >> D'oh. A closer look into the sources of my old project dates 2011, >> and I did not use \abs-... but \...-mm instead and gave all >> di

Re: lengthening broken ties

>> In case it is easy to implement a `minimum-length-broken' property, >> please proceed! It would magically improve *a lot* of scores, I >> guess. > > If it's convenient, have a look at the attached patch/sketch. It > adds a property, minimum-length-left-broken, which lets you adjust > broken bi

Re: lengthening broken ties

> Why not make it possible to give different values of minimum-length > right when you do the basic override? Perhaps minimum-length could > be a pair, one number giving the non-broken value, another giving > the broken. Or--less intrusive--there could be a property alongside > it which acted on

Re: lengthening broken ties

> I've found no way to make it work. OK, thanks for trying. > Why not tackle the NoteColumn instead? > > \version "2.19.15" > > \paper { > indent = 0 > line-width = 50\mm > ragged-right = #f > } > > { > c''1 ~ \break > \once \override Score.NoteColumn.X-offset = 2 %% or

Re: lengthening broken ties

>> However, this has no effect. I guess this is because because the >> `after-line-breaking' callback is invoked too late in the >> formatting process. > > Yes, it appears that 'minimum-length is consulted before line > breaking happens, in the callback for ly:spanner::set-spacing-rods > (in lil

Re: lengthening broken ties

> They can degenerate to a dot, having no horizontal extensions > anymore. extensions -> extent Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

lengthening broken ties

Folks, I'm trying to work around an old problem of broken ties in tightly setted music: They can degenerate to a dot, having no horizontal extensions anymore. Following the example in section `Difficult tweaks' of the notation reference (with slight changes to change the property for all siblin

Re: Hungarian Gregorian

> I can't believe my eyes, it's beautiful! Indeed! Well done, Pierre. However, I have one minor nitpick: For my taste the stems are too long in general. I guess this is something that can be easily adjusted in case other people think the same. Werner

Re: Alternative Quarter Rest

> I’m looking for a good name for a rest style that is like the > default except for using a quarter rest shaped like a mirrored Z. > I’ve seen examples in 19th-C. Italian opera and 20th-C. American > hymnals, so names based on time, place, publisher, or genre do not > fit very well. Although, I

Re: how to make text spanner not sticking out to the right

> \once \override TextSpanner.bound-details.right.attach-dir = #-6 Thanks. However, this solution fails twice. 1. The vertical position of the `a tempo' must not be shifted horizontally relative to the music. In the example, the `a tempo' should exactly start at the last quarter

how to make text spanner not sticking out to the right

Consider the following snippet. \relative c' { f4 f f f | f4 f f f | f4 f f f | f4 f f f | \once \override TextSpanner.bound-details.left.text = "rit." \once \override TextSpanner.bound-details.right.text = "a tempo" f4\startTextSpan f f f\stopTextSpan f4 f f f |

Re: staccato dots and slurs in second voice

>> That's effectively what I'm doing. I'm changing the X-offset >> callback because it's only there that the property >> toward-stem-shift is read (see scm/output-lib.scm). The trick is >> allowing two different concurrent values for toward-stem-shift: 1.0 >> for when the staccato is alone, 0.0

staccato dots and slurs in second voice

Have a look at these two snippets. % slur.ly \relative c' << { c'8( b) } \\ { e,4 } >> % slur-beam.ly \relative c' << { c'8[( b]) } \\ { e,4 } >> % staccato-slur.ly \relative c' << { c'8( b-.) } \\ { e,4 } >> % staccato-slur-beam.

Re: Changing Text Fonts

> BTW, the above output also shows the directories searched by > fontconfig. Oops. I mean that lilypond -dshow-available-fonts 2>&1 | less also shows the directories searched by fontconfig. Werner ___ lilypond-user mailing list lilypond-user

Re: Changing Text Fonts

>> The example below does not work > > To my knowledge, Lilypond has difficulty — i.e., fails completely — > with older Mac OS True Type (.ttf) fonts, and Baghdad is one of > those [at least on my machine]. Being an old Mac OS TTF per se is not a problem. A font must have a Unicode cmap so that

Re: lilypond-user Digest, Vol 146, Issue 98

> I dare say there is a prettier and more concise way of doing this, > but at least I now have something that works! What about the following? #(define-public (pt-to-ss size) "Convert from points to staff space units." ;; The value `output-scale' gives the size (in mm) of the staff ;;

Re: bug with compound glyphs and/or diacritical markings?

> The code > > \version “2.19.15" > \markup \fontsize #12 “й" > > gives > > [a diacritic shifted to the right] > > [n.b., The diacritical mark should be centred directly above the glyph.] > > Is that expected, or is this a bug? > In either case, is there a suggested workaround? For me

Re: size of pdf files

> 1) Is it clear that nobody would need Postscript output itself, >e.g. to produce something different than PDF? PDF can be converted back to PS easily. > 2) Is that a feasible goal? Well, it would be a good solution. However, we need a PDF creation library, I guess... Werner ___

Re: Adjusting the absolute vertical height of staffgroup

> Vertical spacing can get tricky, so here's a helpful visual guide: > > http://lilypond.1069038.n5.nabble.com/attachment/164161/0/vertical-spacing-paper-variables.pdf Very nice! Do we have a comparable image in the lilypond documentation already? Note that in git the command `annotate-spacing

Re: size of pdf files

> Now I thought a bit and added "-dSubsetFonts=false" to the gs > parameter list in backend-library.scm. I also changed > lilyponddefs.ps to include white-on-white print commands for all the > emmentaler glyphs used in the four examples (hint: grep, sed, sort & > uniq make it easy to get a list o

Re: size of pdf files

> How can I force lilypond to include the full emmentaler-design-size > font instead of only a subset? LilyPond itself only produces PS files, *always* embedding complete fonts, AFAIK. Thus ghostscript's `-dSubsetFonts=false' option should work for Emmentaler also. Have you actually checked tha

Re: space-alist problem

> What defines the distance between a time signature and the next note > *with an accidental* (in addition to the TimeSignatures > `extra-spacing-width')? I would expect that the `first-note' (or > `next-note', if set) element of a TimeSignature's `space-alist' > handles this case also, but this

space-alist problem

[Resending to lilypond-user, since the issue might be interesting to more people...] What defines the distance between a time signature and the next note *with an accidental* (in addition to the TimeSignatures `extra-spacing-width')? I would expect that the `first-note' (or `next-note', if set)

Re: absolute font size issues

From: Marc Hohl Subject: Re: absolute font size issues Date: Wed, 12 Nov 2014 20:09:07 +0100 > Am 12.11.2014 um 13:35 schrieb Werner LEMBERG: >> >>> Well, I was about to answer, but somehow ... >> >> :-) >> >>> I defined some \abs-... markup comman

Re: absolute font size issues

> Well, I was about to answer, but somehow ... :-) > I defined some \abs-... markup commands myself Ha! Where are they? I guess this would have saved me many hours of wading through obscure LilyPond Scheme code... > and wondered if it would be feasible to implement a "switch" – > something l

Re: absolute font size issues

> \markup { \abs-fontsize #200 { > \abs-baseline-skip #250 { > \column { A A } } } } An alternative to `\abs-baseline-skip' is a scaling function `pt-to-staff-space', see below. While being more versatile, it's probably more awkward to use... Werner

Re: absolute font size issues

> . What's the unit of \abs-fontsize's `SIZE' parameter? > Typographical Points, i.e. 72.27pt = 1 inch? The documentation > lacks this. After investigations I now know that the unit of `SIZE' is indeed Typographical Points. This *must* be mentioned right there, since it otherwise cont

Re: Where is \staff-space defined?

> It seems suspicious. What happens is that in paper-defaults-init.ly, > there is a line: > > %% ugh. hard coded? > #(layout-set-absolute-staff-size (* 20.0 pt)) > > The comment says it all :-) Not that I am not guilty of hardcoding… > no stones are thrown… What's the problem? `paper-defaul

Re: Where is \staff-space defined?

>> I looked up the source code, but I couldn't find the definition of >> `\staff-space'... > > I’m not sure what ‘\staff-space’ is. I know the meaning of > ‘staff-space’ (without the slash), though. Is that what you meant? No, I mean `\staff-space', e.g. line-width = 50\staff-space as docum

Where is \staff-space defined?

I looked up the source code, but I couldn't find the definition of `\staff-space'... BTW, there isn't an index entry for it. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

absolute font size issues

Folks, to get a consistent global layout of a title, it seems to me that the best solution is to use absolute font-size values so that `set-global-staff-size' doesn't influence the layout. However, there are some issues. . What's the unit of \abs-fontsize's `SIZE' parameter? Typographica

Re: Unicode Font Issues

> If it works on Linux, I may have a way to get Linux on the windows > PC using Virtual Box. On the other hand I am using version 2.18.2 - > perhaps I should try 2.19.5 first. I fear that 2.19.5 will fail on Windows as 2.18.2 does. Werner ___ lil

Re: Unicode Font Issues

>> I tried to use unicode fonts for the lyrics. While the fonts show >> perfectly well in the input file, the output is not correct. Is >> there a workaround? > > If the bottom one is correct then it is rendering correctly on > Ubuntu 14.04, lilypond 2.19.3. ... This means we are again bitten by

Re: Unicode Font Issues

[about lilypond lyrics in Kannada script] > I tried to use unicode fonts for the lyrics. While the fonts show > perfectly well in the input file, the output is not correct. Is > there a workaround? This depends on (a) whether the used Pango library version has support for Kannada, and

Re: Feedback Request for Music Fonts

> The snippet portrayed in the image is from a piece called > Nálada. You probably noticed it as an example score I've used to > showcase some other other fonts. I call this font "Improviso". In case it's a font intended for songbooks, you might call it `Lalala' :-) Werner _

Re: Using greek letters breaks latin glyphs in markup

> It boils down to this: if I use greek letters in a \markup, the > corresponding latin character (alpha -> a, gamma -> g, etc.) is > rendered differently – it appears not smooth, but more pixelated. > Please see the attached screenshot from Okular in which the greek α, > χ and ε have an influence

Re: Bounty for Fixing Ligature Bug?

Sorry for the late reply. >> This is not correct. The most important part, namely to write a >> small test program for Pango that should be run on Windows and/or >> 64bit GNU/Linux platforms, is *not* done. > > I have a couple of development environments for Windows: a gcc-based > one, which I'

Re: Figured bass - rest - hepl please

> My guess, based admittedly on partial evidence, is that these are in > fact intended as indications of a seventh chord, not some sort of > Tasto Solo indication or ... After all, a player of the period would > have had as much difficulty distinguishing that symbol from a 7 as > we have after stu

Re: Bounty for Fixing Ligature Bug?

> I have read it. I know essentially what is happening, but I am not > experienced at all with testing this sort of thing. It seems that > the issue reported is stated pretty clearly, and that the questions > are pretty much answered, This is not correct. The most important part, namely to write

Re: Figured bass - rest - hepl please

> Me too. But my professor told me, that is correctly. > > http://www.imgup.cz/image/gK6 > http://www.imgup.cz/image/gK7 Very interesting. And you are sure this is a rest? Can you give more information on the composer and the piece? Is the original manuscript available online? It seems that

Re: Figured bass - rest - hepl please

> Of course r4 = s4. > But I need have the "symbol of rest" in the figured bass. Never seen this before. Please post a scan of what you want to achieve. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/

Re: Line in lyrics to show half or full note

>> Doing this would not be standard notation, so LilyPond does not >> provide a straight-forward way to achieve it. > > Yeah, I understand this is not standard notation. I am trying to > match up two different notation systems. In some of the Canarese > songs that I am working with, it is traditio

Re: Bounty for Fixing Ligature Bug?

> Last time I checked, this is a problem with Linux 64bit versions as > well. But for some reason it only works on 32bit Linux? > > I would willingly volunteer to do the work, I just have NO idea > where to begin. I have no background or experience with this kind of > coding, anyway... Read htt

Re: Bounty for Fixing Ligature Bug?

> I am not astute nor a programmer to know even how to begin fixing > this issue. I know it has been discussed as a possible limitation > of the pango. However, it seems that it works on some systems and > others not. > > What has to be done to fix the issue? > > What would be an appropriate boun

Re: rest collisions warning but no collision

> They are effectively colliding, which you've avoided by moving them > as pitched rests. Hmm. `Effectively colliding' isn't user friendly... Is there a way to avoid this warning if pitched rests really don't collide? Werner ___ lilypond-user m

Re: a thank you :)

>> today's no special anniversary, but i'd like to publicly thank David >> Kastrup for all the work he's been doing on LilyPond for the last >> years. Many of his patches are relatively small cleanups and code >> simplifications in the areas i have no experience with, so it's hard >> to appreciat

Re: OpusModus

> Just wondering who knows anything about OpusModus > (), and what the various thoughts are. The website looks nice, the screen shots are impressive, but its scripting language OMN looks terrible. It seems they tried hard to avoid Lilypond syntax... Or was it vice versa?

Re: Best practice with inconsistent "à 2"

> I have a large romantic score in front of me. In the handwritten > score the \partcombine stuff is done inconsistently for unisono > sections: sometimes it's written as one voice with "à 2", sometimes > as two voices, i.e. one notehead with stems up and down. So far I > can't see any reason for

Re: lilypond-user Digest, Vol 139, Issue 68

>> It would be nice, yes, but certain properties can't be set to a >> procedure. [...] > > Huh, I remember something like that. At some point of time, we > probably should see whether it is possible to do something about > that. But it was sort of non-trivial if I remember correctly. Do we hav

Re: See the new music fonts in action

> Scorlatti? :-) I like it. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: List defect?

> now there definitely seems to be something wrong with mail delivery > on the list. Some people already reported they were not receiving > some posts at all. With me, some posts pop up another time two days > or so after they were originally sent (including my own). Do any of > you know what migh

Re: BreathingSigns and automatic beams

>> I fully understand what you say, and similar symbols are used for >> singers, too, however, I think this somehow contradicts what >> lilypond is intended to do: engraving well-formatted music. It's >> not lilypond's job to imitate hand-written marks! In other words, >> I want to see some *pri

Re: BreathingSigns and automatic beams

>> I can't believe that it doesn't affect spacing. As soon as you >> insert something visible into the score that has a timing value >> (and a breathing mark definitely has, if probably not specified >> exactly), it *must* take part of the horizontal formatting. You >> even give a hint how to pos

Re: BreathingSigns and automatic beams

> - The mark generally doesn't affect the music spacing or beaming in > any way. I can't believe that it doesn't affect spacing. As soon as you insert something visible into the score that has a timing value (and a breathing mark definitely has, if probably not specified exactly), it *must* ta

Re: Problem reusing music with bass instruments

> (I didn’t know \resetRelativeOctave yet) No wonder, since it is completely undocumented. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to indicate a set of measures should not be played?

> Maybe something like > > [...] Here's the requested backtrace with today's git repository (release/2.19.8-1-25-g0ea80a5). Werner == Program received signal SIGABRT, Aborted. 0xb78a9245 in raise () from /lib/libc.so.6

Re: How to indicate a set of measures should not be played?

> Maybe something like [...] Interestingly, I got the following assertion failure with a self-compiled 2.19.4 (or so) while trying to process your example: ../flower/include/drul-array.hh:35: T& Drul_array::at(Direction) [with T = Skyline]: Assertion `d == 1 || d == -1' failed. I will

Re: Typesetting chord

> Which piece by Chopin is it and what measure? Hehe, if you have played it, you can recognize it immediately :-) It's ballade nr. 1, op. 23; in http://javanese.imslp.info/files/imglnks/usimg/5/54/IMSLP113137-PMLP01646-FChopin_Ballade_No.1__Op.23_BHBand1.pdf it's the last bar on page 7.

Re: Any advice for getting emacs working with lilypond on MacOsX?

> I'm a little confused how to file the bug or what I should say. Is > the suggestion to use > http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs? Aah, you are reading the lilypond mailing lists via gmane. Yes, I think the `bug-lilypond' mailing list gets mapped to `gmane.comp.gn

Re: Any advice for getting emacs working with lilypond on MacOsX?

> If you install from the source, the canonical way to compile and > install emacs is to do the following [...] Oops! I mean `... to compile and install lilypond', of course. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lis

Re: Any advice for getting emacs working with lilypond on MacOsX?

>> Please report the problems with the documentation to the mailing >> list (in case you haven't done so yet; I didn't follow the >> discussion close enough to remember) > > Werner, that was the first thing I did. Right here in this thread. > In the very first message. Yep. It's the correct thi

Re: Any advice for getting emacs working with lilypond on MacOsX?

> I had a bad experience with the lilypond docs on emacs mode, [...] My usual reply to such rants: Please report the problems with the documentation to the mailing list (in case you haven't done so yet; I didn't follow the discussion close enough to remember) so that we can improve it! This is:

Re: Oskar Fried: the Big Bang

> Our edition of Oskar Fried's songs was elected "BEST EDITION 2014" > by the German Music Publishers' Association, and we'll receive the > award at the Frankfurt Musikmesse on Friday! Great! Congratulations! Will there be a live stream of the event? Werner __

Re: articulation script vertically centered between staff lines.

>> Is there any general solution to this? > > I'm afraid that this is the kind of example where a general solution > is not needed. As you said, -\tweak Y-offset will do the job. Well, the `general solution' is a bug fix, of course. Werner ___

Re: Duration Line

> http://lists.gnu.org/archive/html/lilypond-user/2012-12/msg00145.html > In reply to Werner's request I changed the code to the following > (maybe you can adept it to your needs): :-) Very nice! Again a small nit: Is it possible that in case multiple voices share the same moment in time, this i

Re: Custom caesura command

> That's rather awful code. \override/\revert are not really working > all too well for single canned commands like that. > > I'd rather use something like > > caesura = > \tweak #'text #(make-musicglyph-markup "scripts.caesura.straight") > \tweak #'Y-offset #0 \breathe > > { c'\caesura d' e'

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

> Found another worthwhile optimization making a difference > (basically, not discarding and regenerating a blob that is going to > get analyzed next anyway). In your use case where almost all > changes happen in the same large file, this does make a bit of a > difference, in particular regarding

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

>> And the wortliste still takes more than 6 minutes on my computer: > > Which is not even a factor of 3 as compared to previously: But even that is an large improvement. It's now unbearable and no longer unusable :-) Werner ___ lilypond-user mai

Re: kerning/ligatures in opentype fonts

> Werner, I hope you agree with my short summaries of your helpful > explanations? Yep. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: kerning/ligatures in opentype fonts

> You are confused about the problem that is being discussed. Certainly not. > What _you_ are talking about is not how to deal with a defective > "ff" ligature, but rather about the typographic reasons to > distinguish betweem a _working_ "ff" ligature and two separate "ff" > letters when typese

Re: kerning/ligatures in opentype fonts

>> If for a font "ff" leads to collisions, and the ligature is not >> correct at that point, is it recommended to insert space or to >> switch the font? > > Yes, at least for German. Uh, I mean you should insert space. Virtually no font resolves this `properly' today, I reckon. Werner

Re: kerning/ligatures in opentype fonts

> If for a font "ff" leads to collisions, and the ligature is not > correct at that point, is it recommended to insert space or to > switch the font? Yes, at least for German. > Or, stated differently: Should I consider it a sign of low quality > of a font if consecutive letters collide or touch

Re: kerning/ligatures in opentype fonts

> hmm. I wasn't actually aware of that. But it makes sense. ;) Note that the German support for LaTeX goes even one step further: The command "| (to be inserted between the two non-ligature characters) adds some small horizontal space to avoid glyph collisions. As mentioned by Urs, there is

Re: kerning/ligatures in opentype fonts

> Asking for a [selnolig] for LilyPond seems like too much ... Why not? It shouldn't be too difficult to use the data from this lualatex package to write a script that walks over lilypond strings, given that Frescobaldi now has a Python library to parse Lilypond input files. Werner __

Re: kerning/ligatures in opentype fonts

> the ligature is obviously there in my copy of the font. You are aware that `Aufführung' *without* an `ff' ligature is the correct way to write this word in German? `Auf' is a prefix, and as such it should not have a ligature with the rest of the word. A famous example of a similar situation i

Re: kerning/ligatures in opentype fonts

> Does the font handling in Lilypond know about ligatures in opentype > fonts? No. Text handling is done by the Pango library. Unfortunately, we don't have an interface yet to control OpenType features. This is issue #1388. The main problem is designing a good interface for Lilypond; the impl

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