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 16:28:31 +0200	[thread overview]
Message-ID: <p06110400beeef733091c@[193.51.32.222]> (raw)

>On 4 juil. 2005, at 9:54, Patrick Gundlach wrote:
>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
>
>Patrick
>--


Hi Patrick, David 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...
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] does not help neither.

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
PS: When I added two samples of the PDF files to my previous post, it 
was blocked due to the fact that the message was over 40 Kb. So I am 
posting again without the attachments.

             reply	other threads:[~2005-07-04 14:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-04 14:28 Otared Kavian [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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
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-04 19:41           ` Hans Hagen
2005-07-04 15:28     ` 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='p06110400beeef733091c@[193.51.32.222]' \
    --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).