public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "barry....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <barry.revzin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Reference link directly to source
Date: Thu, 16 Jun 2022 15:15:21 -0700 (PDT)	[thread overview]
Message-ID: <f5832066-a4af-484c-8b6d-9a145fa9e962n@googlegroups.com> (raw)


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

When using pandoc to write an HTML page, if I add a reference like [@Meow], 
it will generate a link (with no alt text) to #ref-Meow. And then, at the 
very end of the page, I'll my bibliography, which will itself contain the 
link to the real reference. 

This is pretty annoying in an HTML world, where we pretty much 100% of the 
time want to just go to the reference in question. 

Is there a facility in pandoc directly to just change the way that these 
bibliography links work to add the biblio reference as it does today but 
instead change the link to link directly to the destination, and add text 
with the reference title to the link? (See also 
https://github.com/mpark/wg21/issues/88).

Apparently bikeshed (https://github.com/tabatkins/bikeshed/issues/2299) 
supports this via [@Meow inline].

-- 
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/f5832066-a4af-484c-8b6d-9a145fa9e962n%40googlegroups.com.

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

             reply	other threads:[~2022-06-16 22:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 22:15 barry....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [this message]
     [not found] ` <f5832066-a4af-484c-8b6d-9a145fa9e962n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-16 22:43   ` AW: " denis.maier-NSENcxR/0n0

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=f5832066-a4af-484c-8b6d-9a145fa9e962n@googlegroups.com \
    --to=barry.revzin-re5jqeeqqe8avxtiumwx3w@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).