ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: mf <massifr@fastwebnet.it>
To: Hans Hagen <j.hagen@xs4all.nl>,
	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 18:06:50 +0200	[thread overview]
Message-ID: <540fc7f7-8ec3-e760-4792-ad37ae45fa9f@fastwebnet.it> (raw)
In-Reply-To: <deb8e807-0e05-a13e-f52b-69fdc3fd338a@xs4all.nl>

Il 30/04/20 17:21, Hans Hagen ha scritto:
> On 4/30/2020 3:15 PM, mf wrote:
>> 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.
>>>
>>> It seems that the `--export-filename=` option does the job.
>>>
>>> Thank in advance.
>>>
>>
>> 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.
>>
>> I tried to specify both options with Inkscape 0.92 hoping the wrong 
>> one would be ignored, without success; you get only a warning, not an 
>> error, but the conversion fails anyway.
>>
>> To make ConTeXt work with both versions, it should run "inkscape 
>> --version" before doing the actual conversion, to decide the right 
>> option.
>>
>> 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".
>>
>> There are two other files where that option is used:
>>
>> tex/texmf-context/tex/generic/context/luatex/luatex-fonts-merged.lua
>> tex/texmf-context/tex/context/base/mkiv/font-ocl.lua
>>
>> it's font-related code; if you need it, do the same replacement of 
>> "--export-pdf" in those two files and then remake the format with
>>
>> context --make
>>
>> and the export to pdf will work with Inkscape 1.00.
>> But it won't work with Inkscape 0.92.
> As I don't wan to waste code for testing the version, when do we change 
> this? Now? I downloaded version 1 so it is available for all platforms.
> 

1.0 is a release candidate. Romain is using the unstable version of 
Debian (sid), so he's using Inkscape 1.00rc.

Anyway Inkscape 0.92 will be around for some time, so a better solution 
would be defaulting to the export option of the current version of 
Inkscape unless the user sets an environment variable (INKSCAPE_VERSION?).

So a test of an environment variable instead of spawning a process to 
run "inkscape --version".

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

  reply	other threads:[~2020-04-30 16:06 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 [this message]
2020-04-30 17:56         ` Hans Hagen
2020-04-30 15:35     ` Romain Diss
2020-04-30 17:54       ` Hans Hagen

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=540fc7f7-8ec3-e760-4792-ad37ae45fa9f@fastwebnet.it \
    --to=massifr@fastwebnet.it \
    --cc=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).