public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Alberto Simões" <hashashin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Internal link to a RawBlock created via filter
Date: Sat, 15 Jul 2023 21:39:38 +0100	[thread overview]
Message-ID: <CAAkRyrtVDA8otm8WQNFyp1f2MgAhWu3vXZJvF0-Mwfx43g=8FQ@mail.gmail.com> (raw)
In-Reply-To: <c52b4685-004a-4e98-a620-974b6395c6acn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

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

On Sat, Jul 15, 2023 at 9:24 PM Alberto Simoes <hashashin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> Hello
>
> I am using a filter based on the tikz example in the python pandocfilters
> documentation.
> I am generating one id="foo" and a \label{foo} in the html and latex
> output, respectively, for an internal link target.
>
> Nevertheless, when I use a link to that block, with [Look here](#foo)  the
> link is generated to the first page, and not to the raw block that has the
> label defined.
>
> I suppose that Pandoc is creating an internal index of references before
> generating the latex/html code (??) and is not aware that my RawBlock has a
> link target.
>
>
The generated LaTeX looks good to me...

--------
\begin{figure}[h]
\centering
...
\caption{Vibração simples}
\label{fig1}
\end{figure}

A corda \emph{A} deslocada para o ponto \emph{B} regressa à base
\emph{A}. A vibração simples póde pois representar-se em face da
\protect\hyperlink{fig1}{fig.~1} pela fórmula \(AB + BA\).
----------

What am I missing?

Thank you


-- 
Alberto Simões

-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CAAkRyrtVDA8otm8WQNFyp1f2MgAhWu3vXZJvF0-Mwfx43g%3D8FQ%40mail.gmail.com.

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

  parent reply	other threads:[~2023-07-15 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-15 20:24 Alberto Simoes
     [not found] ` <c52b4685-004a-4e98-a620-974b6395c6acn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-07-15 20:39   ` Alberto Simões [this message]
     [not found]     ` <CAAkRyrtVDA8otm8WQNFyp1f2MgAhWu3vXZJvF0-Mwfx43g=8FQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-15 21:13       ` Alberto Simoes
2023-07-18  0:05   ` John MacFarlane
     [not found]     ` <50EAD892-479F-427D-9CCE-A6CE4B1E4A9C-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-18  7:57       ` Alberto Simões

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='CAAkRyrtVDA8otm8WQNFyp1f2MgAhWu3vXZJvF0-Mwfx43g=8FQ@mail.gmail.com' \
    --to=hashashin-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).