ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Rolf <indiego@gmx.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: glyph path
Date: Wed, 19 Feb 2014 19:41:26 +0100	[thread overview]
Message-ID: <5304FAD6.90202@gmx.net> (raw)
In-Reply-To: <5304A2D7.7000500@gmx.net>

Forgot to tell why I need the glyph paths...
I implemented multi path support in drops yesterday and now I want to
test it with some glyphs. Currently I use Inkscape (export the glyph
path as PDF) and pdftoedit to finally get a MP path. Time consuming and
the result still needs a manual clean-up.

Here is my current test example. Needless to say, that the path blew up
my code in the first run (a too low threshold value) :-D

http://www.wuala.com/indiego/public/ConTeXt/pathtest.pdf


Am 19.02.2014 13:25, schrieb Peter Rolf:
> Hi,
> 
> I tried the "Dcaron" example from the MetaPost manual (page 50) and it
> works nicely when called with "mpost".
> 
> % Dcaron.mp
> fontmapfile"=lm-ec.map";
> beginfig(56);
>     picture q;
>     path p;
>     interim ahlength:=12bp;
>     interim ahangle:=25;
>     q:= glyph "Dcaron" of "ec-lmr10" scaled .2;
>     for item within q:
>         p:= pathpart item;
>         drawarrow p withcolor(.6,.9,.6) withpen pencircle scaled 1.5;
>         for j=0 upto length p:
>             pickup pencircle scaled .7;
>             draw (point j of p -- precontrol j of p)
>                 dashed evenly withcolor blue;
>             draw (point j of p -- postcontrol j of p)
>                 dashed evenly withcolor blue;
>             pickup pencircle scaled 3;
>             draw precontrol j of p withcolor red;
>             draw postcontrol j of p withcolor red;
>             pickup pencircle scaled 2;
>             draw point j of p withcolor black;
>         endfor
>     endfor
> endfig;
> % -------
> 
> But how can I get the glyph path(s) with luatex (mplib)?
> 
> Minimal example (glyph.mkiv) and console output are attached (log is
> empty). Looks like I can't use 'fontmapfile' and without it the glyphs
> are not found.
> 
> 
> Peter
> 
> 
> 
> ___________________________________________________________________________________
> 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://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
> 

___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2014-02-19 18:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 12:25 Peter Rolf
2014-02-19 18:41 ` Peter Rolf [this message]
2014-02-20  8:58   ` Hans Hagen
2014-02-20 10:57     ` Peter Rolf

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=5304FAD6.90202@gmx.net \
    --to=indiego@gmx.net \
    --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).