From: Eros Albertazzi <phyche1@bo.imm.cnr.it>
Subject: suppressing hyphenation and setlayerframed
Date: Tue, 27 Jul 2004 11:32:38 +0200 [thread overview]
Message-ID: <41062136.3080101@bo.imm.cnr.it> (raw)
1-
I would like to suppress hypenation in a text of a \startfiguretext
within a \setlayerframed
I am aware of the thread in jan 03 on the list and the fact
that\setupalign[nothyphenated] (or \nohyphens) overshoot the right margin
On the other hand I do not know where to put the
align={left,nothyphenated,width} that was suggested in the reply
here is the piece I work with:
\setlayerframed[page][preset=righttop,
column=1,line=30][width=\dimexpr((\paperwidth-2cm)/2),align=]{\getbuffer[b]}
with the buffer:
\startfiguretext
[left][]{}
{\externalfigure[t1][width=.2\textwidth]}
... <<<nohypened text>>...
\stopfiguretext
2-
still awfully raw on context I am looking for the options of
\setlayerframed, list and meaning, command that is absent from manuals
or web info-tools
in details.pdf some examples are build with
\setlayer[..][..]{\framed[..]{..}}
what's the difference, if any, betwwen the two form?
reply other threads:[~2004-07-27 9:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41062136.3080101@bo.imm.cnr.it \
--to=phyche1@bo.imm.cnr.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).