ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Meer, Hans van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: Reviewing old messages
Date: Mon, 16 May 2016 15:18:41 +0000	[thread overview]
Message-ID: <61B05466-35FB-4624-A7EC-DE8B3C4007FC@uva.nl> (raw)
In-Reply-To: <5739DC20.2020806@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1287 bytes --]



On 16 May 2016, at 16:41, Wolfgang Schuster <schuster.wolfgang@gmail.com<mailto:schuster.wolfgang@gmail.com>> wrote:

Meer, Hans van der<mailto:H.vanderMeer@uva.nl>
16. Mai 2016 um 16:31
Thanks.

I redid the examples with the autostrut parameter set to respectively yes and no. In the former case I see all have an hbox and in the latter case all have a vbox. So it seems not the align, but the strut being the one determining the box variant.
No, the align settings determines the box type. The \strut at the begin forces horizontal mode which results in both \hbox’es in the same line.

Ok. But when using "strut=no,autostrut=no" I see for all values of align the abc/xyz below each other and none having abcxyz. Doesn't that suggest that all boxes are vbox and that the strut merely forces horizontal mode? Otherwise I do not understand what happens.

Thus I did the experiment again, for all options with \framed[strut=no,autostrut=no,align=OPTION]{\ifvmode V\else H\f.
I  found a V at the front of the output in each and every case.


\starttext

\ifvmode Vertical \else Horizontal \fi mode

\strut
\ifvmode Vertical \else Horizontal \fi mode

\stoptext

Wolfgang
___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 3150 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
___________________________________________________________________________________

  reply	other threads:[~2016-05-16 15:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18 12:55 halign broken Meer, H. van der
2013-04-18 13:03 ` Wolfgang Schuster
2013-04-18 13:16   ` Meer, H. van der
2013-04-18 14:13     ` Hans Hagen
2013-04-18 14:58       ` Aditya Mahajan
2013-04-18 13:26   ` Meer, H. van der
2013-04-18 13:34     ` Wolfgang Schuster
2013-04-18 13:39       ` Meer, H. van der
2013-04-18 13:46         ` Wolfgang Schuster
2016-05-16 13:50           ` Reviewing old messages Meer, Hans van der
2016-05-16 14:03             ` Wolfgang Schuster
2016-05-16 14:31               ` Meer, Hans van der
2016-05-16 14:41                 ` Wolfgang Schuster
2016-05-16 15:18                   ` Meer, Hans van der [this message]
2016-05-16 15:36                     ` Wolfgang Schuster

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=61B05466-35FB-4624-A7EC-DE8B3C4007FC@uva.nl \
    --to=h.vandermeer@uva.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).