internal links

internal links

[Marcin Wojdyr]

Hello,
I'm thinking about converting a DocBook document to Markdown or reST,
and process it with Pandoc. I'd like to produce three output formats:
HTML, chm (Windows help, chunked HTML + two extra files) and PDF, what
should be possible, using Latex or DocBook output from Pandoc.
My first question is: are internal links (<xref> and <link> in
DocBook, foo_ in reST) supported by Pandoc, for output other than
HTML?

Marcin

-- 
Marcin Wojdyr | http://www.unipress.waw.pl/~wojdyr/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss@googlegroups.com
To unsubscribe from this group, send email to pandoc-discuss-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: internal links

[John MacFarlane]

+++ Marcin Wojdyr [Mar 06 08 17:44 ]:
> 
> Hello,
> I'm thinking about converting a DocBook document to Markdown or reST,
> and process it with Pandoc. I'd like to produce three output formats:
> HTML, chm (Windows help, chunked HTML + two extra files) and PDF, what
> should be possible, using Latex or DocBook output from Pandoc.
> My first question is: are internal links (<xref> and <link> in
> DocBook, foo_ in reST) supported by Pandoc, for output other than
> HTML?

Not at the moment.  Note also that Pandoc's reST reader only supports a
subset of the features of reST.

If you tell me how (Pandoc markdown) input should be transformed into
<xref> and <link> elements in DocBook, I might be able to add the
feature.

John

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss@googlegroups.com
To unsubscribe from this group, send email to pandoc-discuss-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: internal links

[Marcin Wojdyr]

On Mar 6, 7:55 pm, John MacFarlane <fiddlosop...@gmail.com> wrote:

> If you tell me how (Pandoc markdown) input should be transformed into
> <xref> and <link> elements in DocBook, I might be able to add the
> feature.

You probably know all these formats better than me, but I guess you
would need to

1) add id to each <section>, based on <title>, like you do for <h1>.
2) use <link> instead of <ulink> when link starts with "#".

