Re: [NTG-context] problem with \startcolumns[distance=0pt]

2016-10-06 Thread Hans Hagen

On 10/6/2016 8:40 AM, Michael Witten wrote:

On Tue, 07 Aug 2012 00:22:08 +0200, Peter Muenster wrote:


The distance is not 0pt here (MKIV):

--8<---cut here---start->8---
\starttext
\startcolumns[distance=0pt]
\input tufte
\stopcolumns
\stoptext
--8<---cut here---end--->8---


It would appear that this problem is still the case, as of the
following version:


i'll fix it (more in tune with mkii as this is the old columns handler)

soon we will default to the mixedcolumns handler and the old mechanism 
will become a module


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | 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
___

Re: [NTG-context] problem with \startcolumns[distance=0pt]

2016-10-06 Thread Michael Witten
On Tue, 07 Aug 2012 00:22:08 +0200, Peter Muenster wrote:

> The distance is not 0pt here (MKIV):
> 
> --8<---cut here---start->8---
> \starttext
> \startcolumns[distance=0pt]
> \input tufte
> \stopcolumns
> \stoptext
> --8<---cut here---end--->8---

It would appear that this problem is still the case, as of the
following version:

  $ context --version | sed -n 2p\;5p
  mtx-context | ConTeXt Process Management 0.63
  mtx-context | current version: 2016.09.24 12:40

In particular, Peter's example produces something like the following:
(I'm assuming these 90-character-plus-CRLF lines made it through the
Internet; if they did not make it, then someone's email-processing
software is non-conformant, so shame on him!)

   We thrive  in  information-thick  worlds screen, pigeonhole, pick over, 
sort, inte-
   because  of  our  marvelous  and  every- grate, blend, inspect, filter, 
lump, skip,
   day capacity  to  select,  edit,  single smooth,   chunk,   average,   
approximate,
   out, structure, highlight, group,  pair, cluster,  aggregate,  outline,  
summarize,
   merge, harmonize, synthesize, focus, or- itemize, review, dip into,  
flip  through,
   ganize,  condense,  reduce,  boil  down, browse, glance into, leaf  
through,  skim,
   choose, categorize,  catalog,  classify, refine,   enumerate,   glean,   
synopsize,
   list, abstract, scan, look into,  ideal- winnow  the  wheat  from  the  
chaff   and
   ize, isolate, discriminate, distinguish, separate the sheep from  the  
goats. 

However, a person whose thoughts are governed by reasonable logic might
instead expect the result to look more like this:

   We thrive  in  information-thick  worldsscreen, pigeonhole, pick over, sort, 
inte-
   because  of  our  marvelous  and  every-grate, blend, inspect, filter, lump, 
skip,
   day capacity  to  select,  edit,  singlesmooth,   chunk,   average,   
approximate,
   out, structure, highlight, group,  pair,cluster,  aggregate,  outline,  
summarize,
   merge, harmonize, synthesize, focus, or-itemize, review, dip into,  flip  
through,
   ganize,  condense,  reduce,  boil  down,browse, glance into, leaf  through,  
skim,
   choose, categorize,  catalog,  classify,refine,   enumerate,   glean,   
synopsize,
   list, abstract, scan, look into,  ideal-winnow  the  wheat  from  the  chaff 
  and
   ize, isolate, discriminate, distinguish,separate the sheep from  the  goats. 


The ConTeXt facilities in question are [mostly] defined here:

   "$TEXROOT"/texmf-context/tex/context/base/mkiv/page-mul.mkiv

After a not-so-cursory review, it seems to me that the problem is a
result of [probably erroneous] references [in various calculations]
to the `offset' parameter, which is presumably a vestigial growth
inherited from `\setupframed'.

Fortunately, meddling by this `offset' parameter can be explicitly
nullfied via including `offset=0pt' in the setup parameters for the
`\startcolumns' command; that is, in order to get the results that
Peter expected, modify Peter's example to be this:

--8<---cut here---start->8---
\starttext
\startcolumns[offset=0pt,distance=0pt]
\input tufte
\stopcolumns
\stoptext
--8<---cut here---end--->8---

If you now include `rule=on', then you get:

   We thrive  in  information-thick  worlds|screen, pigeonhole, pick over, 
sort, inte-
   because  of  our  marvelous  and  every-|grate, blend, inspect, filter, 
lump, skip,
   day capacity  to  select,  edit,  single|smooth,   chunk,   average,   
approximate,
   out, structure, highlight, group,  pair,|cluster,  aggregate,  outline,  
summarize,
   merge, harmonize, synthesize, focus, or-|itemize, review, dip into,  flip  
through,
   ganize,  condense,  reduce,  boil  down,|browse, glance into, leaf  through, 
 skim,
   choose, categorize,  catalog,  classify,|refine,   enumerate,   glean,   
synopsize,
   list, abstract, scan, look into,  ideal-|winnow  the  wheat  from  the  
chaff   and
   ize, isolate, discriminate, distinguish,|separate the sheep from  the  
goats. 

If you now replace `distance=0pt' with `distance=2ex', then you get the
following (I chose `2ex', so as to be able to represent the results more
accurately in plain text):

   We thrive  in  information-thick  worlds | screen, pigeonhole, pick over, 
sort, inte-
   because  of  our  marvelous  and  every- | grate, blend, inspect, filter, 
lump, skip,
   day capacity  to  select,  edit,  single | smooth,   chunk,   average,   
approximate,
   out, structure, highlight, group,  pair, | cluster,  aggregate,  outline,  
summarize,
   merge, harmonize, synthesize, focus, or- | itemize, review, dip into,  flip  
through,
   ganize,  condense,  reduce,  boil  down, | browse, glance into, leaf  
through,  skim,
   choose, categorize,  catalog,  classify, | refine,   enumerate,   glean,