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: Thu, 20 Feb 2014 11:57:37 +0100	[thread overview]
Message-ID: <5305DFA1.8050404@gmx.net> (raw)
In-Reply-To: <5305C3B7.2080608@wxs.nl>

Am 20.02.2014 09:58, schrieb Hans Hagen:
> On 2/19/2014 7:41 PM, Peter Rolf wrote:
>> 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.
> 
> % macros=mkvi
> 
> \definefont[RatherBig][Mono at 60pt]
> 
> \defineeffect [justone] [alternative=outer,rulethickness=1pt]
> \defineeffect [justtwo] [alternative=inner]
> 
> \starttexdefinition example #font#line#text
>     \hbox {
>         \framed [offset=\dimexpr#line/2\relax,strut=no,frame=off] {
>             \definedfont[#font]
>             \defineeffect[bg][alternative=outer,rulethickness=#line]
>             \defineeffect[fg][alternative=inner]
>             \hsmash{\red \effect[bg]{#text}}
>             \hbox  {\blue\effect[fg]{#text}}
>         }
>     }
> \stoptexdefinition
> 
> \starttext
> 
> {\effect[justone]{\RatherBig BIG}}
> 
> {\effect[justtwo]{\RatherBig BIG}}
> 
> \example{Mono at 60pt}{5pt}{BIG}
> 
> \example{Mono at 80pt}{10pt}{BIG}
> 
> \stoptext
> 

Thanks for this nice example (I wasn't aware of this).
But this doesn't really help me with my problem. I guess my example had
too much irritating eye candy, so I made another one :-)

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

The problem is, that I need direct access to the glyphs path(s), as I
must calculate the offset paths for the sub shadows (umbra/penumbra).
Inkscape has a similar function called "inset/outset path", if I
remember right.
In the example I used a negative offset for the umbra shadow (udistance)
and a positive for the penumbra shadow (pdistance). The original path is
drawn as 'arrowpath'.
The path creating algorithm (based on the Tiller-Hanson alg.) works
quite good so far, but still needs a lot of tweaking. And glyphs have a
wide range of shapes, so they are nearly ideal for testing purposes.

Anyhow, it can't be helped, if 'glyph' is not working. I'll test some
ConTeXt generated PDF glyphs (MPpage) then and see if I can optimize the
manual path creation a little bit.

Best wishes,

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
___________________________________________________________________________________


      reply	other threads:[~2014-02-20 10:57 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
2014-02-20  8:58   ` Hans Hagen
2014-02-20 10:57     ` Peter Rolf [this message]

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=5305DFA1.8050404@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).