Markdown: This is [internal link](#header-identifier).
HTML: This is <a href="#header-identifier">internal link</a>.
DocBook: This is <link linkend="header-identifier">internal link</
link>.

But if you would like to support it also in reST output:
http://docutils.sourceforge.net/docs/user/rst/quickref.html#implicit-hyperlink-targets
http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#implicit-hyperlink-targets

it would be better to use full titles rather than mangled, i.e.
[link](#Header identifier) instead of [link](#header-identifier),
and change it only in HTML output.

Marcin

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss@googlegroups.com
To unsubscribe from this group, send email to pandoc-discuss-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: internal links

[John MacFarlane]

Thanks.
I've added this as an enhancement request on the bug tracker. Don't know
when I'll get around to it -- probably not in the very near future.

John

+++ Marcin Wojdyr [Mar 07 08 06:13 ]:
> 
> On Mar 6, 7:55 pm, John MacFarlane <fiddlosop...@gmail.com> wrote:
> 
> > If you tell me how (Pandoc markdown) input should be transformed into
> > <xref> and <link> elements in DocBook, I might be able to add the
> > feature.
> 
> You probably know all these formats better than me, but I guess you
> would need to
> 
> 1) add id to each <section>, based on <title>, like you do for <h1>.
> 2) use <link> instead of <ulink> when link starts with "#".
> 
> Markdown: This is [internal link](#header-identifier).
> HTML: This is <a href="#header-identifier">internal link</a>.
> DocBook: This is <link linkend="header-identifier">internal link</
> link>.
> 
> But if you would like to support it also in reST output:
> http://docutils.sourceforge.net/docs/user/rst/quickref.html#implicit-hyperlink-targets
> http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#implicit-hyperlink-targets
> 
> it would be better to use full titles rather than mangled, i.e.
> [link](#Header identifier) instead of [link](#header-identifier),
> and change it only in HTML output.
> 
> Marcin
> 
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To post to this group, send email to pandoc-discuss@googlegroups.com
> To unsubscribe from this group, send email to pandoc-discuss-unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en
> -~----------~----~----~----~------~----~------~--~---
> 

Internal links

[Dirk Laurie]

At present, Pandoc makes automatic internal links to sections
only.  What options do I have if:

1. I know the target will be HTML.
2. I don't want the automatically generated link name, but my own
    name instead.
2. I want to link to a place in the text that is not a section header.

Some inline HTML?

Re: Internal links

[John MacFarlane]

+++ Dirk Laurie [Dec 13 12 21:58 ]:
> At present, Pandoc makes automatic internal links to sections
> only.  What options do I have if:
> 
> 1. I know the target will be HTML.
> 2. I don't want the automatically generated link name, but my own
>     name instead.
> 2. I want to link to a place in the text that is not a section header.
> 
> Some inline HTML?

Yeah, just insert an anchor:

    <a id="whatever" />

internal links

[alain content]

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

Hi, 

Is it possible to create internal links to some text, tables or figures in 
a pdf or epub document ? I know how to link to headers with {identifiers}, 
but can't find any suggestion that works with tables, figures, or segments 
of plain text.

Thanks for any suggestion, 

Alain

(pandoc 1.15.0.6)

-- 
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/87f5a6da-bc97-45fe-b1d4-6f5fd475b103%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: internal links

[John MacFarlane]

This should work for both pdf and epub:

<span id="foo">
hi there
</span>

and then...

[link](#foo)

+++ alain content [Aug 25 15 15:10 ]:
>   Hi,
>   Is it possible to create internal links to some text, tables or figures
>   in a pdf or epub document ? I know how to link to headers with
>   {identifiers}, but can't find any suggestion that works with tables,
>   figures, or segments of plain text.
>   Thanks for any suggestion,
>   Alain
>   (pandoc 1.15.0.6)
>
>   --
>   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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/87f5a6da-bc97-45fe-
>   b1d4-6f5fd475b103%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/87f5a6da-bc97-45fe-b1d4-6f5fd475b103-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout

Re: internal links

[alain content]

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

Hi John, thanks !

I tried <span> but couldn't seem to make it work. 
<div> works though, more or less (in pdf, it does not point exactly to the 
target but apparently to one  header close  to the target, which is kind of 
ok)

OTOH, is there another way to reference to figures and tables ?

Thanks again


Le mercredi 26 août 2015 03:11:28 UTC+2, John MacFarlane a écrit :
>
> This should work for both pdf and epub: 
>
> <span id="foo"> 
> hi there 
> </span> 
>
> and then... 
>
> [link](#foo) 
>
> +++ alain content [Aug 25 15 15:10 ]: 
> >   Hi, 
> >   Is it possible to create internal links to some text, tables or 
> figures 
> >   in a pdf or epub document ? I know how to link to headers with 
> >   {identifiers}, but can't find any suggestion that works with tables, 
> >   figures, or segments of plain text. 
> >   Thanks for any suggestion, 
> >   Alain 
> >   (pandoc 1.15.0.6) 
> > 
>
>

-- 
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/6ad976fe-96a5-48dd-9e87-bc377c0a9a20%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: internal links

[John MACFARLANE]

Do you get output different from this?

$ pandoc -t latex
<span id="foo">hi there</span>

[link](#foo)
^D

\hyperdef{}{foo}{\label{foo}}{hi there}

\hyperref[foo]{link}

This ought to work.

++ alain content [Aug 26 15 01:56 ]:
>   Hi John, thanks !
>   I tried <span> but couldn't seem to make it work.
>   <div> works though, more or less (in pdf, it does not point exactly to
>   the target but apparently to one  header close  to the target, which is
>   kind of ok)
>   OTOH, is there another way to reference to figures and tables ?
>   Thanks again
>   Le mercredi 26 août 2015 03:11:28 UTC+2, John MacFarlane a écrit :
>
>     This should work for both pdf and epub:
>     <span id="foo">
>     hi there
>     </span>
>     and then...
>     [link](#foo)
>     +++ alain content [Aug 25 15 15:10 ]:
>     >   Hi,
>     >   Is it possible to create internal links to some text, tables or
>     figures
>     >   in a pdf or epub document ? I know how to link to headers with
>     >   {identifiers}, but can't find any suggestion that works with
>     tables,
>     >   figures, or segments of plain text.
>     >   Thanks for any suggestion,
>     >   Alain
>     >   (pandoc 1.15.0.6)
>     >
>
>   --
>   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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/6ad976fe-96a5-48dd-
>   9e87-bc377c0a9a20%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/6ad976fe-96a5-48dd-9e87-bc377c0a9a20-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. 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/20150826183336.GC32489%40D25Q40BGFY13.Berkeley.EDU.
For more options, visit https://groups.google.com/d/optout.

Re: internal links

[alain content]

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

Yes it works. I must have done something wrong on previous attempts. Thanks
again!

2015-08-26 20:33 GMT+02:00 John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>:

> Do you get output different from this?
>
> $ pandoc -t latex
> <span id="foo">hi there</span>
>
> [link](#foo)
> ^D
>
> \hyperdef{}{foo}{\label{foo}}{hi there}
>
> \hyperref[foo]{link}
>
> This ought to work.
>
> ++ alain content [Aug 26 15 01:56 ]:
>
>>   Hi John, thanks !
>>   I tried <span> but couldn't seem to make it work.
>>   <div> works though, more or less (in pdf, it does not point exactly to
>>   the target but apparently to one  header close  to the target, which is
>>   kind of ok)
>>   OTOH, is there another way to reference to figures and tables ?
>>   Thanks again
>>   Le mercredi 26 août 2015 03:11:28 UTC+2, John MacFarlane a écrit :
>>
>>     This should work for both pdf and epub:
>>     <span id="foo">
>>     hi there
>>     </span>
>>     and then...
>>     [link](#foo)
>>     +++ alain content [Aug 25 15 15:10 ]:
>>     >   Hi,
>>     >   Is it possible to create internal links to some text, tables or
>>     figures
>>     >   in a pdf or epub document ? I know how to link to headers with
>>     >   {identifiers}, but can't find any suggestion that works with
>>     tables,
>>     >   figures, or segments of plain text.
>>     >   Thanks for any suggestion,
>>     >   Alain
>>     >   (pandoc 1.15.0.6)
>>     >
>>
>>   --
>>   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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>   To post to this group, send email to
>>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>   To view this discussion on the web visit
>>   [3]https://groups.google.com/d/msgid/pandoc-discuss/6ad976fe-96a5-48dd-
>>   9e87-bc377c0a9a20%40googlegroups.com.
>>   For more options, visit [4]https://groups.google.com/d/optout.
>>
>> References
>>
>>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>>   3.
>> https://groups.google.com/d/msgid/pandoc-discuss/6ad976fe-96a5-48dd-9e87-bc377c0a9a20-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>>   4. https://groups.google.com/d/optout
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "pandoc-discuss" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/pandoc-discuss/ZmL7R6wlYHQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/20150826183336.GC32489%40D25Q40BGFY13.Berkeley.EDU
> .
>
> 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/CAF%3DYBmNQMKhHLqRweY2zDF4KssNyeGVx9MFMT%2BaS3gv97rE42w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: internal links

[alain content]

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

After some more trials...

<span id="foo">hi there</span>

... 

...

[link](#foo)


does  work, somehow, 
but does not really honor the precise target. In a long document as the one 
I'm currently preparing, this does not do the job.
Further, it seems that the hyperref  package does not handle page breaks 
very well.  

I believe that this is more a latex than a pandoc issue as things work well 
in html/epub output.

Any suggestion about how to create internal links (in pdf output) that 
target the exact line of the anchor ?

Thanks ! 
  

-- 
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/1bb3c6c4-a1c6-4431-ba4d-5f2f04833382%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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