Hello Dietmar,
> Abhängig von layout-set-staff-size gibt es Fehler in der
> Darstellung. [...]
Thanks for the report, which I've registered as
https://gitlab.com/lilypond/lilypond/-/issues/6732
Grüße aus Kufstein
Werner
> consisting of root and fifth". Thus the modifier column should
> contain only "nothing", [...]
>
> In addition, the output column for the last two entries should be
> modified to add the chord names: [...]
Thanks for the report, this is now
> Does the (bug?) report I sent get a ticket in
> https://gitlab.com/lilypond/lilypond/-/issues ?
Not yet, I was busy, sorry.
> I ran your suggested - "branch regression test":
> [@master, test-baseline, bytecode, @MyBranch, bytecode, check]
> Indeed lots of regtests failures.
>
> Another
> I'm surprised by your answer as with 2.24.3 there is a clear error
> and with the fix I proposed the output is usable (also far from
> being perfect).
Please define 'usable': I've tried to execute `musicxml2ly` from
version 2.24.3 on your input file, and I couldn't process the output
`.ly`
> Hello, I have a file for which `musicxml2ly` fails, because in line
> 824 variable `i2` is `None`. Changing line 824 from `if i1 > i2:`
> to `if not i2 or i1 > i2:` fixed my issue.
>
> I'm sorry, but I don't have time to investigate this issue more
> (just went in "don't think, fix it mode").
Hello Thomas,
sorry for the late reply.
> "\staffHighlight" does not work properly if there is a tempo marking
> and a whole bar rest in the first bar.
This is now registered in our bug database.
https://gitlab.com/lilypond/lilypond/-/issues/6730
Werner
> programming error: Improbable offset for stencil: -inf staff space
> [...]
> Also attached is a log and a suggested fix.
Thanks for the report. Your suggested fix essentially undoes commit
6ac913499ad6 (from 2013) and unfortunately it makes many regtests
results worse.
You might run `make
> Hello, I have a file for which `musicxml2ly` fails, because in line 824
> variable `i2` is `None`.
Which LilyPond version? And yes, please provide the input file for
testing (you might send it privately to me if necessary).
Werner
> On my Linux machine with 2.25.16, that file nondeterministically
> compiles, segfaults, or triggers a floating point exception. No time
> to investigate more, though.
Trevor, please open an issue!
Werner
> In order to figure out what this means, here's what I tried: [...]
You missed one important step, namely to look up the Learning Manual (LM):
https://lilypond.org/doc/v2.24/Documentation/learning/index.html
The index there already contains entries for `<< ... >>` and friends.
> The
> I would like to suggest to edit the appearance of the tremolo beams
> for notes with ledger lines. At the moment the stem is too short,
> so the tremolo beams are too close to the notehead. (Lilypond
> 2.25.13)
I suggest that you look up our bug database before reporting an issue.
A quick
> I am forwarding this bug report here:
>
> https://bugs.gentoo.org/913928
Thanks for the report! I've fixed the problem with the FontForge
version and with the non-portable `test` options.
https://gitlab.com/lilypond/lilypond/-/merge_requests/2301
Werner
>> In contrast to Jean, I have a different point of view. I think it
>> would be *very* valuable to have documentation strings of *all*
>> functions that might be useful in the long run
>
> Oh, that's also my point of view — it *would* be very valuable.
> Just... IMO not realistic. It already
> The naming of lilypond scheme functions can be really unintuitive
> sometimes. At the very least, the internals reference could use
> some major extensions making clear what the functions do and how,
> with examples. Via [1], it would have been impossible for me to
> understand what
> A suggestion for the Glossary in the documentation since I just
> learned that percent repeats are called "Faulenzer" in colloquial
> German after I had sought the word in vain in the Lilypond glossary
> and documentation. Or two suggestions, really. [...]
Thanks, this is now part of a merge
> I have a file for which convert-ly crashes. [...]
>
> It seems to be fixed by changing line 2152 of convertrules.py by
> putting the second argument as a raw string:
>
> ```
> s = re.sub(r'''((\\"|})\s*){''', r'\2 \\line {', s)
> ```
Thanks for the report!
> In the following example, when a note has a slur and a tie and
> hide-tied-accidental-after-break is enabled, the slur is incorrectly
> placed when another staff has many accidentals.
Thanks for the report. However, I don't think the problem is
especially related to accidentals; it's rather
>> Since I don't have experience with chord names I ask users who need
>> this feature to check whether it works as expected in general.
>
> It works like a charm in my source! Thanks for researching this.
:-)
https://gitlab.com/lilypond/lilypond/-/merge_requests/2281
Werner
>>> I remembered that you can add the Bar_engraver to ChordNames.
>>> Making them transparent so they do not visually interfere with the
>>> SpanBar, but they still take up space.
>>
>> Nice! This begs the question whether we have a real bug or 'just'
>> insufficient documentation...
>
> I was
> Oh, I think I found another option:
>
>
> \version "2.25.13"
>
> #(ly:set-option 'debug-skylines #t)
> \layout {
> \context { \Score
> \override NonMusicalPaperColumn.show-horizontal-skylines = ##t
> }
> \context { \ChordNames
> \consists "Bar_engraver"
> \override
>> Aaron, please file an issue, referring to this e-mail thread.
>
> First time creating an issue, so hopefully this is up to snuff.
Thanks a lot!
> Added: https://gitlab.com/lilypond/lilypond/-/issues/6703
>
> By the by, I do not appear to have permissions for setting labels,
> but I think
>> In some situations, chord names collide with the span bar of a
>> Grand or Piano Staff. Here is an example: [...]
>
> [...] Still sounds like a defect of some sort, as the default
> behavior should probably be handling things.
Aaron, please file an issue, referring to this e-mail thread.
> [...] I don't understand why the default is not "0". Space is rare
> and you often can't waste it, especially not in the title.
If you look at *any* score from a good publisher like Henle you can
see that there is plenty of whitespace around the music *and* the text
– for good reasons, since
> I don't know if this is a bug, but with the very latest Lilypond
> versions (2.25.+) the distance between the top margin and the title
> text does not match the value I specified, in this case 5
> millimeters. [...]
Have you looked into the 'changes' file from LilyPond? The first
entry for
> lilypond-book accepts --loglevel=WARN, but not --loglevel=WARNING.
>
> I think WARN is for lilypond, not lilypond-book (according to the
> documentation), so maybe just misdocumented?
Indeed, it is incorrectly documented; it should be 'WARN' everywhere.
Note that the `lilypond` binary is
> Snippets manual, MIDI chapter, Staff.midiInstrument list omits "guitar
> harmonics" between "distorted guitar" and "acoustic bass" (position
> 32).
Thanks for report; fixed in LSR #338, and the next import will fix it
in the LilyPond documentation.
Werner
Hello Chris,
sorry for the late reply.
> Issuing a \partCombineApart between two tied notes results in a
> warning that the tie is unterminated and omits the tie from the
> printed score. Printing the top part by itself creates the tie
> without issues.
>
> Omitting the tie from the top
> I personally lacked this information on the page "1.8.2 Formatting
> text – Selecting font and font size", mainly the fact that
> text-font-size is in pt (as defined in other sections).
https://gitlab.com/lilypond/lilypond/-/merge_requests/2258
Werner
> This is perhaps not the best place to discuss that, but thinking
> about it, I don't understand why text-font-size is dimensionless
> (when it actually does have a dimension). Wouldn't text-font-size =
> 12 \pt be more intuitive (and, at the same time, allowing also other
> units)?
This is
>> However, 2 * 3.86523438 = 7.73046876 != 7.73242188.
> I'm quite sure this is because of
>
> int pango_size = static_cast (
> std::lround (static_cast (requested_size) * PANGO_SCALE));
>
>
> in lily/font-select.cc, which we cannot really do anything about,
> because the Pango API
>> I think that postings by non-subscribers may go through moderation,
>> so they have a delay, sometimes considerable, before they appear
>> and require some manual interaction.
>
> My last reply showed up in the email archive
> (https://lists.gnu.org/r/bug-lilypond/2024-02/msg6.html)
>> The issue affects all of the other translations:
>> https://lilypond.org/doc/v2.25/Documentation/notation/long-repeats.ca.html
>> https://lilypond.org/doc/v2.25/Documentation/notation/long-repeats.de.html
>> https://lilypond.org/doc/v2.25/Documentation/notation/long-repeats.es.html
>>
> main.cc:641:23: warning: loop variable 'keyval' creates a copy from
> type 'const std::pair,
> std::__cxx11::basic_string >' [-Wrange-loop-construct]
> 641 | for (const auto keyval : init_scheme_variables_global)
> | ^~
> main.cc:641:23: note: use
> I've been wrestling with this mystery for some hours. I've finally
> found how to trigger it. The multimeasure rest causes the
> duplication of the rests in the display in previous measures. A
> non-multimeasure rest does not result in the weird duplication. If
> this is a known issue I
> Here you can find a
> preview:
> https://www.schott-music.com/de/preview/viewer/index/?idx=NTI0Mjcx=524271=0
>
> Voice tenor bar 9 to 10 into first alternative it is bound, were as
> from bar 9 to 13 (page 2) it isn't. It is officially published by
> SCHOTT Music, so I think its correct...
>> > The hyperlinks of both the acciaccatura and the appoggiatura
>> > slurs point to ly/grace-init.ly, which is kind of logical, but
>> > also confusing from a user perspective.
>>
>> I think this a bug, so please open an issue.
>
> I apologise.
Why?
Werner
> I would like to hear your opinions on this one:
>
> snip
> \version "2.25.10"
>
> { \acciaccatura { c'8 } d'4 }
> { \appoggiatura { c'8 } d'4 }
>
>
> The hyperlinks of both the acciaccatura and the appoggiatura slurs
> point to ly/grace-init.ly, which is
> There might be a small misunderstanding in "When a note is tied over
> into two or more alternative endings [...]" this is also needed if
> the tie goes only into the first alternative as well [...]
>From a logical point of view you either have no tie, or you have a tie
that goes into *all*
> I'm in the middle of a clean installation on a mac with Sonoma
> 14.1.2 with an M2 chip. The instructions have been incomplete and
> have varied significantly from the screenshots on the website.
Please give more details. AFAIK, none of the developers are (mainly)
working on a Mac, and I'm
> Also, I'm pretty sure that the intent of FcChar8* in Fontconfig is
> to represent UTF-8 so this is probably worthy of a bug report to the
> Fontconfig people?
Indeed. To do so it would be helpful to check the output of `fc-list`
(ideally with proper patterns to make the result more similar
> I can confirm that replacing
>
> scm_write_line (ly_string2scm (str), port);
>
> with
>
> scm_c_write (port, str.c_str (), str.length ());
>
> fixes the issue on my end. I’d be happy to make a merge request for
> this.
I've updated
https://gitlab.com/lilypond/lilypond/-/merge_requests/2231
> Thanks for making the merge request. Unfortunately, it didn’t fix
> the issue, although it really seems like it should have.
Thanks for the testing it and the detailed analysis. I've changed the
status of the Merge Request to 'draft'.
> I’m starting to think this may be a bug in Guile.
Can
> On macOS Ventura v13.6.3 (and almost certainly other versions), the
> string produced when using -dshow-available-fonts need not be
> encoded as UTF-8.
Thanks, should be fixed with this MR:
https://gitlab.com/lilypond/lilypond/-/merge_requests/2231
Out of interest: Which font shows this
[Pressing 'reply-all' in my e-mail program converted
'bug-lilypond@gnu.org' into a strange address, thus resending.]
>In dense chord clusters, ties sometimes fail to keep at least one
>staff space away from each other.
>
> \version "2.24.2"
> \relative {
> \override
> \language "deutsch"
>
> \new NoteNames { b1 }
Already reported as issue #6305, AFAICS.
https://gitlab.com/lilypond/lilypond/-/issues/6305
Werner
> here is example of this bug: [...]
>
> The problem occurs only if the \showStaffSwitch command is found.
Yes, this is a bug. Thanks for the report; filed as
https://gitlab.com/lilypond/lilypond/-/issues/6684
Werner
> I found bug in arrangement duration dots in a specific case: [...]
There is no bug. Using `\hideNotes` only makes note heads (and dots)
invisible, but they are still positioned. You should rather try
something like the following.
```tex
\version "2.24.3"
\new PianoStaff <<
\new Staff =
> I've noticed at times lilypond produces notes that are not exactly on or
> between the staff lines. I boiled it down to the attached minimum
> example, which shows a D flat that looks floated up about half way to E
> flat. However, if you comment out the header subtitle, the note lands
>
> For example on https://lilypond.org/tiny-examples.html you get the
> following page, with the start of the text not readable.
It's actually
https://lilypond.org/bug-reports.html
Thanks for the report. I'm quite sure that this is an artifact of
changing from the ancient `texi2html`
> When I compile a lilypond file I get the following error: [...]
This is due to an upgrade of homebrew to ghostscript 10.02.1, which
removed a function used by LilyPond.
https://gitlab.com/lilypond/lilypond/-/issues/6675
We already have a fix, but until this is out I suggest to use the
> This bug was not observed with Ghostscript 10.02.0.
Thanks, filed as
https://gitlab.com/lilypond/lilypond/-/issues/6675
Werner
> Many thanks. The patch works fine.
Thanks for testing. This is now
https://gitlab.com/lilypond/lilypond/-/merge_requests/2093
Werner
> The attached snippet provides the basic layout of the bassoon
> diagram.
Thanks. Note that this can be done easier on the command line with
```
lilypond -e="(print-keys-verbose 'bassoon (current-output-port))" > bassoon-keys
```
> For one (left index finger) there must be more
> For the woodwind diagram of the bassoon the half open hole is
> missing for one (one1h). You ay refer
> to https://davidawells.com/resources/fingering-charts/.
Please be more specific and show/describe *exactly* what is missing or
not working, ideally together with a (possibly non-working)
> And no, this is pretty far from perfect and could also benefit from
> being made clear in the NR.
What do you want to have where exactly?
Werner
> So Pango is apparently requesting a font with colored glyphs from
> Fontconfig...
A bug?
Werner
> Following your suggestion, Werner, I tried the test file with the
> cairo back end, and it worked as expected.
Great, please send me the created PDF for further analysis – just to
be sure :-)
> I then deleted the Noto Color Emoji font (synaptic also deleted
> texlive fonts extra links), and
Colin,
>> All this comes about as I'm thinking of getting back to
>> some documentation work, and wanted to compile docs locally. I'll
>> still keep that goal in mind.
>>
>> If you can still reproduce the problem after this cleaning, could
>> you run
>>
>> ```
>> FC_DEBUG=2025
> ran make successfully, got carried away and may have shot myself in
> the foot by running sudo make install.
You should actually do
```
make bytecode
sudo make install-bytecode
```
Without installing the Guile bytecode, LilyPond is slooow.
Werner
> Thanks for reporting. Werner, can you take a look please? It appears
> that 4494a12ec8d3408981b26f4dc4040e2f985da06f breaks `convert-ly -`
> to read stdin (on Windows).
https://gitlab.com/lilypond/lilypond/-/merge_requests/1948
Werner
>> However none of the staff types dan suggested will do what I could
>> previously do. Gregorian divisiones not supported on modern staffs
>> is a reasonable closure for this as a bug however I've previously
>> been able to use the gregorian divisions on a 'normal staff' so
>> from my pov this
>> Thank you so much for the speedy and clear response. I didn't
>> consider that it was because the notehead styles were different!
>> Glad for the understanding.
>
> Maybe there'd be a way for the implementation to check for the same
> glyph instead? For styles with considerable overlap of
Hello John,
> Is this a fix of a magnitude that someone with less technical
> expertise could accomplish? I would volunteer to prepare the MR, if
> it would help more than get in your way.
Sorry, I saw your e-mail too late – I have already pushed an MR :-)
>> Please enclose the first argument of `@defun` with @code{...}, like
>> this:
>>
>>@defun @code{foo-bar::@/baz} bar? bar bar
>
> Thanks for the fix proposal; whom are you talking to with "Please"?
You, of course :-)
I will prepare a MR to fix that.
Werner
> Looks like this comes from the use of "@/", which has been
> introduced with
>
> commit 1f3a6cdc25ab978589fb01894dce34d7d6c1e972
> Author: Werner Lemberg
> Date: Sun Aug 8 15:51:29 2021 +0200
>
> doc: Avoid overlong index entries in generated docume
> "The collection of staves (staff), two or more, as used for writing
> down keyboard, chamber, choral, or orchestral music; a section of
> the score spanning the width of a single page."
>
> This seems to imply the word has two meanings,
Yes.
> but I think in the context of Lilypond, it has
Hello Tom,
> I wonder if the "system" entry in the glossary might be enhanced by
> including the lilypond-specific definition. [...]
>
> Also, there is no entry for "spanner" [...]
thanks for the report; I will take care of this soon.
Werner
Hello Kees,
> Sori and Koron look OK.
Good to hear.
> persian.ly (written by me) was updated on the mailinglist a few
> months ago so use different fonts. Further updates to make it work
> with whatever you guys are doing now should be easy but not
> something I know how to do.
Do you have
12½ years earlier I wrote:
>> Persian accidentals (korn, sori) don't look very nice. [...]
>
> Thanks. I've added your report to the bug database (issue #738).
Now something happened :-) Please have a look at
https://gitlab.com/lilypond/lilypond/-/merge_requests/1047
Werner
>> After having opened a few GitLab issues in response to bug reports
>> on bug-lilypond, I find James extraordinarily patient for having
>> done this over the years. However, I don't get the value in this
>> system compared to letting people creating issues on GitLab
>> directly. When we
>> Ah, that's kind of what I was fearing. Obviously (at least I hope
>> it was obvious; maybe it wasn't) I was trying to format an entire
>> group of lyrics, and having to markup each word was both tedious
>> and ugly. In my use case, it looks like \override
>> LyricText.font-size and
>> I've looked up the cairo bug tracker but couldn't find something
>> related to copy-and-paste of CID-keyed fonts. Masamichi-san, could
>> you submit an issue there so that this gets fixed eventually? I
>> guess this would be beneficial for other projects, too.
>
> In my experiment, Cairo
>>> The problem does not appear if the cairo backend is used, see
>>> https://gitlab.com/lilypond/lilypond/-/merge_requests/853.
>>
>> This is good news!
>
> When copying and pasting from a PDF generated using cairo backend,
> some characters turned into similar but different characters. The
>
>> When using certain fonts (in my case, Noto CJK, both pan-CJK and
>> subset versions), the output looks right but when copied from the
>> generated PDF file, everything becomes garbage. [...]
>
> The problem does not appear if the cairo backend is used, see
>
>> AFAICS, to make copy and paste work for CID fonts it is necessary
>> to add a ToUnicode map. We don't do that currently. [This is
>> probably worth an entry in our issues database.]
This is now issue #6162.
https://gitlab.com/lilypond/lilypond/-/issues/6162
Werner
> When using certain fonts (in my case, Noto CJK, both pan-CJK and
> subset versions), the output looks right but when copied from the
> generated PDF file, everything becomes garbage. [...]
Confirmed.
> It seems to be all about CID. Maybe related to Issue #6058?
Yes and no. The fix for
> Processing `../repeat-volta.ly'
> Parsing...
> Interpreting music...[8]
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...
> fatal error: cannot find SVG font #f
The font problem is issue #3809: the volta number is
[Changing your e-mail address to 'knupero', which is your preferred
one without problems, IIRC]
> [...] here's one hint for the volta-spec-once.ly problem:
> Roboto-Regular is (on my current system) a font without a glyph
> table.
You mean the font doesn't have a 'glyf' table, right? Then you
>> I don't think LilyPond guarantees a particular order of events
>> occuring at the same moment, but I agree that wrapping them should
>> not change the order. An issue has been created to track this
>
> But the regression test script-stack-order.ly is quite explicit
> about the order being
>> I recently downloaded Lilypond v2.23, and with it the big
>> documentation manual, web.pdf.
>
> I think web.pdf is not really a priority with respect to formatting,
> as the name suggests you should just view the web page at
> lilypond.org.
+1
Werner
> Inkscape works very well to convert PDFs to SVG, but if we expect
> our users to do that, then it's debatable whether we should have an
> SVG backend at all.
I agree. However, my SVG knowledge is very small; this means I'm not
qualified to make any decisions.
> (I mean this seriously: the
> How about hosting the fonts on www.lilypond.org and referencing them
> in the @font-face definition?
I think this is not a good idea.
* LilyPond fonts change from version to version, quite often in a
backwards-incompatible way. Hosting them for SVG access would
enforce us to completely
>> IMHO, this is as good (or as bad) as a default as 'serif'. If you
>> want SVG images to be similar to, say, PDF output, you have
>>
>>* to exactly specify which font you want to use for text, and
>>* to convert glyphs to paths, for example, by postprocessing
>> LilyPond's output
> But what is the difference between _\markup and -\markup?
Alas, this is missing in the notation index.[*]
In general, if you use `-` before an object (attached to a note),
LilyPond uses a vertical default position. If you use `^` or `_`
instead, the object's vertical position is forced to be
> With 2.18, I see this instead:
>
> font-family="Century Schoolbook L"
> font-weight="bold"
> font-size="6.9848"
> text-anchor="start"
> fill="currentColor">
>
>
>
IMHO, this is as good (or as bad) as a default as 'serif'. If you
want SVG images to be
> I had seen the "-" operator before but could not find it in
> LilyPond's docs.
If you look into the index, you can find it in the notation reference
(NR):
http://lilypond.org/doc/v2.23/Documentation/notation/expressive-marks-attached-to-notes#index-_002d
Werner
> Probable reason: The fullname property (Vorzeigename) of the fonts
> is set to Untitled-1, it should be the same as the name property:
>
> The following two changes fixed the problem for me: [...]
Thanks for the patch, which is now registered as a merge request.
>> `convert-ly` is a python script. For Windows, rename the file
>>
>> c:\Program Files (x86)\usr\bin\convert-ly
>>
>> to
>>
>> convert-ly.py
>>
>> Then Windows will know to run the python interpreter on this file.
>>
>> NOTE: This script works as is on Linux because the first line of the
> `convert-ly` is a python script. For Windows, rename the file
>
> c:\Program Files (x86)\usr\bin\convert-ly
>
> to
>
> convert-ly.py
>
> Then Windows will know to run the python interpreter on this file.
>
> NOTE: This script works as is on Linux because the first line of the
> script
>> I was engraving a piece of chant in modern notation recently, and
>> discovered that none of the custodes will draw a ledger for middle
>> C (C4) or A5, notes beyond the 5-line staff. These notes do occur
>> in chant and polyphony. [...]
>
> Perhaps this: [...]
>
> The above hack does
>> Does anyone disagree that the above would ideally be treated as if
>> it were this?
>>
>> ```
>> { \grace { c8 d8 } e4 }
>> ```
>
> \grace does not just introduce grace timing. It also does things
> like \stemUp and size reduction. So what should happen with
>
> { \grace { \stemDown c8 } {
> So, let's just choose the LPPL and there are no issues.
Sounds like a sensible idea. It seems that the TeX Gyre font are no
longer under development or maintenance; the last release is from
2009. The recent URW fonts are from 2016.
On the other hand, a switch to a new default is not urgent,
> In any case, I'm subscribed so I'll cross-post and CC James so
> that the patch (which looks correct to me) is not lost.
I've just applied it to staging.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
> @ruser{Engraving ties manually} in Learning Manual is incorrect, as
> such a node doesn't exist.
Fixed in staging, thanks for the report.
> Perhaps there's a way to use a index link?
texinfo's @anchor command is what you are searching for :-)
Werner
> Hi! How is this going? Do you think the Python 3 conversion will be
> done by mid-November, or should I file an exception to prevent
> lilypond's removal from Fedora?
Please file an exception. Mid-November certainly doesn't work for us.
Werner
>> I'll send them to you privately.
>
> Now fixed.
Thanks a lot!
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
> There are actually 2 files needed - the standard one and the -small
> one - and I don't remember how they're created - I don't have my
> "lilypond" PC on now, but perhaps make doc might make them?
>
> See https://github.com/gperciva/lilypond-extra/tree/master/ly-examples
>
> If you can get the
>> It's a long time since I did this, but I think to update the
>> example pictures, you have to create updated versions locally, push
>> them to the lilypond-extra repo and then pull those on the website
>> and copy them to the web directory.
>
> OK. However, my main question is why this
>> How comes that the HTML code from
>>
>> http://lilypond.org/examples.html
>>
>> is sensitive to recent changes in `staging' or `master' without
>> updating the images? For example, the Schenker graph image is
>> still the one coming with 2.19.83.
>>
>> This definitely looks like a bug.
>
>
> the example on http://lilypond.org/examples.html#Customized-Output is
> missing:
> http://lilypond.org/ly-examples/stockhausen-klavierstueckII.png is not
> found.
Hmm, weird. I've renamed it in a recent commit for orthogonality with
other examples. The old name is
1 - 100 of 506 matches
Mail list logo
