Have a look at the image in this section:
http://www.lilypond.org/doc/v2.17/Documentation/notation/displaying-staves#nested-staff-groups
Whatever the snippet tries to show, it is cut off.
Werner
___
lilypond-devel mailing list
I'm having trouble with make, I've never had this kind of problem. Maybe
some system update broke something?
$ make
[...]
/home/fede/lilypond-git/scripts/build/out/run-and-check LANG= makeinfo
--enable-encoding --error-limit=0 -I /home/fede/lilypond-git/Documentation
-I. -I./out
2013/5/28 Werner LEMBERG w...@gnu.org
Have a look at the image in this section:
http://www.lilypond.org/doc/v2.17/Documentation/notation/displaying-staves#nested-staff-groups
Whatever the snippet tries to show, it is cut off.
it was correct in v2.16:
Hello,
*Countdown – May 31 – 06:00 GMT* *
* *
* *
* *
*
3380http://code.google.com/p/lilypond/issues/detail?id=3380q=label%3APatch-reviewsort=patchcolspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified
Enhancement
David Kastrup review Patch: Fix
I'm having trouble with make, I've never had this kind of problem.
Maybe some system update broke something?
`Broken' is the wrong word, but ...
I'm on debian sid texinfo v5.1
... don't use version 5.1 but stay with version 4.13!
All the error and warning messages you are getting deserve
Werner LEMBERG w...@gnu.org writes:
I'm having trouble with make, I've never had this kind of problem.
Maybe some system update broke something?
`Broken' is the wrong word, but ...
I'm on debian sid texinfo v5.1
... don't use version 5.1 but stay with version 4.13!
All the error and
All the error and warning messages you are getting deserve fixes,
but given that 5.1 is about 20 or more times slower than 4.13,
there's currently no gain to update.
[...] for a normal make which builds documentation without images,
the added time at the end is already a slight nuisance
- Original Message -
From: Werner LEMBERG w...@gnu.org
To: lilypond-devel@gnu.org
Sent: Tuesday, May 28, 2013 8:01 AM
Subject: ugly left-side cropping in documentation
Have a look at the image in this section:
Jan Nieuwenhuizen jann...@gnu.org writes:
18:41:52 janneke@peder:~/vc/lilypond
$ ps2pdf toc.preview.eps
GPL Ghostscript 9.07: ERROR: A pdfmark destination page 4 points
beyond the last page 1.
Oh. _Interesting_. Maybe the error message is formatted into
insufficient or
Werner LEMBERG w...@gnu.org writes:
All the error and warning messages you are getting deserve fixes,
but given that 5.1 is about 20 or more times slower than 4.13,
there's currently no gain to update.
[...] for a normal make which builds documentation without images,
the added time at the
http://lilypond.org/doc/v2.17/Documentation/notation/modifying-single-staves#staff-symbol
This snippet, taken from the documentation (section `Modifying single
staves'):
\new Staff \with {
\override StaffSymbol.ledger-extra = #4
}
\relative c'' { f'4 a, d, f, }
produces the attached
As distributions move on to Texinfo 5, we are going to get a rather
awkward transitioning problem.
I fear so. On the other hand, the warning messages are reasonable (at
least most of the time :-), and fixing them should be straightforward.
A completely different issue is our hand-crafted
Phil Holmes m...@philholmes.net writes:
- Original Message -
From: Werner LEMBERG w...@gnu.org
To: lilypond-devel@gnu.org
Sent: Tuesday, May 28, 2013 8:01 AM
Subject: ugly left-side cropping in documentation
Have a look at the image in this section:
Have a look at the third example in this section
http://lilypond.org/doc/v2.17/Documentation/notation/modifying-single-staves#ossia-staves
and note how the bar number is positioned incorrectly. Is this an
incomplete example or a bug?
Werner
Have a look at the third example in this section
http://lilypond.org/doc/v2.17/Documentation/notation/modifying-single-staves#ossia-staves
and note how the bar number is positioned incorrectly. Is this an
incomplete example or a bug?
BTW, I think it's the latter: if a staff is not
Is this an incomplete example or a bug?
Well, an incomplete example is a bug.
:-)
That being said, the bar number engraver uses
ly:side_position_interface::move-to-extremal-staff for its vertical
positioning. The same would likely be done for marks. The question
is what we should be
2013/5/28 Werner LEMBERG w...@gnu.org
As distributions move on to Texinfo 5, we are going to get a rather
awkward transitioning problem.
I fear so. On the other hand, the warning messages are reasonable (at
least most of the time :-), and fixing them should be straightforward.
A
David Kastrup d...@gnu.org writes:
Jan Nieuwenhuizen jann...@gnu.org writes:
18:41:52 janneke@peder:~/vc/lilypond
$ ps2pdf toc.preview.eps
GPL Ghostscript 9.07: ERROR: A pdfmark destination page 4 points
beyond the last page 1.
Oh. _Interesting_. Maybe the error message is
maybe ./configure should check the installed version of texinfo and
print a warning if it's 4.13?
Until errors and bad output are fixed, I would even suggest to abort
for a version larger than 4.13.
Werner
___
lilypond-devel mailing list
The `motto' of the `text' section looks horrible:
http://lilypond.org/doc/v2.17/Documentation/notation/text
My suggestion is to replace it with a different snippet which is less
demanding w.r.t. horizontal space.
Werner
___
lilypond-devel
Hello folks,
I've read in a recent Lily Report that help would be welcome for this.
How do I proceed to start working on it?
Regards,
--
Jacques Menu
Ch. de la Pierre 12
1023 Crissier
mailto:jacques.m...@tvtmail.ch
___
lilypond-devel mailing list
Jacques Menu jacques.m...@epfl.ch writes:
Hello folks,
I've read in a recent Lily Report
Man, I wish you did.
that help would be welcome for this. How do I proceed to start
working on it?
Posting to this list is a good start. I hope somebody will answer with
a better answer soon. If
Jaques
On 28 May 2013 13:37, Jacques Menu jacques.m...@epfl.ch wrote:
Hello folks,
I've read in a recent Lily Report that help would be welcome for this.
How do I proceed to start working on it?
Regards,
http://code.google.com/p/lilypond/issues/list?can=2q=OpSys%3DOSX
Is a list of the
The `motto' of the `text' section looks horrible:
http://lilypond.org/doc/v2.17/Documentation/notation/text
My suggestion is to replace it with a different snippet which is less
demanding w.r.t. horizontal space.
This is now issue #3381.
Werner
2013/5/28 Werner LEMBERG w...@gnu.org:
Is this an incomplete example or a bug?
Well, an incomplete example is a bug.
:-)
That being said, the bar number engraver uses
ly:side_position_interface::move-to-extremal-staff for its vertical
positioning. The same would likely be done for
That being said, the bar number engraver uses
ly:side_position_interface::move-to-extremal-staff for its
vertical positioning. The same would likely be done for marks.
The question is what we should be doing here with regard to
interrupted staves in general, and/or with regard to ossia
2013/5/28 Werner LEMBERG w...@gnu.org:
That being said, the bar number engraver uses
ly:side_position_interface::move-to-extremal-staff for its
vertical positioning. The same would likely be done for marks.
The question is what we should be doing here with regard to
interrupted staves in
This reduced example looks very weird to me.
Yes.
Why would someone want this isolated Clefs (and the TimeSignature)?
It only demonstrates why the bar number in the original code is
positioned so high. \stopStaff only hides staff lines; it doesn't
make the Staff context disappear
2013/5/28 Werner LEMBERG w...@gnu.org
A completely different issue is our hand-crafted
`lilypond-texi2html.init' file. No idea whether this is compatible
with texinfo 5.
http://lists.gnu.org/archive/html/help-texinfo/2011-02/msg00013.html
2013/5/28 Werner LEMBERG w...@gnu.org
maybe ./configure should check the installed version of texinfo and
print a warning if it's 4.13?
Until errors and bad output are fixed, I would even suggest to abort
for a version larger than 4.13.
added to the tracker:
2013/5/28 Federico Bruni fedel...@gmail.com
maybe ./configure should check the installed version of texinfo and print
a warning if it's 4.13?
tonight I'll downgrade texinfo and try again
ok, I've downgraded to v4.13 in debian stable and pinned the package
I also had to (re?)install
Werner LEMBERG w...@gnu.org writes:
That being said, the bar number engraver uses
ly:side_position_interface::move-to-extremal-staff for its
vertical positioning. The same would likely be done for marks.
The question is what we should be doing here with regard to
interrupted staves in
Hello James,
Thanks for the answer.
Which software setup is to be used, on which version of OS X?
I run 10.8.3 with Xcode 4.4.1, can create specific partitions for other
versions if needed.
JM
Le 28 mai 2013 à 18:09, James pkx1...@gmail.com a écrit :
Jaques
On 28 May 2013 13:37,
33 matches
Mail list logo
