public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Mueller <kg.schmidt94-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Output-Format Plain removes Markdown-Hyperlinks []()
Date: Fri, 14 Jan 2022 03:20:57 -0800 (PST)	[thread overview]
Message-ID: <f3cf23c8-71a0-4825-812d-652b8d1ccc71n@googlegroups.com> (raw)


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

Hello together.

I'm working on a project where we use one input markdown file to create 
HTML but also TXT files.
The problem I have is with markdown hyperlinks in the form of []().

While for the output format html they are kept:
*$ echo "prefix [this is a link](www.google.de) suffix" | pandoc -f 
markdown -t html*
*<p>prefix <a href="www.google.de">this is a link</a> suffix</p>*

the url is completely removed for plain output:
*$ echo "prefix [this is a link](www.google.de) suffix" | pandoc -f 
markdown -t plain*
*prefix this is a link suffix*

Is there a way/plugin to keep the url within the plain output?
(e.g.  by keeping the markdown  [this is a link](www.google.de) as it is, 
but handling all other markdown as usual?)

Thank you
Peter

-- 
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/f3cf23c8-71a0-4825-812d-652b8d1ccc71n%40googlegroups.com.

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

             reply	other threads:[~2022-01-14 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 11:20 Peter Mueller [this message]
     [not found] ` <f3cf23c8-71a0-4825-812d-652b8d1ccc71n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-15 14:41   ` BPJ
     [not found]     ` <c26e9460-27b6-ed81-2701-e1f3dcbac293-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-01-15 14:44       ` BPJ

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=f3cf23c8-71a0-4825-812d-652b8d1ccc71n@googlegroups.com \
    --to=kg.schmidt94-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).