public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Melroch <melroch-Re5JQEeQqe8AvxtiuMwx3w@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: Tue, 01 Aug 2017 12:44:29 +0000	[thread overview]
Message-ID: <CADAJKhBETYNY+31e2gKm4dhJGc3QWLnqoEvACP9stVCox6-xdg@mail.gmail.com> (raw)
In-Reply-To: <9f9f5fed-7f09-494f-b69a-b04915d99333-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 4827 bytes --]

That's strange. As far as I know Pandoc's automatic targets are created
anyway. At least they are when converting to HTML or LaTeX. I'm on holiday
so away from any computer with a real Pandoc install but I used the online
demo to convert an equivalent example and it seems that when converting to
OpenDocument no anchors for headings are created. I tried with a span and a
Pandoc heading id too, without any change in the results.

tis 1 aug. 2017 kl. 11:23 skrev CesarJ M <cesarjorgemartinez-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:

> This not working when it convert to docx, pdf or odt
>
>
> El martes, 1 de agosto de 2017, 10:23:12 (UTC+2), CesarJ M escribió:
>>
>> The workaround using anchor tags:
>> # <a name="1-title"></a>1. Title
>> [1. Title](#1-title)
>>
>> But this is very ugly solution
>>
>>
>> El martes, 1 de agosto de 2017, 9:22:04 (UTC+2), CesarJ M escribió:
>>>
>>> I'll try to use anchor tags, but
>>>
>>> There is no other solution?
>>>
>>> Why the text of the reference headers is modified removing the first 1.?
>>>
>>> Regards
>>>
>>> El lunes, 31 de julio de 2017, 19:46:58 (UTC+2), BP escribió:
>>>>
>>>> You can either keep a separate version of the file in Pandoc Markdown
>>>> with manually added GitHub style ids, which Pandoc will pick up, e.g. as
>>>> `doc/readme.pdc` and convert it to GitHub Markdown when you make changes:
>>>>
>>>>     # 1. Description {#1-description}
>>>>
>>>> or add an anchor tag with a pandoc-style id as value of the `name`
>>>> attribute
>>>>
>>>>     # <a name="description">1. Description</a>
>>>>
>>>> which for some reason will be preserved by the GitHub sanitizer and let
>>>> you use `#description` as URL in links. The latter method looks uglier when
>>>> unrendered but has the advantage that you can have only one version of the
>>>> file which looks good when rendered on GitHub.
>>>>
>>>> mån 31 juli 2017 kl. 12:41 skrev CesarJ M <cesarjorg...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
>>>>
>>>>> 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>>>> To post to this group, send email to pandoc-...-/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
>>>>> <https://groups.google.com/d/msgid/pandoc-discuss/a5021369-5323-4cdc-ab5a-ecac3b78983f%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit 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/9f9f5fed-7f09-494f-b69a-b04915d99333%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/9f9f5fed-7f09-494f-b69a-b04915d99333%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit 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/CADAJKhBETYNY%2B31e2gKm4dhJGc3QWLnqoEvACP9stVCox6-xdg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 6554 bytes --]

  parent reply	other threads:[~2017-08-01 12:44 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 [this message]
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=CADAJKhBETYNY+31e2gKm4dhJGc3QWLnqoEvACP9stVCox6-xdg@mail.gmail.com \
    --to=melroch-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).