From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/8117
Path: main.gmane.org!not-for-mail
From: Jonathan Beach <jmbeach@techie.com>
Newsgroups: gmane.comp.tex.context
Subject: RE: font tryout
Date: Mon, 3 Jun 2002 17:02:31 -0400 (EDT)
Sender: owner-ntg-context@let.uu.nl
Message-ID: <Pine.LNX.4.33.0206031625580.19021-100000@boogie.insight.rr.com>
References: <5.1.0.14.1.20020603154226.02bbac80@server-1>
Reply-To: <jmbeach@techie.com>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Trace: main.gmane.org 1035398549 24890 80.91.224.250 (23 Oct 2002 18:42:29 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 18:42:29 +0000 (UTC)
Original-To: <ntg-context@ntg.nl>
In-Reply-To: <5.1.0.14.1.20020603154226.02bbac80@server-1>
Xref: main.gmane.org gmane.comp.tex.context:8117
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:8117

On Mon, 3 Jun 2002, Hans Hagen wrote:
> Does miktex come with the normal texmf (tex live) fonts? If so, doesn't
>
> \setupencoding[default=ec]
> \usetypescript [berry] [ec]
>
> \setupbodyfont[pos,10pt]
>
> some text in times
>
> work?
>
> Hans

I don't know about the other persons in this thread, but using the above
code allowed me to create file using the postscript fonts for the first
time using the MikTeX/ConTeXt installation on my Windows machine.  Thanks,
Hans.

One observation, my file contained a number of \={o} which should produce
an 'o' with an macron accent.  However, using the postscript fonts, the
result was a long dash through the middle of the letters.

This does not happen with the default Computer Modern fonts and it does
not happen if I process the file with an older version of ConTeXt (texexec
reports version 1.9) installed on my linux machine as part of teTeX (with
postscript or Computer Modern).  Since the use of the \={o} was in
romanized Japanese, I was able to switch to \^{o} with acceptable results.

Is there anyway to fix this?