cgnieder / leadsheets Goto Github PK

Hi,

I have a problem which is easily illustrated in the following picture:

As you can see, the chords slide down vertically when there is enough space in the line below.
How can I prevent this?

My code is quite normal:

\begin{chorus}
	%refrain

	^{C} I'm here without you baby, ^{G} But you're still on my lonely ^{Am}mind  

	I think about you baby ^{F}and  I dream a^{G}bout  you all the  ^{C}time 

	I'm here without you baby, ^{G}  But you're still with me in my ^{Am}dreams ,
                            
	And to^{F}night , there's  ^{G}only  you and ^{C}me   ^{G}yeah .  ^{Am}  ^{F}  ^{G} 
\end{chorus}

Thanks in advance, love the project.
Taxel

I have this song-snippet:

\begin{document}
\begin{song}[remember-chords]{title={Zwergentrinklied II}}
\begin{verse}
doch ^{D}heut sind wir hier ^{E}beisammen und das ^{D}Gestern ^{E}scheint so ^{A}fern.
\end{verse}
\begin{verse}
Heute ^messen wir uns nicht mit ^Äxten, sondern  ^besten^falls mit ^Bier!
\end{verse}
\end{song}
\end{document}

Error message:

! Package inputenc Error: Invalid UTF-8 byte sequence.See the inputenc package documentation for explanation.Type H <return> for immediate help.... \end{song}

Workaround: I set a class for the second verse and wrote the chords again in it.

Currently it is not possible (or maybe I was just not able to get it right) to use dotted rests. It would be nice if one could use \*quarterrest (or similar) to print a dotted quarter rest.

When I use the ^ shortcut for recalling chords in a verse-environment I get the error

! LaTeX Error: Invalid UTF-8 byte sequence (<c4>\group_end:).

I created a minimal example with which I get this error:

\documentclass{article}

\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage[slovene]{babel}

\usepackage{leadsheets}

\setleadsheets{empty-chord-dim=0pt,smash-chords=true}

\begin{document}
	\begin{song}[remember-chords=true]{title={Example title}}

		\begin{verse}
			bol^Gj je
		\end{verse}

		\begin{verse}
			ni^č ne
		\end{verse}

	\end{song}
\end{document}

I found a workaround to this problem (using ^* {}č instead of ^č), but I don't believe this is the intended way to write this.

I'm attaching a log file of trying to generate a pdf (the command I ran is latex -output-format=pdf minimalexample.tex):
minimalexample.log

Is there any way to fix this?

How would one go about formatting it with wider margins and a larger sans-serif font? I tried the normal LaTeX commands and those didn't seem to work.

Consider the following code:

\setleadsheets{print-tags={test}}

% Gets included, as expected:
\includeleadsheet{test1.tex}  % has tag 'test'

% Doesn't get included, as expected:
\includeleadsheet{test2.tex}  % has tags 'other1', 'other2'

% Impossible to include now:
% \setleadsheets{ ?? }
\includeleadsheet{test3.tex}  % has no tags

\setleadsheets{print-tags= }  % after this, any include will be filtered out

% Doesn't get included:
\includeleadsheet{test4.tex}  % has arbitrary tags

This results in only the inclusion of file test1.tex.

After a tag filter has ben set, there is no way to include a song that doesn't have any tags.

I would like to be able to reset the print-tags option to the initial state where included leadsheets are not filtered by tag.
As far as I understand from reading the documentation as well as the code, this is currently not feasible without directly accessing package internals.

Setting an empty filter value would be an, in my opinion intuitive, syntax to disable the filtering. Even though I might find it intuitive, I'm aware that this probably isn't unambiguous.
Currently however, doing that sets the filter to an empty list. Consequently any included file will not match the filter and thus not be included.

Another option would be to pass a special value for that purpose. But then this value could never occur as an actual tag, which might pose complications of all sorts.

A third option would be to have a seperate command to switch the behaviour (e.g. \setleadsheets{print-all}).

After looking into the code, I believe that the relevant part in the code is this:

