bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 836 in lilypond: [in progress] output-suffix as a (Score) cont


From: lilypond
Subject: Re: Issue 836 in lilypond: [in progress] output-suffix as a (Score) context property
Date: Mon, 15 Mar 2010 13:54:00 +0000

Updates:
        Owner: Carl.D.Sorensen
        Cc: -Carl.D.Sorensen
        Labels: -Patch Regression

Comment #4 on issue 836 by percival.music.ca: [in progress] output-suffix as a (Score) context property
http://code.google.com/p/lilypond/issues/detail?id=836

%% graham: added "regression" because closing this issue involves regtest stuff.
%% owned by Carl because Ian Hulin is a frog.

%% Comments from Ian Hulin:
I went the music-function route because there was a feeling that contexts were properties which were reserved for the phase of music translation and producing grobs. When I started working on this I reckoned contexts were Lilypond-speak for sets of attributes within the compiler, so it seemed reasonable to attach some new attributes to the the compilation unit (i.e an implicit or explicit \book block) to achieve this. However, although the \book block is treated as OO object in the C++ code, I got very confused trying to work out what was at top-level, what was the
object hierarchy and what was the context hierarchy.

So I worked out a way of doing it with music functions and parser variables instead, which met the demand from users for begin able to rename to backend output files
simply from within code.

If people really want this functionality via a context-like interface I'll have another crack at it, but I don't really feel I understand the way Lily fits together
well enough yet.



%% is the issue finished?
I got lost in how the regression test files get generated. I thought it would be
enough to have a file called something like
"output-filename-Zčeskýchluhůahájů.ly" - here's the file contents
\version "2.13.5"

\header {
 texidoc = "Using extended Latin characters like š and č
 in output file-names should not cause any problems with
 backend processors."

 dedication = "Lilypond Regression Test"
 title = "Má Vlast"
 subtitle = "Symphonic Tone Poem Cycle"
 instrument = "Orchestra"
 composer = "Bedřich Šmetana"
 opus = "Opus 64"
}
% Set up variables
globalIV = {\key f \major \time 4/4}
violinmIV = \relative c'' { \globalIV  d1 | }

%Now produce back-end files with names using extended accents

\book {
 \header {
  subsubtitle = "IV. Z českých luhů a hájů"
 }
 \score {
   \new Staff  \violinmIV
   \layout { }
   \midi { }
 }
}

But I couldn't work out how to stitch this in to the reg test suite using this name, since the make check seemed to insist on generating its own names on the fly, which made it dfficult writing a test testing to see whether files with a specific name
were generated.

The CG Chap 8 has no content on regression tests so I'm stuck.


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

reply via email to

[Prev in Thread] Current Thread [Next in Thread]