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
