public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: 'russurquhart1' via pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Reference Links with ../DIr type paths
Date: Tue, 18 May 2021 17:19:10 -0700	[thread overview]
Message-ID: <m2wnrvini9.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <ae688578-4e21-4e83-b7d8-ff0c42177e9bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


If you want reliable links in a PDF, link to a heading or
other anchor.

E.g. in /install/index.md, you'll have a heading

# My heading {#foobar}

and then in /access-authentication/install-rbac/index.md,
you'll link to

[here](#foobar)




"'russurquhart1' via pandoc-discuss"
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> writes:

> Having some issues with getting this to work. I have the following 
> directory structure:
>
> /access-authentication
>    /install-rbac
>       index.md
> /install
>    index.md
>
> The first index.md file has a link like the following:
>
> - Version 1.4 or [higher](../../install/index.md)
>
> Clicking that link, in the generated PDF, causes a message saying it 
> doesn't know what to do with that URL.
>
> If i leave it as, just for grins:
>
> - Version 1.4 or [higher](../../install)
>
> The text shows like it should be a link but is not.
>
> Is this due to concatenating all the files from a list.txt file and passed 
> to Pandoc via xargs? 
> Thanks again!!
>
> Russ
>
> On Tuesday, May 18, 2021 at 4:43:14 PM UTC-5 russurquhart1 wrote:
>
>> Very cool! (As a tech writer, may I suggest that you add this as an 
>> example to your docs, or at least front facing ones as I didn't see it!) 
>>
>> Thanks again!
>>
>>
>> Russ
>>
>> On Tuesday, May 18, 2021 at 3:14:10 PM UTC-5 John MacFarlane wrote:
>>
>>> Relative paths are okay.
>>>
>>> "'russurquhart1' via pandoc-discuss"
>>> <pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> writes:
>>>
>>> > On the heels of John's help, I'mhoping to be able to cross another 
>>> thing 
>>> > off my preprocessing script.
>>> >
>>> > I know that a Markdown reference link can be of the form:
>>> >
>>> > [Here is the link](/foo/bar/index.md)
>>> >
>>> > The Markdown we use allows for links like:
>>> >
>>> > [Here is the link](../../two_directories_up/index.md)
>>> >
>>> > (Actually it provides a shortcut of:
>>> >
>>> > [Here is the link](../../two_directories_up)
>>> >
>>> > My concern is the '../' parent directory directive. Is there a way for 
>>> the 
>>> > Pandoc Markdown parser to resolve this correctly, or will i have to add 
>>> > something in the preprocessor to resolve the full path name?
>>> >
>>> > Thanks again for all the help!!
>>> >
>>> > Russ
>>> >
>>> > -- 
>>> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>> > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/pandoc-discuss/e7bd5360-6f74-44c1-8126-7a83dc393298n%40googlegroups.com
>>> .
>>>
>>
>
> -- 
> 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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/ae688578-4e21-4e83-b7d8-ff0c42177e9bn%40googlegroups.com.


      parent reply	other threads:[~2021-05-19  0:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 19:09 'russurquhart1' via pandoc-discuss
     [not found] ` <e7bd5360-6f74-44c1-8126-7a83dc393298n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-18 20:13   ` John MacFarlane
     [not found]     ` <m2fsyjkdfg.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-18 21:43       ` 'russurquhart1' via pandoc-discuss
     [not found]         ` <a7b46e7d-f7d1-4515-910f-ffdd21ab9bf2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-18 22:21           ` 'russurquhart1' via pandoc-discuss
     [not found]             ` <ae688578-4e21-4e83-b7d8-ff0c42177e9bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-19  0:19               ` John MacFarlane [this message]

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=m2wnrvini9.fsf@MacBook-Pro.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).