[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font
From: |
Neil Puttock |
Subject: |
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font |
Date: |
Tue, 26 Jul 2011 21:47:10 +0100 |
On 26 July 2011 21:33, Graham Percival <address@hidden> wrote:
> I think this is the best solution as well. It might be nice to
> add a bit more documentation about how somebody who really
> disliked the new font could go about replacing it, but we've never
> viewed documentation as holding back programming work in the past.
> So go for it.
Since my suggestion appears to have passed most people by (probably my
own fault for its obscurity :), I'll reiterate: why not add support
for switching to the old-style clef via the \clef command? This only
requires a suitable name for the old clef and two single-line
additions to scm/parser-clef.scm (assuming the metafont code for the
old clef remains).
Cheers,
Neil
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 2011/07/25
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 2011/07/25
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 2011/07/25
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 2011/07/27
Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 2011/07/27