ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jan U. Hasecke via ntg-context" <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Jan U. Hasecke" <juh+ntg-context@mailbox.org>
Subject: Problem with SVG an conversion mp (was: Improving pandoc's ConTeXt output)
Date: Mon, 6 Jun 2022 07:21:13 +0200	[thread overview]
Message-ID: <Yp2OydX9KCLV8Bie@odysseus> (raw)
In-Reply-To: <CAANrE7oG-r7ya35MZa3Xu6txrb2fjpLxYw0KS3VTvO8Va3__Bw@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 852 bytes --]

Am Sun, Jun 05, 2022 at 04:52:52PM -0700 schrieb Thangalin:
> This allows me to eliminate the dependency on both Pandoc and Inkscape.
> I've also encountered some problems with SVG to MP, but Hans is usually
> quick to fix the bugs given a minimal working example that pinpoints the
> problem. Either way, it's possible to retain the Inkscape step by telling
> ConTeXt not to use the MP conversion, as you alluded to, Juh.

So true. So here is a mwe, which works with inkscape and not with mp.

As some svg works with mp, I guess that mp cannot handle all svg
dialects. But this is only a guess.

juh


-- 
Autoren-Homepage: ......... http://literatur.hasecke.com
Satiren & Essays: ......... http://www.sudelbuch.de
Privater Blog: ............ http://www.hasecke.eu
Netzliteratur-Projekt: .... http://www.generationenprojekt.de



[-- Attachment #1.1.2: mwe.tex --]
[-- Type: text/x-tex, Size: 121 bytes --]

\starttext
%\externalfigure[figure][width=10cm,conversion=mp]
\externalfigure[figure][width=10cm,conversion=mp]
\stoptext

[-- Attachment #1.1.3: figure.svg --]
[-- Type: image/svg+xml, Size: 9398 bytes --]

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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:[~2022-06-06  5:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05  7:07 Improving pandoc's ConTeXt output Albert Krewinkel via ntg-context
2022-06-05  8:20 ` juh via ntg-context
2022-06-05  9:39   ` Denis Maier via ntg-context
2022-06-05 14:15   ` Albert Krewinkel via ntg-context
2022-06-05 16:38     ` juh+ntg-context--- via ntg-context
2022-06-05 23:52       ` Thangalin via ntg-context
2022-06-06  5:21         ` Jan U. Hasecke via ntg-context [this message]
2022-06-06  5:51         ` juh+ntg-context--- via ntg-context
2022-06-05  9:46 ` Denis Maier via ntg-context
2022-06-05 10:01 ` Hans Hagen via ntg-context
2022-06-05 11:08   ` Wolfgang Schuster via ntg-context
2022-06-05 14:30     ` Albert Krewinkel via ntg-context
2022-06-06 20:47       ` Henning Hraban Ramm via ntg-context
2022-06-08 13:43 ` Albert Krewinkel via ntg-context

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=Yp2OydX9KCLV8Bie@odysseus \
    --to=ntg-context@ntg.nl \
    --cc=juh+ntg-context@mailbox.org \
    /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).