From: Giuseppe Bilotta <gip.bilotta@iol.it>
Subject: Re: Two framed texts on the same line
Date: Fri, 25 Nov 2005 16:12:07 +0100 [thread overview]
Message-ID: <1083648101.20051125161207@iol.it> (raw)
In-Reply-To: <1191176180.20051125121527@iol.it>
For what it's worth, I'm now using the following:
\defineframedtext[lepi][align=raggedright,width=fit,offset=0pt,frame=off,location=none]
\defineframedtext[repi][align=raggedright,width=fit,offset=0pt,frame=off,location=none]
\definepairedbox[lrepi][location={right,top}]
\noindent
\startlepi[none]
\obeylines
{\bf Coordinatore}
prof. F.~Nicolosi
\stoplepi\hfill\startrepi[none]
\obeylines
{\bf Tutor}
prof. G.~Russo
\stoprepi
The [none] spec is required until the location=none
specification is fixed :)
TeX does complain about underfull boxes, but the output is
just what I need.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2005-11-25 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 11:15 Giuseppe Bilotta
2005-11-25 13:04 ` Hans Hagen
2005-11-25 14:20 ` Re[2]: " Giuseppe Bilotta
2005-11-25 14:32 ` Hans Hagen
2005-11-25 15:05 ` Re[2]: " Giuseppe Bilotta
2005-11-25 15:12 ` Giuseppe Bilotta [this message]
2005-11-25 17:30 ` 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=1083648101.20051125161207@iol.it \
--to=gip.bilotta@iol.it \
--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).