From: CesarJ M <cesarjorgemartinez-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Reference links to numbered headers of README.md not work in converted formats
Date: Mon, 31 Jul 2017 03:40:35 -0700 (PDT) [thread overview]
Message-ID: <a5021369-5323-4cdc-ab5a-ecac3b78983f@googlegroups.com> (raw)
In-Reply-To: <d38c609f-a5c6-4b57-8006-536a977def43-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1066 bytes --]
Correct the message:
I number the headers using my own numbers, and links to these headers, as
example:
# 1 MyTitle
# 2 Other Title
...
[MyLinkTitle](#1-mytitle)
Then, when I convert this file (by example to docx format), and open it,
the MyLinkTitle is not working.
In the documentation it is said that I need to write the reference as:
[MyTitle](#mytitle)
But, if we use this form in github repository, the link is not working in
github web.
How do I fix this problem?
Regards,
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a5021369-5323-4cdc-ab5a-ecac3b78983f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1547 bytes --]
next prev parent reply other threads:[~2017-07-31 10:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 10:07 CesarJ M
[not found] ` <d38c609f-a5c6-4b57-8006-536a977def43-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-31 10:40 ` CesarJ M [this message]
[not found] ` <a5021369-5323-4cdc-ab5a-ecac3b78983f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-31 17:46 ` Melroch
[not found] ` <CADAJKhD_x=xv55RC=+-1hoLM38bUXsQgTXQPEg7nGto4hZrC3g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-01 7:22 ` CesarJ M
[not found] ` <74beb961-303e-49af-86d9-04193ca2b8b3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-01 8:23 ` CesarJ M
[not found] ` <5b0bae39-4471-4d1f-a304-c3ac1c49c60b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-01 9:23 ` CesarJ M
[not found] ` <9f9f5fed-7f09-494f-b69a-b04915d99333-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-01 12:44 ` Melroch
2017-08-01 19:41 ` John MacFarlane
[not found] ` <20170801194100.GB29242-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-08-02 8:08 ` CesarJ M
[not found] ` <108edc7f-37e3-4764-944d-7689152df990-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-02 13:49 ` John MacFarlane
[not found] ` <20170802134922.GB38349-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-08-03 11:05 ` CesarJ M
[not found] ` <70c54296-7cf7-4a57-ad6b-e7d18edf1ae7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-11 16:18 ` CesarJ M
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=a5021369-5323-4cdc-ab5a-ecac3b78983f@googlegroups.com \
--to=cesarjorgemartinez-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).