From: Hans Hagen <pragma@wxs.nl>
Subject: Re: mfonts.tex from manuals
Date: Thu, 01 Dec 2005 20:16:20 +0100 [thread overview]
Message-ID: <438F4C04.4020003@wxs.nl> (raw)
In-Reply-To: <20051123151451.17543@mail.comp.lancs.ac.uk>
Adam Lindsay wrote:
>I tried to run texfont demofont.dat, but failed.
>First off, Hans, am I missing a runtools.rb? I can't find it.
>
>
indeed, i need to add that one to the zip (i'll send you a copy)
>Secondly, I think the current demofont.dat has a bug because it triggers
>an obscure texfont filtering feature. I changed the comments at the head
>of the file to work around it:
>
># we assume that demofont.afm and demofont.pfb are present
># run with:
># texfont demofont.dat
>
>
interesting -)
>Okay, another couple hacks to cross further hurdles:
>
>The top of my mfonts.tex now looks like:
>
>\preloadtypescripts % I wanted to speed things up a bit!
>
>
ah, i have that one in my cont-sys.tex
>\startnotmode[atpragma]
>\startMPenvironment[global]
> % Current bug in distribution
> \definefontsynonym [LMSans-Italic] [LMSans-Oblique]
> \definefontsynonym [LMSans-BoldItalic] [LMSans-BoldOblique]
> % lucida gets called all over the place
> \definetypescriptsynonym [lucida] [palatino]
> \usetypescript[adobekb][8r,ec]
>\stopMPenvironment
>\stopnotmode
>
>
>
ok
>\usetypescriptfile [type-buy]
>\usetypescriptfile [typeface]
>
>\environment ../allkind/mcommon.tex
>
>
>
already fixed
>... That much ought to fix the main body (though with the synonyms and
>substitutions, the fonts it mentions in the text are not always going to
>match the actual fonts used now!)
>
>Go down a little bit, and you'll see the title page font set:
>
>\startnotmode[atpragma]
>
> \startMPenvironment[global]
> \usetypescript[handwriting,map][lucida][texnansi]
> \definefontsynonym[TitlePage-Bold][LucidaHandwriting-Italic]
> %usetypescript[calligraphy,map][chancery][texnansi]
> %definefontsynonym[TitlePage-Bold][Chancery]
>% ...
>
>comment out the lucida lines, and uncomment the chancery lines, and you
>should be in business for a full run!
>
>
i'll upload a patched style,
Hans
next prev parent reply other threads:[~2005-12-01 19:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 23:27 David Arnold
2005-11-23 7:27 ` Taco Hoekwater
2005-11-23 10:47 ` Hans Hagen
2005-11-23 15:14 ` Adam Lindsay
2005-11-25 1:37 ` David Arnold
2005-11-25 10:41 ` Adam Lindsay
2005-11-25 19:27 ` David Arnold
2005-11-25 20:14 ` Hans Hagen
2005-11-25 20:26 ` David Arnold
2005-11-25 22:42 ` Gerben Wierda
2005-11-25 23:35 ` Henning Hraban Ramm
2005-11-25 23:58 ` Adam Lindsay
2005-11-26 0:41 ` Hans Hagen
2005-12-01 19:16 ` Hans Hagen [this message]
2005-12-01 1:45 ` David Arnold
2005-12-06 14:20 ` Mojca Miklavec
2005-12-06 16:13 ` Hans Hagen
[not found] <20051207133722.90749.qmail@web54404.mail.yahoo.com>
2005-12-09 13:04 ` Mojca Miklavec
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=438F4C04.4020003@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/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).