ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Pablo Rodriguez <oinos@gmx.es>
Subject: Re: question about followtext in MP
Date: Wed, 23 May 2018 18:05:07 +0200	[thread overview]
Message-ID: <0d91752c-5b21-8198-daa7-cf5717f86e47@xs4all.nl> (raw)
In-Reply-To: <ac21007d-6b29-d223-8e46-8f0ce39c1bd3@gmx.es>

On 5/23/2018 5:50 PM, Pablo Rodriguez wrote:
> On 05/22/2018 10:22 PM, Hans Hagen wrote:
>> On 5/22/2018 9:05 PM, Pablo Rodriguez wrote:
>>> Dear list,
>>> [...]
>>> Is there any way to followtext in q without changing text direction?
>>>
>>> I need to write the text counter-clockwise, but on outside of the path.
>>>
>>> Reverse changes both text direction and side of the text (related to the
>>> path) and I don’t want to change text direction.
>> it will probably always look bad
>>
>>       \startMPcode
>>          path p ; p := reverse halfcircle scaled (5cm + 0.5LineHeight);
>>          path q ; q := reverse halfcircle rotatedaround (origin, 180)
>>              scaled (5cm +1.3LineHeight);
>>          draw fullcircle scaled 5cm;;
>>          draw followtext(p, "\strut just follow the tokens\enspace") ;
>>          draw followtext(reverse q, "\strut just follow the
>> tokens\enspace") ;
>>         \stopMPcode
> 
> Many thanks for your reply, Hans.
> 
> Is there any way to set origin to another value than (0, 0) in MP?
> 
> I realize it might sound weird, but it would make things easier in an
> example that I’m working on.
redefining origin is a bad idea (don't expect help if you do that)

you can alway sdo

currentpicture := currentpicture shifted - center currentpicture;

-----------------------------------------------------------------
                                           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
___________________________________________________________________________________

  reply	other threads:[~2018-05-23 16:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22 19:05 Pablo Rodriguez
2018-05-22 20:22 ` Hans Hagen
2018-05-23 15:50   ` Pablo Rodriguez
2018-05-23 16:05     ` Hans Hagen [this message]
2018-05-23 16:34       ` Alan Braslau
2018-05-23 16:40       ` Pablo Rodriguez
2018-05-23 17:19         ` Alan Braslau
2018-05-23 19:06           ` Pablo Rodriguez
2018-05-23 21:24             ` Alan Braslau
2018-05-24 16:11               ` Pablo Rodriguez
2018-05-24 16:30                 ` Alan Braslau
2018-05-24 18:27                   ` Pablo Rodriguez
2018-05-23 16:10     ` Alan Braslau

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=0d91752c-5b21-8198-daa7-cf5717f86e47@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=oinos@gmx.es \
    /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).