ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Lars Huttar <lars_huttar@sil.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: difference between TeX behavior and ConTeXt
Date: Tue, 25 Nov 2008 16:09:10 -0600	[thread overview]
Message-ID: <492C7786.5070609@sil.org> (raw)
In-Reply-To: <alpine.LNX.2.00.0811251625320.9316@nqv-yncgbc>

On 11/25/2008 3:27 PM, Aditya Mahajan wrote:
> On Tue, 25 Nov 2008, Lars Huttar wrote:
> 
>> Hello,
>>
>> I've been reading through the TeXbook to solidify the foundations for
>> TeX programming. In an exercise on roman and italic text, ConTeXt seems
>> to behave differently from what the book specifies (Plain TEX) at a
>> fairly fundamental level.
>>
>> I could understand ConTeXt possibly changing the details of \rm's
>> definition, e.g. a change in default font family; but it would really be
>> surprising to find that the logic of \rm's behavior has been changed.
>>
>> Please help me understand if this is a bug or if there is a design
>> principle of ConTeXt that I should be aware of...
> 
> It is a design decision. See the chapter of typography 
> (http://context.aanhet.net/svn/contextman/context-reference/en/co-typography.pdf) 
> in the new manual (under preparation).
> 
> Aditya

Thanks for the explanation.
I hope that when the manual is finished it will make this clearer.
Currently, the draft chapter says
"As will be explained later, the command \rm is used to switch to a
roman/serif/regular style"
which does not seem to be happening.

The explanation of \em shows that ConTeXt's \em has different behavior
from Plain TeX's \it (especially when nesting styles), but doesn't say
that \it or \rm have changed behavior.

Lars
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-11-25 22:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 21:21 Lars Huttar
2008-11-25 21:27 ` Aditya Mahajan
2008-11-25 22:09   ` Lars Huttar [this message]
2008-11-25 23:37     ` Rory Molinari
2008-11-26  4:30       ` Lars Huttar
2008-11-26  7:34         ` Peter Münster
2008-11-26  8:41         ` Marcin Borkowski
2008-11-26  9:57           ` Hans Hagen
2008-11-26 13:43           ` Lars Huttar
2008-11-26 14:02             ` Lars Huttar
2008-11-26 14:11             ` Taco Hoekwater
2008-11-26 18:51               ` Lars Huttar
2008-11-27  9:57                 ` Taco Hoekwater
2008-12-01 17:03                   ` Lars Huttar
2008-11-26  9:55         ` Hans Hagen
2008-11-25 21:29 ` Lars Huttar
2008-11-26  4:15   ` Idris Samawi Hamid ادريس سماوي حامد
2008-11-26  6:26     ` Lars Huttar

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=492C7786.5070609@sil.org \
    --to=lars_huttar@sil.org \
    --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).