On Sun, 30 Jan 2011 16:13:10 -0800, Carl Sorensen wrote:
On 1/30/11 3:33 PM, "Keith OHara" wrote:
The commands to adjust automatic beaming changed at 2.13.4 and again at
2.13.29, with NOT_SMART conversion rules. Only the first rule is triggered on
scores for the last stable version, and i
On 1/30/11 3:33 PM, "Keith OHara" wrote:
> Carl,
>The commands to adjust automatic beaming changed at 2.13.4 and again at
> 2.13.29, with NOT_SMART conversion rules. Only the first rule is triggered on
> scores for the last stable version, and it refers to commands in the 2.13.4
> manual tha
Carl,
The commands to adjust automatic beaming changed at 2.13.4 and again at
2.13.29, with NOT_SMART conversion rules. Only the first rule is triggered on
scores for the last stable version, and it refers to commands in the 2.13.4
manual that users will not have.
It seems appropriate to
I have a very similar setup (2.7.32 self-compiled with gcc 4.0.1 on
debian unstable/testing) and get exactly the same message (except for
the .ly filename).
The Python version is: Python 2.3.5 (#2, Nov 20 2005, 16:40:39)
Although debian has both Python 2.3 and 2.4 installed, the default
vers
fixed.
[EMAIL PROTECTED] writes:
> The new strategy in version 2.3.x to automatically switch to
> \notes syntax causes problems in examples like
> \version "2.2.6"
> \score{
>\context Voice = a \notes \relative c' {c d e f}
> }
>
> since the name used for the Voice context happens to be a no
The new strategy in version 2.3.x to automatically switch to
\notes syntax causes problems in examples like
\version "2.2.6"
\score{
\context Voice = a \notes \relative c' {c d e f}
}
since the name used for the Voice context happens to be a note name.
Maybe it's easy to add convert-ly rule that
[EMAIL PROTECTED] writes:
> > Yes it would, but how would you parse a balanced parenthesis
> > expression using regular expressions?
>
> I know my automata theory, but when thinking about it once again, there is
> really a solution. (DON'T LAUGH! READ ON)
>
> There are 318 pieces of music on Mut
>
> Yes it would, but how would you parse a balanced parenthesis
> expression using regular expressions?
>
In theory, it can't be done, as balancing requires context-free
beyond regular grammars. In practice though, specially given the scope
(convert.ly is not meant to be used zillions of time
On Saturday 27 March 2004 00.39, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > Really? Doing _nothing_ would actually be satisfactory.. The problem is
> > that one parenthesis is moving:
> > 1.8: a4_#'(italic "Simile") c
> > 1.9: a4_#'(italic "Simile" c)
> > so if you just would detect th
On Friday March 26 2004 17:00, Han-Wen Nienhuys wrote:
>
> [EMAIL PROTECTED] writes:
> > > Yes it would, but how would you parse a balanced parenthesis
> > > expression using regular expressions?
> >
> > Ah.. So you're somehow limited to regexps.. explains everything :)
> >
> > I have to ad
[EMAIL PROTECTED] writes:
> > Yes it would, but how would you parse a balanced parenthesis
> > expression using regular expressions?
>
> Ah.. So you're somehow limited to regexps.. explains everything :)
>
> I have to admit that for a while, I thought it was due to laziness that you
> left
> > Really? Doing _nothing_ would actually be satisfactory.. The problem is
> > that one parenthesis is moving:
> > 1.8: a4_#'(italic "Simile") c
> > 1.9: a4_#'(italic "Simile" c)
> > so if you just would detect the #', you could assume that it would be
> > followed by a nonempty balanced parenthes
[EMAIL PROTECTED] writes:
> On Friday 26 March 2004 01.47, Han-Wen Nienhuys wrote:
> > [EMAIL PROTECTED] writes:
> > > It might be too much to demand that convert-ly should upgrade
> > > #'(italic "Simile")
> > > to
> > > \markup {\italic { "Simile" }}
> > > , but the movement of a parenthesis move
On Friday 26 March 2004 01.47, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > It might be too much to demand that convert-ly should upgrade
> > #'(italic "Simile")
> > to
> > \markup {\italic { "Simile" }}
> > , but the movement of a parenthesis movement is IMHO a clear bug, as
> > opposed
[EMAIL PROTECTED] writes:
> It might be too much to demand that convert-ly should upgrade
> #'(italic "Simile")
> to
> \markup {\italic { "Simile" }}
> , but the movement of a parenthesis movement is IMHO a clear bug, as opposed
> to a limitation.
Unfortunately, I don't see good way to fix thi
Along the same lines, the following
\version "1.7.1"
g2. \f \spanrequest \start "text" g8 \spanrequest \stop "text" \fz r |
is converted by convert-ly -t1.9.0 into
\version "1.9.0"
g2. -\f #(ly:export (make-span-event 'TextSpanEvent START) g8)
#(ly:export (make-span-event 'TextSpanEvent STOP)) \f
Hi,
This doesn't qualify as a necessary bugfix for 2.2, since it occured in 2.0
already. But anyways:
When converting from 1.8 to 1.9, with the new markup syntax, there is a
problem with parentheses. The following:
\version "1.8.0"
\score {
\notes {a4_#'(italic "Simile") c}
}
is translated to
On Tuesday 23 March 2004 19.18, Doug Asherman wrote:
> Hi:
>
>
> I'm seeing the following in most cases with convert-ly (note: all of
> these cases worked find with 2.1.32):
The crash occurs also with the file containing only the line:
\version "2.1.32"
To use convert-ly before this has been fixe
Hi:
I'm seeing the following in most cases with convert-ly (note: all of
these cases worked find with 2.1.32):
convert-ly (GNU LilyPond) 2.1.34
Processing `popsong.ly' ... Applying conversions: 2.1.23, 2.1.24,
2.1.25, 2.1.26, 2.1.27, 2.1.28, 2.1.29, 2.1.30, 2.1.31, 2.1.33,
Traceback (most rece
19 matches
Mail list logo
