public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Don Mankewich <don.mankewich-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Links to external PDF don't work in PDF output
Date: Sun, 17 Sep 2017 14:11:49 -0700 (PDT)	[thread overview]
Message-ID: <2f9ebd82-d6e2-4947-81bd-36045e26e7b7@googlegroups.com> (raw)
In-Reply-To: <3e084be5-8931-4391-ab2c-7361e992c544-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

I'm using pandoc 1.19.1.2. I'm running it on a machine with Windows 10 
Home. I'm using Git Bash to run pandoc because I need the wildcard 
expansion workaround suggested by another user to expand *.md as I want to 
PDF multiple documents.

$ pandoc -v
pandoc.exe 1.19.2.1
Compiled with pandoc-types 1.17.0.4, texmath 0.9, skylighting 0.1.1.4

On Friday, September 15, 2017 at 10:14:01 AM UTC+10, Don Mankewich wrote:
>
> I'm creating documents with markdown which include reference links to 
> external PDF documents which exist in the same folder. When I use pandoc to 
> generate a PDF document from my markdown, there appear to be links in the 
> PDF when I hover over the labels but the external PDF does not open when I 
> click the link. I don't get any warnings of skipped files. Here's an 
> example of my markdown reference, it's in a numbered list. 
>
>  [ats alert tables](ats-alert-database-diagram.pdf)
>
> I have read that pandoc references relative file paths according to the 
> directory where pandoc is executed but I'm running pandoc in the directory 
> containing the external PDF so I shouldn't have to add further pathing 
> information should I? I'm also using Harp JS to create a static site from 
> my content and the link references work in Harp so I don't want to change 
> that to support pandoc. Ideally the relative paths should for both pandoc 
> and Harp.
>
> Any suggestions? 
>

-- 
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/2f9ebd82-d6e2-4947-81bd-36045e26e7b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

  parent reply	other threads:[~2017-09-17 21:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15  0:14 Don Mankewich
     [not found] ` <3e084be5-8931-4391-ab2c-7361e992c544-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-15 15:33   ` John MacFarlane
2017-09-17 21:11   ` Don Mankewich [this message]
2017-09-18  1:30   ` Don Mankewich
     [not found]     ` <5e3baa08-1fe4-417e-b930-4e0ee8a44568-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-18  4:25       ` John MacFarlane
2017-09-18  4:57   ` Don Mankewich
2017-09-18  5:09   ` Don Mankewich
2017-09-20 22:31   ` Don Mankewich

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=2f9ebd82-d6e2-4947-81bd-36045e26e7b7@googlegroups.com \
    --to=don.mankewich-pkbjnfxxiarbdgjk7y7tuq@public.gmane.org \
    --cc=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).