From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Creating SVG: using MetaFun, exporting proper units, conversion to DXF
Date: Wed, 29 Jun 2016 14:12:46 +0200 [thread overview]
Message-ID: <dce567f7-8dea-39c1-a990-016f7cc0a71c@wxs.nl> (raw)
In-Reply-To: <CALBOmsZ_e57=sMRL36Lrmg4yyikLK7A+g46ceBhWkv2f+BcB9w@mail.gmail.com>
On 6/29/2016 12:31 PM, Mojca Miklavec wrote:
> Hi,
>
> I want to play with CNC and don't yet have any experience with CAD
> software (nor the licence for the expensive ones) other than perhaps
> some Blender, so I decided to try to use the super ugly route with
> metapost -> svg -> dxf -> g-code
> for the first time.
>
> I have a few questions.
>
> (1) I love Hans' shortcuts in metafun, but I seem to remember that things like
> input metafun;
> or perhaps
> input mp-tool;
> used to work, so that I don't have to remember to use
> mpost -mem=metafun my-drawings.mp
> when compiling the graphics.
>
> Did the method with "input" ever work (or is it supposed to work)? Now
> I'm getting a bunch of weird errors.
> I would love to specify everything in the source file and then just
> call mpost. If that doesn't work, that's fine, I can still add
> "-mem=metafun", but ...
input metafun.mpiv ;
> (2) I guess that using "raw metapost" is the only sane way to generate
> SVG. If I use metapost inside ConTeXt that's probably not going to
> work, right?
>
> (3) Is there any way to convince the SVG output mode to generate something like
> <svg ... width="100.0mm" height="100.0mm" ... >
> rather than
> <svg ... width="283.46456692913387" height="283.46456692913387" ... >
> because the program I use to convert SVG to DXF has troubles
> interpreting "points" properly. I read somewhere that they assume 90
> points per inch because that's Inkskape's default.
why not just
\startMPpage
whatever you want
\stopMPpage
and then use mudraw (mutools) to go from pdf to svg (that's what i do
when i need svg)
> (4) Does anyone have a better proposal for conversion into DXF (or
> G-code)? I'm currently playing with FreeCAD and I've seen some
> tutorials showing that AutoCAD can open PDF directly, but I don't want
> to buy AudoCAD just for the sake of converting files.
>
> (Not to mention that FreeCAD's SVG importer crashes when reading
> output from MetaPost unless I manually remove parts of the SVG, but
> that's an unrelated problem that I'm somehow able to overcome.)
>
> Thank you,
> Mojca
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | 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:[~2016-06-29 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 10:31 Mojca Miklavec
2016-06-29 12:12 ` Hans Hagen [this message]
2016-06-29 20:49 ` Mojca Miklavec
2016-06-30 7:15 ` Hans Hagen
2017-02-16 20:07 ` William Adams
2017-02-17 6:33 ` Mojca Miklavec
2016-06-29 21:05 ` Jan Tosovsky
2017-07-27 1:52 ` Mojca Miklavec
2017-07-27 8:49 ` Hans Hagen
2017-07-27 14:21 ` Mojca Miklavec
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=dce567f7-8dea-39c1-a990-016f7cc0a71c@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).