* \startalignment
@ 2016-01-12 18:07 Alan BRASLAU
2016-01-12 18:29 ` \startalignment Wolfgang Schuster
0 siblings, 1 reply; 5+ messages in thread
From: Alan BRASLAU @ 2016-01-12 18:07 UTC (permalink / raw)
To: mailing list for ConTeXt users
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...
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:
\startparagraph
\input tufte
\startalignment [middle]
\input ward
\stopalignment
\input dawkins
\stopparagraph
Indeed, curious behavior.
Alan
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: \startalignment
2016-01-12 18:07 \startalignment Alan BRASLAU
@ 2016-01-12 18:29 ` Wolfgang Schuster
2016-01-12 20:07 ` \startalignment Hans Hagen
0 siblings, 1 reply; 5+ messages in thread
From: Wolfgang Schuster @ 2016-01-12 18:29 UTC (permalink / raw)
To: mailing list for ConTeXt users
[-- Attachment #1.1: Type: text/plain, Size: 1306 bytes --]
> 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.
> 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
[-- Attachment #1.2: Type: text/html, Size: 2589 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: \startalignment
2016-01-12 18:29 ` \startalignment Wolfgang Schuster
@ 2016-01-12 20:07 ` Hans Hagen
2016-01-12 20:43 ` \startalignment Alan BRASLAU
0 siblings, 1 reply; 5+ messages in thread
From: Hans Hagen @ 2016-01-12 20:07 UTC (permalink / raw)
To: mailing list for ConTeXt users
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: \startalignment
2016-01-12 20:07 ` \startalignment Hans Hagen
@ 2016-01-12 20:43 ` Alan BRASLAU
2016-01-12 21:18 ` \startalignment Hans Hagen
0 siblings, 1 reply; 5+ messages in thread
From: Alan BRASLAU @ 2016-01-12 20:43 UTC (permalink / raw)
To: Hans Hagen; +Cc: mailing list for ConTeXt users
On Tue, 12 Jan 2016 21:07:38 +0100
Hans Hagen <pragma@wxs.nl> wrote:
> >> 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)
I guess that I do not know TeX well-enough to understand why your
MWE below gives different line breaks.
\starttext
\bgroup \raggedright \input tufte \par \egroup
\bgroup \raggedright \input tufte \egroup \par
\stoptext
From a practical point-of-view, what would be the "correct" way of
achieving the following (i.e. no paragraph breaks):
\setupwhitespace [big]
\starttext
\input tufte
\\
\startframed
[frame=off,offset=0pt,before=,after=,width=\textwidth,align=middle]
\input ward \stopframed
\\
\input dawkins
\stoptext
Alan
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: \startalignment
2016-01-12 20:43 ` \startalignment Alan BRASLAU
@ 2016-01-12 21:18 ` Hans Hagen
0 siblings, 0 replies; 5+ messages in thread
From: Hans Hagen @ 2016-01-12 21:18 UTC (permalink / raw)
To: Alan BRASLAU; +Cc: mailing list for ConTeXt users
On 1/12/2016 9:43 PM, Alan BRASLAU wrote:
> On Tue, 12 Jan 2016 21:07:38 +0100
> Hans Hagen <pragma@wxs.nl> wrote:
>
>>>> 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)
>
> I guess that I do not know TeX well-enough to understand why your
> MWE below gives different line breaks.
>
> \starttext
>
> \bgroup \raggedright \input tufte \par \egroup
>
> \bgroup \raggedright \input tufte \egroup \par
>
> \stoptext
because the par builder kicks in when \par is issued so when that
happens after teh group the settings for left/rightskip used are not the
one inside the group
Hans
-----------------------------------------------------------------
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2016-01-12 21:18 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-01-12 18:07 \startalignment Alan BRASLAU
2016-01-12 18:29 ` \startalignment Wolfgang Schuster
2016-01-12 20:07 ` \startalignment Hans Hagen
2016-01-12 20:43 ` \startalignment Alan BRASLAU
2016-01-12 21:18 ` \startalignment Hans Hagen
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).