Re: Issue 884 in lilypond: pageBreak resets page-count property
Comment #20 on issue 884 by PhilEHolmes: pageBreak resets page-count property http://code.google.com/p/lilypond/issues/detail?id=884 I've checked this with the versions of Lily that I have, and the behaviour is incorrect from 13.31 onwards. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: PDF hyperlinks
Am Montag, 27. Dezember 2010, um 01:34:47 schrieb Dan Eble: The only mention I can find of PDF hyperlinks is for the point-and-click feature. LilyPond also supports URL hyperlinks with the \with-url command. They are written out to the intermediate .ps file as pdfmark and correctly converted to PDF. I would like to create a PDF with page references (toc/index/etc.) that jump to the page when clicked. Internal links (to a particular position marked by a \label) are not supported so far. Is that something that can be done in scheme? If so, in which file and functions should I begin? I don't think it can be done in Scheme alone. I don't think it would be too hard, though. Basically, it can be done with pdfmark, too. For the specification of the pdfmark Postscript extension see http://partners.adobe.com/public/developer/en/acrobat/sdk/pdf/pdf_creation_apis_and_specs/pdfmarkReference.pdf What needs to be done is: 1) In the Postscript backend (scm/famework-ps.scm or scm/output-ps.scm) written in Scheme: -) Write out each \label as a named destination to the .ps file. The code is [ /Dest /nameOfYourLabel /DEST pdfmark and needs to be inserted on the page where the label was placed. -) For the link, you also need to insert [ /Rect [70 650 210 675] /Dest /nameOfYourLabel /Subtype /Link /ANN pdfmark where the [70 650 210 675] specify the exact rectangle for the link. 2) Of course, the non-trivial part of all this is how to get the information about label and link to the ps backend... I don't have a clear idea how to propagate that information from the markup interpretation to the backend. It might be able to do this in Scheme, but maybe also some C++ is required. From a quick look at the code, all labels are collected in the label-page- table variable of the paper object, but I don't know if this is available in the backend... In any case, this is a very good enhancement request, so bug squad, please open a bug report (enhancement request) for this. Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Writing metadata to the PDF file
The request for PDF hyperlinks of \page-ref and \label reminded me that it might be a nice enhancement to write out some of the \header fields as DOCINFO fields (i.e. metadata) to the PDF file. The advantage would be that PDF readers would display the title (instead of the filename) in the window title, and the document information would contain more information about the author, title, etc. All that needs to be done is to insert a DOCINFO pdfmark into the Postscript and gs will take care of it: [ /Author string /Title string /Subject string /Keywords string /DOCINFO pdfmark The DOCINFO pdfmark Postscript extension is documented by Adobe on page 28 of http://partners.adobe.com/public/developer/en/acrobat/sdk/pdf/pdf_creation_apis_and_specs/pdfmarkReference.pdf Now, I'm looking at the ps backend, but I don't know how to get access to the global header object from the write-preamble function in scm/framework-ps.scm. Any idea how to obtain the global header object so I can extract things like title or composer? Thanks, Reinhold PS: Bug squad, can you please file this as an enhancement request, so that it doesn't get lost? -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: including gregorian.ly breaks lyrics alignment in melismas
2010/12/27 Janek Warchoł lemniskata.bernoull...@gmail.com:
Hi,
Search for gregorian in tracker didn't show any results like this,
so i report:
including gregorian.ly breaks horizontal spacing when there are lyrics.
Example:
\include gregorian.ly
\new Voice = foobar { f'( a' g' f') }
\new Lyrics \lyricsto foobar \lyricmode { lalah }
It breaks also with \addlyrics:
\include gregorian.ly
\new Voice = foobar { f'( a' g' f') }
\addlyrics { lalah }
Hi!
I compiled with 2.13.43 and I did not see an issue here.
The result is exactly the same if we comment \include gregorian.ly ,
so this tends to mean if there is an issue it is not due to this.
I suppose you consider an issue the fact that the syllable is
left-aligned instead of horizontally centered below the first note.
This is due to the slur and is normal behaviour AFAIK.
The slur is creating a melismata and LilyPond tries to horizontally
center the syllable below the whole slurred passage. But it needs to
stay below the first note also (because that's where the syllable begins),
so it is left-aligned.
Seems normal to me, so not an issue here IMHO.
Cheers,
Xavier
--
Xavier Scheuer x.sche...@gmail.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1463 in lilypond: Writing metadata to the PDF file
Status: Accepted Owner: Labels: Type-Enhancement Priority-Medium New issue 1463 by brownian.box: Writing metadata to the PDF file http://code.google.com/p/lilypond/issues/detail?id=1463 Reported by Reinhold Kainhofer, http://lists.gnu.org/archive/html/bug-lilypond/2010-12/msg00382.html : %-8--- The request for PDF hyperlinks of \page-ref and \label reminded me that it might be a nice enhancement to write out some of the \header fields as DOCINFO fields (i.e. metadata) to the PDF file. The advantage would be that PDF readers would display the title (instead of the filename) in the window title, and the document information would contain more information about the author, title, etc. All that needs to be done is to insert a DOCINFO pdfmark into the Postscript and gs will take care of it: [ /Author string /Title string /Subject string /Keywords string /DOCINFO pdfmark The DOCINFO pdfmark Postscript extension is documented by Adobe on page 28 of http://partners.adobe.com/public/developer/en/acrobat/sdk/pdf/pdf_creation_apis_and_specs/pdfmarkReference.pdf Now, I'm looking at the ps backend, but I don't know how to get access to the global header object from the write-preamble function in scm/framework-ps.scm. Any idea how to obtain the global header object so I can extract things like title or composer? Thanks, Reinhold PS: Bug squad, can you please file this as an enhancement request, so that it doesn't get lost? %-8--- ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Writing metadata to the PDF file
On Mon 27 Dec 2010, 15:40 Reinhold Kainhofer wrote: The request for PDF hyperlinks of \page-ref and \label reminded me that it might be a nice enhancement to write out some of the \header fields as DOCINFO fields (i.e. metadata) to the PDF file. The advantage would be that PDF readers would display the title (instead of the filename) in the window title, and the document information would contain more information about the author, title, etc. All that needs to be done is to insert a DOCINFO pdfmark into the Postscript and gs will take care of it: [ /Author string /Title string /Subject string /Keywords string /DOCINFO pdfmark Added as 1463: http://code.google.com/p/lilypond/issues/detail?id=1463 Thank you. -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: including gregorian.ly breaks lyrics alignment in melismas
2010/12/27 Xavier Scheuer x.sche...@gmail.com:
2010/12/27 Janek Warchoł lemniskata.bernoull...@gmail.com:
including gregorian.ly breaks horizontal spacing when there are lyrics.
Example:
\include gregorian.ly
\new Voice = foobar { f'( a' g' f') }
\new Lyrics \lyricsto foobar \lyricmode { lalah }
Hi!
I compiled with 2.13.43 and I did not see an issue here.
The result is exactly the same if we comment \include gregorian.ly ,
so this tends to mean if there is an issue it is not due to this.
I suppose you consider an issue the fact that the syllable is
left-aligned instead of horizontally centered below the first note.
This is due to the slur and is normal behaviour AFAIK.
The slur is creating a melismata and LilyPond tries to horizontally
center the syllable below the whole slurred passage. But it needs to
stay below the first note also (because that's where the syllable begins),
so it is left-aligned.
Seems normal to me, so not an issue here IMHO.
This surely sounds like normal bahaviour! Looks like i'm getting
different output than you do. I attach my output.
(in addition to strange alignment, including gregorian.ly causes the
indent to disappear on my computer)...
I'm using LilyPond 2.13.43 (i'll install .44 right now) on Windows 7
Professional PC.
cheers,
Janek
attachment: with gregorian.pngattachment: without gregorian.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: PDF hyperlinks
Am Montag, 27. Dezember 2010, um 15:34:05 schrieb Reinhold Kainhofer: 2) Of course, the non-trivial part of all this is how to get the information about label and link to the ps backend... I don't have a clear idea how to propagate that information from the markup interpretation to the backend. It might be able to do this in Scheme, but maybe also some C++ is required. From a quick look at the code, all labels are collected in the label-page- table variable of the paper object, but I don't know if this is available in the backend... I forgot to add that the link itself would then be implemented completely similar to \with-url. So, the only non-trivial thing is really how to get the information about where to place the label (as a DEST pdfmark) into the ps backend. Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: including gregorian.ly breaks lyrics alignment in melismas
2010/12/27 Janek Warchoł lemniskata.bernoull...@gmail.com: I'm using LilyPond 2.13.43 (i'll install .44 right now) Installed. It breaks exactly the same with 2.13.44 :( Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: including gregorian.ly breaks lyrics alignment in melismas
2010/12/27 Janek Warchoł lemniskata.bernoull...@gmail.com:
This surely sounds like normal bahaviour! Looks like i'm getting
different output than you do. I attach my output.
(in addition to strange alignment, including gregorian.ly causes the
indent to disappear on my computer)...
I'm using LilyPond 2.13.43 (i'll install .44 right now) on Windows 7
Professional PC.
Right!
I was focusing on lyrics alignment, not indent.
So apparently \include gregorian.ly removes the indent.
I'm not used to ancient notation but I suppose it is normal behaviour
for that kind of notation.
I have looked at ly/gregorian.ly and it _does_ contain
\layout {
indent = 0.0
(line 223)
so it is intentional.
If you want default (i.e. modern notation) behaviour simply add
\layout {
indent = 15\mm
}
*after* \include gregorian.ly
So not a bug apparently.
Cheers,
Xavier
--
Xavier Scheuer x.sche...@gmail.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: including gregorian.ly breaks lyrics alignment in melismas
2010/12/27 Xavier Scheuer x.sche...@gmail.com:
2010/12/27 Janek Warchoł lemniskata.bernoull...@gmail.com:
This surely sounds like normal bahaviour! Looks like i'm getting
different output than you do. I attach my output.
(in addition to strange alignment, including gregorian.ly causes the
indent to disappear on my computer)...
I'm using LilyPond 2.13.43 (i'll install .44 right now) on Windows 7
Professional PC.
Right!
I was focusing on lyrics alignment, not indent.
So apparently \include gregorian.ly removes the indent.
I'm not used to ancient notation but I suppose it is normal behaviour
for that kind of notation.
I have looked at ly/gregorian.ly and it _does_ contain
\layout {
indent = 0.0
(line 223)
so it is intentional.
Ok, so there is no problem with indent, but the notes *are* still
aligned wrongly! Look at the with gregorian attachment - the gap
after first note is too big (i marked it in red).
cheers,
Janek
attachment: with gregorian.pngattachment: without gregorian.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Segfault with multimeasure rests and metronome markings
We've run into a segfault in all versions of LilyPond after 2.13.32,
including 2.13.44. I've narrowed it down to occur when a tempo marking
is placed over a multimeasure rest when the Metronome_mark_engraver has
been added to the staff containing the rest:
\version 2.13.44
% works in 2.13.32 and prior
\score {
\new Staff {
\tempo 4=150
R1 |
}
\layout {
\context {
\Score
\remove Metronome_mark_engraver
\remove Staff_collecting_engraver
}
\context {
\Staff
\consists Metronome_mark_engraver
\consists Staff_collecting_engraver
}
}
}
Console output:
Processing `RestSegfault.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects.../home/csnyder/bin/ly-choose: line 29:
7328 Segmentation fault $ly $*
LilyPond [RestSegfault.ly] exited with return code 139.
(ly-choose is my own wrapper script to run the version of LilyPond
specified in the \version parameter; the segfault still occurs when this
script is not used)
I'm running Kubuntu 10.10 64-bit using the official LilyPond binaries.
Thanks,
Chris
--
Chris Snyder
Adoro Music Publishing
(616) 828-4436
www.adoromusicpub.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR 3.2.3 Reference to page numbers - buggy? (issue 884)
Le 27/12/2010 05:09, Colin Campbell disait :
On Sun, 2010-12-26 at 18:09 +0100, Jean-Charles Malahieude wrote:
Something has become buggy since version 2.12.3 and I don't know how to debug
it:
\book {
\label #'firstScore %% page 1
\score {
{
c'1
\pageBreak
\mark A \label #'markA %% page 2
c'1 \label #'markTheEnd %% page 2
}
}
\markup { The first score begins on page \page-ref #'firstScore 0 ? }
%% prints page 1
\markup { Mark A is on page \page-ref #'markA 0 ? }
%% prints page 1
\markup { Finish line on page \page-ref #'markTheEnd 0 ? }
%% prints page 2
}
This looks like issue 884 pageBreak resets PageCount property, which
had been marked fixed in 2.13.35. I've tested it against 2.12.3 and
2.13.44 and confirmed the regression, so I re-opened issue 884.
May I guess that it is due to \mark falling before the first note event
is generated?
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: including gregorian.ly breaks lyrics alignment in melismas
Janek Warchoł wrote Monday, December 27, 2010 4:45 PM Ok, so there is no problem with indent, but the notes *are* still aligned wrongly! Look at the with gregorian attachment - the gap after first note is too big (i marked it in red). I know next to nothing about ancient notation, but whoever wrote gregorian.ly clearly intended this behaviour as the file contains the override \override SpacingSpanner #'packed-spacing = ##t on line 258, which requests notes to be packed as tightly as possible. This is presumably to enable the usual packed spacing of Gregorian ligatures when the other facilities in gregorian.ly are used, so it is not a bug. If you want to use normal spacing simply revert this setting: \revert Score.SpacingSpanner #'packed-spacing Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1335 in lilypond: bad shapes of scripts.varsegno, accordion.push, and noteheads.s0re
Updates: Status: Fixed Labels: fixed_2_13_37 Comment #6 on issue 1335 by Carl.D.Sorensen: bad shapes of scripts.varsegno, accordion.push, and noteheads.s0re http://code.google.com/p/lilypond/issues/detail?id=1335 SHape notes are fixed with commit 76a8b5e1b13c26d0d4f09ee74bbc43f5b1392e7a ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 884 in lilypond: pageBreak resets page-count property
Updates: Owner: --- Labels: -Priority-High Priority-Critical Comment #21 on issue 884 by percival.music.ca: pageBreak resets page-count property http://code.google.com/p/lilypond/issues/detail?id=884 Why downgrade the priority? if it was Critical before, it's Critical now. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1438 in lilypond: Change to figured-bass-extenders-markup.ly regtest
Updates: Labels: -Priority-High Priority-Critical Comment #1 on issue 1438 by percival.music.ca: Change to figured-bass-extenders-markup.ly regtest http://code.google.com/p/lilypond/issues/detail?id=1438 I'm not convinced that it's actually a problem, but if it is, it'd be Critical. (if this is intended behavior, then we should clarify that and mark the report invalid) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1318 in lilypond: midi2ly broken on Mac OS X
Updates: Labels: -Type-Defect -Priority-High Type-Build Priority-Critical Comment #1 on issue 1318 by percival.music.ca: midi2ly broken on Mac OS X http://code.google.com/p/lilypond/issues/detail?id=1318 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1098 in lilypond: Unable to print long scores
Updates: Status: Invalid Comment #8 on issue 1098 by percival.music.ca: Unable to print long scores http://code.google.com/p/lilypond/issues/detail?id=1098 I'm not seeing any examples here, so there's nothing we can investigate. If you construct an example, feel free to open a new issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1442 in lilypond: staff-staff padding all appears after the last nonstaff
Comment #3 on issue 1442 by k-ohara5...@oco.net: staff-staff padding all
appears after the last nonstaff
http://code.google.com/p/lilypond/issues/detail?id=1442
A closely related symptom that could be helpful for debugging, even though
it is not the same issue.
If there are several Dynamics lines below a staff, and if the line(s)
closest to the staff are empty for a whole system, then the first non-empty
Dynamics is placed to allow *twice* the requested minimum-distance from the
staff.
\version 2.13.43
\score {
\new Staff { s1*3 }
\new Dynamics { s1\mp \break s1 \break s1\mp }
\new Dynamics { s1\sustainOn s\sustainOn s\sustainOn }
%{%}
% Non-essential override to show the extra space varies with
% minimum-distance (and indepenent of padding)
\layout { \context { \Dynamics
\override VerticalAxisGroup #'nonstaff-relatedstaff-spacing
#'minimum-distance = #5
}}}
Fortunately, default Dynamics have zero minimum-distance to their parent
staff. The analogous situation with Lyrics (which has a minimum-distance
by default) does not show the effect.
(The only way I could see the double-distance with Lyrics was to put them
between Piano staves and leave in place the Keep_alive_together_engraver.)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1381 in lilypond: Add documentation for text dynamic spanners like \cresc
Comment #2 on issue 1381 by k-ohara5...@oco.net: Add documentation for text dynamic spanners like \cresc http://code.google.com/p/lilypond/issues/detail?id=1381 fixed 2.13.44 http://lilypond.org/doc/v2.13/Documentation/notation/expressive-marks-attached-to-notes#dynamics ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1381 in lilypond: Add documentation for text dynamic spanners like \cresc
Updates: Status: Fixed Labels: fixed_2_13_44 Comment #3 on issue 1381 by pnorcks: Add documentation for text dynamic spanners like \cresc http://code.google.com/p/lilypond/issues/detail?id=1381 Thanks, Keith. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
