[docutils:patches] #81 latex2e: Allow footnotes to be more easily customizable

This is a multi-part message in MIME format.
--===============7507022859939847422==
Content-Type: multipart/related; boundary="===============1032956594207511073=="

This is a multi-part message in MIME format.
--===============1032956594207511073==
Content-Type: multipart/alternative; boundary="===============6115898507247984769=="
MIME-Version: 1.0

--===============6115898507247984769==
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

- **status**: open --> pending-remind



---

**[patches:#81] latex2e: Allow footnotes to be more easily customizable**

**Status:** pending-remind
**Group:** None
**Created:** Wed Jul 13, 2011 10:35 AM UTC by Kirill Smelkov
**Last Updated:** Wed May 13, 2026 10:24 PM UTC
**Owner:** nobody


For example Russian GOST 19.106 requires that footnotes contain
footnote-number + "\)" which in plain LaTeX could be done as

\renewcommand\{\thefootnote\}\{\arabic\{footnote\}\)\}
^
note "\)"

but Docutils uses its own \DUfootnotemark and \DUfootnotetext macros
with hyperlinks setup which redefine \thefootnote in-there and the
above-shown tweak does not work.

So in order to make even small tweaks for foot notes, users have to
either "fork" \DUfootnotemark and \DUfootnotetext in their stylesheet,
or better, what I'm proposing here, just redefine here-introduced
\DUthefootnote, e.g. like this:

\providecommand\*\{\DUthefootnote\}\[1\]\{\#1\)\}

Thanks,
Kirill


---

Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/docutils/patches/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/patches/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.
--===============6115898507247984769==
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<div class="markdown_content"><ul>
<li><strong>status</strong>: open --&gt; pending-remind</li>
</ul>
<hr/>
<p><strong><a class="alink" href="https://sourceforge.net/p/docutils/patches/81/">[patches:#81]</a> latex2e: Allow footnotes to be more easily customizable</strong></p>
<p><strong>Status:</strong> pending-remind<br/>
<strong>Group:</strong> None<br/>
<strong>Created:</strong> Wed Jul 13, 2011 10:35 AM UTC by Kirill Smelkov<br/>
<strong>Last Updated:</strong> Wed May 13, 2026 10:24 PM UTC<br/>
<strong>Owner:</strong> nobody</p>
<p>For example Russian GOST 19.106 requires that footnotes contain<br/>
footnote-number + ")" which in plain LaTeX could be done as</p>
<p>\renewcommand{\thefootnote}{\arabic{footnote})}<br/>
^<br/>
note ")"</p>
<p>but Docutils uses its own \DUfootnotemark and \DUfootnotetext macros<br/>
with hyperlinks setup which redefine \thefootnote in-there and the<br/>
above-shown tweak does not work.</p>
<p>So in order to make even small tweaks for foot notes, users have to<br/>
either "fork" \DUfootnotemark and \DUfootnotetext in their stylesheet,<br/>
or better, what I'm proposing here, just redefine here-introduced<br/>
\DUthefootnote, e.g. like this:</p>
<p>\providecommand*{\DUthefootnote}[1]{#1)}</p>
<p>Thanks,<br/>
Kirill</p>
<hr/>
<p>Sent from sourceforge.net because [email protected] is subscribed to <a href="https://sourceforge.net/p/docutils/patches/">https://sourceforge.net/p/docutils/patches/</a></p>
<p>To unsubscribe from further messages, a project admin can change settings at <a href="https://sourceforge.net/p/docutils/admin/patches/options.">https://sourceforge.net/p/docutils/admin/patches/options.</a>  Or, if this is a mailing list, you can unsubscribe from the mailing list.</p></div>
--===============6115898507247984769==--

--===============1032956594207511073==--


--===============7507022859939847422==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============7507022859939847422==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline