On 16-Apr-05, at 7:34 AM, Stephen wrote:
The problem appears when you put all the movements together **under
the same score**. I consider this to be a midi bug. If you put each
movement in its own score, all your engraving problems would disapear,
the movements would appear as they do in the sep
Attatched is a version or act1.ly, act1_.ly, that puts the final movement in
its own score block. I know you may not want to put each movement in its own
score, but lilypond expects this by default and notice how all the problems
associated with doing it as you have it set up disappear.
Stephen
Added to Changelog:
2005-04-17 Bernard Hurley <[EMAIL PROTECTED]>
* scm/framework-eps: When \betweenLilyPondSystem is defined
systems are in separate paragraphs.
Rationale:
Some LaTeX commands do not take effect until the end of the paragraph -
in this case after all the syst
I can't think of a situation where anyone except a beginner who didn't
understand the philosopy behind lllypond would want to use a
"no-accidental" style. OTOH it is useful to have workarounds for bugs.
\noAccidental seems ideal for this. It is not as cumbersome as having to
change the accidental-s
> What's an Implementation documenter? Is this providing documentation
> for programmers?
>
> Cheers,
> - Graham
>
Yes, so that programmers can find their way around the code. I'm not
sure that "Implementation Documenter" is that best term to use, but I
can't think of a better one at present. T
I forward the feature request (or maybe it should be seen as a bug
report) at the end of this email to lilypond-devel.
/Mats
Karl Hammar wrote:
On 1-Apr-05, at 12:38 PM, Karl Hammar wrote:
If I use \partial 4 R1*1/4, it will work in the full score,
but it gives me a lot of:
Music.23.ly:10:18:
> Citerar Stephen <[EMAIL PROTECTED]>:
>
> > I think we want Lilypond to continue to follow standard practive. If we give
> > users the ability to violate those rules then total novices will start
> > making mistakes.
>
> We don't have to document the feature in a way such that novices will be ab
> Karl,
>
> The problem appears when you put all the movements together **under the same
> score**. I consider this to be a midi bug.
No, the unwanted accidentals are still there if I remove the midi block.
> If you put each movement in its
> own score, all your engraving problems would disap
> Citerar Karl Hammar <[EMAIL PROTECTED]>:
...
> > > \version "2.4.0"
> > >
> > > #(define-public (print-+100-text-callback grob)
> > > (let* ( ;(text (ly:grob-property grob 'text))
> > > (text (number->string (+ 100 (string->number (ly:grob-property
> > grob
> > > 'text)
> > >
On 14-Apr-05, at 5:01 AM, Bernard Hurley wrote:
I have somewhat rashly volunteered to be Implementation documenter.
Han-Wen informs me that various abortive starts have already been made
on this. So if you have any material that would be useful, please
e-mail
it to me.
What's an Implementation doc
Citerar Stephen <[EMAIL PROTECTED]>:
> I think we want Lilypond to continue to follow standard practive. If we give
> users the ability to violate those rules then total novices will start
> making mistakes.
We don't have to document the feature in a way such that novices will be able
to
use it.
Citerar Stephen <[EMAIL PROTECTED]>:
I'm changing my mind about syntax - I think the best way would be to have a new
accidental style called no-accidentals, which would suppress all accidentals
except on notes with !. This is probably trivial to implement (but I don't have
the src here).
Erik
>
Citerar Karl Hammar <[EMAIL PROTECTED]>:
>
> > On Friday 15 April 2005 10.56, Karl Hammar wrote:
> > > [EMAIL PROTECTED]:
> > > > It also changes the numbering of all subsequent bars. I don't know the
> > > > author's intent in this case (I didn't write that snippet), but I
> guess
> > > > it cou
Use text markup!
/Mats
Laura Conrad wrote:
Former versions of abc2ly appended a second title line to the title
header line, with "", which used to translate to a line break,
between the lines. This no longer seems to work (current cvs).
I haven't figured how you get a line break in the t
Former versions of abc2ly appended a second title line to the title
header line, with "", which used to translate to a line break,
between the lines. This no longer seems to work (current cvs).
I haven't figured how you get a line break in the title these days; if
someone tells me, I could
> "LC" == Laura Conrad <[EMAIL PROTECTED]> writes:
LC> This ABC file that I reported problems with on 2.4.2 also has problems
LC> on current (2005-04-16 Han-Wen Nienhuys) CVS.
This one was a user error. Sorry.
--
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617)
This is in current (ChangeLog 2005-04-16 Han-Wen Nienhuys
<[EMAIL PROTECTED]>) CVS, on Debian unstable, with gs 8.14. The
command was "debuild -B".
debuild.log
Description: Binary data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://li
Current (2005-04-16 Han-Wen Nienhuys) CVS, make ran without errors,
but "make install" produces the following:
install.log
Description: Binary data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-
For the attached file, when I run abc2ly, and then lilypond, I get a
lot of errors that say:
programming error: Infinity or NaN encountered
The lilypond output is as you would expect.
cantus.abc
Description: Binary data
--
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 6
This ABC file that I reported problems with on 2.4.2 also has problems
on current (2005-04-16 Han-Wen Nienhuys) CVS.
The abc file is attached. It looks like there's something wrong with
markup on multi-voice music.
Abc2ly-snapshot says:
[solo5]# abc2ly-snapshot test.abc
/usr/bin/abc2ly-snapsh
This problem report on 2.4.2 is still a problem in current CVS.
> "LC" == Laura Conrad <[EMAIL PROTECTED]> writes:
LC> The attached abc file is in G minor, so it should print with a key
LC> signature of two flats. When I use Pedro's abc2ly-snapshot, 2.4.2,
LC> there's no key sign
Karl,
The problem appears when you put all the movements together **under the same
score**. I consider this to be a midi bug. If you put each movement in its
own score, all your engraving problems would disapear, the movements would
appear as they do in the separate scores. The midi files would
Laura Conrad writes:
> No, it's 2.5.19.
Ok. You're seeing problems that are fixed in CVS. I just tried, and
succceeded in make web with gs 8.01.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
I reported a 'make all' failure earlier. Now I'm getting a different
exit error:
all-font-metrics.cc:36: error: `pango_ft2_font_map_set_resolution'
undeclared (first use this function)
all-font-metrics.cc: In destructor `All_font_metrics::~All_font_metrics
()':
all-font-metrics.cc:52: error: `pa
Op za, 16-04-2005 te 12:41 +0100, schreef Bernard Hurley:
> Added to changelog:
>
> 2005-04-16 Bernard Hurley <[EMAIL PROTECTED]>
>
> * framework-eps.scm: code added so that a macro \betweenLilyPondSystem
> with one parameter can be defined in a LaTeX file when processed
>
Op za, 16-04-2005 te 10:09 +0100, schreef Bernard Hurley:
> Lilypond makes a good job of deciding breaks between systems, once this
> is done page breaks are easy again I might want them to follow the
> general format of the rest of my document, which does not only contain
> music, but contains fi
Added to changelog:
2005-04-16 Bernard Hurley <[EMAIL PROTECTED]>
* framework-eps.scm: code added so that a macro \betweenLilyPondSystem
with one parameter can be defined in a LaTeX file when processed
by lilypond-book this will be evaluated between the systems of
> "JN" == Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
JN> Laura Conrad writes:
>> Here's what happened. Now what? It isn't at all clear that this has
>> anything to do with the gs version.
JN> Is this latest CVS? I'm afraid that I cannot build with gs-8.01, and
JN> I
On Sat, 2005-04-16 at 01:08 +0200, Han-Wen Nienhuys wrote:
> > When called from lilypond-book, LilyPond does _not_ take care of
> > formatting the pages. This is precisely the reason I started using it.
> > So that I can have a multi-movement score with fancy headers, table of
> > contents, etc. Wh
I had a strange thing happen with my Fedora Core 3 system. It was
filled with filesystem inconsistencies and did not seem to be able to
repair itself. I have reinstalled it (I managed not to lose my data)
and tried to compile CVS again. I ran down the list of requirements for
compiling and I thi
Laura Conrad writes:
> Here's what happened. Now what? It isn't at all clear that this has
> anything to do with the gs version.
Is this latest CVS? I'm afraid that I cannot build with gs-8.01, and
I can with gs-8.50 (from CVS). I'm trying gs-afpl-8.14 now.
Jan.
--
Jan Nieuwenhuizen <[EMAI
31 matches
Mail list logo
