I'd like to get some Postscript Type1 fonts working with MK IV
(installed via the minimals under Linux). I placed the *.pfb fonts
in ~/.fonts and did:
mtxrun --script fonts --reload
mtxrun --script fonts --list --all --pattern=*
...but the output doesn't show any of the *.pfb fonts. The *
Am 28.08.10 01:16, schrieb John Magolske:
I'd like to get some Postscript Type1 fonts working with MK IV
(installed via the minimals under Linux). I placed the *.pfb fonts
in ~/.fonts and did:
mtxrun --script fonts --reload
mtxrun --script fonts --list --all --pattern=*
...but the ou
On 28-8-2010 1:16, John Magolske wrote:
I'd like to get some Postscript Type1 fonts working with MK IV
(installed via the minimals under Linux). I placed the *.pfb fonts
in ~/.fonts and did:
mtxrun --script fonts --reload
mtxrun --script fonts --list --all --pattern=*
but the outp
* Hans Hagen [100828 15:34]:
> On 28-8-2010 1:16, John Magolske wrote:
>> I'd like to get some Postscript Type1 fonts working with MK IV
>> (installed via the minimals under Linux).
>
> put the afm files in the tree as well
>
> - either in the afm subtree (with pfb's in the type1 subtree)
> - or i
On 08/29/2010 08:50 AM, John Magolske wrote:
Is it inherently tricky to get Type1 PS Mac fonts working with ConTeXt
& luatex on Linux?
It should not be.
Also, the SabonLT-Roman.afm file that came from Linotype has a section
titled "StartKernData", but .afm files generated using type1afm,
fo
* Taco Hoekwater [100829 00:24]:
> On 08/29/2010 08:50 AM, John Magolske wrote:
>>
>> Is it inherently tricky to get Type1 PS Mac fonts working with ConTeXt
>> & luatex on Linux?
>
> It should not be.
>
>> load afm> reading /home/john/.fonts/SomeMacintoshPSfont.afm
>
> Why the odd afm name? Is
On 08/29/2010 10:11 AM, John Magolske wrote:
Anyhow, to re-cap, I did:
* go to the iMac& find a font named "SomeMacintoshPSfont"
* use Fontforge to generate "SomeMacintoshPSfont.pfb"
* use the type1afm utility to generate "SomeMacintoshPSfont.afm"
* put these pfb& afm files in the ~/.fonts di
On Sat, Aug 28, 2010 at 11:50:38PM -0700, John Magolske wrote:
>
> Also, the SabonLT-Roman.afm file that came from Linotype has a section
> titled "StartKernData", but .afm files generated using type1afm,
> fontforge, font2afm, etc. have no kerning section. Would using such
> .afm files cause sub-
* Khaled Hosny [100829 08:37]:
> On Sat, Aug 28, 2010 at 11:50:38PM -0700, John Magolske wrote:
> >
> > Also, the SabonLT-Roman.afm file that came from Linotype has a section
> > titled "StartKernData", but .afm files generated using type1afm,
> > fontforge, font2afm, etc. have no kerning section
On Sun, Aug 29, 2010 at 11:17:18PM -0700, John Magolske wrote:
> * Khaled Hosny [100829 08:37]:
> > On Sat, Aug 28, 2010 at 11:50:38PM -0700, John Magolske wrote:
> > >
> > > Also, the SabonLT-Roman.afm file that came from Linotype has a section
> > > titled "StartKernData", but .afm files genera
* Khaled Hosny [100830 18:29]:
> Try Taco's suggestion, I myself got unpredictable results with ~/.fonts,
> try instead ~/texmf/fonts/{afm,type1} or even ~/texmf/fonts/data
Thanks! This solved my problem:
% mkdir -p ~/texmf/fonts/data
% mv *.{pfb,afm} ~/texmf/fonts/data
% export OSFONTDIR=
On 08/31/2010 08:27 AM, John Magolske wrote:
* Khaled Hosny [100830 18:29]:
Try Taco's suggestion, I myself got unpredictable results with ~/.fonts,
try instead ~/texmf/fonts/{afm,type1} or even ~/texmf/fonts/data
We should try to find what is causing the erratic behavior of ~/.fonts
Best wi
On 08/31/2010 09:31 AM, Taco Hoekwater wrote:
On 08/31/2010 08:27 AM, John Magolske wrote:
* Khaled Hosny [100830 18:29]:
Try Taco's suggestion, I myself got unpredictable results with ~/.fonts,
try instead ~/texmf/fonts/{afm,type1} or even ~/texmf/fonts/data
We should try to find what is cau
On Mon, Aug 30, 2010 at 11:27:00PM -0700, John Magolske wrote:
> * Khaled Hosny [100830 18:29]:
> > Try Taco's suggestion, I myself got unpredictable results with ~/.fonts,
> > try instead ~/texmf/fonts/{afm,type1} or even ~/texmf/fonts/data
>
> Thanks! This solved my problem:
>
> % mkdir -p ~
On Tue, Aug 31, 2010 at 11:19:50AM +0200, Taco Hoekwater wrote:
> On 08/31/2010 09:31 AM, Taco Hoekwater wrote:
> >On 08/31/2010 08:27 AM, John Magolske wrote:
> >>* Khaled Hosny [100830 18:29]:
> >>>Try Taco's suggestion, I myself got unpredictable results with ~/.fonts,
> >>>try instead ~/texmf/f
On Tue, 31 Aug 2010, Khaled Hosny wrote:
On Tue, Aug 31, 2010 at 11:19:50AM +0200, Taco Hoekwater wrote:
On 08/31/2010 09:31 AM, Taco Hoekwater wrote:
On 08/31/2010 08:27 AM, John Magolske wrote:
* Khaled Hosny [100830 18:29]:
Try Taco's suggestion, I myself got unpredictable results with ~/
* Khaled Hosny [100831 13:16]:
> On Mon, Aug 30, 2010 at 11:27:00PM -0700, John Magolske wrote:
> >
> > % mkdir -p ~/texmf/fonts/data
> > % mv *.{pfb,afm} ~/texmf/fonts/data
> > % export OSFONTDIR="$HOME/.fonts;$HOME/texmf/fonts/data"
>
> I think the OSFONTDIR is unnecessary here, context
17 matches
Mail list logo
