From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: Create pseudo small caps.
Date: Thu, 4 Sep 2003 06:29:15 +0100 [thread overview]
Message-ID: <20030904052915.24872@smtp.btinternet.com> (raw)
In-Reply-To: <200309031734.04125.john@wexfordpress.com>
John,
First off, make sure you don't already have the font buried somewhere. I
found Charter SC (faked) in my TeXLive 7 installation:
\showfont[bchrc8t]
Ah, but there's a typo/omission in type-enc.tex. That particular line
should be:
\definefontsynonym [ec-bchr8a-capitalized-800] [bchrc8t] [encoding=ec]
If you put that single line in your input file, and then call the default
charter face with:
\usetypescript[berry][ec] % or [8r]
\definetypeface[charter][rm][serif][charter][default][encoding=ec]
\setupbodyfont[charter]
...you should be set. If the font isn't there, or you prefer to use
something other than ec-encoding, then read on.
As for texfont, I have only done this particular one using texfont in a
batch mode, but it should be at least close to the mark.
Make sure the directory tree where you find your fonts is writeable. Make
sure that $texmf/fonts/afm/bit is correctly named 'bitstrea'. (ah,
another bug, this time in TeXLive...)
texfont /path/to/context/data/type-tmf.dat --en=8r --inst -make \
--fontroot=/path/to/texmf-fonts --co=charter --ve=bitstrea
This should (I'm a little rusty) run texfont on Hans's built-in
batchfile, selecting only charter. With that done, I think this ought to work:
\definetypeface[charter][rm][serif][charter][default][encoding=8r]
\setupbodyfont[charter]
If you want to run texfont only to make smallcaps, I think the command
you want is:
sudo texfont --en=ec --fontroot=/path/to/texmf-local --inst --make \
--ve=bitstrea --co=charter --source=auto --ca=0.8 bchr8a
I'll leave it to you to integrate that one into your typescript.
I was going to ask about the \kap series of commands, but none seem to
give a mix of (faked) caps and small caps.
Hope that helps a bit,
adam
John Culleton said this at Wed, 3 Sep 2003 17:34:04 -0400:
>On Tuesday 02 September 2003 16:06, John Culleton wrote:
>> I am using Bitstream Charter following the directions on Bill
>> McClain's page for typescripts. Now I want to use \sc in both regular
>> and expanded form. What is the best way to add a \sc typeface to my
>> file?
>
>Bill McC suggested that Texfont could be used to create a small caps
>version but I haven't figured it out yet. If I don't find any other
>answer I will either use a small caps font from another typeface or
>else
>do a kludge like
> \fonta H\fontb ELLO
>---to get "Hello" in caps and small caps,
>\fonta being Charter at 11pts and \fontb being Charter at perhaps 6pts.
>Surely there is a better way??
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay atl@comp.lancs.ac.uk
Computing Dept, Lancaster University +44(0)1524/594.537
Lancaster, LA1 4YR, UK Fax:+44(0)1524/593.608
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2003-09-04 5:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 20:06 John Culleton
2003-09-03 21:34 ` John Culleton
2003-09-04 5:29 ` Adam Lindsay [this message]
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=20030904052915.24872@smtp.btinternet.com \
--to=atl@comp.lancs.ac.uk \
--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).