From: Alan Bowen <acbowen@princeton.edu>
Subject: deviant bodyfont size query
Date: Sun, 26 Jun 2005 17:28:19 -0400 [thread overview]
Message-ID: <17D8DF31-0254-4D5E-B5E2-D276DD438D1D@princeton.edu> (raw)
Until the last three updates to ConTeXt, I was getting output without
error messages inspite of the fact that I was calling for bodyfont
sizes of 10.5 pt and 9.5 pt. Now, when I process the same documents
I get error messages and the output has 10pt and 9pt text where I had
originally asked for the deviant sizes.
Unfortunately, this output is smaller than I was getting before.
Moreover, when I call for bodyfont sizes of 11pt and 10pt now, the
output is larger.
The problem is that i ned to maintain the appearance of the documents
that I have been typesetting. So what was I getting before—how were
these deviant bodysizes rendered—and, more important, does anyone
know how can I get the same result now?
Cheers, Alan
next reply other threads:[~2005-06-26 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 21:28 Alan Bowen [this message]
2005-06-27 8:10 ` Taco Hoekwater
2005-06-27 10:27 ` Alan Bowen
2005-06-27 10:54 ` Hans Hagen
2005-06-28 11:04 ` Alan Bowen
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=17D8DF31-0254-4D5E-B5E2-D276DD438D1D@princeton.edu \
--to=acbowen@princeton.edu \
--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).