Please search the mailing list archives for discussions on
this topic.
/Mats
Nicholas Haggin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greetings, all.
I have recently been experiencing problems with vertical placement
of staves in lilypond-book after upgrading
On 1-Aug-05, at 11:59 PM, Mats Bengtsson wrote:
Please search the mailing list archives for discussions on
this topic.
I think that this is new information, though -- at least, I've been
following
this with some interest, and I didn't know that this bug was triggered
by including
Sacha Standen wrote:
Also, tying notes to skips appears not to be possible as here:
\version 2.6.1.1
{c' ~ s}
Forgot to answer this one. It has never worked to tie a note to a
skip, just as it doesn't work to tie a note to a note with a
different pitch. See the section on Hidden Notes in
Where did you add the setting? The following should work.
\version 2.6.1
{s2 gis''4. fis''8\stemUp } \\
{ \set tieWaitForNote = ##t b8~ fis'~ a'~ cis''~ b fis' a' cis''2 }
Please read the details in the manual on what the construct
{...} \\ {...}
actually does in terms of contexts, to find
Right, this highlights that there is a round-off problem involved
as well, which further illustrates that the current solution isn't
really stable. The problem is that LaTeX points pt don't exactly
correspond to PostScript points bp. In fact 72.27pt = 72bp =1 inch.
The default text width in a
Guy Banay wrote:
I didn't know that, but maybe I should've guessed. Anyway, GS-ESP-8.01
(the one that's installed by default on Ubuntu 5.04) generates
readable pdf without complaining.
I guess we should check for GS 8.x and not GS 8.15 specifically
(although I'm surprised that Ubuntu
Mats Bengtsson wrote:
Note that the same problem would have appeared even if LaTeX and
PostScript had used the same definition of point, since the text
width of a LaTeX document does not have to be an integer number
of points, whereas the width of an eps file is rounded to the
closest integer
When you define the \header inside the \score block, only the piece
(and presumably opus) fields are printed. Is this expected behaviour?
If the \header is defined before the \score (ie
\header{}
\score{}
then all headers are printed.
% 2.6.1, only piece is printed, not title.
\score{
{ c'\f
Mats Bengtsson wrote:
It seems that there is a hiresbb option to the graphics and
graphicx packages that makes it read the %%HiResBoundingBox
instead of BoundingBox. However, the rounding problem is
easily solved by adding \linebreak commands.
Have you thought about the bounding boxes for the
Han-Wen Nienhuys writes:
I guess we should check for GS 8.x and not GS 8.15 specifically
(although I'm surprised that Ubuntu doesn't ship the latest GS).
The last time I checked, debian's gs-8.01 and gs-8.14 did not work.
Jan.
--
Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The
I didn't know about this feature/bug either!
However, you may want to use
\paper{
scoreTitleMarkup = \bookTitleMarkup
}
anyway in your case to get full titles on all scores.
/Mats
Graham Percival wrote:
When you define the \header inside the \score block, only the piece
(and presumably
Graham Percival wrote:
When you define the \header inside the \score block, only the piece
(and presumably opus) fields are printed. Is this expected behaviour?
If the \header is defined before the \score (ie
\header{}
\score{}
Yes. Otherwise, we'd get two titles if the \header for \book was
It seems that there is a hiresbb option to the graphics and
graphicx packages that makes it read the %%HiResBoundingBox
instead of BoundingBox. However, the rounding problem is
easily solved by adding \linebreak commands.
Have you thought about the bounding boxes for the different score
lines?
From: Graham Percival [mailto:[EMAIL PROTECTED]
When you define the \header inside the \score block, only the piece
(and presumably opus) fields are printed. Is this expected behaviour?
If the \header is defined before the \score (ie
\header{}
\score{}
then all headers are printed.
Did you expect me to remember your initial message of this
thread? It's over a week since I read it! ;-)
Seriously, it turns out that the cause of your problem was that
you used a Windows style path instead of Cygwin/Unix style.
Just replace the backslash in
\include ..\stuff.ly
with an ordinary
Han-Wen Nienhuys wrote:
Mats Bengtsson wrote:
It seems that there is a hiresbb option to the graphics and
graphicx packages that makes it read the %%HiResBoundingBox
instead of BoundingBox. However, the rounding problem is
easily solved by adding \linebreak commands.
Have you thought about
Han-Wen Nienhuys writes:
(although I'm surprised that Ubuntu doesn't ship the latest GS).
Ubuntu is a snapshot of debian/unstable with extra user-experience
polish. Only since July 15th, 8.15 is in debian (fixing a whishlist
bug from a lilypond user :-)
Maybe we could check a specific gs
Both problems pointed out in this thread show a limitation in
the handling of volta brackets. A volta bracket is only printed
over contexts where the property voltaOnThisStaff is set to true.
At the beginning of a score, this property is automatically
set to true for the topmost Staff context and
Mats -
Thanks for the insight. Pretty #$@ subtle, especially for a DOS\Windows
guy.
Note that without the #(ly:set-point-and-click 'line-column), the \include
..\stuff.ly works fine.
As presented below it also works, just gives the error message:
Error invoking `latex \\nonstopmode \\input
Fairchild wrote:
Note that without the #(ly:set-point-and-click 'line-column), the \include
..\stuff.ly works fine.
Exactly, that's the only situation where the path of the file is
included in the LaTeX code.
I can't find any documentation of \include other than simple use examples.
It
Mats -
You state: The initialization of LilyPond is done in a number of files that
are included as soon as you start the program. Nothing that you have to
bother about.
I would like to know what files are included. They contain default settings
-- often useful and more reliably correct that the
Heikki Johannes Junes writes:
I have tried to use LilyPad.
Therefore, it is impossible to make a file shorter using only LilyPad.
Thanks. Fixed in CVS.
Jan.
--
Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien |
22 matches
Mail list logo
