From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: framedtext
Date: Mon, 11 Apr 2016 19:10:48 +0200 [thread overview]
Message-ID: <570BDA98.3010406@gmail.com> (raw)
In-Reply-To: <42AFAD26-1009-4AAC-A4AD-62481239FA04@uva.nl>
[-- Attachment #1.1: Type: text/plain, Size: 981 bytes --]
> Meer, Hans van der <mailto:H.vanderMeer@uva.nl>
> 11. April 2016 um 18:49
>
>
> Could be of course. But the question is: from where the
> counterintuitive behavioud of \hfil and \hfil?
> It is my nature to be not satisfied until I know ;-)
It's easy to explain on the following example.
%%%% begin example
\starttext
\hfil Text\hfil
\hfill Text\hfill
\stoptext
%%%% end example
At the end of a paragraph TeX removes the last skip and inserts the
\parskipfill [1] value which is by default "0pt plus 1fil".
For the first text line this results in the expected output but not for
the second line because the inserted "fil" is smaller than the needed
"fill". You can check this when you change the \parskipfill
stretchability from fil to fill:
%%%% begin example
\starttext
\hfill Text\hfill
\start \parfillskip = 0pt plus 1 fill
\hfill Text\hfill \par
\stop
\stoptext
%%%% end example
[1] https://www.tug.org/utilities/plain/cseq.html#parfillskip-rp
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2401 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-04-11 17:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 10:08 framedtext Meer, Hans van der
2016-04-11 10:28 ` framedtext Mari Voipio
2016-04-11 10:36 ` framedtext Meer, Hans van der
2016-04-11 16:13 ` framedtext Alan BRASLAU
2016-04-11 16:49 ` framedtext Meer, Hans van der
2016-04-11 16:59 ` framedtext Hans Hagen
2016-04-11 17:10 ` Wolfgang Schuster [this message]
2016-04-11 19:44 ` framedtext Meer, Hans van der
-- strict thread matches above, loose matches on Subject: below --
2010-03-23 12:34 framedtext Hans van der Meer
2010-03-23 18:00 ` framedtext 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=570BDA98.3010406@gmail.com \
--to=schuster.wolfgang@gmail.com \
--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).