From: Gerben Wierda <gerben.wierda@rna.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: followtext, lmt_followtext and an offset of the glyphs typeset along the path
Date: Sun, 3 May 2020 15:01:35 +0200 [thread overview]
Message-ID: <106114AC-5BC6-4CF2-A1C8-03262138DA46@rna.nl> (raw)
In-Reply-To: <69BD595D-F6CA-47F4-86D4-2428A2ABF893@scorecrow.com>
[-- Attachment #1.1: Type: text/plain, Size: 1613 bytes --]
>>>> Am 01.05.2020 um 10:26 schrieb Gerben Wierda <gerben.wierda@rna.nl>:
>>>>
>>>> I have been looking at lmt_followtext and followtext to get typesetting done along a path. That works fine, except that in my case, I need the text to not be exactly on that path, I need it to hover slightly above tor below he path. Given that the path may have an unpredictable form, that means that all the glyphs need to be shifted a bit, there is no generic transfrom of the entire text string that will work,
>>>
>>> Can’t you duplicate and shift the path, i.e. keep the original visible and make the copy that carries the text invisible? That’s what I would do in a graphical application, but I would be surprised if MP wouldn’t know a transformation for this purpose.
>>
>> No, that is what I did in the example, fiddling, but there is no transformation that will work in all cases. E.g. on the left side of the bump, I need to go to the upper left, on the right side to the upper right. There is no single shift that helps me. Nor a scale rotation or shift combination. That could be managed by only going up (though the distance to the path would vary, on the sides the text would be very close or on the top it would be too far.)
>>
>
> There is an example, at the link below, of creating a parallel path that claims to cope with sharp bends in the original path. You might be able to adapt it?
> <https://therion.speleo.sk/wiki/metapost#shuttering_two_parallel_lines <https://therion.speleo.sk/wiki/metapost#shuttering_two_parallel_lines>>
That looks great. I’m going to investigate.
G
[-- Attachment #1.2: Type: text/html, Size: 5081 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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:[~2020-05-03 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 8:26 Gerben Wierda
2020-05-01 15:10 ` Henning Hraban Ramm
2020-05-01 16:33 ` Gerben Wierda
2020-05-02 14:37 ` ntg
2020-05-03 13:01 ` Gerben Wierda [this message]
2020-05-03 15:52 ` followtext, lmt_followtext and an offset of the glyphs typeset along the path (suggestion works) Gerben Wierda
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=106114AC-5BC6-4CF2-A1C8-03262138DA46@rna.nl \
--to=gerben.wierda@rna.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).