From: mf <massifr@fastwebnet.it>
To: ntg-context@ntg.nl
Subject: Re: lmtx update / teaser
Date: Tue, 2 Mar 2021 11:15:21 +0100 [thread overview]
Message-ID: <4d7d579e-8bc5-7de1-704f-cd1d1b41653f@fastwebnet.it> (raw)
In-Reply-To: <6c34da9c-9315-b282-0130-ea1226d39bdc@xs4all.nl>
Il 01/03/21 15:44, Hans Hagen ha scritto:
>
> \starttext
>
> \startuseMPgraphic{circle}
> lmt_parshape [
> path = fullcircle scaled 136mm,
> offset = 2mm,
> bottomskip = - 1.5LineHeight,
> ] ;
> \stopuseMPgraphic
>
> \start
> \startshapedparagraph[list=circle,mp=circle,repeat=yes,method=cycle]%
list=... refers to a previous \startparagraphshape definition, so mp=...
tells ConTeXt that the definition is derived from MetaPost code instead.
Just mp=... could be enough, but maybe "list=xyz,mp=xyz" makes it clear
that mp is used to get a parshape from MetaPost instead of a
\startparagraphshape definition.
> \setupalign[verytolerant,stretch,last]\dontcomplain
What's the meaning of \dontcomplain? Why is it needed there?
BTW, \startparagraphshape, \stopparagraphshape, \startshapedparagraph,
\stopshapedparagraph should be added to the .xml documentation files.
The "right", "left", "both", "copy", "repeat" syntax in
\startparagraphshape is really handy.
Thanks,
Massi
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-03-02 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 14:44 Hans Hagen
2021-03-01 17:27 ` Otared Kavian
2021-03-01 18:13 ` Hans Hagen
2021-03-02 10:15 ` mf [this message]
2021-03-02 10:33 ` Hans Hagen
2021-03-02 10:47 ` 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=4d7d579e-8bc5-7de1-704f-cd1d1b41653f@fastwebnet.it \
--to=massifr@fastwebnet.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).