ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: LMTX MetaFun SVG trouble, a portion of the SVG is cut of in the PDF
Date: Thu, 17 Dec 2020 18:45:58 +0100	[thread overview]
Message-ID: <6dfba09d-a5ff-3152-f812-8fccc47c889d@gmx.es> (raw)
In-Reply-To: <CAL+bK4NPg-7cWLqL0H=ECUrB7x49W5JBuL6rC6X9EVkMcHMZqg@mail.gmail.com>

On 12/17/20 5:08 PM, Neven Sajko wrote:
> On Thu, 17 Dec 2020 at 15:27, Aditya Mahajan <adityam@umich.edu> wrote:
> [...]
>> Can you check with a desktop pdf viewer as well.
>
> It looks the same with MuPDF.

Hi Neven,

it seems to be an issue with the conversion of the SVG file.

> This is a combined TeX file containing two different ways I took to
> try to accomplish the same thing:

How about a much simpler approach?

  \starttext
  \framed[offset=overlay]

{\externalfigure[hammingCoderStopwatch-hammingCoder-gcc-RowsSparse-1023-1013.svg]
      [width=\textwidth, offset=20pt]}
  \stoptext

In that case, if you use \externalfigure, ConTeXt will invoke Inkscape
to convert the file. The output is way better.

Just in case it may help,

Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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-12-17 17:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 14:03 Neven Sajko
2020-12-17 15:27 ` Aditya Mahajan
2020-12-17 16:08   ` Neven Sajko
2020-12-17 17:45     ` Pablo Rodriguez [this message]
2020-12-17 20:56       ` Pablo Rodriguez
2020-12-18 15:41 ` 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=6dfba09d-a5ff-3152-f812-8fccc47c889d@gmx.es \
    --to=oinos@gmx.es \
    --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).