You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since version 2.15.0, Markdown has supported the relativeReferences option that enables the user to specify relative references in autolinks (e.g. see <#my-table>). The LaTeX renderer prototype for links special-cases relative references and typesets them using the \ref command, ignoring the text and the title of the references:
However, this also affects relative references in direct links (e.g. see [my table](#my-table "some title")) and indirect links (e.g. see [my table][] ... [my table]: #my-table "some title"), where a user may expect that the text and the title would not be ignored.
Previously in LaTeX, both `<#fragment>` and `[some text](#fragment
"title")` would produce the `\ref{fragment}` command with the default
link renderer prototype. Now, only `<#fragment>` produces
`\ref{fragment}`, whereas `[some text](#fragment "title")` becomes
`some text\footnote{title: \url{#fragment}}`. Closes#127.
Since version 2.15.0, Markdown has supported the
relativeReferences
option that enables the user to specify relative references in autolinks (e.g.see <#my-table>
). The LaTeX renderer prototype for links special-cases relative references and typesets them using the\ref
command, ignoring the text and the title of the references:markdown/markdown.dtx
Lines 23143 to 23169 in a8e5838
However, this also affects relative references in direct links (e.g.
see [my table](#my-table "some title")
) and indirect links (e.g.see [my table][]
...[my table]: #my-table "some title"
), where a user may expect that the text and the title would not be ignored.Hats off to @drehak for discovering the issue.
The text was updated successfully, but these errors were encountered: