From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem including svg files with Inkscape 1.0~rc1-4
Date: Thu, 30 Apr 2020 19:54:43 +0200 [thread overview]
Message-ID: <eef36691-3edb-0191-e719-783f6d39bc64@xs4all.nl> (raw)
In-Reply-To: <20200430153546.GA50580@nereid.neptune>
On 4/30/2020 5:35 PM, Romain Diss wrote:
> Hi,
>
>> Il 30/04/20 14:09, Romain Diss ha scritto:
>>> Hi,
>>>
>>> The last release candidat of Inkscape (1.0~rc1-4 on my Debian sid)
>>> doesn't provide the `--export-pdf=` option anymore. So context can not
>>> convert svg files into the corresponding `m_k_i_v_*` pdf.
>> The command line syntax has changed in version 1. See this:
>> http://wiki.inkscape.org/wiki/index.php/Release_notes/1.0#Command_Line
>>
>> So it's --export-filename in Inkscape 1.00, and --export-pdf in previous
>> versions.
>> If the conversion you need is done by
>> tex/texmf-context/scripts/context/ruby/graphics/inkscape.rb
>> you should edit that file and replace "--export-pdf" with
>> "--export-filename".
> Thanks for this workaround but I suppose I'll need to edit that file
> again after each context update…
>
> However, the change in `inkscape.rb` has no effect, even after updating
> the format with `context --make`… Any idea ?
Hi,
just wondering ... do you need that script when you use mkiv?
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-04-30 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200430120906.GA48095.ref@nereid.neptune>
2020-04-30 12:09 ` Romain Diss
2020-04-30 13:15 ` mf
2020-04-30 15:21 ` Hans Hagen
2020-04-30 15:21 ` Hans Hagen
2020-04-30 16:06 ` mf
2020-04-30 17:56 ` Hans Hagen
2020-04-30 15:35 ` Romain Diss
2020-04-30 17:54 ` Hans Hagen [this message]
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=eef36691-3edb-0191-e719-783f6d39bc64@xs4all.nl \
--to=j.hagen@xs4all.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).