Output break positions (question or feature request)

Hi, as asked on the -user list I am looking for a way to collect the positions of all breaks in a LilyPond score. http://lists.gnu.org/archive/html/lilypond-user/2015-01/msg00185.html suggests that at the time engravers are doing their work the line and page breaking hasn't been performed so e

Problem with enharmonic tie in partcombine (can let LilyPond crash)

Hi, I encountered a strange crash that is related to enharmonic ties. I'm using an engraver that is passed a grob. One particular snippet of input code lets now crash LilyPond. I can't easily produce a compiling (i.e. crashing) example because it's quite intertwined with project specific libra

wish: ly:cheapest-breaking (or whatever name)

Hi list, following up on a thread that I started some time ago (http://lists.gnu.org/archive/html/lilypond-devel/2014-11/msg00139.html) I'd like to draw the conclusions from that and ask for an additional breaking "algorithm". It would be nice to have a compilation mode that doesn't care abo

Re: How to pack notes very tightly?

on changing >horizontal spacing mentions setting base-shortest-duration to adjust >horizontal spacing ( >http://www.lilypond.org/doc/v2.16/Documentation/notation/changing-horizontal-spacing), >but in fact, it seems as though common-shortest-duration is the >variable >that really

Re: How to pack notes very tightly?

Am 20. Januar 2015 13:25:25 MEZ, schrieb James : >On 20/01/15 07:29, Urs Liska wrote: >> Forwarding to bug-lilypond. >> Could someone please verify this > >Verify what precisely? If what the NR states is wrong. Or if it needs enhancement by the other property. > >Ja

Re: wish: ly:cheapest-breaking (or whatever name)

Am 23.01.2015 um 13:35 schrieb Ralph Palmer: On Mon, Jan 19, 2015 at 9:33 AM, Urs Liska <mailto:u...@openlilylib.org>> wrote: Hi list, following up on a thread that I started some time ago (http://lists.gnu.org/archive/html/lilypond-devel/2014-11/msg00139.html) I&

Retrieving information about breaks (was: Partial compilation (again))

aining all break points of a given LilyPond run. If that's not currently accessible I'd like to add that as a feature request. Urs Am 21.11.2014 um 14:44 schrieb Urs Liska: Am 21.11.2014 13:33, schrieb David Kastrup: Urs Liska writes: Am 21. November 2014 12:36:59 MEZ, s

Re: Retrieving information about breaks

do yet is handle mid-measure breaks, but I know where I can look that up ;-) So this isn't a feature request anymore ... Best Urs Am 23.01.2015 um 17:42 schrieb David Nalesnik: Hi Urs, On Fri, Jan 23, 2015 at 9:33 AM, Urs Liska <mailto:u...@openlilylib.org>> wrote: Picking

Re: website: new screenshots for Denemo and Frescobaldi?

Am 14.03.2015 um 13:21 schrieb Federico Bruni: Hi all What about adding new screenshots for Denemo and Frescobaldi? Good idea. They are on top of the easier editing page and the images are very out-of-date. I've uploaded some here: http://sixbarsjail.it/tmp/lily/ I did not put too much

Re: cadence font and lilypond-book

Am 17.03.2015 um 09:57 schrieb Marc Hohl: Am 17.03.2015 um 09:36 schrieb Urs Liska: Am 17.03.2015 um 09:32 schrieb Marc Hohl: Hi list, hi Abraham, I asked about this subject before, but now I think I did everything right, but still ... I use the self-compiled lilypond and install it

Re: cadence font and lilypond-book

Am 17.03.2015 um 10:27 schrieb Urs Liska: I can't test it because I don't have any .lytex files available, but obviously there should be some point in the build/installation process that determines the correct paths relative to the installation directory. Oops, no. Of course the i

Re: cadence font and lilypond-book

Am 17.03.2015 um 10:53 schrieb Marc Hohl: Am 17.03.2015 um 10:27 schrieb Urs Liska: [...] does not help here, lilypond-book has ceased to work, obviously. I checked the contents of lilypond-book in a number of installations and have the impression there's a quite serious bug (if I&

Re: cadence font and lilypond-book

Am 17.03.2015 um 11:20 schrieb Marc Hohl: Am 17.03.2015 um 10:57 schrieb Urs Liska: Am 17.03.2015 um 10:53 schrieb Marc Hohl: Am 17.03.2015 um 10:27 schrieb Urs Liska: [...] does not help here, lilypond-book has ceased to work, obviously. I checked the contents of lilypond-book in a

Issue with symbol-list? and ly:parser-include-string

As this thread suggested https://lists.gnu.org/archive/html/lilypond-devel/2015-03/msg00193.html there is an issue with the parser when a symbol-list? predicate is used as a function argument and ly:parser-include-string in that function. As it turned out the problem is reproducible with very li

Ghostscript problem in 2.19.18

Hi, just trying out the binary releases again, and I notice that with 2.19.18 all documents fail with the following message: Layout output to `document.ps'... Converting to `./document.pdf'... warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLev

Re: Ghostscript problem in 2.19.18

Am 13.04.2015 um 14:19 schrieb Masamichi HOSODA: This is on Debian with the linux-386 binary and applies to _any_ file, even { c } . Compiling with the 2.19.17 binary works. Compiling with the 2.19.18 binary fails. Compiling with a custom build from current master works. As there are no relevan

Re: Ghostscript problem in 2.19.18

Am 13.04.2015 um 16:04 schrieb Masamichi HOSODA: I have just installed lilypond-2.19.18-1.linux-x86.sh on another machine running Debian 7 stable with latest updates. And the error is identical. Maybe (this is a big maybe) I'll have a chance to test it on another (different) 32bit Linux installat

Re: Ghostscript problem in 2.19.18

Am 13.04.2015 um 16:47 schrieb Masamichi HOSODA: gs: Interpreter revision (905) does not match gs_init.ps revision (915). lilypond-2.19.18-1.linux-x86.sh includes gs-9.15. However, lilypond seems to be invoking the external gs-9.05 instead of included gs-9.15. My ubuntu 64 bit environment hav

Re: Ghostscript problem in 2.19.18

Am 14.04.2015 um 16:22 schrieb Masamichi HOSODA: OK. Compiling a file with lilypond-2.19.18-1.linux-x86.sh ends with Invoking `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./document.pdf -c.

Re: compile failure - "parsed object should be dead" in 2.19.20

ith binary releases. It is related to calling a system vs. a packaged Ghostscript. At least it doesn't seem to be an issue with my personal configuration ... Urs -- Urs Liska www.openlilylib.org ___ bug-lilypond mailing list bug-lilypon

Re: my favorite bug :-)

Am 01.05.2015 um 13:53 schrieb Masamichi HOSODA: The bug would be fixed if lilypond would make ghostscript use a complete path to the intermediate lines.ps file for the ps to pdf conversion. Does anyone know how to convert from any path (relative and absolute path) to absolute path in scheme (

\tempo collision with cross staff beam

Hi bug squad, I ran into a collision bug. With a cross-staff beam present \tempo doesn't take any objects above the staff into account. If you comment out the beam in the following example the \tempo is correctly shifted upwards to accomodate the dynamic. Result is identical with 2.18.2 and 2

musicxml2ly doesn't handle nested tuplets

When dealing with export of nested tuplets to MusicXML (https://github.com/wbsoft/python-ly/issues/25) I realized that the exported MusicXML can be properly read by Finale but not be reimported through musicxml2ly. https://github.com/wbsoft/python-ly/issues/25#issuecomment-107363569 shows how

Re: musicxml2ly doesn't handle nested tuplets

Am 5. Juni 2015 13:55:04 MESZ, schrieb Ralph Palmer : >On Tue, Jun 2, 2015 at 10:54 AM, Urs Liska wrote: > >> When dealing with export of nested tuplets to MusicXML ( >> https://github.com/wbsoft/python-ly/issues/25) I realized that the >> exported MusicXML can be pro

Re: musicxml2ly doesn't handle nested tuplets

Am 05.06.2015 um 15:09 schrieb Urs Liska: I can't tell from the LilyPond documentation whether MusicXML - either >import, export, or both - is explicitly supported by LilyPond. Before I >submit this as an issue, can someone please confirm for me that >LilyPond >does suppor

Remove old "News" entry from home page

Hi, I've just stumbled over it again: The first thing you see on lilypond.org after the latest release informations is the "news" item about the Fried edition prize. I really think this should be either removed or pushed downward by new "news". Isn't there anything worthwile that can be added here

Re: PDF Links in Windows

Am 05.10.2015 um 11:18 schrieb Federico Bruni: > Il giorno lun 5 ott 2015 alle 10:57, Federico Bruni > ha scritto: >> Il giorno lun 5 ott 2015 alle 9:54, Urs Liska ha >> scritto: >>> I think what he wants is the following: >>> - view the PDF in Acrobat

Re: PDF Links in Windows

Am 05.10.2015 um 12:42 schrieb James: > Hello, > > On 05/10/15 10:23, Urs Liska wrote: >> Am 05.10.2015 um 11:18 schrieb Federico Bruni: >>> Il giorno lun 5 ott 2015 alle 10:57, Federico Bruni >>> ha scritto: >>>> Il giorno lun 5 ott 2015 alle 9:

Re: PDF Links in Windows

Am 05.10.2015 um 15:04 schrieb Henning Hraban Ramm: > On OSX, my old Acrobat Pro 9 as well as Adobe Reader 11 try to open > LilyPond’s "textedit://" links with LilyPad, after asking if they may or > should block such attempts. So the "security reasons" seem to apply only on > Windows (I don’t

Re: Accidentals tied over a system break

Am 8. Oktober 2015 19:59:57 MESZ, schrieb Sven : >Sorry, I didn't know this is a known issue. > >And thanks for correcting me on how to actually remove the second >sharp, >Urs: \once \omit Accidental get's rid of the bugger, while \once \hide >Accidental makes it transparent, leaving its space in

SubdivideBeam gives undesired result when beaming over more than a quarter note

Since the fix for #4355, respectively commits 8fa2d858 and 0382ed88, it is not possible anymore to subdivide beams that are longer than a quarter note. \version "2.19.32" { \set subdivideBeams = ##t % This is correctly subdivided \set baseMoment = #(ly:make-moment 1 8) \repeat unfold 16 c

Re: Problem understanding subdivided beam

r note -> no beam. I've written a feature request/bug report to bug-lilypond. Urs > > Cheers, > Jan-Peter > > Am 19.11.2015 um 09:42 schrieb Urs Liska: >> Hi, >> >> I have a problem getting a beam subdivision right, and I can't seem to >>

Re: SubdivideBeam gives undesired result when beaming over more than a quarter note

it cl config Rietveld server (host[:port]) [codereview.appspot.com]: Allura server []: You must provide the address of the Allura tracker server: ``` What should I do now? Urs Am 19.11.2015 um 10:43 schrieb Urs Liska: > Since the fix for #4355, respectively commits 8fa2d858 and 0382ed88, it > is no

dynamics-barline collision

Hi list, I am somewhat surprised that dynamics can still collide with barlines as shown in the attached image. I thought this kind of issue had been quite long overcome. The \pp is defined in a Dynamics context, and of course I can work around the collision by overriding self-alignment-X. But is

Irregularity in horizontal spacing

Hi, one more question. I am right now experiencing an irregularity in the horizontal spacing that is very small but still pretty annoying. In the attached image you can see how the quavers are spaced out irregularly. It is most obvious in the melody staff but you can also see it in the piano left

Re: Irregularity in horizontal spacing

y. And in effect inacceptably. As I have to get that score ready ASAP I can't wait for a proper fix (if it should be considered a bug) but need a workaround that works better than having to space the notes in all measures manually. Urs > - Abraham > > On Friday, November 20, 2015,

Re: Irregularity in horizontal spacing

Weitergeleitete Nachricht Betreff: Re: Irregularity in horizontal spacing Datum: Fri, 20 Nov 2015 23:04:42 +0100 Von: Urs Liska An: bug-lilypond@gnu.org Am 20.11.2015 um 17:09 schrieb tisimst: > Are you referring to the final 16ths in each of the beamed groups in

Re: Irregularity in horizontal spacing

Am 21.11.2015 um 00:01 schrieb Simon Albrecht: > On 20.11.2015 23:19, Urs Liska wrote: >> Weitergeleitete Nachricht >> Betreff: Re: Irregularity in horizontal spacing >> Datum: Fri, 20 Nov 2015 23:04:42 +0100 >> Von: Urs Liska >> An: bug-lilypo

Re: Irregularity in horizontal spacing

ach (lambda (space) #{ \extraSpace #(car space) #(cdr space) #}) spaces)) which now allows me to write \extraSpaces #'((3 . 3) (3 . 6)) etc. Best Urs Am 21.11.2015 um 01:06 schrieb Urs Liska: > > Am 21.11.2015 um 00:01 schrieb Simon Albrecht: >> On 2

Re: Irregularity in horizontal spacing

Am 23.11.2015 um 09:57 schrieb Simon Albrecht: > On 23.11.2015 09:49, Urs Liska wrote: >> Just to finish this thread up (apart from the opened issue) I'll report >> how I finally dealt with the issue in my score. >> >> It turns out that >> \override S

Another beam subdivision issue

After completing my patch for #4664 I tested beam subdivision with another example and was unpleasantly surprised that the other example produced a wrong result. This example should render the subdivisions with a regular alternation of two and one beams. Instead all beam subdivisions show two beam

Ugly collision when acciaccatura is followed by downward stem

I encountered a rather ugly rendering of an acciaccatura. As you can see in the first attachment the slurs is colliding pretty hard with the beam. In addition, it seems that an acciaccatura's slur always crosses the stem of the following note if that happens to be downwards, see the second attachm

Re: Ugly collision when acciaccatura is followed by downward stem

Am 26.11.2015 um 12:16 schrieb lilyp...@maltemeyn.de: > Am 2015-11-26 10:33, schrieb Urs Liska: >> PS: A non-bug question: I tweaked that slur using \shape, but could >> someone give me a hint as to use other properties to override, so the >> slur doesn't cross the st

Re: slurs with more than 2 control points

om the Bugs mailing list archive at Nabble.com. > ___ > bug-lilypond mailing list > bug-lilypond@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-lilypond > -- Urs Liska www.openlilylib.org ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Command line option to have barcheck failures cause errors instead of warnings

Hi, there was the request for a way to have barcheck failures cause errors instead of warnings: http://lists.gnu.org/archive/html/lilypond-user/2015-12/msg00074.html I think this is a valid use case as very often you don't actually want to have the compiled score when it contains barcheck failure

Re: Fontmap entry for Fontmap.local ends prematurely!

Am 07.12.2015 um 00:24 schrieb Karl Berry: > We have no plans for any more 2.18.x releases, so ca you confirm if you > still get the same problem when using the lastest development (2.19.x) > available download? > > The old version is working ok for my (minimal) purposes for the momen

Re: Another beam subdivision issue

d within that function I would be happy to give it a try. Of course ready-made solutions are OK too, but I'd be willing to learn ... Best Urs Am 25.11.2015 um 16:34 schrieb Urs Liska: > After completing my patch for #4664 I tested beam subdivision with > another example and was unpleasant

Re: Noteheads slightly too large

Am 12.12.2015 um 00:02 schrieb Simon Albrecht: > Thanks for the report. > This *may* be intended, which should be checked - if someone recalls any discussion. At least I recall speaking someone from a major publishing house about how they c

Re: Noteheads slightly too large

Am 12.12.2015 um 11:11 schrieb Simon Albrecht: > On 12.12.2015 00:43, Urs Liska wrote: >> >> Am 12.12.2015 um 00:02 schrieb Simon Albrecht: >>> Thanks for the report. >>> <https://sourceforge.net/p/testlilyissues/issues/4693/> >> This *may* be intended,

ly:one-line-breaking doesn't properly handle indent value/side margins

Hi, while testing the new #ly:one-line-auto-height-breaking I noticed some issues with the already available #ly:one-line-breaking. It seems the left and right margins are not properly handled in that mode: The right margin is way too large to my eyes, which you can see when setting right-margin

Re: ly:one-line-breaking doesn't properly handle indent value/side margins

Am 18.01.2016 um 17:04 schrieb Urs Liska: > Hi, > > while testing the new #ly:one-line-auto-height-breaking I noticed some > issues with the already available #ly:one-line-breaking. > > It seems the left and right margins are not properly handled in that mode: > > The

git-cl traceback (timeout?)

When uploading a patch git-cl failed with the transcript below: I'm not sure if that's caused by git cl (I had just pulled the newest version) or if it's a simple time-out on my side, but: a) If it's a git-cl issue it should be fixed b) If it's a time-out such an error should be handled by git-cl

Re: git-cl traceback (timeout?)

Am 19.01.2016 um 12:29 schrieb Trevor Daniels: > Hi Urs > > What did you enter in response to the query? I pressed ENTER (to create a new issue item) Urs > > Trevor > > - Original Message - > From: "Urs Liska" > To: ; "Phil Holmes" >

Re: Poor line break decisions

Am 23. Januar 2016 18:51:35 MEZ, schrieb Kevin Barry : >Compiling your code on my system (fedora, 2.19.35) does not reproduce >this >problem. Could it be a problem with your environment? LilyPond also >doesn't >give any warnings in the process. Yes, Chris, any warnings on your side (->barchecks)

Re: Poor line break decisions

rent devel version at hand, sorry. Urs > > Cheers, > Harm > > ___ > bug-lilypond mailing list > bug-lilypond@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-lilypond > -- Urs Liska www.openlilylib.org ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Automatically shift dynamics horizontally?

The fact that dynamics are always aligned to their notes can cause unnecessarily large distances between staves as you can for example see in the attached image generated from the following code. \version "2.19.35" off = { % uncomment either of the following lines % \once \override DynamicText.X

Multiple beams too close to noteheaD

Hi all, I've always found that beams with three or more beams look too tight, but now reading Gould, p. 19 confirms that, and I consider this a type-ugly bug: According to Gould outer beams starting with the third should move away from the notehead, and "beams should never be closer to the notehe

Multiple beams too close to notehead

Hi all, I've always found that beams with three or more beams look too tight, but now reading Gould, p. 19 confirms that, and I consider this a type-ugly bug: According to Gould outer beams starting with the third should move away from the notehead, and "beams should never be closer to the notehe

Re: Multiple beams too close to noteheaD

Am 01.02.2016 um 10:15 schrieb Werner LEMBERG: >> Attached you'll find examples for three and four beams, and I expect >> this to continue with more beams. I have colored the ones too close >> in red and adjusted them (blue) to Gould's minimum distance. > Thanks for your analysis, to which I agr

Re: Fwd: lilypond-book/pdflatex: LaTeX Error: Environment lilypond undefined.

I *think* it's wrong usage, but I didn't have the time to inspect too closely. The error message about the undefined \lilypond environment indicates that LaTeX tries to compile the original file and not the one processed by lilypond-book. The OP should check the *actual* result of the lilypond-bo

Re: Noteheads slightly too large

Am 9. Februar 2016 14:59:45 MEZ, schrieb Gilberto Agostinho : >Hi Schneidy, > > >Schneidy wrote >> Here's a workaround > >That doesn't seem to work for me, I still get the noteheads creeping >out the >staff lines, and if I lower the magnification value more (like 0.98 or >less) >the noteheads su

Exporting fonts as outlines in SVG (was: \markup \sans ... does not always give sans-serif output in svgs in 2.19.36)

Slightly OT but still related: would it be possible to (optionally) export text fonts as outlines in the SVG? As it is SVG is only properly displayed if the fonts are installed on the viewer's machine - something you can't expect when producing for web display (which should be a major target for th

Re: \markup \sans ... does not always give sans-serif output in svgs in 2.19.36

Am 17.02.2016 um 16:48 schrieb Paul Morris: > “serif” “sans-serif” and “monospace” are officially defined as meaningful > values for the font-family property for svg files. They tell an svg renderer > (like a web browser) to “use a font of this type when displaying this svg > image”.[1] > >

Use "#f" instead of "false" in manuals (was: OT: pagenumber)

Am 05.03.2016 um 09:51 schrieb Blöchl Bernhard: > Setting myself into the situation of a maybe user wanting to switch > off the pagenumber I would google "lilypond pagenumber". Google is > correcting me to page number (in correct English written separately). > > The first hit is > LilyPond Notati

Re: removing old stuff

Am 30. März 2016 15:38:42 MESZ, schrieb Federico Bruni : >Hi all > >If you search "lilypond blog site:lilypond.org", you'll find these old >pages. > >I think that this should be removed from the server: >http://lilypond.org/blog/ I think so. IIRC we discussed whether we wanted to integrate the

Re: Weird error when using skipTypesetting

Am 04.04.2016 um 23:30 schrieb Sharon Rosner: > Hi all, > > I’m getting a bunch of "programming error: insane spring distance > requested, ignoring it” etc errors when compiling the following: > > \version "2.19.37" > > music = \relative c' { > c1 d e f \bar "||" > \set Score.skipTypesetting

Re: Problems with literal fonts

Hm, if you want help or suggestions you should give us a better idea of what you want. If I compile your example I can't read music either, but it's not related to the size of any text fonts ... Urs Am 14.04.2016 um 09:40 schrieb Paolo Bacchetta: > Fonts in title and authors are simply way too b

Re: dodecaphonic-no-repeat and mid bar breaks

Am 20.04.2016 um 10:44 schrieb Phil Holmes: > "Simon Albrecht" wrote in message > news:5716a647.7070...@mail.de... >> On 19.04.2016 15:02, Phil Holmes wrote: >>> "Gilberto Agostinho" wrote in >>> message news:57161fa5.7000...@gmail.com... Hello bug squad, When using the accidenta

Re: reduce the news in home page

I'm surprised that the Fried songs news item is still online. I *did* prepare a patch to remove it, obviously I didn't finish that ... Urs Am 20. April 2016 17:56:36 MESZ, schrieb Federico Bruni : >I think that there are some old news in the home page that should be >removed. > >I would move to

Re: regression: point-and-click no longer includes absolute path

ine-char-column location > \testpaths > > > commit f30a8189adbbeefa2103e2c2e194040f66bc2291 > Refs: release/2.19.27-1-280-gf30a818 > Author: Urs Liska > AuthorDate: Tue Jan 19 10:52:33 2016 +0100 > Commit: Urs Liska > CommitDate: Sun Jan 24 21:24:52 2016 +0100 >

Re: reduce the news in home page

Am 16.05.2016 um 18:12 schrieb Federico Bruni: > Il giorno lun 16 mag 2016 alle 9:34, Urs Liska ha > scritto: >> However, I suggest that once this is completed we reconsider the >> old-news display. >> Currently there's http://lilypond.org/old-news.html wher

Re: regression: point-and-click no longer includes absolute path

Am 17.05.2016 um 09:31 schrieb Mark Knoop: > Thanks Urs, > > At 09:37 on 13 May 2016, Urs Liska wrote: >> Which version of LilyPond and what Linux exactly do you use (2.19.40 >> binary release?)? > lilypond 2.19.40, on Fedora 23, distro build (lilypond-2.19.40-1.fc23)

Changed behaviour of point-and-click

As reported by Mark Knoop in http://lists.gnu.org/archive/html/bug-lilypond/2016-05/msg5.html this commit commit f30a8189adbbeefa2103e2c2e194040f66bc2291 Author: Urs Liska Date: Tue Jan 19 10:52:33 2016 +0100 #4747: Remove (all) uses of is-absolute? The check for absolute

Re: Changed behaviour of point-and-click

Am 17.05.2016 um 14:30 schrieb Mark Knoop: > At 05:47 on 17 May 2016, Urs Liska wrote: >> Mark, can you give us a reason why you consider relative >> point-and-click links "broken"? > I am unaware of any way for the pdf viewer, or the whatever handles the > textedi

Re: Can't download Lilypond(!)

Am 04.06.2016 um 15:33 schrieb Mike: > Hi there, I'm using the link offered on your webpage > http://download.linuxaudio.org/lilypond/binaries/linux-64/lilypond-2.18.2-1.linux-64.sh > but it's not working, is the server down? I've been trying since this > morning... > > Unable to connect > Firef

Re: Wrongly combined note heads

Am 23.06.2016 um 09:19 schrieb Andrew Bernard: > Fixing lilypond would presumably > mean adopting one particular style that may not be what everybody wants. or rather: setting *a default* that not everybody wants. But having to override the default because it's not your preferred way is clearly

Re: old style arguments in overrides using #' generate errors

I can't pinpoint it but the oldstyle syntax was accepted for some time but is now invalid. As was said convert-ly should handle this. HTH Urs Am 21. Juli 2016 15:05:43 MESZ, schrieb Karim Haddad : >Hi > >I am not sure it is a bug, but with LilyPond 2.19.45 version > >we have this error : > >er

Ratio black and whole noteheads

Hi all, addressing a question I received about the attached score where the dotted crotchet in r.h. (middle of the excerpt) was considered to be placed too far to the left I investigated why this looks weird. Gould doesn't give a proper example of a whole note in parallel with a black note (at le

Re: Ratio black and whole noteheads

Am 25.07.2016 um 12:29 schrieb Andrew Bernard: > Hi Urs, > > Gould means 5:6. [Dear me, fractions in proportions.] Of course she means 5:6, I have just copied more literally "2 1/2 semibreves to 3 black noteheads". And it made the difference more clear with having the same denominator on both si

Re: 2.19.46 seg faulting

Am 31. Juli 2016 15:10:54 MESZ, schrieb Andrew Bernard : >I am reluctant to even mention it, but a perfectly OK score that runs >fine on 2.19.45 now seg faults on 2.19.46. > >is there any change that is known to cause such behaviour? I am unable >to discern what it may be, since my code is uncha

Crash: Unterminated tie with articulation in temporary voice

The attached file produces a crash on LilyPond 2.19.47 while it compiles fine on 2.18.2. I don't have any earlier 2.19 versions ready to narrow it down further. It is a temporary polyphonic situation, and there's an unfinished tie - in the second voice - with an articulation attached to the same

Re: Crash: Unterminated tie with articulation in temporary voice

Am 08.09.2016 um 21:53 schrieb David Kastrup: > Urs Liska writes: > >> The attached file produces a crash on LilyPond 2.19.47 while it compiles >> fine on 2.18.2. I don't have any earlier 2.19 versions ready to narrow >> it down further. > What does "produc

Re: Crash: Unterminated tie with articulation in temporary voice

Am 09.09.2016 um 09:24 schrieb Mark Knoop: > At 01:57 on 09 Sep 2016, Thomas Morley wrote: >> 2016-09-09 0:13 GMT+02:00 Simon Albrecht : >> _Cannot_ confirm crash with a build from most recent master, i.e from: >> commit 5944d20489bb5b8e4c4907fa3b3bcae9ec275ccb >> >> with: >> gcc --version >> gcc

Re: Major Minor Chord

Am 09.09.2016 um 17:42 schrieb Andrew Bernard: > Hi Craig, > > Not at all. This is not a bug. If you want this to express the chord > construct you are describing, explicitly put in the accidentals. Lilypond > has no notion of standard chords in various periods of music, unless you > are using a

Re: problem with \partcombine and dynamics/hairpins

Hi Kieren, no time to really look into it. But in https://git.openlilylib.org/bfsc/das-trunkne-lied/tree/master/library/ly/to-lilylib are two "remove-" files that deal with this issue IIRC. Maybe they're if help. Urs Am 25. September 2016 19:16:42 MESZ, schrieb Kieren MacMillan : >Hi all, >

Re: More than 5 nested tuplets of large value hangs Lilypond permanently

Am 13.11.2016 um 07:28 schrieb mclaren: > \version "2.18.2" > > << > > \new Staff { > \clef "treble" > > % This is a Nancarrow-style 1% acceleration. It hangs Lily permanently with > message "Preprocessing graphical objects..." > % One fewer nested tuplet runs without error. To prove this, co

Re: More than 5 nested tuplets of large value hangs Lilypond permanently

Am 13.11.2016 um 15:57 schrieb Urs Liska: > % One fewer nested tuplet runs without error. To prove this, comment out > %next line, and uncomment the line after that. Sorry, I forgot to remove this comment. The proper way to check is to comment out the innermost tuplet by editi

Re: Word hyphenation in LilyPond version 2.18.2.

Am 23. Dezember 2016 08:45:15 MEZ, schrieb Werner LEMBERG : > >> What we need is automatic hyphenation for lyrics ... but the >> standard algorithm (read the thesis ofFranklin Mark Liang) is not >> optimal because it is not designed to find _all_ possible >> hyphenations and because hyphenation

Re: Word hyphenation in LilyPond version 2.18.2.

Am 25. Dezember 2016 23:02:45 MEZ, schrieb Werner LEMBERG : > >>> Is there a set of official rules how hyphenation is done for >>> lyrics? I just found some forums where the advice is rather >>> ambiguous. >> >> Well, for the german language you would use the official hyphenation >> rules that a

Re: Word hyphenation in LilyPond version 2.18.2.

Am 26.12.2016 um 00:27 schrieb Knut Petersen: > >>> Heutzutage gehen immer weniger Zuschauer in The- >>> ater, egal ob Opernaufführungen oder Sprechthea- >>> ter. > > Der Soldat ging in die Wach- > stube und holte seine Wachs- > tube aus dem Schrank. LOL. > > The sentence above demonstrat

Re: Word hyphenation in LilyPond version 2.18.2.

be "vowels at the border of syllables with at least three letters (and at least one other vowel?) can be hyphenated as a syllable in lyrics". But surely I'm still missing something. And of course I don't think it's necessary to catch 100% of the cases. I'd say anythi

Re: Word hyphenation in LilyPond version 2.18.2.

Am 26. Dezember 2016 10:15:19 MEZ, schrieb Werner LEMBERG : > >> Remember that I suggest applying the "lyrics" rule as a second >> pass. So: >> >> "re-al" and "Teak-holz" are the results of the first pass, then: >> >> Teakholz isn't interesting at all as it doesn't have vowels at >> syllable bo

Re: Word hyphenation in LilyPond version 2.18.2.

Am 28. Dezember 2016 19:04:51 MEZ, schrieb Werner LEMBERG : > >> But I still think it should be possible to define some rules to apply >> as a second pass to lyrics that have been hyphenated by Frescobaldi, >> and I think this should be possible without false positives (although >> being strict o

Re: Word hyphenation in LilyPond version 2.18.2.

Am 28.12.2016 um 19:33 schrieb Werner LEMBERG: >>> Dialog -> Di-a-log >>> Bibliothek -> Bi-bli-o-thek >>> Geometrie -> Ge-o-me-trie >> Well, here I'd say if it significantly reduces the number of >> syllables that have to be split manually then it's better to have >> than not. At least you

Italic numbers for fingerings (feature request)

Hi all, if I'm not mistaken (and a very recent post in the German forum http://www.lilypondforum.de/index.php?topic=2465.0 seems to confirm that) LilyPond doesn't have built-in support for italics in fingerings. As using italics for fingerings is a regular use case (e.g. to differentiate between

Re: Italic numbers for fingerings (feature request)

Am 16.02.2017 um 23:27 schrieb tisimst: > Hi, Urs! > > On Thu, Feb 16, 2017 at 3:08 PM, Urs Liska [via Lilypond] < > ml-node+s1069038n200207...@n5.nabble.com> wrote: > >> if I'm not mistaken (and a very recent post in the German forum >> http://www.lilypon

Re: Italic numbers for fingerings (feature request)

Am 17.02.2017 um 01:39 schrieb Simon Albrecht: > On 16.02.2017 23:27, tisimst wrote: >> On Thu, Feb 16, 2017 at 3:08 PM, Urs Liska wrote: >> >>> if I'm not mistaken (and a very recent post in the German forum >>> http://www.lilypondforum.de/index.php?t

Description of \\ construct in NR

Hi, I stumbled over something I consider an omission in the NR but before submitting a patch I'd like to clarify. http://lilypond.org/doc/v2.19/Documentation/notation/multiple-voices#-The-double-backslash-construct states that within the << \\ >> construct "temporary voices are created and then d

Re: Description of \\ construct in NR

Am 10.03.2017 um 17:37 schrieb Urs Liska: > Hi, > > I stumbled over something I consider an omission in the NR but before > submitting a patch I'd like to clarify. To comment: what I found is surely not recommendable syntax, even if it is very useful in my current case. So I&#

Re: Description of \\ construct in NR

Am 10. März 2017 20:47:26 MEZ schrieb Noeck : >Hi Urs, > >Am 10.03.2017 um 17:44 schrieb Urs Liska: >> |{ << { a'1~ } \\ { r2 f'2~ } >> % c''1 << { a'1 } \\ { f'2 r2 } >> >}| > >With the c''1 between the

<    1   2   3   4   >