> IIRC, the problem is that mftrace reads system installed AFMs,
> (eg. from a 2.4 release in /usr) using kpsewhich, extracting foundry
> and font name from there. I believe I fixed that bug some time ago.
> What version of mftrace do you run?
I use version 1.1.1 -- anyway, the problem is gone n
[EMAIL PROTECTED] writes:
> Hi,
>
> On Mon, 17 Jan 2005, Werner LEMBERG wrote:
>
> > > > > Is there interest in this for www.lilypond.org?
> > > >
> > > > No. It's not our own server, and we're sucking up too much
> > > > bandwidth as it is.
> > >
> > > I didn't know that... Pity.
> >
> > In case
[EMAIL PROTECTED] writes:
> Hello,
>
> On Fri, 14 Jan 2005 11:45:46 +0100, Han-Wen Nienhuys <[EMAIL PROTECTED]>
> wrote:
> > * use (list->vector (map number->character (iota 26))) to contruct
> > the vector
> integer->char perhaps? I've done something similar. Patch is against
> cvs, does it l
[EMAIL PROTECTED] writes:
>
> Currently, we have the funny situation that the DVI output of a
> LilyPond document created with `-b tex' can be viewed with xdvi (using PS
> fonts) but the result of dvips doesn't work at all, inspite of
> correctly loading all fonts.
>
> Reason is that lilypond.map
On 16-Jan-05, at 9:14 AM, Mats Bengtsson wrote:
The relevant properties are called |soloText||, soloIIText| and
aDueText.
It seems that some information on these properties are missing in the
manual.
The only place I could find the documentation of them is in
http://lilypond.org/doc/v2.4/Docume
What's the new naming convention for nodes? For example, I see:
@node Harmonic notes, , Other instrument specific notation, Other
instrument specific notation
@node Popular music, Orchestral music, Tablatures, Notation manual
@node Chord names, Chords mode, Popular music, Popular music
but later
On 10-Jan-05, at 5:41 AM, Mats Bengtsson wrote:
- I normally use a separate identifier for annotations like
tempo changes ("Andante", ...) that should only appear on the
top of the full score but in all the individual parts. Of course,
such a thing can also be done with \tag commands, but it
On 7-Jan-05, at 1:33 AM, Mats Bengtsson wrote:
Since the identifier \RemoveEmptyStaffContext is defined in
ly/engraver-init.ly, its definition will not change when you
redefine the \Staff identifier in you .ly file. If you think about
it, you will realize that this "bug" is the only way to make it
On 6-Jan-05, at 1:29 PM, Nicolas Sceaux wrote:
Speaking of \keepWithTag, I usually use a custom version of it,
that let me write:
\keepWithTag #'tag1 music
or
\keepWithTag #'(tag1 tag2 ...) music
or
\keepWithTag #'() music
(the last one being the same as \removeWithTag)
So your version adds t
Matthias Neeracher <[EMAIL PROTECTED]> writes:
> It seems that 2.5.8 now needs bison 2.0, due to its use of %locations
> (not sure when that was introduced, but it does not work in 1.28). The
> documentation says bison 1.25 or higher is required, so that probably
> should be changed.
What I have
> Have you rebuilt the fonts lately (I can hardly imagine you haven't
> with all your work on mf sources)?
Yes. I always build lilypond from scratch, never updating the sources
-- maybe I've done something wrong. Will try again today.
Werner
_
> Basically, it doesn't matter at all since the .enc files are for
> documentation purposes only.
After the font has been created -- and in the font itself the encoding
vector has no name.
Werner
___
lilypond-devel mailing list
lilypond-devel@g
Werner LEMBERG writes:
> Reason is that lilypond.map (needed for dvips) is created incorrectly.
> It blindly assumes that the PS font name is identical to the file
> name, but this is a wrong assumption. See the table below. I tried
> to fix it, but the heck I'm not able to find the place where
Currently, we have the funny situation that the DVI output of a
LilyPond document created with `-b tex' can be viewed with xdvi (using PS
fonts) but the result of dvips doesn't work at all, inspite of
correctly loading all fonts.
Reason is that lilypond.map (needed for dvips) is created incorrect
> > * buildscripts/mf-to-table.py: Use `FetaAlphabetEncoding' for
> > feta-alphabet*.
>
> Why is this? feta-alphabet is ascii encoded.
It was `FetaEncoding' which is definitely wrong. Having
StandardEncoding or something similar is perhaps a bad idea also since
it implies the availabili
Hi,
On Mon, 17 Jan 2005, Werner LEMBERG wrote:
> > > > Is there interest in this for www.lilypond.org?
> > >
> > > No. It's not our own server, and we're sucking up too much
> > > bandwidth as it is.
> >
> > I didn't know that... Pity.
>
> In case you have the bandwidth you could set something up
Werner LEMBERG writes:
> Log message:
> * buildscripts/mf-to-table.py: Use `FetaAlphabetEncoding' for
> feta-alphabet*.
Why is this? feta-alphabet is ascii encoded.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien
17 matches
Mail list logo