What follows is my attempt at how either the first or the last option mentioned above could be implemented. It seems to be possible with little effort (though I only recently learned expl3 syntax and might have overlooked something).

First option: \setleadsheets{print-tags=} (empty value to reset):

    print-tags           .code:n     =
      \tl_if_blank:nTF {#1}
        { \bool_set_false:N \l__leadsheets_print_selected_bool }
        {
          \bool_set_true:N \l__leadsheets_print_selected_bool
          \clist_set:Nn \l__leadsheets_print_tags_clist {#1}
        } ,

Second option: \setleadsheets{print-all} (dedicated option key):

    print-all            .bool_set_inverse:N = \l__leadsheets_print_selected_bool ,

probably extended with the inverse key print-selected for completeness:

    print-selected       .bool_set:N = \l__leadsheets_print_selected_bool ,

If either of this looks good to you, I would be happy if this got implemented. If you would like, I can also submit a pull request.
Thank you for providing this excellent package!

The URL http://www.mychemistry.eu/forums/forum/leadsheets/ in the README currently leads to a 404 error.

The leadsheet_en.tex doesn't compile due to a missing image file.

Hi @cgnieder, I really enjoy working with this package so far, but I am having trouble understanding how to use the musejazz font to work.

The main reason for my confusion is that the fonts at https://github.com/musescore/ are separated in musejazz.otf and musejazzText.otf.

leadsheets apparently only loads the first one. This is why I only see the b and # characters but not the chord itself (C#m becomes #).

Is there a musejazz font which is not separated or another way how to fix this? I would appreciate being able to use that font.

Thanks in advance
Taxel

A lyrics word might consist of multiple syllables of which each should be able to carry a chord symbol

To me, it looks like a section

\begin{intro}
^{C} ^{G} ^{C}
\end{intro}

is not transposed when a transpose option is given for a song.

Let me start off by saying I'm very new to LaTeX, so I might be doing something fundamentally flawed here.

I'd like to only specify the chorus one time, and then have it print repeatedly (chords and lyrics) in-between the verses. Some googling pointed me towards using \newcommand to define a reusable command. So, I defined my chorus inside of the it.

\documentclass{article}
\usepackage{leadsheets}
\begin{document}
\begin{song}[transpose=5,remember-chords,verse/numbered]{title={Here Comes The Sun}, band={The Beatles}, 
  key={A}}


\newcommand\mychorus
{
  \begin{chorus}
    ^{A} Here comes the sun  do doo do do \\
    ^{D} Here comes the sun, \\
    ^{B7} And I say, ^{A} It's all right \\
  \end{chorus}
}

\mychorus % This behaves as expected

\begin{verse}
  ^{A} Little darling It's been a long,^{D} cold lonely win^{E7}ter \\
  ^{A} Little darling It feels like years^{D} since it's been here^{E7} \\
\end{verse}

\mychorus % This prints the chords twice

\end{song}
\end{document}

The first usage of \mychorus behaves as I'd expect. However, the second usage prints any ^ chords two times, one right over the other. Interestingly, the lower one doesn't get transposed (maybe that's a clue 🤷).

Thank you for the wonderful library! I'm really excited to get to work moving all my old lead sheets off of Google Docs and into something much more maintainable!

Similar to what the songs package offers, an option should be provided to map the "root" names of the chord only for printing the chords in standard letters or the solfege notation (I am not proposing to define chordnames using solfege). The songs package does it with these two commands to map the letters to the Solfege notation.
\notenamesin{A}{B}{C}{D}{E}{F}{G}
\notenamesout{LA}{SI}{DO}{RE}{MI}{FA}{SOL}

The user might select the preferred output method as follows

Hello, I think it would be interesting to get the option to bring down the numbers relative to 7th, 9th, 11th, etc. chords and any other symbol in general (half-diminished, diminished etc.), as they seem to be hardwired to \textsuperscript{}. Thank you for your work on this awesome package.

There should be an option to control the space between the chordnames and the lyric line (see red arrows). The itemize template in the documentation only shows how to control the space between two lyric lines.

I am trying to include some minimal music score into the \begin{song} ... \end{song} environment. The idea is to provide at the top of the song lyric (with chords) some basic melodies for nursery rhymes e.g. "Old MacDonald has a farm".

I went with a basic Lilypond file just to try something out with the simplest melody.

I have ly/sample.ly with:

% command `lilypond --version`
\version "2.20.0"
{
  c' e' g' e'
}

Then I invoke the following command to generate sample.pdf:

cd $(PWD)/songs/ly && \
	lilypond --pdf --pspdfopt=TeX sample.ly

Then in nursery-rhymes-old-macdonald-had-a-farm.tex inside \begin{song} ... \end{song} I have:

\begin{figure}[htpb]
    \centering
    \includegraphics[width=0.8\textwidth]{ly/sample.pdf}
    \caption{The score for the main melody}
    \label{fig:sample-score}
\end{figure}

But this leads to the error ! LaTeX Error: Not in outer par mode. that I am not able to troubleshoot.

I have to say that I come from an endless list of various attempts, some of the bumps are related to the issues with the command lilypond-book not expanding LaTeX code from this leadsheets library like \includeleadsheet[gobble-preamble=false]{songs/nursery-rhymes-old-macdonald-had-a-farm.tex}.

Is this kind of flow possible at all within leadsheets?

I often use the "remember-chords"-function. Sometimes my song also has multiple choruses which have different chords.
I'd wish to use the remember-function only for a chosen verse-environment.
Currently I either leave out the remember function or I create a new environment for my alternate chorus

A solution like this would be nice-to-have:

\begin{song}[remember-chords=verse]{}

\begin{verse}
^{F}My first Verse
\end{verse}

\begin{chorus}[numbered=true]
^{C}My Chorus
\end{chorus}

\begin{verse}
^My second Verse
\end{verse}

\begin{chorus}[numbered=true]
^{G}My alternate Chorus
\end{chorus}

\end{song}

As the title says, when setting print-chords=false, the result is different from what one gets when no chord commands are included in the source. This happens with chords that are set between words (i.e. over a space), they leave a large space.

Consider the following code and its output for example.

\documentclass{leadsheet}
\begin{document}
  \begin{song}[print-chords=false,obey-lines]{}
    \begin{verse}
      One two three four.
      One ^{D}two three^{G} four.
      One ^{D}two three^*{G} four.
      One ^{D}two three^*-{G} four.
    \end{verse}
  \end{song}
\end{document}

Note that neither the starred nor the smashed version alter this behaviour. What I would expect is that at least the starred variant would gobble the space. In general though, I would expect output equivalent to omitting the chord commands when setting print-chords=false, as is the case with any chords set over text.

Also note that obey-lines doen't influence this. I just set it to make the example look a bit better.

First of all, thank you for this fantastic package.

I am encountering a problem and probably it's my own fault as I am not a TeX specialist. I am trying to add the transposed key of my songs to the Table of Contents. (Actually I want to add it to different Indexes using imakeidx with xindy, but it looks like the problem is just the same with the TOC.)
The keys are correctly transposed inside the song environment and the section title, but in the TOC they are the original key.

This is my MWE:

\documentclass[a4paper]{article}
\usepackage{leadsheets}
\usepackage[ngerman]{babel}
\usepackage{hyperref}

\setchords{
  sharp=\#,
  flat=b,
  format=\bfseries
}

\definesongproperty{transpose} % because I have to check if the property is set, and "capo" can't be negative

\definesongtitletemplate{minimal}{%
    %
    \ifsongproperty{transpose}{\setleadsheets{transpose=\songproperty{transpose}}}{}%
    %
    \section{\songproperty{title} (\expandcode{\writechord{\songproperty{key}}})}%
    }



\begin{document}

\tableofcontents

\begin{song}{
    title={The Test Song 1},
    key=Em,
    transpose=-1
    }
    \begin{verse}
        ^{C/D}Lyrics ^{D}go ^{G}here
    \end{verse}
\end{song}

\begin{song}{
    title={The Test Song 2},
    key=Em,
    transpose=1
    }
    \begin{verse}
        ^{C/Dm}Lyrics ^{D}go ^{G}here
    \end{verse}
\end{song}


\end{document}

Contents of the .toc file:

I am not sure if \expandcode{\writechord{\songproperty{key}}} is even supposed to do what I am trying to achieve. I studied the documentation over and over again, I also tried fiddling around with expansion (which I quite don't understand fully), but nothing seams to work.

Is there a way to have the correctly transposed key in TOCs and Indexes?

When I compile a minimal example I get this error. But it doesn't happen when I compile the documentation of leadsheets...

I see leadsheets uses the songs package, is it possible to print a chart diagram (gtab command)? for some reason the gtab command doesn't seem to be defined.

Greetings & thank you for this amazing library.

Do you have any option to add the bass note on a chord?

Example:

my-^{A/B}word

Thank you.

When compiling in pdflatex and xelatex, I get the following compile errors:

! LaTeX3 Error: Variant form 'cnV' deprecated for base form '\prop_gput:cnn'.
(LaTeX3)        One should not change an argument from type 'c' to type 'c':
(LaTeX3)        base form is already a variant.

Type <return> to continue.
 ...                                              
                                                  
l.45 \cs_generate_variant:Nn \prop_gput:cnn {cnV}

It seems to be in leadsheets.library.properties.code.tex.

Using leadsheets 0.6a on ubuntu

Still debugging, but I get an error for this snippet:

\begin{song}{title={What like}, interpret={Everlast}}\index{What like}
    what it's l\chord{C}ike\chord{Dm} 
\end{song}

Error:

! Argument of \__leadsheets_set_chord:nwn has an extra }.
<inserted text> 
                \par 
<to be read again> 
                   }
<argument> ...mpa_box \l__leadsheets_song_body_tl 
                                                  \leadsheets_set_property:n...

\use_ii:nnn #1#2#3->#2
                      
\__leadsheets_start_measuring:nw ...{height}{0pt}}
                                                  \__leadsheets_stop_measuri...

\leadsheets_end_song:n ...dsheets_stop_measuring: 
                                                  \tl_use:N \l__leadsheets_s...
<argument> ...-1}{\leadsheets_end_song:n {song-1}}
                                                  \group_end: \end {song}
