From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [Metapost] Using mkIV and metapost to produce SVG
Date: Tue, 06 May 2014 13:15:41 +0200 [thread overview]
Message-ID: <5368C45D.2040504@wxs.nl> (raw)
In-Reply-To: <OFBAD979EB.2759887B-ONC1257CCF.00416B56-C1257CCF.00416B57@integrator-ag.de>
On 5/5/2014 1:54 PM, ralf.waldvogel@pta.de wrote:
> Dear all,
>
> I would like to produce an svg file from a Metapost input file using
> some of ConTeXt's typesetting features (esp. using System OTF Fonts)
> using something like:
>
> \startbuffer[buffer:dummy]
> \start
> \startcolor[white]
> \framed[align=middle,width=28mm,frame=off]
> {
> \SansBodyBold % Font definition done earlier
> Test to \par
> rendered \par
> }
> \stopcolor
> \stop
> \stopbuffer
>
> % ....
>
>
> \startuniqueMPgraphic{mp:margin}
> picture text;
> text := btex \getbuffer[buffer:dummy] etex;
> draw text shifted(-11.8mm,-4.8mm );
>
> % Some more fancy drawing her
> \stopuniqueMPgraphic
>
> Can I render that with MetaPost to SVG?
no
> Is it possible to render text as paths not as referenced glyphs in
> MetaPost/ConTexT?
no, unless you use the graphic text features
>
> Unfortunately I have to stick to SVG as the resulting output format.
> Converting from PDF to SVG is not an option at the moment due a)
> performance considerations and b) trouble with generated font names in
> the resulting ConTeXt PDF file (inkscape as well as pdf2svg produce real
> strange results).
performance should not really be an issue as one can cache
what strange results?
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2014-05-06 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 11:54 ralf.waldvogel
2014-05-06 11:15 ` Hans Hagen [this message]
2014-05-06 11:31 ralf.waldvogel
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=5368C45D.2040504@wxs.nl \
--to=pragma@wxs.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).