Hi Michael,
Am 09.12.2011 um 21:23 schrieb André Wobst:
> ... just browsing the source code, doesn't look difficult at all ...
changeset 3234 introduces a pfm fallback to the preferred afm font metrics to avoid approximations of font properties in the PDF font descriptor. This silences the warning about missing metric information when no afm is available but a pbm is installed in the same directory as the pfb file. It would be great if you could check whether this works for you. I did some tests here, but just using the good old cmr10
André
--
by _ _ _ Dr. André Wobst, Amselweg 22, 85716 Unterschleißheim
/ \ \ / ) wobsta@..., http://www.wobsta.de/
/ _ \ \/\/ / PyX - High quality PostScript and PDF figures
(_/ \_)_/\_/ with Python & TeX: visit http://pyx.sourceforge.net/

Hi Michael,
you know what? PyX can use PFM files itself! However, this needs some LaTeX integration. :-/
... just browsing the source code, doesn't look difficult at all ...
André
Am 09.12.2011 um 10:15 schrieb Michael J Gruber:
> André Wobst venit, vidit, dixit 09.12.2011 00:44:
>> Hi Michael,
>>
>> Am 07.12.2011 um 23:45 schrieb Michael J Gruber:
>>> Wow, that is quite some news. What does this mean for commercial
>>> fonts which are sold without the afm, but specifically to be used
>>> with TeX? MTPro2 is meant to produce high quality type setting with
>>> LaTeX, and is used by some journals, for example.
>>
>>
>> Technically a Type1 font without an AFM file is incomplete. (There is
>> a very, very old and awfully bad alternative called PFM font metric;
>> in case you have this one, there is the possibility to extract the
>> date from that too.) Also it might be, that all the information is
> [...]
>
> Thanks for this and all the other info! It shows (again) how much
> insight went into PyX.
>
> For the record: PCteX hasn't yet answered my request for MTPro2 afms,
> but the set comes with pfms. "pf2afm" (from the ghostscript) package
> happily created foo.afm ("pf2afm foo"), using foo.pfb and foo.pfm, for
> all my foo from MTPro2.
>
> This (after putting the afms in the proper place) quelled the PyX
> warnings, of course. I assume it will matter for xetex/luatex also.
>
> Cheers,
> Michael
--
by _ _ _ Dr. André Wobst, Amselweg 22, 85716 Unterschleißheim
/ \ \ / ) wobsta@..., http://www.wobsta.de/
/ _ \ \/\/ / PyX - High quality PostScript and PDF figures
(_/ \_)_/\_/ with Python & TeX: visit http://pyx.sourceforge.net/

André Wobst venit, vidit, dixit 09.12.2011 00:44:
> Hi Michael,
>
> Am 07.12.2011 um 23:45 schrieb Michael J Gruber:
>> Wow, that is quite some news. What does this mean for commercial
>> fonts which are sold without the afm, but specifically to be used
>> with TeX? MTPro2 is meant to produce high quality type setting with
>> LaTeX, and is used by some journals, for example.
>
>
> Technically a Type1 font without an AFM file is incomplete. (There is
> a very, very old and awfully bad alternative called PFM font metric;
> in case you have this one, there is the possibility to extract the
> date from that too.) Also it might be, that all the information is
[...]
Thanks for this and all the other info! It shows (again) how much
insight went into PyX.
For the record: PCteX hasn't yet answered my request for MTPro2 afms,
but the set comes with pfms. "pf2afm" (from the ghostscript) package
happily created foo.afm ("pf2afm foo"), using foo.pfb and foo.pfm, for
all my foo from MTPro2.
This (after putting the afms in the proper place) quelled the PyX
warnings, of course. I assume it will matter for xetex/luatex also.
Cheers,
Michael

On Thu, Dec 8, 2011 at 02:46, Blair Hall <b.hall@...> wrote:
> I have just tried to install the latest PyX 0.11.1, but I failed miserably.
You can work with a revision from SVN. You can setup.py install it, or
use it straight from the working copy.
I run on r3231 and it works on my WinXP. The current head (r3233)
should be fine too.