From: Umut Acar <umutacar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: code block translation from latex to html
Date: Thu, 7 May 2020 17:28:37 -0700 (PDT) [thread overview]
Message-ID: <49108dd7-3ee5-41b5-9b8c-92c558ff46b5@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1539 bytes --]
At some point after pandoc version 2.7.2, pandoc started translating code
blocks to html from LaTeX sources somewhat differently.
For example, the code block
```
\begin{lstlisting}
...
2 (int)
\end{lstlisting}
```
used to produce the following html
```
<a class="sourceLine" id="cb2-4" title="4"><span class="dv">2</span> (<span
class="dt">int</span>)
```
It now produces the following
```
<span id="cb2-4"><a href="#cb2-4"></a><span class="dv">2</span> (<span
class="dt">int</span>) </span>
```
On a browser, the latter renders the code "int" as a html link to itself;
the code line is rendered as a link (to itself).
Also, because the code anchor id's such as `cb2-4` are not unique (multiple
code blocks generate the same id's), clicking on a code line sends the
browser to the first instance of that id, usually somewhere up the page.
The new translation is also dropping the code line numbers.
Any thoughts about what might be going on and suggestions about how this
could be fixed? I would be happy with the prior behavior code lines were
not assigned anchor tags and were numbered serially.
--
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/49108dd7-3ee5-41b5-9b8c-92c558ff46b5%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2390 bytes --]
next reply other threads:[~2020-05-08 0:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 0:28 Umut Acar [this message]
[not found] ` <49108dd7-3ee5-41b5-9b8c-92c558ff46b5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-08 4:45 ` John MacFarlane
[not found] ` <m2eerv8279.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-05-08 14:09 ` Umut Acar
2020-06-14 1:19 ` Umut Acar
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=49108dd7-3ee5-41b5-9b8c-92c558ff46b5@googlegroups.com \
--to=umutacar-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).