ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared KAVIAN <otared@gmail.com>
Subject: Re: Re: Confusion with font instructions
Date: Mon, 4 Jul 2005 13:20:50 +0200	[thread overview]
Message-ID: <3cb063a605070404202f1e953b@mail.gmail.com> (raw)
In-Reply-To: <20050704103304.25666@mail.comp.lancs.ac.uk>

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

On 7/4/05, Adam Lindsay <atl@comp.lancs.ac.uk> wrote:
> Patrick Gundlach said this at Mon, 4 Jul 2005 09:54:06 +0200:
> 
> >Hello David,
> >
> >> I am new to ConTeXt, as my question is about to reveal.
> >
> >This questions can also come from more experienced users :)
> >
> >> Which set of instructions should I follow, in order to allow use of
> >> Palatino or Times, on Mac OS X, Gerben Wierda's TeX distribution, latest
> >> ConTeXt installed?
> >
> >OK, do you have LaTeX working? Then you can use the standard
> >postscript fonts for ConTeXt as well. Have a look at the (yet
> >unfinished page)
> >
> >http://contextgarden.net/Psnfss
> 
> Sadly, that page relies on type-pre, which is deprecated!
> (Yes, the situation changes again.)
> 
> So, the situation should now be:
> 
> % Times, Helvetica, Courier:
> \usetypescript [adobekb]   [\defaultencoding] % default=ec
> \usetypescript [postscript][\defaultencoding]
> \setupbodyfont [postscript]
> 
> % or, for Times, Helvetica, and Latin Modern TT:
> \usetypescript [adobekb][\defaultencoding]
> \usetypescript [times]  [\defaultencoding]
> \setupbodyfont [times]
> 
> % or, for Palatino & Latin Modern TT:
> \usetypescript [adobekb]  [\defaultencoding]
> \usetypescript [palatino] [\defaultencoding]
> \setupbodyfont [palatino]
> 
> The situation is "dynamic" because, to Hans's increasing frustration,
> the font files that get distributed change with just about every release
> of tetex (which gwTeX is mostly based on) or TeXLive.
> 

Hi David, Patrick and Adam,


It is right that handling fonts is extremely disappointing and instable...
For instance, what used to work does not work anymore properly with
the new version of ConTeXt I installed two weeks ago... (please see
below).
For instance:

\usetypescript [adobekb][\defaultencoding]
\setupbodyfont[postscript]
\usetypescript[times][\defaultencoding] %or helvetica, or palatino
\setupbodyfont[times,12pt]

used to work fine, but now it results in ConTeXt creating, the first
time, a whole bunch of things regarding fonts, and then the resulting
PDF contains some ugly jagging bitmap-looking characters
(interestingly this happens only to the text characters, not to the
math characters...). Adding

\usetypescript [postscript][\defaultencoding]

before \setupbodyfont[postscript] does not change anymorethe situation.

I wanted to answer David's question on Saturday but when I tried my
examples, I was dispappointed and did not answer.

Best regards: OK

[-- Attachment #2: before.pdf --]
[-- Type: application/pdf, Size: 121346 bytes --]

[-- Attachment #3: after.pdf --]
[-- Type: application/pdf, Size: 133678 bytes --]

[-- Attachment #4: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2005-07-04 11:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-03  7:13 David Rogers
2005-07-04  7:54 ` Patrick Gundlach
2005-07-04 10:33   ` Adam Lindsay
2005-07-04 11:20     ` Otared KAVIAN [this message]
2005-07-04 15:07     ` David Rogers
2005-07-04 15:29       ` Hans Hagen
2005-07-04 16:39         ` David Rogers
2005-07-04 19:09           ` Radhelorn
2005-07-05  0:34             ` Solved! was " David Rogers
2005-07-04 19:41           ` Hans Hagen
2005-07-04 15:28     ` Hans Hagen
2005-07-04 14:28 Otared Kavian
2005-07-04 15:11 ` Adam Lindsay
2005-07-04 16:02   ` David Rogers
2005-07-04 16:28     ` Adam Lindsay
2005-07-04 19:43     ` Hans Hagen
2005-07-04 17:56   ` Otared Kavian
2005-07-04 21:33     ` Hans Hagen
2005-07-04 22:43       ` Otared Kavian
2005-07-05 17:09       ` Radhelorn
     [not found]     ` <42C99E9D.9090304@wxs.nl>
     [not found]       ` <20050704231144.13609@mail.comp.lancs.ac.uk>
2005-07-05  9:23         ` Otared Kavian
2005-07-05 16:18           ` David Rogers
2005-07-05 16:25             ` Adam Lindsay
2005-07-05 16:45               ` David Rogers
2005-07-06  9:19               ` Otared Kavian
2005-07-06 10:09                 ` Radhelorn
2005-07-04 15:18 ` Hans Hagen
2005-07-04 16:41   ` David Rogers
2005-07-04 19:33     ` 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=3cb063a605070404202f1e953b@mail.gmail.com \
    --to=otared@gmail.com \
    --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).