rops symbol) (symbol?)
(let ((m (chain-assoc-get symbol props)))
(if (markup? m)
(interpret-markup
layout
(cons (list (cons symbol `(,property-recursive-markup
,symbol))) props)
(markup->string m))
empty-stencil)))
\header {
asdf = \markup \with
thank you very much!
Best
Joei
On 2024-03-19 11:15 am, Johannes Roeßler wrote:
And I aim to separate content from style - but in order to have the
right (and changing) footer text for each piece in a book
environment, I need to get this information from the header and can't
define it in
On 2024-03-19 11:15 am, Johannes Roeßler wrote:
And I aim to separate content from style - but in order to have the
right (and changing) footer text for each piece in a book environment,
I need to get this information from the header and can't define it in
the common \paper env - or do I miss
this information from the header and can't define it in the
common \paper env - or do I miss something?
And defining and adding your idea with the \as-string command seems not
to work:
-8<--
\version "2.24.0"
#(define-markup-command
(as-string layout props
On 2024-03-19 9:35 am, Johannes Roeßler wrote:
Hi,
I'd like to make an automatic footer, using infos from the header
block.
What do I have to change, to get rid of (or override) the format from
the title?
-8<--
\version "2.24.0"
{a4}
\header {
titl
Hi,
I'd like to make an automatic footer, using infos from the header block.
What do I have to change, to get rid of (or override) the format from
the title?
-8<--
\version "2.24.0"
{a4}
\header {
title =
\markup
\fill-line {
\override
de song.ily
>
> song.ily
> \include [.ily files containing the notes, edition-engraver tweaks, etc.]
Different versions will share some tweaks and also have individual/unshared
tweaks, so I can’t quite tell yet whether this structure would be sufficient
(never mind optimal).
&g
-engraver tweaks, etc.]
\header {
[header parameters shared by both versions]
[differing header parameters defined in global variables]
}
\score {
[contexts built from variables defined in \include-d files]
}
Optionally, you could use the output names and book blocks so that you can
Hi Timothy,
> How about setting up some Scheme variables that are later used to build
> variants of the score?
OOO I like this!
There are some further complications coming up that might render this
unfeasible/impractical… but it’s a great suggestion, and I can definitely see
where to use it
On 22/01/2024 19:09, Kieren MacMillan wrote:
Is there a more efficient construct where the book name and header variables
could be “injected” or “conditionalled” in? Or is that just overcomplicating
this particular problem-space? (n.b., In future questions, the problem-space is
naturally
=
<<
[contexts built from variables defined in \include-d files]
>>
\header {
[header parameters shared by both versions]
}
\book {
\bookOutputName "MySong_full"
\header {
[header parameters specific to the Full Version, e.g., song number]
}
\score { \
On Wed, Sep 13, 2023 at 12:34 AM Jean Abou Samra wrote:
> Suppose tagline "worked" in \score blocks. What would this code print?
>
> \version "2.24.2"
>
> \score {
> \header {
> tagline = "Tagline 1"
> }
> { c' }
> }
>
>
> Well, I could imagine that the last 'tagline' entry wins.
It is at least not more consistent than the existing behavior, which
is also documented. Ergo, I see no bug here.
Best,
Jean
signature.asc
Description: This is a digitally signed message part
> Another observation: tagline is not in either the command index or
> the index in the Notation Manual. The documentation I could find on
> tagline was pretty sparse (unless I missed something).
I've added index entries in
https://gitlab.com/lilypond/lilypond/-/merge_requests/2104
> Suppose tagline "worked" in \score blocks. What would this code print?
>
> \version "2.24.2"
>
> \score {
> \header {
> tagline = "Tagline 1"
> }
> { c' }
> }
>
> \score {
> \header {
> tagline = &
Le mardi 12 septembre 2023 à 15:38 -0700, Knute Snortum a écrit :
> Hi everyone.
>
> I have a few observations that I'd like to share. Nothin too urgent.
>
> If you put tagline = ##f in a header block, it will work everywhere except in
> the score block.
Suppose tagline
Dear Knute,
Searching `lilypond "tagline"` on google I found
https://lilypond.org/doc/v2.23/Documentation/notation/creating-titles-headers-and-footers
where it is stated "The default LilyPond footer text can be changed by
adding a tagline in the top-level \header bl
Hi everyone.
I have a few observations that I'd like to share. Nothin too urgent.
If you put tagline = ##f in a header block, it will work everywhere except
in the score block. Here is a MWE to illustrate this:
\version "2.25.7"
% \header { tagline = ##f } % <-- this
Hi Joseph,
On Mon, Aug 21, 2023 at 8:08 PM Joseph Srednicki
wrote:
> Hello:
>
> When coding organ pieces, I want the registration to appear following the
> header.
>
> In the following example, I inserted the registration in a markup block
> before the score block.
You could "fake" the opus by putting it in markup instead of the header
(see attached).
--
Knute Snortum
On Mon, Aug 21, 2023 at 5:08 PM Joseph Srednicki
wrote:
> Hello:
>
> When coding organ pieces, I want the registration to appear following the
> header.
>
>
Hello:
When coding organ pieces, I want the registration to appear following the
header.
In the following example, I inserted the registration in a markup block before
the score block. When Lilypond renders the music, there is a large gap between
the lines containing the composer's name
On 8/20/2023 11:35 AM, Jean Abou Samra wrote:
Le dimanche 20 août 2023 à 10:54 -0400, Rik Kabel a écrit :
Hello list,
I have a few pieces that have been engraved for my choir with 2.18.10
that include catalog numbers entered as
\header {
...
number = \markup { \fontsize #4 \sans
Jean Abou Samra writes:
> Le dimanche 20 août 2023 à 10:54 -0400, Rik Kabel a écrit :
>>
>> Hello list,
>>
>> I have a few pieces that have been engraved for my choir with 2.18.10 that
>> include catalog numbers entered as
>>
>> >
&
Le dimanche 20 août 2023 à 10:54 -0400, Rik Kabel a écrit :
>
> Hello list,
>
> I have a few pieces that have been engraved for my choir with 2.18.10 that
> include catalog numbers entered as
>
> >
> > \header {
> > ...
> > number =
Hello list,
I have a few pieces that have been engraved for my choir with 2.18.10
that include catalog numbers entered as
\header {
...
number = \markup { \fontsize #4 \sans \ellipse 11B }
...
}
The number variable seems to be gone with current versions, and I can
Le mercredi 15 mars 2023 à 22:49 +0100, Jean Abou Samra a écrit :
> -
> use `-dseparate-page-formats=pdf` if you want to get one output file per page
> (or per system if also using lilypond-book-preamble.ly),
>
>
> -
> use `-dtall-page-formats=pdf` if you want to get squashed pages.
P.S. Can
Le mercredi 15 mars 2023 à 17:32 -0400, Fr. Samuel Springuel a écrit :
> The attached file compiles differently under 2.22 and 2.24: 2.24 introduces a
> page break that isn’t present in 2.22. This is causing some havoc in my
> lyluatex tool chain. Any idea what’s causing the problem and how to
The attached file compiles differently under 2.22 and 2.24: 2.24 introduces a
page break that isn’t present in 2.22. This is causing some havoc in my
lyluatex tool chain. Any idea what’s causing the problem and how to fix it?
convert-ly doesn’t change anything in the file when upgrading the
, Jean, this is worth being in the LPNR!
> >
> > If I'm not mistaken, this marvelous code could easily be generalized
> > to provide a command (during music) which sets arbitrary variables
> > that may be retrieved in header/footer definitions, and which could be
> > ma
be retrieved in header/footer definitions, and which could be
made part of core LilyPond.
My list of "stuff to do for LilyPond over the holidays" is already
overlong, and I'm sure I couldn't do it half as well, but I'm putting
it on my list anyway - unless Jean himself feels ent
Devnull. Some
> > people do it with a Dynamics as well. Devnull works
> > with everything you might want to take out of the
> > individual parts: \time, \tempo, \mark, etc.
Thanks, that works beautifully.
> > For not repeating the title between \header and \tocItem,
> >
Am 11.12.22 um 10:32 schrieb Jacques Menu:
Thumbs up, Jean, this is worth being in the LPNR!
If I'm not mistaken, this marvelous code could easily be generalized to
provide a command (during music) which sets arbitrary variables that may
be retrieved in header/footer definitions, and which
(table (or (ly:output-def-lookup paper
>> 'page-number-scene-text-table #f)
>> (let ((table (make-hash-table)))
>>(ly:output-def-set-variable! paper
>> 'page-number-scene-text-table table)
>>
table)))
> (first-system
>(any (lambda (line)
> (ly:prob-property line 'system-grob #f))
> lines))
> (scene-text
>(if first-system
>
FT)))
(assq-ref (ly:grob-property first-column 'details)
'scene-text))
"")))
(hashv-set! table page-number scene-text)))
pages))
}
%%% EXAMPLE
\header {
title = "Silly Opera"
}
{
\sceneMark &
Hi Brin,
> I was hoping to find a way that didn't force a page break (or even
> necessarily a line break) between scenes. Is that something that's possible,
> or is the page break required?
As far as I know:
1. a separate bookpart is required to change the properties that the titling
cenes/sub-scenes
> that can then be stitched together later in various combinations. But I'm
> missing the step of how to get the header at the top of the page to reflect
> what the current scene is at a given moment, since evenHeaderMarkup and
> oddHeaderMarkup in the paper block don't seem to be ab
m missing
> the step of how to get the header at the top of the page to reflect what the
> current scene is at a given moment, since evenHeaderMarkup and
> oddHeaderMarkup in the paper block don't seem to be able to pull
> title/subtitle information from any except the top-level \header bl
On Fri, Dec 9, 2022 at 2:56 PM Kieren MacMillan
wrote:
> Hi Brin,
>
> > I am working on an opera and would like to use text in the header to
> help the performers keep track of where they are in the score. So ideally,
> the header on each page should say something like &quo
Hi Brin,
> I am working on an opera and would like to use text in the header to help the
> performers keep track of where they are in the score. So ideally, the header
> on each page should say something like "Title of Opera: Act I, scene ii",
> with the scene reflectin
Hello!
I am working on an opera and would like to use text in the header to help
the performers keep track of where they are in the score. So ideally, the
header on each page should say something like "Title of Opera: Act I, scene
ii", with the scene reflecting whatever the cur
Le 06/12/2022 à 19:05, Jean Abou Samra a écrit :
Le 06/12/2022 à 18:10, Joel C. Salomon a écrit :
The requirement that `\tocItem` is either outside the `\score` block
or within a music variable is making it awkward for me to keep it near
where the score `\header` block defines the piece title
Le 06/12/2022 à 18:10, Joel C. Salomon a écrit :
The requirement that `\tocItem` is either outside the `\score` block
or within a music variable is making it awkward for me to keep it near
where the score `\header` block defines the piece title. And I have
entirely failed to figure out a way
The requirement that `\tocItem` is either outside the `\score` block
or within a music variable is making it awkward for me to keep it near
where the score `\header` block defines the piece title. And I have
entirely failed to figure out a way to re-use the piece title.
Minimal example below
On 2022-06-27 17:27, Thomas Morley wrote:
I try to code sort of a tablature for Akkordzither.
Instead of longish descriptions best look at the image at the bottom of
https://gitlab.com/Thomas_Morley/zither-ly/-/tree/development
This looks very much like klavarskribo. I wonder if Wilbert
of a TabStaff running top to bottom as opposed
to the usual left to right.
If I use a portrait-paper-size, I can use the default header and need
to rotate the TabStaff. Not knowing how to do it different, I did so
putting the TabStaff into \markup.
This is the master-branch of above linked repo.
Alas
Am Mo., 27. Juni 2022 um 13:23 Uhr schrieb Jean Abou Samra :
>
>
>
> Le 27/06/2022 à 12:12, Thomas Morley a écrit :
> > Hi,
> >
> > https://lsr.di.unimi.it/LSR/Item?id=467 provides a markup-command to
> > access header-entries for use in arbitrary markup.
>
Le 27/06/2022 à 12:12, Thomas Morley a écrit :
Hi,
https://lsr.di.unimi.it/LSR/Item?id=467 provides a markup-command to
access header-entries for use in arbitrary markup.
Alas it's limited to $defaultheader.
Although there is a comment to add/access other headers like from
\score, \bookpar
Hi,
https://lsr.di.unimi.it/LSR/Item?id=467 provides a markup-command to
access header-entries for use in arbitrary markup.
Alas it's limited to $defaultheader.
Although there is a comment to add/access other headers like from
\score, \bookpar explicit \book, I found no way to do so.
I tried
-aligned header for an entire sonata, which is
easiest achieved using toplevel markup, and then using the header
mechanism for the movement headers (which I intended to include a common
composer field, but I’m reconsidering that).
There are lots of ways. You could integrate the specific
title
Le 06/06/2022 à 14:32, Simon Albrecht a écrit :
Hi everyone,
%%%
\version "2.23.9"
\bookpart {
\markup \fontsize #10 "general title"
\header {
title = "specific title"
}
\score {
{ 1 }
}
}
why does "general
Hi everyone,
%%%
\version "2.23.9"
\bookpart {
\markup \fontsize #10 "general title"
\header {
title = "specific title"
}
\score {
{ 1 }
}
}
why does "general title" appear below "specific title&q
臘♂️
That did it, thank you!
> On Dec 3, 2021, at 12:07 PM, Jean Abou Samra wrote:
>
> Le 03/12/2021 à 18:04, Nate Whetsell a écrit :
>> Thanks for your help!
>>
>> Using \justify as
>>
>> ```
>> \paper {
>> scoreTitleMarkup = \markup {
>>\column {
>> \fromproperty #'header:piece
Le 03/12/2021 à 18:04, Nate Whetsell a écrit :
Thanks for your help!
Using \justify as
```
\paper {
scoreTitleMarkup = \markup {
\column {
\fromproperty #'header:piece
\justify { #'header:instruction }
}
}
}
```
may be on the right track, but this results in (for all cases):
Thanks for your help!
Using \justify as
```
\paper {
scoreTitleMarkup = \markup {
\column {
\fromproperty #'header:piece
\justify { #'header:instruction }
}
}
}
```
may be on the right track, but this results in (for all cases):
```
test.ly:7:17: error: not a markup
Nate Whetsell writes:
> Thanks, but unfortunately using a backtick and commas seems to produce the
> same output. If it’s helpful, here’s the same example with a backtick and
> commas:
>
> ```
> \version "2.22.0"
>
> \paper {
> scoreTitleMarkup = \markup {
>\column {
> \fromproperty
rkup expression does not work.
(2 . ,(markup #:line (#:simple "Does not work")))
; Using a string works.
(3 . "Works")))
\book {
#(do ((study-number 1 (1+ study-number)))
((> study-number 3))
(let ((header (make-module)))
(module-define! header 'pie
tore markups in an alist, and then use those markups in a header?
>
> Below is an example illustrating the issue I’m having. Any help would be
> greatly appreciated!
>
> Thanks,
> Nate
>
> ```
> \version "2.22.0"
>
> \paper {
> scoreTitleMarkup = \mar
in a header?
Below is an example illustrating the issue I’m having. Any help would be
greatly appreciated!
Thanks,
Nate
```
\version "2.22.0"
\paper {
scoreTitleMarkup = \markup {
\column {
\fromproperty #'header:piece
\justify-field #'header:instruction
}
}
}
On Mon, Nov 29, 2021 at 5:59 AM David Wright
wrote:
> On Wed 24 Nov 2021 at 19:44:59 (+0100), Paolo Prete wrote:
>
>
>
> If you do this regularly, I would suggest that that's just
> what you do, copy your source through a simple filter to a
> temporary file and compile that.
>
> [cut]
Hello
On Wed 24 Nov 2021 at 19:44:59 (+0100), Paolo Prete wrote:
> > and then comment or comment out parts of the score that I don't need to
> > render. So, for example, if I need to render only section 2, I would
> > comment section 3 and section 1 but I have to comment the markup block
> > separately
021 at 7:07 PM Valentin Petzel wrote:
> Hello Paolo,
>
> you've missunderstood what I meant. If you have each section in a separate
> file you can simly compile that file instead of uncommenting stuff. And you
> can have header and first section in the same file.
>
> Cheers,
>
Hello Paolo,
you've missunderstood what I meant. If you have each section in a separate file
you can simly compile that file instead of uncommenting stuff. And you can have
header and first section in the same file.
Cheers,
Valentin
24.11.2021 18:08:50 Paolo Prete :
> Hello Valen
nt scores (you can tweak the second score so that it does not
> in
> fact look like it’s a new score) in different files. Then you could have a
> file header.ly which contains the header, a file secI.ly which contains
> the
> first section, secII.ly which contains the second section and so o
score so that it does not in
fact look like it’s a new score) in different files. Then you could have a
file header.ly which contains the header, a file secI.ly which contains the
first section, secII.ly which contains the second section and so on. And then
you could simply do
\include
Hello,
Given a header like this:
\markuplist {
\fill-line {
\override #'(font-name . "Liberation Sans")
\override #'(font-size . 6)
"Author"
}
\vspace #4
\fill-line {
\override #'(font-name . "Liberation Sans")
\override #'(font-size . 15)
Thank you, I'll surely proceed in this way.
On Tue, Nov 23, 2021 at 2:46 AM Mark Probert wrote:
>
> Hi, Paolo.
>
> Here is a version that could work in that way, with modification. It
> shows one way to achieve the result by ignoring the headers and doing
> it all in text with associated font
Hello,
in Italy it's very common to have a printed score with the very first page
formatted as this image shows:
https://www.stretta-music.com/media/images/712/776712_detail-00.jpg
Basically, it is a sequence of fields, all horizontally centered, following
this order, from top to bottom:
1)
Thanks David! It works.
19.11.2021 14:24, David Kastrup пишет:
Павел writes:
Hello lilyponders! I want to produce \header block in my function, to
use my function instead \header block. But I can't seem to find the
correct syntax for this. It doesn't work like that:
genheader = #(define
Павел writes:
> Hello lilyponders! I want to produce \header block in my function, to
> use my function instead \header block. But I can't seem to find the
> correct syntax for this. It doesn't work like that:
>
> genheader = #(define-music-function
> (
Hello lilyponders! I want to produce \header block in my function, to
use my function instead \header block. But I can't seem to find the
correct syntax for this. It doesn't work like that:
genheader = #(define-music-function
(mystring) ( string? ) #{
\header { piece = \markup\bold
p.s.
>> I'm trying to add some instruction text in my score. I would like to
>> position it between the header and the music, but I cannot seem to figure
>> out how to do this, as markup cannot be placed inside a score block. I also
>> tried taking the header out of the
Hi Erika,
> I'm trying to add some instruction text in my score. I would like to position
> it between the header and the music, but I cannot seem to figure out how to
> do this, as markup cannot be placed inside a score block. I also tried taking
> the header out of the score
On Mon, Oct 4, 2021 at 8:13 AM Erika Pirnes wrote:
>
> I'm trying to add some instruction text in my score. I would like to position
> it between the header and the music, but I cannot seem to figure out how to
> do this, as markup cannot be placed inside a score block. I also
I'm trying to add some instruction text in my score. I would like to position
it between the header and the music, but I cannot seem to figure out how to do
this, as markup cannot be placed inside a score block. I also tried taking the
header out of the score block which still seemed to produce
Thank you for that cheat sheet! Is this part of the official documentation
or your own work?
All the best
Christian
Noeck schrieb am Mo., 1. Feb. 2021, 23:46:
> Hi David,
>
> you are looking for markup-system-spacing:
>
> \paper {
> markup-system-spacing.basic-distance = #10
> }
>
>
Thanks, Joram. This is helpful.
Noeck writes:
> Hi David,
>
> you are looking for markup-system-spacing:
>
> \paper {
> markup-system-spacing.basic-distance = #10
> }
>
> Flexible vertical spacing \paper variables:
>
Hi David,
you are looking for markup-system-spacing:
\paper {
markup-system-spacing.basic-distance = #10
}
Flexible vertical spacing \paper variables:
http://lilypond.org/doc/v2.20/Documentation/notation/flexible-vertical-spacing-paper-variables
Cheat Sheet:
Thank you! I could have sworn I tried almost exactly that and got
errors. But this does work!
And thanks for the amazingly quick response!
-David
"Hwaen Ch'uqi" writes:
> Greetings David,
>
> You can invoke the \column and \vspace commands inside markup, like this:
>
Greetings David,
You can invoke the \column and \vspace commands inside markup, like this:
\header {
piece = \markup \column {
"blah blah"
\vspace #2
}
}
hth,
Hwaen Ch'uqi
On 2/1/21, David Zelinsky wrote:
> Is there a way to put some space between the he
> Is there a way to put some space between the header material and the
> first staff? None of my searching as produced anything relevant.
>
> Here's an example:
>
> -
>
> \version "2.20.0"
> \include "english.ly"
>
> \score
Is there a way to put some space between the header material and the
first staff? None of my searching as produced anything relevant.
Here's an example:
-
\version "2.20.0"
\include "english.ly"
\score {
{
c''' c''' c''' c'''
}
}
\header {
piece =
; >>
> >> The "enteredby" header field is mentioned in
> >> https://lilypond.org/doc/v2.23/Documentation/snippets/titles#titles-demonstrating-all-headers.
> >>
> >> However, I can't find any reference to this field in the PDF output.
> >>
Am Sa., 30. Jan. 2021 um 17:06 Uhr schrieb Kuredant :
>
> Hello,
>
> The "enteredby" header field is mentioned in
> https://lilypond.org/doc/v2.23/Documentation/snippets/titles#titles-demonstrating-all-headers.
>
> However, I can't find any reference to this field i
Hello,
The "enteredby" header field is mentioned in
https://lilypond.org/doc/v2.23/Documentation/snippets/titles#titles-demonstrating-all-headers.
However, I can't find any reference to this field in the PDF output.
Does anyone know how this field is used by LilyPond?
That's it...thanks!
On Mon, Nov 23, 2020 at 9:19 AM Knute Snortum wrote:
> I think that would be "markup-system".
>
> --
> Knute Snortum
>
>
>
> On Mon, Nov 23, 2020 at 6:01 AM Marc Shepherd wrote:
>
>> What parameter controls the minimum amount o
Dear Marc,
it's markup-system.minimum-distance
(or basic-distance or padding – depending on what want)
https://joramberger.de/files/LilypondSpacing.pdf
HTH
Joram
I think that would be "markup-system".
--
Knute Snortum
On Mon, Nov 23, 2020 at 6:01 AM Marc Shepherd wrote:
> What parameter controls the minimum amount of space between the bottom of
> the header and the first line of music?
>
> --
> Marc Shepherd
>
On Mon, 23 Nov 2020 at 15:01, Marc Shepherd wrote:
>
> What parameter controls the minimum amount of space between the bottom of
the header and the first line of music?
Hello,
markup-system-spacing.minimum-distance
See NR 4.1.4 Flexible vertical spacing \paper variables > List of
What parameter controls the minimum amount of space between the bottom of
the header and the first line of music?
--
Marc Shepherd
On 14/03/2020 19:14, Noeck wrote:
So I did another try and used the footer markup, but I can't use
fromproperty in Scheme code. This is what I tried:
\version "2.20.0"
\header { title = "Title" }
\paper {
oddFooterMarkup = \markup \fill-line {
\null
#(if
tly why \fromproperty is the wrong tool for me here as I
> want to change the header fields based on what is there now not later.
I spoke too soon here. It would actually be nice to put the includes first.
Can I use fromproperty also in Scheme code? Or does the late evaluation
contradict with the us
-url #"url" "License" endif?? }
How about something like this? Comment out "licence = ..." to remove
the copyright statement.
\version "2.20.0"
\header {
licence = "CC-BY-NC 4.0"
copyright =
#(if (defined? 'licence)
(markup
#:li
Dear Aaron,
thank you for your mail.
> It may be your intention, but markup->string strips out formatting.
Yes, it is my intention. I want to work with strings and not markup as I
want to completely separate the formatting from the header fields.
> Next, why use strings and stri
Aaron Hill writes:
> On 2020-03-12 11:49 am, Noeck wrote:
>> Thanks Francisco! That's great news!
>> It also works across separate header blocks and even from within
>> included files. And it is easier to turn it into a string than for the
>> \fromproperty mech
On 2020-03-12 11:49 am, Noeck wrote:
Thanks Francisco! That's great news!
It also works across separate header blocks and even from within
included files. And it is easier to turn it into a string than for the
\fromproperty mechanism. So this works for me:
\header {
title = "my
Thanks Francisco! That's great news!
It also works across separate header blocks and even from within
included files. And it is easier to turn it into a string than for the
\fromproperty mechanism. So this works for me:
\header {
title = "my title"
composer = "will be rep
This shows that header fields behave just like plain markups and can be
used inside other markups:
\header {
title="The title"
composer=\markup{Composer of \italic\title }
}
{ b }
On 7/3/20 18:50, Timothy Lanfear wrote:
On 07/03/2020 14:52, Noeck wrote:
Thank yo
->string …)
did not work.
2) Can this be put in a command which I can move to a separate file?
Like \evaluateHeaders
Cheers,
Joram
Ok, so here is an example of a function to create a bookpart consisting
of a single blank page by clearing all the header variables. It should
give some cl
> Does this solve your problem?
> …
> copyright = \markup \concat { "© " \fromproperty #'header:author }
Thank you, Timothy,
this is how far I got already. It is probably a step in the right
direction. But there are two issues with it:
1) I would like to use some Scheme code on the fields
1 - 100 of 747 matches
Mail list logo
