From: Alan Bowen <acbowen@princeton.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: error message query
Date: Wed, 03 Sep 2008 22:57:48 -0400 [thread overview]
Message-ID: <BAC2F667-AF51-409C-B2FE-33EDF5B9CCBB@princeton.edu> (raw)
In-Reply-To: <BD6230C6-0440-4ACF-86E6-C29B5A81A7F4@uni-bonn.de>
Thomas—
The problem seems limited to one of my environments. With the one for
the journal, MKII and \def\ {|~|} work when the Greek module is loaded
and when real Greek is set. In short, the changes made in your Greek
module seem happily restricted to text in \localgreek{...} and so on.
I am at a loss to see how \def\ {|~|} collides with the many macros in
the problem environment right now, hence my query about a cleverer way
to make the definition.
By the way, I use |~| to reduce stretch and to get the right spacing
after any period within a sentence. It’s unbreakability is an
undesirable side effect. (The string A.|~\E|~|Samuel”, for example,
breaks with a hyphen as in “A. E.-” which is certainly not good.)
Apparently, we have lost the functionality of the old “\ ” when
\mainlanguage[en].
Cheers, Alan
On Sep 3, 2008, at 17;44,35 , Thomas A. Schmitz wrote:
>
> On Sep 3, 2008, at 9:48 PM, Alan Bowen wrote:
>
>> It appears that the problem is my definition
>>
>> \def\ {|~|}
>>
>> Though this definition works in a simple test file, it apparently
>> conflicts with something in my environment file and produces the
>> error
>> message reported previously. So, is there a “safer” way to define
>> \<space> as {|~|}?
>>
>> Alan
>
> Since you seem to be using Greek in your file: both | and ~ are made
> inactive in the Greek environment, so if you use '\ ' within Greek
> stuff, you're running into trouble. I don't see a solution within mkii
> if you want the nonbreakable space.
>
> Thomas
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-09-04 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 19:48 Alan Bowen
2008-09-03 21:44 ` Thomas A. Schmitz
2008-09-04 2:57 ` Alan Bowen [this message]
2008-09-04 8:39 ` Wolfgang Schuster
2008-09-04 12:10 ` 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=BAC2F667-AF51-409C-B2FE-33EDF5B9CCBB@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).