ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	mf <massifr@fastwebnet.it>
Subject: Re: Problem including svg files with Inkscape 1.0~rc1-4
Date: Thu, 30 Apr 2020 17:21:30 +0200	[thread overview]
Message-ID: <deb8e807-0e05-a13e-f52b-69fdc3fd338a@xs4all.nl> (raw)
In-Reply-To: <a491f3fc-21e2-5f03-d66d-2308c4b87450@fastwebnet.it>

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.

there's one more file: grph-con.lua ... (the merged file is not relevant 
as it is for generic but no one uses that one for fonts (like emoji) 
that use svg and the merged file is generated from other files anyway)

Here I also need to adapt the font-ocl replacement file (font-ocm) which 
reminds me that i need to add some already long pending code to the 
luatex binary one of these days.

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
___________________________________________________________________________________

  parent reply	other threads:[~2020-04-30 15:21 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 [this message]
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

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=deb8e807-0e05-a13e-f52b-69fdc3fd338a@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=massifr@fastwebnet.it \
    --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).