public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: TRS-80 <lists.trs-80-C7oIis/24ff2zvSPaPeTFA@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Orgmode (.org) to Markdown (.md) not handling in-page link correctly
Date: Wed, 02 Dec 2020 16:25:56 -0500	[thread overview]
Message-ID: <2e5032e461d6c74bef1c4226956bf7b9@isnotmyreal.name> (raw)

Hallo,

First time I ever emailed this list.  I would like to thank everyone for
all their hard work.  I think Pandoc is the neatest thing since sliced
bread and I recommend it to people all the time.  :)

I ran into small issue recently, trying to convert Orgmode to Markdown.
I was using command line (v 2.9.2.1-1+b1, amd64, Debian Testing):

```
pandoc -f org -t commonmark README.org
```

I actually tried all flavors of Markdown as output, as I recall all had
the same result.  Which was that an inline link to somewhere in the same
page did not end up in the output correctly.  Example:

```
[[*Setup][Setup]]
```

Which in Orgmode is a link to the headline Setup on the same page, with
the description "Setup."

However this gets converted to italicized text, instead of a link for
some reason?  Output becomes:

```
*Setup*
```

I don't know enough about pandoc internals to know whether it's on the
Orgmode part or the Markdown part, or somewhere in between.

As instructed on Help page[0], I searched both the mailing list as well
as GitHub issues but did not seem to find anything related.  So I
thought the best first step might be to start here on the mailing list.

Cheers,
TRS-80

[0] https://pandoc.org/help.html


             reply	other threads:[~2020-12-02 21:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 21:25 TRS-80 [this message]
     [not found] ` <2e5032e461d6c74bef1c4226956bf7b9-C7oIis/24ff2zvSPaPeTFA@public.gmane.org>
2020-12-02 21:50   ` Joost Kremers
     [not found]     ` <87k0tzop2m.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2020-12-03  8:18       ` Albert Krewinkel
2020-12-02 22:09   ` John MacFarlane
     [not found]     ` <m24kl3q2qh.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-12-02 22:56       ` TRS-80

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=2e5032e461d6c74bef1c4226956bf7b9@isnotmyreal.name \
    --to=lists.trs-80-c7oiis/24ff2zvspapetfa@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).