Op zaterdag 26 januari 2008, schreef Werner LEMBERG:
> > > font_family: parmesan22.45
> > > font_identifier: parmesan22.45
> > > [...]
> > >
> > > Font family, name and identifier should be 23, right?
> >
> > Yes, I think so, for backwards compatibility. Will look
> > font_family: parmesan22.45
> > font_identifier: parmesan22.45
> > [...]
> >
> > Font family, name and identifier should be 23, right?
>
> Yes, I think so, for backwards compatibility. Will look at it soon.
> Thanks for investigation!
This is fixed now in th
Op zondag 20 januari 2008, schreef John Mandereau:
> I've experienced problems with latest clean build of Git branch master,
> with new mf->pfb conversion by mf2pt1: dynamics and time signatures are
> sometimes printed with some Helvetica font instead of feta-alphabet.
Same here, and also the syst
> With global staff size 20, everything is ok. When using other staff
> sizes, LP fails to find the correct feta-alphabet font, and therefore
> it's not included in the .ps and .pdf output. It seems that mf2pt1
> gives the fonts wrong names, thats why LP fails to find them:
Aah, yes! I've n
... and here's the output of "strings mf/out/feta-alphabet*.pfb | grep
FontName":
[15:52:21][Macintosh-2]src/lilypond.git% strings mf/out/feta-
alphabet*.pfb | grep FontName
/FontName /feta-alphabet11.22-Medium def
/FontName /feta-alphabet12.6-Medium def
/FontName /feta-alphabet14.14-Medium d
Some input to this problem:
With global staff size 20, everything is ok. When using other staff
sizes, LP fails to find the correct feta-alphabet font, and therefore
it's not included in the .ps and .pdf output. It seems that mf2pt1
gives the fonts wrong names, thats why LP fails to find th
> Yes, he has, and he made some other changes too;
Ah, ok.
> I played a bit with git bisect, running "make clean && make" each
> time, and found that at least one of these commits caused this font
> selection problem: [...]
I'm abroad with a slow internet connection (and limited time) so I
won'
Werner LEMBERG wrote:
> Hmm. But the current master branch doesn't call mf2pt1 at all,
> AFAIK... Han-Wen hasn't merged yet his changes into the master
> branch, has he?
Yes, he has, and he made some other changes too; I played a bit with git
bisect, running "make clean && make" each time, and f
> > Please use the update mf2pt1 files which I've committed to the
> > main branch.
>
> You mean 68ffa130b219bee4a3dec6dbb65f92a660d19552 "Important update
> to mf2pt1 2.4.3", don't you?
Yes.
> I built with current master branch, I'm sure I didn't miss it.
Hmm. But the current master branch do
Le dimanche 20 janvier 2008 à 11:55 +0100, Werner LEMBERG a écrit :
> > I've experienced problems with latest clean build of Git branch
> > master, with new mf->pfb conversion by mf2pt1:
>
> Please use the update mf2pt1 files which I've committed to the main
> branch.
You mean 68ffa130b219bee4a3
> I've experienced problems with latest clean build of Git branch
> master, with new mf->pfb conversion by mf2pt1:
Please use the update mf2pt1 files which I've committed to the main
branch.
> dynamics and time signatures are sometimes printed with some
> Helvetica font instead of feta-alphabet.
Hello,
I've experienced problems with latest clean build of Git branch master,
with new mf->pfb conversion by mf2pt1: dynamics and time signatures are
sometimes printed with some Helvetica font instead of feta-alphabet.
This doesn't happen all the time, though, it seems to happen randomly:
in many
12 matches
Mail list logo
