[frogs] Re: thanks to whomever put this in the LSR... |
[ Thread Index |
Date Index
| More lilynet.net/frogs Archives
]
Hi Reinhold,
I'm having a look at seeing if I can pick up the work Marek Klein did on
-devel. It covered amending the coded generating output file suffixes
to allow users to code user-specified names as the suffix. It changes
the function print-with-book in file lily-library.scm so one of the
internal variables uses a Scheme alist.
How much more work would it be to implement Patrick's suggestion below?
..
..
..
But it would be nice to have an option to override the file-name for
any arbitrary book. Something like
\book {
\paper {
output-file-name = "Blah"
}
\score {
...
}
}
..
..
..
As I understand it, the above would allow allow you to have a file
called something like "mozsym40.ly" and use
\paper {
output-file-name="SinfoniaK550"
}
to generated SinfoniaK550.pdf, .png, .mid, .midi or whatever.
If you were using a file with multiple \bookparts or \score blocks,
1. should output-file-name in these blocks replace the definition in
the \book \paper block (if present) to produce Allegro.pdf, .midi
or
2. should it act like #(define output-suffix "Allegro") so you produce
a file SinfoniaK550-Allegro.pdf, .midi etc? Or
3. should we have a separate output-file-suffix property to do this
trick, which would be for use only in \bookpart blocks?
I'm trying to get a clear idea of what would be clearest for users
before I send myself cross-eyed looking at the code.
Any opinions/pointers to set this Frog off in the right direction are
welcome.
Cheers,
Ian Hulin
Reinhold Kainhofer wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Donnerstag, 4. Juni 2009 01:01:24 schrieb Mats Bengtsson:
See
http://lists.gnu.org/archive/html/lilypond-user/2009-02/msg00833.html
and followups for the previous discussion on the topic. As far as I can
see, an implementation proposal is already available, just to commit.
Hmm, it seems that this has been completely forgotten... Does anyone have the
time to put the finishing touches on the patch?
In particular, get rid of the global var and properly use the variable from
the parser-lookup, also the comment is no longer valid.
Cheers,
Reinhold
- --
- ------------------------------------------------------------------
Reinhold Kainhofer, reinhold@xxxxxxxxxxxxx, http://reinhold.kainhofer.com/
* Financial & Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iD8DBQFKLAEsTqjEwhXvPN0RAlG1AKCEYYXJYUFeCSFTTZkARZ4zBpaHcACdGvkd
q0WId+UluAUa48LVj+7dAVA=
=UqgS
-----END PGP SIGNATURE-----
---
----
Join the Frogs!