ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Willi Egger" <w.egger@boede.nl>
Subject: Re: How to use charter?
Date: Wed, 16 Jul 2003 12:09:51 +0200	[thread overview]
Message-ID: <006501c34b82$a0ff6670$0100a8c0@vademecum> (raw)
In-Reply-To: <20030716080751.GA24935@asta.tu-darmstadt.de>

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

Hi Alexander,


> I am trying to use the Bitstream Charter as a font. Unluckily,
> all the umlauts fail to appear. Here is how I do it:
>
> \definefont[bchr][bchr8t at 12pt]
> \starttext
> \bchr \"a \"o \"u \SS{}
> \stoptext

I am for sure no font guru. I would suggest you to install the charter fonts
with texfont.

What I have done in the last quarter of an hour:

Create a directory \texmf\fonts\source\bitstrea\charter
Copy the *.afm and *.pfb files to that directory.
Copy the attached file type-charter.dat to that directory (this is the
charter-section form type-tmf.dat provided by Hans).
Copy texnansi.enc from the dvips environment to that directory.

open a Dos box and run texfont --batch type-charter.dat

Add the map file to pdftex.cfg: map +texnansi-bitstrea-charter.map

Run the attached test file...

You do not have to elaborate a typescript file, because charter is builtin
in the typescripts provided with ConTeXt.


Success Willi

[-- Attachment #2: type-charter.dat --]
[-- Type: application/octet-stream, Size: 507 bytes --]

# You can process this file as follows, using texfont.pl:
#
#   texfont --encoding=ec --batch texfont.dat
#   texfont --batch texfont.dat    if you have set the encoding as below
#
# where 'ec' can be replaced by 'texnansi', '8r' or otherwise.


# bit charter

--en=texnansi --ve=bitstrea --co=charter --so=auto
--en=texnansi --ve=bitstrea --co=charter --so=auto --ca=* bchr8a
--en=texnansi --ve=bitstrea --co=charter --so=auto --sl=* bchr8a
--en=texnansi --ve=bitstrea --co=charter --so=auto --sl=* bchb8a

[-- Attachment #3: charter.tex --]
[-- Type: application/octet-stream, Size: 549 bytes --]

% Testfile for the Bitstream charter font collection
% W. Egger
% 16.07.03

\setupoutput[pdftex]

\definetypeface [Myfont] [rm] [serif] [charter] [default] [encoding=texnansi]

\setupbodyfont[Myfont,rm,12pt]

\startbuffer[Text]
    \input knuth
\stopbuffer

\starttext

\section{Charter Roman}

\getbuffer[Text]

\section{Charter Bold}

{\bf \getbuffer[Text]}

\section{Charter Bold-slanted (Built by texfont)}

{\bs \getbuffer[Text]}

\section{Charter Small Caps with \type{\sc}}

{\sc \getbuffer[Text]}

\stoptext

  reply	other threads:[~2003-07-16 10:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16  8:07 Alexander Klink
2003-07-16 10:09 ` Willi Egger [this message]
2003-07-16  9:59   ` Alexander Klink
2003-07-16 12:03     ` Henning Hraban Ramm
2003-07-16 12:06       ` Alexander Klink
2003-07-16 13:28       ` wmcclain
2003-07-16 12:21     ` Jens-Uwe Morawski
2003-07-16 12:18       ` Alexander Klink
2003-07-16 14:20         ` Jens-Uwe Morawski
2003-07-16 13:18       ` \filbreak equivalent in ConTeXt Duncan Hothersall
2003-07-16 12:08 ` How to use charter? Jens-Uwe Morawski

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='006501c34b82$a0ff6670$0100a8c0@vademecum' \
    --to=w.egger@boede.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).