public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "kurt.pfeifle via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: `\includepdf{...}` raw LaTeX massively scaled down in PDF output by adding `![](image)` to Markdown
Date: Sat, 16 Apr 2016 19:19:37 -0700 (PDT)	[thread overview]
Message-ID: <a632a733-60a7-4996-9ad5-4600d9d8da0c@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1561 bytes --]



I’ve just submitted a bug report (#2856)

*“If Markdown input contains image, then \includepdf{some.pdf} output 
scales down far too much.”*
https://github.com/jgm/pandoc/issues/2856

I have an MWE (minimally working -- i.e. showing the buggy behavior -- 
example) attached to the report there.

The problem is: 

   1. If I use *only* \includepdf{some.pdf} LaTeX snippets within my 
   Markdown, then PDF output is fine. 
   2. As soon as I add one ![](some-image.format) Markdown statement to my 
   file, the previously good some.pdf content gets massively scaled down. 

My current workaround is to use ![](some.pdf) to get my external PDF 
content in, but for me this is a crutch only, for various reasons (one 
reason is that I cannot add Table-of-Contents entries for the 
PDFs-included-as-images as I can do when using \includepdf{...}).

Does anyone know a better workaround?

Is this bug report better addressed to LaTeX developers?
​

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a632a733-60a7-4996-9ad5-4600d9d8da0c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 6111 bytes --]

             reply	other threads:[~2016-04-17  2:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-17  2:19 kurt.pfeifle via pandoc-discuss [this message]
     [not found] ` <a632a733-60a7-4996-9ad5-4600d9d8da0c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-04-17 13:25   ` kurt.pfeifle via pandoc-discuss
2016-04-20  7:47 ` Ulrike Fischer
     [not found]   ` <16afpmc7j9mzp.dlg-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>
2016-04-21 20:05     ` kurt.pfeifle via pandoc-discuss

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=a632a733-60a7-4996-9ad5-4600d9d8da0c@googlegroups.com \
    --to=pandoc-discuss-/jypxa39uh5tlh3mbocffw@public.gmane.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).