ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jens-Uwe Morawski <morawski@gmx.net>
Subject: Re: Getting the PDF postscript fonts to work
Date: Wed, 5 Feb 2003 21:50:04 +0100	[thread overview]
Message-ID: <20030205215004.488177c1.morawski@gmx.net> (raw)
In-Reply-To: <877kce5yxc.fsf@dellius.nederware.nl>

On 06 Feb 2003 08:07:27 +1300
Berend de Boer <berend@pobox.com> wrote:

> Nagy Bence <gimb@freemail.hu> writes:
> 
> > > Has anyone been able to use the standard PDF postscript fonts with
> > > context? I recently upgraded to tetex 2.0, latest context, so had to
> > > restart with the font stuff.
> > > 1. After tinkering I could get the URW stuff working, but I want the
> > >    Adobe.
> > I have the same problem, but I couldn't find the right solution and
> > URW fonts doesn't work too.
> 
> OK, what to do:
> 
> 1. Run texfont on context/data/type-tmf.dat like this:
> 
>   texfont --encoding=texnansi --fontroot=/usr/share/texmf --batch type-tmf.dat
> 
> That should produce the right .tmf files.
> 
> 2. In your cont-sys.tex (/usr/local/texmf/tex/context/cont-sys.tex)
>    have only the following:
> 
> ====================
> % This seems to be Hans preferred encoding
> \setupencoding[\s!default=texnansi]
> ====================
> 
> No other \usesetypescript, or \setupencoding should be present.
> 
> 3. If you run this test file:
> 
> ====================
> \setupbodyfont
>   [pos,10pt]
> 
> \starttext
> 
> hello world.
> 
> {\ss hello again!}
> 
> {\tt the end.}
> 
> \stoptext
> ====================


Since a complete teTeX installation should include the LaTeX
PSNFSS package you don't need to generate the fonts (TFMs)
yourself.

Simply

====================
 \usetypescript[berry][ec]
 \setupbodyfont
   [pos,10pt]
 
 \starttext
 
 hello world.
 
 {\ss hello again!}
 
 {\tt the end.}
 
 \stoptext
====================

should work. This will use T1 (aka ec) encoded fonts not the
standard LY1 (aka texnansi) encoding. Therefore you have to
setup the proper input regime (\enableregime)

Jens

  reply	other threads:[~2003-02-05 20:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04  7:45 Berend de Boer
2003-02-04 12:26 ` Hans Hagen
2003-02-04 17:41   ` Berend de Boer
2003-02-04 17:59     ` Hans Hagen
2003-02-04 18:03     ` Matt Gushee
2003-02-04 23:20       ` Jens-Uwe Morawski
2003-02-05  8:48       ` Hans Hagen
2003-02-05 12:55       ` Siep
2003-02-05 12:33 ` Nagy Bence
2003-02-05 17:45   ` Patrick Gundlach
2003-02-05 19:07   ` Berend de Boer
2003-02-05 20:50     ` Jens-Uwe Morawski [this message]
2003-02-06  9:42       ` Nagy Bence
2003-02-05 23:07     ` Nagy Bence
2003-02-06  1:43       ` Berend de Boer
2003-02-06  9:33         ` Nagy Bence
2003-02-06 10:11           ` Hans Hagen
2003-02-06 11:30             ` mari.voipio
2003-02-06 18:50               ` Henning Hraban Ramm
2003-02-07  8:27               ` Hans Hagen
2003-02-07  6:52           ` Berend de Boer
2003-02-06 10:03       ` Hans Hagen
2003-02-06 11:18         ` mari.voipio
2003-02-09 15:04         ` Thomas Esser
2003-02-06 10:06       ` 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=20030205215004.488177c1.morawski@gmx.net \
    --to=morawski@gmx.net \
    --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).