From: "Richard Hensh" <hensh@math.msu.edu>
Subject: RE: mfonts
Date: Tue, 7 Aug 2001 08:09:11 -0400 [thread overview]
Message-ID: <DFENJMIHOAJHLPPLNIINGEKLCBAA.hensh@math.msu.edu> (raw)
In-Reply-To: <DFENJMIHOAJHLPPLNIINOEJNCBAA.henshr@rgsgroup.com>
I downloaded the latest betas and I am now able to generate and use the
necessary font files. One curious note, the only thing that fails is the
generation of the virtual font files. This is a MikTeX installation (but I
have installed the fptex distribution since texfont.pl seems to require the
tools mktexlsr and Kpathsea). The command line and subsequent messages are
shown below.
>texfont --fontroot=F:/localtexmf --ven=FontsThings --col=hand --ma --in
TeXFont 1.2 - ConTeXt / PRAGMA ADE 2000-2001 (BETA)
encoding vector : texnansi
vendor name : fontsthings
source path : .
font collection : hand
texmf font root : f:/localtexmf
pdftex map file : texnansi-fontsthings-hand.map
source path : .
processing files : all on afm path
copying files : afm
copying : hand.afm
copying files : pfb
copying : hand.pfb
generating tfm : texnansi-raw-hand (from hand)
generating vf : texnansi-hand (from texnansi-raw-hand)
texnansi-raw-hand: No such file or directory
font identifier : PPHandwritingNormal
generating : ls-r databases
mktexlsr: VARTEXFONTS is not defined. Defaulting to
`J:\Storage\updates\TeX\Ty
pe\install'.
mktexlsr: Updating F:/localtexmf/ls-R...
mktexlsr: Done.
BTW, some font names seem to contain -raw- as part of their name but the tex
file that shows proper usage suggests the wrong name, e.g. the texfont
command generated the following suggestions in
texnansi-fontsthings-hand.tex:
\definefontsynonym[PPHandwritingNormal][texnansi-hand][encoding=texnansi]
instead of
\definefontsynonym[PPHandwritingNormal][texnansi-raw-hand][encoding=texnansi
]
It's easy enough to fix by hand but can this be repaired programmatically?
thanks
ricky
> -----Original Message-----
> From: owner-ntg-context@let.uu.nl [mailto:owner-ntg-context@let.uu.nl]On
> Behalf Of Richard Hensh
> Sent: Sunday, August 05, 2001 1:48 AM
> To: ntg-context@ntg.nl
> Subject: mfonts
>
>
> I'm really enjoying the tools that are described in mfonts.pdf but I'm
> having some problems with some of the fancier switches.
>
> For example, the following command line works as expected:
>
> >texfont.pl --ven=Larabie --col=zrnic --enc=texnansi --ma
> --fontroot=F:\loca
> ltexmf --in
>
> however, this one yields the error that follows:
>
> >texfont.pl --ven=Larabie --col=zrnic --enc=texnansi --ma
> --fontroot=F:\loca
> ltexmf --in --ap --sla=0.167 zrnic
>
> encoding vector : texnansi
> vendor name : larabie
> font collection : zrnic
> texmf font root : f:\localtexmf
> pdftex map file : texnansi-larabie-zrnic.map
> source path : .
> processing files : all in pattern zrnic
> copying files : afm
> copying : zrnic.afm
> copying files : pfb
> copying : zrnic.pfb
> slant factor : 0.167
> processing aborted : unknown tfm file zrnic
>
>
> Can anyone explain what I'm doing wrong?
>
> BTW, what is the proper encoding file to use?
>
>
> thanks
> ricky
>
>
next prev parent reply other threads:[~2001-08-07 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-05 5:48 mfonts Richard Hensh
2001-08-06 8:03 ` mfonts Hans Hagen
2001-08-07 12:09 ` Richard Hensh [this message]
2001-08-08 8:37 ` mfonts Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DFENJMIHOAJHLPPLNIINGEKLCBAA.hensh@math.msu.edu \
--to=hensh@math.msu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).