From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: double followtokens?
Date: Sat, 7 Apr 2018 23:25:13 +0200 [thread overview]
Message-ID: <026e5b07-3364-2011-50bf-29a249fb41b7@xs4all.nl> (raw)
In-Reply-To: <b5d04160-ebc7-0e29-457d-0ba045ad4f94@gmx.es>
On 4/7/2018 11:04 PM, Pablo Rodriguez wrote:
> Dear list,
>
> I have the following sample:
>
> \useMPlibrary[txt]
>
> \starttext
>
> \startuseMPgraphic{followtokens}
> path RotPath ; RotPath := reverse halfcircle ;
> % path RotPath ; RotPath := halfcircle rotatedaround (origin, 180) ;
> \stopuseMPgraphic
>
> \followtokens{Just follow the tokens}
> \stoptext
>
> How can I get both paths (in diverse directions)?
>
> I would like to repeat the same text twice, separating both sentences
> with a character.
>
> I have to ask this, beause MetaPost is all Greek to me.
i have no clue what you mean but this will change the direction
\followtokens{\cldcontext{
table.concat (
table.reverse (
utf.totable (
"Just fillow the öëps tokens"
)
)
)
}}
because you want to get kerning and ligatures etc right although fonts
might lack the kern pair for weird words
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2018-04-07 21:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 21:04 Pablo Rodriguez
2018-04-07 21:25 ` Hans Hagen [this message]
2018-04-07 22:11 ` Pablo Rodriguez
2018-04-08 14:41 ` Hans Hagen
2018-04-08 14:56 ` Build for Alpine Linux Brian Hunt
2018-04-08 20:50 ` Mojca Miklavec
2018-04-08 21:09 ` Arthur Reutenauer
2018-04-08 21:26 ` Henri Menke
2018-04-08 21:45 ` Arthur Reutenauer
2018-04-09 0:50 ` Henri Menke
2018-04-09 18:59 ` Brian Hunt
2018-04-09 19:35 ` Arthur Reutenauer
2018-04-10 11:05 ` Brian Hunt
2018-04-10 12:26 ` Brian Hunt
2018-04-10 16:27 ` Alan Braslau
2018-04-10 20:55 ` Arthur Reutenauer
2018-04-11 12:30 ` Brian Hunt
2018-04-11 20:08 ` Brian Hunt
2018-04-11 20:24 ` Aditya Mahajan
2018-04-11 20:37 ` Hans Hagen
2018-04-11 21:08 ` Brian Hunt
2018-04-13 11:14 ` Mojca Miklavec
2018-04-13 11:42 ` Henri Menke
2018-04-13 19:54 ` Henning Hraban Ramm
2018-04-13 20:02 ` Aditya Mahajan
2018-04-13 12:49 ` Hans Hagen
2018-04-11 23:13 ` Henri Menke
2018-04-13 10:37 ` Brian Hunt
[not found] ` <CALBOmsaXyTXhR=j6Ht1LwKGcfxMD4sHjQnEOxtjH-4gc3b5R8g@mail.gmail.com>
[not found] ` <20180417152547.GA1755070@phare.normalesup.org>
2018-04-17 15:54 ` Thomas A. Schmitz
2018-04-08 18:10 ` double followtokens? Pablo Rodriguez
2018-04-08 21:17 ` Hans Hagen
2018-04-09 18:25 ` Pablo Rodriguez
2019-01-01 18:17 ` Hans van der Meer
2019-01-01 20:17 ` 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=026e5b07-3364-2011-50bf-29a249fb41b7@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).