From: "Idris Samawi Hamid" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: strutted pars?
Date: Fri, 28 Dec 2007 09:02:22 -0700 [thread overview]
Message-ID: <op.t31yt8khnx1yh1@your-b27fb1c401> (raw)
In-Reply-To: <20071228094135.82d26eaa.schuster.wolfgang@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
On Fri, 28 Dec 2007 01:28:23 -0700, Hans Hagen <pragma@wxs.nl> wrote:
> \dontleavehmode \begstrut bla bla \endstrut \par
On Fri, 28 Dec 2007 01:40:50 -0700, Taco Hoekwater <taco@elvenkind.com>
wrote:
> That was a bad example, just try it :-)
Ok, better example attached :-)
> But if you have a chuck of well-controlled text, there is a trick:
> \lineskiplimit=-10000pt
> blaq blaq {\tfc blaq blaq} blaq blaq blaq blaq blaq blaq
> blaq blaq blaq blaq blaq blaq blaq blaq blaq blaq blaq blaq blaq blaq
> {\tfc blaq blaq} blaq blaq blaq blaq blaq blaq
On Fri, 28 Dec 2007 01:41:35 -0700, Wolfgang Schuster
<schuster.wolfgang@googlemail.com> wrote:
> %\lineskiplimit=0pt
> \lineskip=0pt
>
> blah blah {\tfc blah blah} blah blah blah blah blah blah
> blah blah blah blah blah blah blah blah blah blah blah blah blah blah
> {\tfc blah blah} blah blah blah blah blah blah
I have attached a file and pdf that illustrate all four scenarios; none of
the above solutions seems to work, but maybe I need to tinker with the
def's in test-strut.tex.
For my purposes Hans' approach is the most useful (if we can make it work)
because otherwise it makes me have to do more copy-editing of paragraphs
and I might miss some (based on Taco's observation it is probably not wise
to make this global).
Best wishes
Idris
--
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shi`i Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
[-- Attachment #2: test-strut.pdf --]
[-- Type: application/pdf, Size: 3446 bytes --]
[-- Attachment #3: test-strut.tex --]
[-- Type: application/x-tex, Size: 1523 bytes --]
[-- Attachment #4: Type: text/plain, Size: 487 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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2007-12-28 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 21:20 Idris Samawi Hamid
2007-12-28 8:28 ` Hans Hagen
2007-12-28 8:40 ` Taco Hoekwater
2007-12-28 8:41 ` Wolfgang Schuster
2007-12-28 16:02 ` Idris Samawi Hamid [this message]
2007-12-28 16:07 ` Taco Hoekwater
2007-12-28 16:21 ` Idris Samawi Hamid
2007-12-28 16:39 ` Hans Hagen
2007-12-28 18:20 ` Idris Samawi Hamid
2007-12-28 19:10 ` Idris Samawi Hamid
2007-12-28 20:34 ` Hans Hagen
2007-12-28 22:14 ` Idris Samawi Hamid
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=op.t31yt8khnx1yh1@your-b27fb1c401 \
--to=ishamid@colostate.edu \
--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).