From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \startalignment
Date: Tue, 12 Jan 2016 21:07:38 +0100 [thread overview]
Message-ID: <56955D0A.4030302@wxs.nl> (raw)
In-Reply-To: <569545FD.2030903@gmail.com>
On 1/12/2016 7:29 PM, Wolfgang Schuster wrote:
>> Alan BRASLAU <mailto:alan.braslau@cea.fr>
>> 12. Januar 2016 um 19:07
>> Hello,
>>
>> Jean-Michel pointed out to me the following curiosity:
>>
>> \starttext
>> \input tufte
>> \startalignment[middle]
>> \input ward
>> \stopalignment
>> \input tufte
>> \stoptext
>>
>> The startalignment applies to the preceding text, too. Strange...
> It’s a normal behaviour for TeX, the question is should \startalignment
> end the previous paragraph or not.
when tex breaks a paragraph into lines the current values of relevant
parameters is used (left and right skips, spacing, etc)
\bgroup \raggedright \inptu tufte \par \egroup
\bgroup \raggedright \inptu tufte \egroup \par
>> I never noticed this before as I have the habit of coding
>> \startalignment\stopalignment blocks set-off with leading and trailing
>> blank lines for better readability. But such practice could lead to
>> undesired results. Consider the following example:
>>
>> \setupwhitespace [big]
>>
>> \starttext
>> \input tufte
>>
>> \startalignment[middle]
>> \input ward
>> \stopalignment
>> \input dawkins
>> \stoptext
>>
>> So \stopalignment implicitly imposes a \par.
>> If I were to omit the blank line before \startalignment so that no big
>> whitespace be included before the centered block, the tufte text will
>> get middle aligned. Also, perhaps I might not wish for the dawkins text
>> to be separated by a big whitespace, logically as in:
> You can use \startpacked … \stoppacked to suppress blank lines inserted
> by \setupwhitespace.
>
> Wolfgang
>
>
> ___________________________________________________________________________________
> 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 : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-01-12 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 18:07 \startalignment Alan BRASLAU
2016-01-12 18:29 ` \startalignment Wolfgang Schuster
2016-01-12 20:07 ` Hans Hagen [this message]
2016-01-12 20:43 ` \startalignment Alan BRASLAU
2016-01-12 21:18 ` \startalignment 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=56955D0A.4030302@wxs.nl \
--to=pragma@wxs.nl \
--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).