> > > On my system `pkg-config --cflags pangoft2' correctly returns
> > > the path to the top pango header directory
> > > (-I/usr/local/include/pango-1.0). A missing call to pkg-config?
After further inspection I found this problematic code in
configure.in:
# This is developer only anyway, h
[EMAIL PROTECTED] writes:
> Hi.
> In scm/define-markup-commands.scm,
> \sharp, \flat, etc. and \note-by-number are
> looking up wrong glyph-strings (in CVS).
> I attatch a patch for this problem.
>
> Tatsuya.
Thanks!
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanw
[EMAIL PROTECTED] writes:
> > * Remove all support code for encoding within LilyPond. [...]
> > Encoding is either handled by (La)TeX, or by Pango. This means
> > that
> >
> > \encoding
> >
> > will disappear, as will the inputencoding field in \layout{}
>
> We need a new command to se
[EMAIL PROTECTED] writes:
>
> > > how do you think we should handle encoding for the TeX backend? I
> > > am tempted to just dump
> > >
> > > \usepackage[utf8]{inputenc}
> > >
> > > [...]
> > >
> > > we still need to do something with encoding, to
> > >
> > > 1. dump the appropriate \usepackage
Hi.
In scm/define-markup-commands.scm,
\sharp, \flat, etc. and \note-by-number are
looking up wrong glyph-strings (in CVS).
I attatch a patch for this problem.
Tatsuya.
patch
Description: Binary data
___
lilypond-devel mailing list
lil
> * Remove all support code for encoding within LilyPond. [...]
> Encoding is either handled by (La)TeX, or by Pango. This means
> that
>
> \encoding
>
> will disappear, as will the inputencoding field in \layout{}
We need a new command to select the backend -- I propose \TeXformat
and
> > how do you think we should handle encoding for the TeX backend? I
> > am tempted to just dump
> >
> > \usepackage[utf8]{inputenc}
> >
> > [...]
> >
> > we still need to do something with encoding, to
> >
> > 1. dump the appropriate \usepackage headings
> >
> > 2. select a reasonable guessti
> I thought that you had once told me that that Latin1 is a subset of
> UTF-8.
Latin1 is a subset of *Unicode*, not of UTF-8. Any character code
>= 0x80 is represented with two or more bytes in UTF-8.
> Or should we be using a different unicode->bytes layout scheme?
Where exactly is the proble
> > On my system `pkg-config --cflags pangoft2' correctly returns the
> > path to the top pango header directory
> > (-I/usr/local/include/pango-1.0).
> >
> > A missing call to pkg-config?
>
> did you rerun autoconf and do configure once again?
I *always* start with a fresh CVS, doing ./autogen.
