Re: [frogs] chord_name_engraver - help with c++ ...

[Wols Lists <antlists@xxxxxxxxxxxxxxx>]

On 06/07/11 22:04, Jan Warchoł wrote:
> Could you prepare a formal patch? You'll need to modify
> lilypond-git/Documentation/notation/chords.itely, around line 450.
> Look at adjacent code to see how it should be formatted.

Done. Not sure how well I've done it - I don't know where to find the
"make" output to take a look at it :-) ... hmmm - I've looked at the
docu and it seems not to be created by default, and needs apache, etc
etc etc

Anyways, it didn't seem that difficult, except I haven't twigged what
@funindex is for, so haven't used it - should I have?

Cheers,
Wol

From 5da87456d11663f10ff2aab0e3e2ea63b6b42c36 Mon Sep 17 00:00:00 2001
From: Wol <anthony@xxxxxxxxxxxxxxx>
Date: Wed, 6 Jul 2011 23:42:34 +0100
Subject: [PATCH 3/3] Documentation for the capoPitch chordname property

---
 Documentation/notation/chords.itely |   27 +++++++++++++++++++++++++++
 1 files changed, 27 insertions(+), 0 deletions(-)

diff --git a/Documentation/notation/chords.itely b/Documentation/notation/chords.itely
index 1109075..12e9390 100644
--- a/Documentation/notation/chords.itely
+++ b/Documentation/notation/chords.itely
@@ -506,6 +506,33 @@ Rests passed to a @code{ChordNames} context will cause the
 }
 @end lilypond
 
+@cindex Transposing guitar chords for capo
+
+If the @code{capoPitch} property is set, then the chords will additionally be printed
+transposed for a guitar with the capo set appropriately.
+
+In make-pitch, leave the first argument at 0, the second argument is the
+interval (-2 is a third), and the third argument adjusts it up or down a
+semitone.
+
+@lilypond[verbatim,quote,ragged-right]
+<<
+  \new ChordNames \chordmode {
+    c1
+    b1
+    g1
+    c1
+  }
+  \set ChordNames.capoPitch = #(ly:make-pitch 0 -2 -1/2)
+  \chordmode {
+    c1
+    b1
+    g1
+    c1
+  }
+>>
+@end lilypond
+
 @snippets
 
 @c Keep index entries with following snippet
-- 
1.7.3.4