From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: sacling isue in lmt_followtext
Date: Sat, 5 Dec 2020 15:03:50 +0100 [thread overview]
Message-ID: <ce4a4331-0d97-0663-ad1f-79f604aa8f36@gmx.es> (raw)
Hi Hans,
I have this sample:
\starttext
\startMPcode{doublefun}
draw lmt_followtext [
text = " ·\input{zapf} ",
path = ((12,0)--(32,15)--(50,0)--(45,26)--(64,42)
--(40,42)--(32,65)--(24,42)--(0,42)--(0,42)
..(20,26)--(12,0)),
autoscaleup = "max",
reverse=true,
] xsized TextWidth ;
\stopMPcode
\stoptext
Text doesn’t scale properly (I would say starting with latest from
2020.12.03 19:02). It gets worse with \dorecurse{2}.
With current latest (2020.12.04 20:22), each glyph seems to have a
different scaling.
I even wonder whether all glpyhs are embedded (using
\setupbodyfont[dejavu] and \input{aristotle-grc}).
But this may be my impression, since random scaling in each glyph might
be distorting the glyphs
With latest from 2020.12.01 17:52, I get perfect scaling in lmt_followtext.
Am I missing something or have I hit a bug?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2020-12-05 14:03 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=ce4a4331-0d97-0663-ad1f-79f604aa8f36@gmx.es \
--to=oinos@gmx.es \
--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).