> -Original Message-
> From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 18, 2004 2:10 PM
>
> I would like to start integrating your file into scm/fret-diagrams.scm
> - however, could I ask you to use hyphenated chord names?
> When fret-diagrams.scm enters the Lilypon
[EMAIL PROTECTED] writes:
>
>
> > -Original Message-
> > From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> > [...]
> > I would like to start integrating your file into scm/fret-diagrams.scm
> > - however, could I ask you to use hyphenated chord names?
> > When fret-diagrams.scm enters
On Tue, 18 May 2004 15:43:07 -0600 "Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
>
>
> > -Original Message-
> > From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> > [...]
> > I would like to start integrating your file into
> scm/fret-diagrams.scm
> > - however, could I ask you to use h
On Tue, 2004-05-18 at 09:57, Werner LEMBERG wrote:
> > > So what I'm actually/probably looking for is something like:
> > >
> > > pango_addchar (&string, "font", "lilypond-feta, r16",
> > > "char-name", "noteheads-0", 0);
> >
> > Generally, I think we'd leave this up to the applic
> -Original Message-
> From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
> [...]
> I would like to start integrating your file into scm/fret-diagrams.scm
> - however, could I ask you to use hyphenated chord names?
> When fret-diagrams.scm enters the Lilypond distribution, we
> have to t
[EMAIL PROTECTED] writes:
> I've been toying with the implications of developing a fret-diagram
> context and engraver. It seems to me that one of the major benefits to
> having a context and engraver, rather than a markup, is that it allows
> transposition to be applied to music expressions. But
[EMAIL PROTECTED] writes:
> > directory. Then one can use the script you
> > wrote by adding just one line in the beginning of the file:
> >
> > \include "fret-diagram-init.ly"
> >
> > By adding this line into "ly/declarations-init.ly", one may
> > use the scripts even without any extra
> 1. find out what freetype does, ie, where feta charaters get
> mapped,
Since the feta fonts don't contain a single character which could be
mapped directly to Unicode, no Unicode cmap is constructed at all.
Instead, FreeType uses the artificial platform/encoding ID pair (7,2)
-- `7' is T
