From: David <davidandrewrogers@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: inter-word spacing (initials)
Date: Thu, 17 Jul 2008 07:53:25 -0700 [thread overview]
Message-ID: <20080717075325487307.1231b7a6@gmail.com> (raw)
In-Reply-To: <115224fb0807170701od1af866gbb083290b3f633ce@mail.gmail.com>
On Thu, 17 Jul 2008 16:01:17 +0200, Wolfgang Schuster wrote:
> 2008/7/17 David <davidandrewrogers@gmail.com>:
>> On Thu, 17 Jul 2008 07:46:21 -0400, Alan Bowen wrote:
>>
>>> Thanks, David. I tried
>>>
>>> \starttext
>>> A. E. Samuel\crlf
>>> A.\ E.\ Samuel\crlf
>>> A.~E.~Samuel
>>>
>>> \stoptext
>>>
>>> and can see no difference (ConTeXt ver: 2008.07.14 18:07 MKII). The
>>> tilde is not really a good way for me to go. The problem is that I
>>> publish a journal in which the bibliography is punctuated mainly by
>>> "." Introducing tildes (which make spaces non-breaking) would affect
>>> the line-breaking negatively.
>>
>> Oh - sorry about that.
>>
>> What happens if you use your preferred way, but add the command
>> \fixedspaces somewhere previously in the document?
>>
>> I've discovered that this command is now required to get either the \ .
>> or the ~. to have any effect for me. The problem is, I don't know how
>> to turn it off afterwards. :-)
>
> You can't, there is no command to reset it but this should do it.
>
> \def\variablespaces
> {\letcatcodecommand \ctxcatcodes `\~ \nonbreakablespace}
Thanks Wolfgang. I prefer to have this behaviour available all the
time, and I don't understand why anyone would want it turned off - just
wanted to apologize for giving incomplete information.
(Any idea why \fixedspaces has been changed from default to optional?)
Thanks
David
___________________________________________________________________________________
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-07-17 14:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 21:30 Alan Bowen
2008-07-17 2:27 ` David
2008-07-17 11:46 ` Alan Bowen
2008-07-17 13:46 ` David
2008-07-17 14:01 ` Wolfgang Schuster
2008-07-17 14:53 ` David [this message]
2008-07-18 15:26 ` Wolfgang Schuster
2008-07-17 15:13 ` Alan Bowen
2008-07-18 4:33 ` David
-- strict thread matches above, loose matches on Subject: below --
2008-08-02 22:57 Alan Bowen
2008-08-03 2:46 ` Charles P. Schaum
2008-08-03 16:19 ` Alan Bowen
2008-08-03 16:05 ` Hans Hagen
2008-08-03 16:25 ` Alan Bowen
2008-08-03 20:45 ` Hans Hagen
2008-08-04 13:28 ` Alan Bowen
2008-08-04 14:23 ` Hans Hagen
2008-08-04 17:23 ` Alan Bowen
2008-07-18 17:35 Alan Bowen
2008-07-18 18:40 ` Peter Rolf
2008-07-18 20:33 ` Alan Bowen
2008-07-18 19:22 ` Peter Münster
2008-07-18 20:38 ` Alan Bowen
2008-07-15 21:26 Alan Bowen
2008-07-17 11:56 ` Wolfgang Schuster
2008-07-17 12:19 ` 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=20080717075325487307.1231b7a6@gmail.com \
--to=davidandrewrogers@gmail.com \
--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).