public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Michael Becker <michael-QF1XyMwE1Uwv0rdu9s6TydBPR1lH4CV8@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Citation Cross References in Word
Date: Sat, 31 Dec 2022 08:33:35 -0800 (PST)	[thread overview]
Message-ID: <99cca45b-75f5-439c-8068-0171b86c58b2n@googlegroups.com> (raw)


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

First off, I apologize if this has already been answered somewhere. I 
simply can't seem to find the answer.

I am producing Word docs with Pandoc. In these docs I'm generating chicago 
based citations, i.e., number linked to endnotes.  The footnote link in 
text is working perfectly, it will take me to the appropriate note at the 
end of the document. But, in Word the return link in the notes back to the 
related in text link does not work. It does work in the Pandoc HTML export 
but it does not work in the converted docx file. It appears that the link 
back to the intext footnote is being deleted as the hyperlink is empty. 
When I click on it it returns me back to the top of the document and not to 
the location of the in-text footnote. 

Does anyone of any idea what I might be doing wrong?

-- 
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/99cca45b-75f5-439c-8068-0171b86c58b2n%40googlegroups.com.

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

             reply	other threads:[~2022-12-31 16:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-31 16:33 Michael Becker [this message]
     [not found] ` <99cca45b-75f5-439c-8068-0171b86c58b2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-12 22:20   ` John MacFarlane

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=99cca45b-75f5-439c-8068-0171b86c58b2n@googlegroups.com \
    --to=michael-qf1xymwe1uwv0rdu9s6tydbpr1lh4cv8@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).