ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Kumar Appaiah <akumar@iitm.ac.in>
To: ntg-context@ntg.nl
Cc: preining@logic.at
Subject: Re: Problems with fonts
Date: Tue, 6 Feb 2007 07:27:55 +0530	[thread overview]
Message-ID: <20070206015755.GA7054@localhost> (raw)
In-Reply-To: <20070206013938.GA6414@localhost>

On Tue, Feb 06, 2007 at 07:09:38AM +0530, Kumar Appaiah wrote:
> Same holds for \Omega. Actually, there is something wrong with the
> fonts; CMR fonts don't seem to be used. Here is an example:
> 
> See caption for figures 4, 5, 6 etc. These should have a \Omega
> wherever there's a blank. Also move to the last page, the font
> rendering for math is far from OK. I am, in general, unhappy with the
> fonts: http://www.ee.iitm.ac.in/~ee03b091/ee03b091.pdf
> 
> A similar document made with the old ConTeXt is:
> http://www.ee.iitm.ac.in/~ee03b091/ee03b091_nice.pdf
> The fonts render very well in Acrobat as well as have all
> symbols. This is what I was mentioning.

And the TeX source (to the second document actually) with EPS images,
is at http://www.ee.iitm.ac.in/~ee03b091/compile.tar.bz2

Thanks.

Kumar
-- 
Kumar Appaiah,
462, Jamuna Hostel,
Indian Institute of Technology Madras,
Chennai - 600 036

  reply	other threads:[~2007-02-06  1:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-04 14:34 Kumar Appaiah
2007-02-04 17:35 ` Mike Bird
2007-02-05  5:09   ` Kumar Appaiah
     [not found] ` <6faad9f00702040956v3451f48bka360adefcda9eeff@mail.gmail.com>
2007-02-05 11:31   ` Fwd: [NTG-context] " Norbert Preining
2007-02-05 12:52     ` Norbert Preining
2007-02-05 13:53       ` Hans Hagen
2007-02-05 17:07         ` [NTG-context] " Norbert Preining
2007-02-06  1:39           ` Kumar Appaiah
2007-02-06  1:57             ` Kumar Appaiah [this message]
2007-02-06  4:55               ` Aditya Mahajan
2007-02-06  8:05                 ` Taco Hoekwater
2007-02-06  8:37                   ` Kumar Appaiah
2007-02-06  8:52                     ` Kumar Appaiah
2007-02-06  9:17                       ` Hans Hagen
2007-02-06  9:36                         ` Kumar Appaiah
2007-02-06  9:39                           ` Hans Hagen
2007-02-06  9:49                           ` Taco Hoekwater
2007-02-06  9:06                     ` Hans Hagen
2007-02-06  9:05                 ` Hans Hagen
2007-02-06  9:12             ` Hans Hagen
2007-02-06 13:53             ` Norbert Preining
2007-02-07  3:03               ` Kumar Appaiah
2007-02-07  8:24                 ` Taco Hoekwater
2007-02-07 11:03                   ` Kumar Appaiah
2007-02-07 13:22                     ` Taco Hoekwater
2007-02-07 14:03                       ` Hans Hagen
2007-02-07 14:32                       ` Kumar Appaiah
2007-02-07 14:44                         ` Taco Hoekwater
2007-02-07 14:55                       ` Kumar Appaiah
2007-02-08  1:23                         ` Kumar Appaiah
2007-02-08  7:36                           ` Kumar Appaiah
2007-02-08  7:41                           ` Mojca Miklavec
2007-02-08  8:33                             ` Hans Hagen
2007-02-08 17:13                             ` Kumar Appaiah
2007-02-08  8:35                           ` 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=20070206015755.GA7054@localhost \
    --to=akumar@iitm.ac.in \
    --cc=ntg-context@ntg.nl \
    --cc=preining@logic.at \
    /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).