ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Kumar Appaiah <akumar@iitm.ac.in>
To: ntg-context@ntg.nl
Subject: Re: Problems with fonts
Date: Wed, 7 Feb 2007 08:33:55 +0530	[thread overview]
Message-ID: <20070207030355.GA6769@localhost> (raw)
In-Reply-To: <20070206135341.GA29310@gamma.logic.tuwien.ac.at>

On Tue, Feb 06, 2007 at 02:53:41PM +0100, Norbert Preining wrote:
> This is strange. I have these \Omegas occuring without any problem!
> 
> I also tried a minimal example:
> \starttext
> This should be Omega subscript s: $\Omega_s$
> 
> This should be 2 times pi cdot 11: $2\pi \cdot 11$ 
> \stoptext
> and it showed up correct.

OK, so here's the diagnosis. The file you have quoted above is what I
used.

1. texexec test.tex: Gives a PDF which renders all symbols. However,
   the font display in Acrobat isn't perfect (it's a bit light), but
   should be perfect when printed.

2. texexec --dvi test.tex;dvips test.dvi;ps2pdf test.ps: Same result
   as the previous.

3. texexec --dvi test.tex;dvips -Ppdf test.dvi;ps2pdf test.ps: Oops!
   \cdot is missing!!!!

4. texexec --dvi test.tex;dvipdf test.dvi: Oops! \cdot is missing again!

If you still need test.log, I can upload it, but it doesn't have
anything strange. Also, as Taco had suggested regarding the map file,
I checked that original-public-lm.map has the entry for cmr10 etc.

Finally, hoping that I'm being smart, I have bzip2ed the output of
dvips -d 127 -Ppdf test.dvi. Please check the directories searched for
the map file; the directory in which original-public-lm resides is
/usr/share/texmf/fonts/map/pdftex/context and it doesn't appear on
that list, but I'd like you to confirm.

Get it at http://www.ee.iitm.ac.in/~ee03b091/dvips_output.bz2

Thanks.

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

  reply	other threads:[~2007-02-07  3:03 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
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 [this message]
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=20070207030355.GA6769@localhost \
    --to=akumar@iitm.ac.in \
    --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).