ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "honyk" <j.tosovsky@email.cz>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: Including a large SVG image
Date: Mon, 3 Jun 2013 18:53:38 +0200	[thread overview]
Message-ID: <7037.52849153734$1370278443@news.gmane.org> (raw)
In-Reply-To: <CAF=dkzw=SHhBiFdw7LsqrcckixDqkAijBNfLgCTbpT12JUnoPA@mail.gmail.com>

> Sander Maijers wrote:
> >> I have a few SVG graphics of multiple megabytes. They contain a lot
> >> of objects (text/shapes). All graphics except for one gets properly
> >> included in my ConTeXt document.
> 
> Marco Patzer wrote:
> > Maybe inkscape failed to convert the file. Is a corresponding
> > m_k_i_v_filename.svg.pdf file generated?
> 
> It might be informative to try running the Inkscape conversion
> manually. This is the command line ConTeXT uses:
> 
>     inkscape "%oldname%" --export-dpi=600 -A "%newname%"
> 
> (The quotation marks are literal: they are there in case the filename
> has spaces, e.g.)

If processing in Inkscape fails, you can try another tool: http://xmlgraphics.apache.org/batik/tools/rasterizer.html

It can (despite its name) transcode SVG to vector PDF:

java -Xmx2G -jar batik-rasterizer.jar -m application/pdf image.svg

In that case you have to transcode your files first and reference PDF variants in your input.

Jan

___________________________________________________________________________________
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:[~2013-06-03 16:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03 11:12 Sander Maijers
2013-06-03 11:25 ` Marco Patzer
2013-06-03 13:46   ` Sietse Brouwer
2013-06-03 16:53     ` honyk [this message]
     [not found]     ` <00ab01ce607a$e55f2ea0$b01d8be0$@tosovsky@email.cz>
2013-06-04 17:35       ` Sander Maijers
2013-06-05 10:38         ` Sietse Brouwer
2013-06-05 12:58           ` Sander Maijers
2013-06-05 13:01             ` luigi scarso
2013-06-05 13:06               ` Sander Maijers
2013-06-05 13:09                 ` luigi scarso
2013-06-05 13:13                   ` Sander Maijers
2013-06-05 13:15                     ` luigi scarso
2013-06-08 10:04                       ` Sander Maijers
2013-06-09 22:21                         ` Sander Maijers
2013-06-09 23:04                           ` luigi scarso
2013-06-10  8:26                             ` luigi scarso
2013-06-10  9:23                               ` Sietse Brouwer
2013-06-10  9:28                                 ` luigi scarso
2013-06-10  0:25                           ` Sietse Brouwer
2013-06-10  9:08                           ` Marco Patzer
2013-06-10 10:26                             ` Sander Maijers
2013-06-10 10:37                               ` luigi scarso
2013-06-15 14:01                                 ` Sander Maijers

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='7037.52849153734$1370278443@news.gmane.org' \
    --to=j.tosovsky@email.cz \
    --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).