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 14:31:33 +0000 [thread overview]
Message-ID: <38D1FB3E-2605-424C-B6B7-AA3D821CEFE5@uva.nl> (raw)
In-Reply-To: <5739D317.8080604@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1673 bytes --]
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.
Hans van der Meer
On 16 May 2016, at 16:03, 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 15:50
Sifting through my TeX-mailbox, I came along this post of Wolfgang Schuster and decided to try all variations given to the align parameter on \framed.
Curious in which cases the \hbox and in which the \vbox is chosen, not unimportant of course.
I did this by typesetting \hbox{abc}\hbox{xyz} inside a framed. For \hbox want expects abcxyz as output and for \vbox abc and below it xyz. As can be seen in the first two examples.
To my surprise none of the \framed[align=..] options exhibits \vbox character!
Thus my question: has the behaviour of \framed[align=..] changed in the mean time? Three years is of course an eternity when seen in the perspective of the speed with which ConTeXt is evolving 😃. Or is there another reason why the \vbox effect is not shown in any of the examples?
\framed adds a \strut at the begin and end of the content.
\starttext
\vbox{\hbox{First}\hbox{Second}}
\vbox{\strut\hbox{First}\hbox{Second}}
\framed[align=flushleft]{\hbox{First}\hbox{Second}}
\framed[align=flushleft,strut=no,autostrut=no]{\hbox{First}\hbox{Second}}
\stoptext
Wolfgang
___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 3560 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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-05-16 14:31 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 [this message]
2016-05-16 14:41 ` Wolfgang Schuster
2016-05-16 15:18 ` Meer, Hans van der
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=38D1FB3E-2605-424C-B6B7-AA3D821CEFE5@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).