Graham Percival writes:
> HWN, JCN:
> In scm/define-context-properties.scm , we have
> @usermanref{Setting automatic beam behavior}
>
> This produces a link with %20 in it; the actual link should have -
> Is this a bug in texinfo, or our definition of @usermanref{}, or...?
Thanks, should be fixed
Pedro Kröger writes:
> if you are using the ps backend (it's the default now) you have to save
> your file as unicode.
...or simply run convert-ly to recode automagically.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien |
On 27-Mar-05, at 3:58 PM, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
That's useful info, but why is
\cresc c
equivalent to
c \setTextCresc \<
? Why not go with a postfix \cresc?(thus "\cresc" =
"\setTextCresc
\<" )
IMO, the hairpin and the cresc - - - are two styles of conveying the
sa
On 29-Mar-05, at 4:01 AM, Christian Hitz wrote:
the proposed syntax for \raise does not work anymore (see [1]). The ""
is discarded. It works with " ", but this also moves the raised text
to the right.
True. According to the docs, the following text should be at the same
level:
\version "2.5.1
Will Oram <[EMAIL PROTECTED]> writes:
> title = "Akademische Fest-Overtüre."
>
> Prints as: Akademische Fest-Overt
>
> Tip o' the hat,
if you are using the ps backend (it's the default now) you have to save
your file as unicode.
Pedro
__
First off, 2.5.17 is the first version I've managed to get working on
my machine. And it looks awesome. Stunning. The change to the new font
(Century Schoolbook?) definitely gives it the 100 year-old score feel,
and not something my math professor churned up in LaTeX. I lied the
first time abou
On Wed, 2005-03-23 at 19:43 -0500, Will Oram wrote:
> While processing PS output for a rather large ly project, lily 2.5.16
> experiences a bus error. It says so very quietly in normal output mode,
> so to elaborate in --verbose :
> ---
>
> I know outputs like these are often not very helpful
On 27-Mar-05, at 10:01 PM, Rodney Lancaster wrote:
There appears to be an issue with the \pageBreak with multiple scores
in a book when there is a header for each score.
Try putting the page break in the header. Search the lilypond-user;
somebody posted
how to do this recently.
Alternatively, w
On 27-Mar-05, at 10:37 PM, Jeffrey Philpott wrote:
As a followup to my report of 24.03 here is the following output when
I use code directly in the file:
Please include enough info so that we know what you're talking about
without referring to other emails.
/usr/bin/lilypond-book-snapshot (GNU Lil
