From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Inkscape command line arguments have changed
Date: Tue, 19 May 2020 11:26:28 -0700 [thread overview]
Message-ID: <CAANrE7pw8LDnjVJ3Cz+S7cy3LRnRAOBEiZVjFFXPWPK+byK4Ew@mail.gmail.com> (raw)
$ inkscape --version
Inkscape 1.0 (4035a4fb49, 2020-05-01)
Pango version: 1.44.7
With the new release of Inkscape, --export-pdf no longer exists. The
new options appear to be:
--export=type=pdf
--export=pdf-version=1.5 (or 1.4)
--export-filename=filename.pdf
Aditya has shown a work-around on TeX.SE. I've changed the code a little:
\startluacode
figures.programs.inkscape={
command="inkscape",
pdfargument=[[
"%oldname%"
--export-dpi=600
--export=type=pdf
--export-filename="%newname%"
]],
pngargument=[[
"%oldname%"
--export-dpi=600
--export=type=png
--export-filename="%newname%"
]],
}
\stopluacode
Unfortunately, this does override outdated command line argument.
ConTeXt appears to pass in the old argument:
context --purgeall --trackers=graphics.conversion filename.tex
Shows:
Unknown option --export-pdf=images/m_k_i_v_genealogy.svg.pdf
How would you replace the export-pdf option for the new version of Inkscape?
(I'll send a bug to the Inkscape issue tracker; it strikes me that
--export-pdf could have remained an alias.)
Thank you!
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2020-05-19 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 18:26 Thangalin [this message]
2020-05-19 18:50 ` Thangalin
2020-05-19 19:20 ` mf
[not found] ` <e39e10a0-ce58-f605-7982-33aa2534773d@fastwebnet.it>
[not found] ` <e384bb93-1827-3f2c-eee0-b00ed886cd28@fastwebnet.it>
[not found] ` <CAANrE7qdHw0jFbFhKXUeZOvBXOQ7JL1+frWOAVS1mMi0Ny-NyA@mail.gmail.com>
2020-05-19 20:32 ` Thangalin
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=CAANrE7pw8LDnjVJ3Cz+S7cy3LRnRAOBEiZVjFFXPWPK+byK4Ew@mail.gmail.com \
--to=thangalin@gmail.com \
--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).