ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Figure Help
Date: Thu, 10 Nov 2011 09:57:34 +0100	[thread overview]
Message-ID: <4EBB91FE.60201@wxs.nl> (raw)
In-Reply-To: <007001cc9f29$7d1a4190$774ec4b0$@gmx.de>

On 9-11-2011 22:49, Christian wrote:
>>>> May be I missed one or the other mail on this topic.
>>>> There is indeed support for svg-inclusion in MKIV. In order to be
>>>> possibly of help I would like you to send a minimal example.
>>>
>>> Note: When I include the extension in the filename (testimage.svg) I
>>> get "!LuaTeX error: cannot find image file 'm_k_i_v_testimage.pdf'"
>>> probably due to some failed conversion stuff.
>>
>> Is write18 enables? Do you have inkscape binary in your PATH?
>
> Well, no and no. And the way I see it, proper svg support should not need a prior conversion to pdf done by an entirely different program.
> If I wanted that, I can as well save it as pdf or convert it myself.
>
> I knew about the detour via inkscape, but I hoped for native support.
>
> So I guess svg is not supported then?

no, and it would be a typical example of adding something to the engine 
that's bigger than the engine itself which is definitely not on our 
agenda (the leaner the meaner)

also, converting svg runtime and doing that each run is pretty 
inefficient; the mkiv runtime conversion only converts (using inkscape) 
when the file has changed and including a pdf file is pretty fast

(the same is true for png files: the pfd format supports png compression 
which is not the same as embedding png so for some variants it's better 
to convert beforehand so that inclusion is faster)

Hans

-----------------------------------------------------------------
                                           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
___________________________________________________________________________________


  parent reply	other threads:[~2011-11-10  8:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04  2:58 Kip Warner
2011-11-04  3:22 ` Pontus Lurcock
2011-11-04  9:32 ` Hans Hagen
2011-11-08  3:26   ` Kip Warner
2011-11-08  5:21     ` Pontus Lurcock
2011-11-08 16:59     ` Willi Egger
2011-11-09 20:58       ` Christian
2011-11-09 21:41         ` Aditya Mahajan
2011-11-09 21:49           ` Christian
2011-11-09 22:08             ` Aditya Mahajan
2011-11-10  8:57             ` Hans Hagen [this message]
2011-11-11  4:18   ` Kip Warner

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=4EBB91FE.60201@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).