ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
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 22:49:30 +0200	[thread overview]
Message-ID: <CALBOmsZZfrOb0boqZ7u9qVc9Sibec9c2TUbO_cBH19m6nu6MqA@mail.gmail.com> (raw)
In-Reply-To: <dce567f7-8dea-39c1-a990-016f7cc0a71c@wxs.nl>

On 29 June 2016 at 14:12, Hans Hagen wrote:
> 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 ;

How should one properly compile that file then to get the SVG?

Using just "mpost something.mp" doesn't work that way.

>> (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)

Given that metapost supports SVG natively I imagined that it would
produce a simpler/cleaner output. Thanks a lot for the suggestion,
I'll test it.

It turned out that the (opensource) tools I used for converting SVG
into DXF gives very weird result, so I have to change the other parts
of the "toolchain" as well.

Nevertheless, the question about whether one could convince MP to
output true units in cm/mm/in.

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
___________________________________________________________________________________

  reply	other threads:[~2016-06-29 20:49 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
2016-06-29 20:49   ` Mojca Miklavec [this message]
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=CALBOmsZZfrOb0boqZ7u9qVc9Sibec9c2TUbO_cBH19m6nu6MqA@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).