Patrick Gundlach wrote:
Hi,
Just list another one, font files received from the vendor is usually
in capital
letters, such as PJN_.PFB, but the copy_files routine in texfont.pl only
copy *.pfb, then all the type1 files will not be copy to texmf...
This, of course, is a problem
Patrick Gundlach 写道:
Hi,
Then we must have different texfont.pl version. Each time afm2tfm is
called, it uses either -T or -p. Running afm2tfm without those
parameters doesn't make very much sense. (Unless you are an english
speaking person that never typesets foreign languages.)
Hi,
Just list another one, font files received from the vendor is usually
in capital
letters, such as PJN_.PFB, but the copy_files routine in texfont.pl only
copy *.pfb, then all the type1 files will not be copy to texmf...
This, of course, is a problem that should be addressed. But I
jjgod wrote:
Patrick Gundlach mailto:patrick.at.gundla.ch wrote:
Then we must have different texfont.pl version. Each time afm2tfm is
called, it uses either -T or -p. Running afm2tfm without those
parameters doesn't make very much sense. (Unless you are an english
speaking person that
Taco Hoekwater wrote:
There are in total 4 calls to aftm2tfm in the script, of which the
second and third use '-p' also (check the value of $encstr). The last
one is a 'panic response' if nothing else seems appropriate.
Well, let's search the script from top to bottom:
1. { my $command =
jjgod wrote:
Well, let's search the script from top to bottom:
1. afm2pl does NOT invoke afm2tfm, even with -f afm2tfm option
(you can check this in the source code of afm2pl by yourself)
You are right, sorry. So only three calls to afm2tfm in total.
Is there an afm2pl executable in miktex,
jjgod wrote:
Did you contact the MikTeX maintainers about that?
It seems the MikTeX maintainer have noticed that, but
no official bugfix release at present.
afaik it is/will-be fixed in the latest release
Hans
-
Hi,
Then we must have different texfont.pl version. Each time afm2tfm is
called, it uses either -T or -p. Running afm2tfm without those
parameters doesn't make very much sense. (Unless you are an english
speaking person that never typesets foreign languages.)
Accoding to
Hi,
I've just updated my MikTeX distribution, which
use a 2005-07-12 version of context package. Since
then MikTeX could not generate the cont-en format
file, when I use texexec --make en, it reports
TeX capacity not enough, so I have to modify the
jjgod wrote:
So I suggest the maintainer of context avoid using
the -p option, it seems
||afm2tfm \$file\ texfont.tfm|
|
does the same job in this piece of code.
But then: how do you specify the encoding of the mapfile/psfont? -p is
a pretty important switch when using non-ascii encoings.
[...]
But then: how do you specify the encoding of the mapfile/psfont? -p is
a pretty important switch when using non-ascii encoings.
So what output infomation will afm2tfm generate when -p option is
on?
The encoding of the fonts in the postscript/pdf file. And an entry for
the mapfile,
Patrick Gundlach mailto:patrick.at.gundla.ch wrote:
Then we must have different texfont.pl version. Each time afm2tfm is
called, it uses either -T or -p. Running afm2tfm without those
parameters doesn't make very much sense. (Unless you are an english
speaking person that never typesets
Hi,
I've just updated my MikTeX distribution, which
use a 2005-07-12 version of context package. Since
then MikTeX could not generate the cont-en format
file, when I use texexec --make en, it reports
TeX capacity not enough, so I have to modify the
localtexmf/miktex/config/miktex.ini file,
13 matches
Mail list logo