\use_ii:nnn #1#2#3->#2
                      
l.3 \end{song}

It only happens sometimes if the last thing before \end{song} is a \chord

Some guidance:
https://texfaq.org/FAQ-extrabrace

I am trying to get my head around deep LaTeX topics - so far I've been writing "normal" stuff like maths, but I cannot figure out how to extend the standard LaTeX distribution with niche (but great!) packages like leadsheets.

As far as I understand the package when on CTAN (https://github.com/cgnieder/leadsheets) should be already included in the standard LaTeX distribution, but when I try to compile a document I get:

LaTeX2e <2020-02-02> patch level 2
L3 programming layer <2020-02-14>

! LaTeX Error: File `leadsheet.cls' not found.

Type X to quit or <RETURN> to proceed,
or enter new name. (Default extension: cls)

So I tried to figure out how to use the LaTeX package manager tlmgr like this: tlmgr install leadsheet --verify-repo=none -v, but the package is not found with the message: tlmgr install: package leadsheet not present in repository.

I have to use --verify-repo=none because for some reason Debian based Linux environments are messing with the CTAN certificates.

Is there a proper way/command/procedure of extending LaTeX functionality with leadsheets? How can I "install" leadsheets?

I would prefer to write "H"(de)/"B"(en) always as "H" while writing "B"(de)/"Bb"(en) always as "Bb".
I know it is not theoretically wrong, but for my musician colleges it is more clear to write it that way.
If I write the chords like this:

\begin{song}{}
\begin{chorus}
^{H}Eitsch and not ^{Bb}Bee
\end{chorus}
\end{song}

I get the desired Output, but transposing the song won't work in none of the possible combinations of (german/english input/output)

Is there a way to achieve it with the current version or is there a simple workaround?

Hej,
one thing I'd like very much would be an option to have all bars automatically only in the 'chord row', i.e. not disrupting the song text flow, but only subtly indicating when two chords are played in one measure. Right now I'm trying something like
^-{|C} It's easy if ^{Cmaj7}you ^-{|F}try \\
but it would be much more convenient if there was an option for this.

I'm currently in the process of redoing a songbook that is maintained in Word. Till now I used the songs package but I is kind of inflexible. leadsheets seems to be the nicer option but I have one problem which is formatting words with one then one chord. If I add more then one the layout gets messed up.

with second chord

without second chord

source

\documentclass{article}
\usepackage[full]{leadsheets}
\usepackage[utf8]{inputenc}
\usepackage[ngerman]{babel}
\usepackage{array}
\usepackage{lmodern}

\setleadsheets{
  verse/numbered = true,
  align-chords = l
}

\begin{document}

\begin{song}{title={Die Moorsoldaten}}
\begin{verse}
^{e}Wohin auch das Auge blicket, ^{a}Moor und ^{e}Heide ^{H7}nur rings^{e}um. \\
^{G}Vogelsang uns nicht erquicket, ^{a}Eichen ^{e}stehen ^{H7}kahl und ^{e}krumm.
\end{verse}

\begin{chorus}[name={R}]
^{D}Wir ^{G}sind die Moorsol^{D}daten und ^{e}ziehen mit dem ^{H7}Spaten ins ^{e}Moor.
\end{chorus}

\begin{verse}
^{e}Hier in dieser öden Heide ^{a}ist das ^{e}Lager ^{H7}aufgeb^{e}aut, \\
^{G} wo wir fern von jeder Freude ^{a}hinter Stachel^{H7}draht ver^{e}staut.
\end{verse}

\begin{verse}
^{e}Morgens ziehen die Kolonnen ^{a}in das ^{e}Moor zur ^{H7}Arbeit ^{e}hin, \\
^{G}graben bei dem Brand der Sonnen, ^{a}doch zur Heimat ^{H7}steht der ^{e}Sinn.
\end{verse}

\begin{verse}
^{e}Heimwärts, heimwärts! Jeder sehnet ^{a}sich nach ^{e}Eltern, ^{H7}Weib und ^{e}Kind. \\
^{G}Manche Brust ein Seufzer dehnet, ^{a}weil wir ^{e}hier ge^{H7}fangen ^{e}sind.
\end{verse}

\begin{verse}
^{e}Auf und nieder geh’n die Posten, ^{a}keiner, ^{e}keiner ^{H7}kann hin^{e}durch. \\
^{G}Flucht wird nur das Leben kosten, ^{a}vierfach ^{e}ist um^{H7}zäunt die ^{e}Burg.
\end{verse}

\begin{verse}
^{e}Doch für uns gibt es kein Klagen: ^{a}ewig ^{e}kann’s nicht ^{H7}Winter ^{e}sein. \\
^{G}Einmal werden froh wir sagen: ^{a}Heimat, ^{e}du bist ^{H7}wieder ^{e}mein!
\end{verse}
\end{song}

\end{document}

I'm finding use for explicitly referring to chords with a missing 5th, so I've patched in functionality for that. PR incoming.

Trying the example given in section 8.1. A First Example of the manual give me the error
./test3.tex:19: LaTeX Error: Variable \l__leadsheets_songs_height_prop undefined.
Example tested (taken from p. 14 of the documentation):
\documentclass{article}
\usepackage{leadsheets}
\begin{document}

\begin{song}{title={Mary Had A Little Lamb}, music={Stevie Ray Vaughan},
lyrics={traditional}, tags={srv,blues}}
\begin{verse}
Mary had a little lamb \
Its fleece was white as snow, yea \
Everywhere the child went \
The little lamb was sure to go, yea
\end{verse}
\begin{verse}
He followed her to school one day \
And broke the teacher's rule \
What a time did they have \
That day at school
\end{verse}
\end{song}

\end{document}

I am trying to create a PDF index from the sections of a document using the hyperref package. When the \section comes from the leadsheets songtemplate, the "Umlauts" coming form the song properties are not displayed correctly.

This test document can reproduce the issue:

\documentclass{scrartcl}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage[ngerman]{babel}

\usepackage{hyperref}

\usepackage{leadsheets}

\setleadsheets{title-template=custom}

\definesongtitletemplate{custom}{\section{\songproperty{interpret}}}

\begin{document}

\section{ÄÖÜ 1}
hello world

\begin{song}{interpret={ÄÖÜ 2}}
\begin{verse}
^{Em}hello ^{Am}world
\end{verse}
\end{song}

\section{ÄÖÜ 3}
hello world

\end{document}

I have used the lastest texlive docker image to create the PDF:

docker run -ti -v "$(pwd):/data" -w /data --user $UID:$UID texlive/texlive pdflatex test.tex

In the resulting PDF file, the index entry coming from the template is broken:

Currently, wrapfigure does not work to place verse text and images side-by-side. This would be a nice feature to add images to songbooks.

Minimal working example:

\documentclass{article}
\usepackage{graphicx}
\usepackage{wrapfig}
\usepackage{leadsheets}

\begin{document}

\begin{song}{title=test}
  \begin{verse}
    This ^{A}is a verse \\
    This ^{A}is a verse \\
    This ^{A}is a verse \\
    This ^{A}is a verse \\
    This ^{A}is a verse \\
    This ^{A}is a verse \\
    This ^{A}is a verse \\
    This ^{A}is a verse \\
    This ^{A}is a verse \\
    This ^{A}is a verse \\
    This ^{A}is a verse \\
    This ^{A}is a verse \\
    This ^{A}is a verse \\
  \end{verse}
  \begin{wrapfigure}{R}{0.3\textwidth}
    \centering
    \includegraphics[width=0.25\textwidth]{example-image-a}
  \end{wrapfigure}
\end{song}

\end{document}

A long song will sometimes need more than one page, especially if printed on small paper formats like A5.

AFAIK leadsheets currently has no option to do a pagebreak only between verse-like environments (this means a Verse-like Environment is never broken and always on one page). I tried
\pagebreak[3]

This moves up to three lines according to my experiments, but that is not enough in all cases. Of course I could use \pagebreak[4], but this forces me to rework the whole book after every Change.

Another idea:

\nopagebreak
begin{verse}
    …
end{verse}

…

does nothing. AFAIK it is because of the \itemize environment used internally.

For Reference see the following example.
test.tex
(Renamed from "test.tex")
test.pdf

This is either a request for a feature or for support, I think.

PS. Please Note that this is my first github issue. I may still have a lot to learn.

Using the external library with LaTeX 3 results in the error

! LaTeX3 Error: Use \file_get:nnN not \tl_set_from_file:Nnn deprecated on
(LaTeX3) 2021-01-01. For 6 months after that date one can restore a
(LaTeX3) deprecated command by loading the expl3 package with the
(LaTeX3) option 'undo-recent-deprecations'.

when trying to use the \includeleadsheet[]{} command.

Hyphenation does not work for long words containing chords. The long word is printed beyond the right margin. The word on the lyric line with chord should be hyphenated or moved to the next lyric line

I want to incorporate information about use of capodaster (and write song text with needed transposition). Since transposition works just OK, there is a problem with \capo command used in title-template. If command \capo is used within song environment - it works OK, but placed in tittle-template - does strange things (just prints "*" if used with capo property checking or "Capo: . fret" otherwise).

Am I doing something against Author's intention or is it a bug?

when trying to use the musejazz library.

Although package leadsheets is exactly what I need to create simple songbook to sing with friends, there are two "small" features/enchantments that could make it even more nice:

1. There is a common practice to put chords at the end of each line of text instead of over it – it's useful when you just play guitar and singing is not your best thing to do or just to print songbook in more compact form. Maybe it could be done as a style/option for verse-like environments (to switch style – just for given song or whole songbook)?
2. Sometimes minor chords are noted as "d" instead "Dm" – actually it's kind of standard in popular Polish songbooks. Is there an easy way to "learn" transposer of different notations? On the other hand – we follow German notation with A-B-H-C but sometimes something like A-A#-H-C could be spotted :) This is rather "cosmetic" change, so it's not the first thing to do.