ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Maarten Sneep <sneep@nat.vu.nl>
Subject: Re: Re: Using the free PS Fonts with ConTeXt
Date: Tue, 11 Feb 2003 14:26:21 +0100	[thread overview]
Message-ID: <03021114262105.09642@mondriaan> (raw)
In-Reply-To: <87lm0o43ct.fsf@gundla.ch>

Thanks for the suggestions. Here are the results.

On Monday 10 February 2003 15:28, you wrote:
> Maarten Sneep <sneep@nat.vu.nl> writes:
> > I'm trying to use the free postscript fonts that come with teTeX
> > (urw palatino, times, helvetica, courier and various others, you
> > know the list) in ec encoding.
>
> I'll send you a testfile off list. Please tell me if it is working. A
> couple days ago I have sent a testfile (I think it was to Wolfgang)
> with a changed berry typeface (from type-enc.tex).

With \usetypescriptfile[debian] it is working. The standard way (as defined 
by Hans Hagen) doesn't.

> could you please send me the psfonts.map and pdftex.map files from
> your distribution?

See the attachments.

> > 1 - I've used texfont on the type-ftm.dat file in the default
> > installation
>
> Oh you don't need to reinstall your fonts! The TeX font files already
> a complete mess in an average TeX distribution. No need to increase
> this mess.

But how do you then generate the virtual fonts, or is there some trick in the 
map files to reencode on the fly?

> > My direct questions:
> > a - Did anyone succeed in using the free postscript fonts on Mac OS X,
> >     using a distribution that I use (i.e. the most recent version)
>
> I am not using tetex 2.0 on Mac OS X. Only texlive. And i had a
> successfull attempt.
>
> > b - What were the exact commands that you used? Can you send me a simple
> >     test file?
>
> Yes.
>
> > c - Did you experience the same EC.enc vs ec.enc naming problem?
>
> (I am not using texfont)

But at some point the ec.enc file must be read...

Kind regards,

Maarten Sneep

  reply	other threads:[~2003-02-11 13:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 11:58 Maarten Sneep
2003-02-10 12:42 ` Hans Hagen
2003-02-10 13:03   ` Maarten Sneep
2003-02-10  9:50     ` John Culleton
2003-02-10 13:26   ` Bruce D'Arcus
2003-02-11 13:29   ` Maarten Sneep
2003-02-11 19:14     ` Harri Hakula
2003-02-11 20:32       ` Patrick Gundlach
2003-02-11 21:19         ` Bruce D'Arcus
2003-02-11 21:34           ` Patrick Gundlach
2003-02-11 22:07             ` Hans Hagen
2003-02-11 22:24               ` Patrick Gundlach
2003-02-11 23:52                 ` Hartmut Henkel
2003-02-12  7:53                   ` mapfiles and pdftex Patrick Gundlach
2003-02-12  8:09                     ` Hans Hagen
2003-02-12 14:07                       ` Jens-Uwe Morawski
2003-02-13 11:06                         ` Hans Hagen
2003-02-13 15:56                           ` Jens-Uwe Morawski
2003-02-13 16:43                             ` Hans Hagen
2003-02-13  6:25                   ` Re: Using the free PS Fonts with ConTeXt Berend de Boer
2003-02-10 14:28 ` Patrick Gundlach
2003-02-11 13:26   ` Maarten Sneep [this message]
2003-02-11 14:25     ` Patrick Gundlach
2003-02-12 14:11       ` Jens-Uwe Morawski
2003-02-13  8:42         ` Patrick Gundlach
2003-02-10 14:30 ` Adam Lindsay
2003-02-11 13:22   ` Maarten Sneep

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=03021114262105.09642@mondriaan \
    --to=sneep@nat.vu.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).