From: Hans Hagen <pragma@wxs.nl>
Subject: Re: bold \tt and pdf-output
Date: Tue, 06 Dec 2005 09:18:52 +0100 [thread overview]
Message-ID: <4395496C.9080802@wxs.nl> (raw)
In-Reply-To: <Pine.LNX.4.58.0512052019430.8623@gaston.free.fr>
� wrote:
>Hello,
>
>with bold typewriter font I have more success, but one problem remains:
>pdf-output. There is the same problem as with bold small caps:
>
>kpathsea: Running mktexpk --mfmode / --bdpi 72 --mag 1+14/72 --dpi 86 cmbtt10
>mktexpk: Mismatched mode ljfzzz and resolution 72; ignoring mode.
>mktexpk: Can't guess mode for 72 dpi devices.
>mktexpk: Use a config file, or update me.
>kpathsea: Appending font creation commands to missfont.log.
>
>This is my test-file:
>
>\definebodyfont [12pt] [tt] [bf=cmbtt10 at 12pt]
>\definebodyfont [11pt] [tt] [bf=cmbtt10 at 11pt]
>\definebodyfont [10pt] [tt] [bf=cmbtt10]
>\definebodyfont [9pt] [tt] [bf=cmbtt9]
>\definebodyfont [8pt] [tt] [bf=cmbtt8]
>\starttext
>{\tt Normal and \bf bold Typewriter.}
>\stoptext
>
>Could there be support for bold typewriter in the distribution?
>
>
looks like some metafont problem; however, forget about those fonts,
take a look at latin modern instead: it has narrow tt, light tt and
heavy tt (which is what you're looking for)
Hans
next prev parent reply other threads:[~2005-12-06 8:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 19:22 Peter Münster
2005-12-06 8:18 ` Hans Hagen [this message]
2005-12-06 9:19 ` Taco Hoekwater
2005-12-06 17:30 ` Peter Münster
2005-12-06 19:35 ` Hans Hagen
2005-12-10 11:32 ` Peter Münster
2005-12-12 9:34 ` Taco Hoekwater
2005-12-12 11:34 ` Vit Zyka
2005-12-12 17:48 ` problems with bold small caps (was: Re: bold \tt and pdf-output) Peter Münster
2005-12-13 10:14 ` problems with bold small caps Taco Hoekwater
2005-12-13 10:57 ` Taco Hoekwater
2005-12-13 12:24 ` Adam Lindsay
2005-12-13 11:01 ` Hans Hagen
2005-12-13 11:46 ` Vit Zyka
2005-12-12 10:52 ` bold \tt and pdf-output 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=4395496C.9080802@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).