public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Cassandra Lyderitz <cassandra.lyderitz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Format cross-references and web hyperlinks differently in Word
Date: Sat, 8 Jan 2022 11:09:50 -0800 (PST)	[thread overview]
Message-ID: <60a0cabf-884e-452c-b094-9f6b1a9f546an@googlegroups.com> (raw)


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

Is there a way to format cross-references and web hyperlinks differently 
when converting Markdown to MS Word with Pandoc? 

On the one hand, since the output remains digital, I definitely need 
clickable cross-references to images, tables etc., so I need to set the 
`ref-hyperlink` parameter to `true`. 
I need the clickable cross-references not to stand out from the surrounding 
text, i. e. they need to remain without underscores and black. 

On the other hand, I would like the true hyperlinks, i. a. web links, to be 
blue and underscored. Moreover, it would be great if the web links were 
clickable. 

However, in the proposed sample doc template, the same `Hyperlink` style is 
governing the appearance of both objects. I have seen such unused styles  
as `Smart Link` and `Smart Hyperlink`, but do they mean anything to pandoc? 

Thanks in advance for any response. 

-- 
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/60a0cabf-884e-452c-b094-9f6b1a9f546an%40googlegroups.com.

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

             reply	other threads:[~2022-01-08 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08 19:09 Cassandra Lyderitz [this message]
     [not found] ` <60a0cabf-884e-452c-b094-9f6b1a9f546an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-08 20:12   ` BPJ
     [not found]     ` <CADAJKhAW8LSVGBS56UmSM+4xjV9skk4dMcE8HPTNFkFrdJQ9Nw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-01-09 10:00       ` Cassandra Lyderitz

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=60a0cabf-884e-452c-b094-9f6b1a9f546an@googlegroups.com \
    --to=cassandra.lyderitz-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).