ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jonathan Beach <jmbeach@techie.com>
Subject: RE: font tryout
Date: Mon, 3 Jun 2002 17:02:31 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0206031625580.19021-100000@boogie.insight.rr.com> (raw)
In-Reply-To: <5.1.0.14.1.20020603154226.02bbac80@server-1>

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?


  reply	other threads:[~2002-06-03 21:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-01 10:24 Kris Hermans
2002-06-02  7:59 ` Nigel King
2002-06-02 12:56   ` Ville Voipio
2002-06-03 13:26     ` Kris Hermans
2002-06-03 13:43       ` Hans Hagen
2002-06-03 21:02         ` Jonathan Beach [this message]
2002-06-04  5:26         ` Kris Hermans
2002-06-04 16:20         ` John Devereux
2002-06-04 18:53           ` Bill McClain
2002-06-05 22:04           ` 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=Pine.LNX.4.33.0206031625580.19021-100000@boogie.insight.rr.com \
    --to=jmbeach@techie.com \
    /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).