From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Reference links to numbered headers of README.md not work in converted formats
Date: Wed, 2 Aug 2017 06:49:22 -0700 [thread overview]
Message-ID: <20170802134922.GB38349@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <108edc7f-37e3-4764-944d-7689152df990-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Please see the issue I linked to, and comment if you think
any information on GitHub's algorithm is missing there.
+++ CesarJ M [Aug 02 17 01:08 ]:
> Hi,
> I've been doing several tests:
> The GitHub formas does (from github.com), to resolve links:
> - It downcases the header string
> - remove anything that is not a letter, number, space or hyphen
> - changes any space to a hyphen.
> - If that is not unique, add "-1", "-2", "-3",... to make it unique
> Using the markdown_github, trying to convert to html, convert to
> follow:
> Header:
> <h1 id="title">1. Title</h1> (fail, must be id="1-title")
> Link:
> <a href="#1-title">1. Title</a> (correct)
>
> Using --toc option, also do the same:
> <ul>
> <li><a href="#title">1. Title</a></li>
> </ul>
> Seeing a odt converted file, the title destination (right-click in the
> link, modify hyperlink, destination in the document), appear as "1.1.
> Title".
> I try to disable the auto_identifiers extension
> (markdown_github-auto_identifiers) but not work:
> <ul>
> <li><a>1. Title</a></li>
> </ul>
> <h1>1. Title</h1>
> <a href="#1-title">1. Title</a>
> Disabling not workaround the problem :-(
> El martes, 1 de agosto de 2017, 21:41:15 (UTC+2), John MacFarlane
> escribió:
>
> See
> the manual under "Extension: auto_identifiers" and also
> [1]https://github.com/jgm/pandoc/issues/2821
> +++ CesarJ M [Aug 01 17 00:22 ]:
> > Why the text of the reference headers is modified removing the
> first
> > 1.?
>
> --
> 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 [2]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [3]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [4]https://groups.google.com/d/msgid/pandoc-discuss/108edc7f-37e3-4764-
> 944d-7689152df990%40googlegroups.com.
> For more options, visit [5]https://groups.google.com/d/optout.
>
>References
>
> 1. https://github.com/jgm/pandoc/issues/2821
> 2. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 4. https://groups.google.com/d/msgid/pandoc-discuss/108edc7f-37e3-4764-944d-7689152df990-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 5. https://groups.google.com/d/optout
--
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/20170802134922.GB38349%40Johns-MacBook-Pro.local.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2017-08-02 13:49 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
[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 [this message]
[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=20170802134922.GB38349@Johns-MacBook-Pro.local \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).