From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: footnotes export verbatim
Date: Mon, 25 Feb 2013 09:09:08 +0100 [thread overview]
Message-ID: <87ppzoyfvf.fsf@gmail.com> (raw)
In-Reply-To: <CAJcAo8sm_mN=bZx5+q_1JgmEFkff+A0og78mMOzyvWHD9+Oo3g@mail.gmail.com> (Samuel Wales's message of "Sun, 24 Feb 2013 13:12:56 -0700")
Samuel Wales <samologist@gmail.com> writes:
> On 2/24/13, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>> Samuel Wales <samologist@gmail.com> writes:
>>> On 2/20/13, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>>>> The basic syntax is similar to the one used by `footnote.el', i.e.
>>>> a footnote is defined in a paragraph that is started by a footnote
>>>> marker in square brackets in column 0, no indentation allowed. If you
>>>> need a paragraph break inside a footnote, use the LaTeX idiom `\par'.
>>>
>>> I am aware of that, but blank lines were allowed after a while. One
>>> issue was filling.
>>>
>>> Even \par fails to work now. :(
>>
>> It should now be fixed. Just replace \par with an empty line.
>
> The fix does not work.
>
> I tried blank line and it still exported verbatim.
>
> I then tried \par, and it still filled the footnote and inserted
> "\par" into it.
I think we're not talking about the same thing. The fix allows empty
lines in regular footnote definitions, not inline ones.
> If this cannot be fixed, then I need some way of filtering to achieve
> it.
Filtering cannot help you here, since you need to, at least, agree with
the structure of the document being parsed.
If you want lists, tables, paragraphs... in a footnote, regular
definitions are the way to go.
If, for some reason, you refuse to use regular definitions, you could
write a hook which would call `org-footnote-normalize', in order to
transform your inline definitions in regular definitions, and then
replace "\par" with an empty line.
That hook function can be added in `org-export-before-parsing-hook'.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-02-25 8:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 20:47 footnotes export verbatim Samuel Wales
2013-02-20 15:18 ` Nicolas Goaziou
2013-02-20 17:21 ` Samuel Wales
2013-02-20 17:32 ` Nicolas Goaziou
2013-02-20 20:13 ` Samuel Wales
2013-02-20 20:43 ` Nicolas Goaziou
2013-02-20 20:59 ` Samuel Wales
2013-02-21 14:27 ` Eric S Fraga
2013-02-23 3:08 ` Samuel Wales
2013-02-24 13:50 ` Nicolas Goaziou
2013-02-24 20:12 ` Samuel Wales
2013-02-25 8:09 ` Nicolas Goaziou [this message]
2013-02-26 22:35 ` Samuel Wales
2013-02-26 23:24 ` Nicolas Goaziou
2013-02-26 23:28 ` Nicolas Goaziou
2013-02-26 23:40 ` Samuel Wales
2013-03-19 4:13 ` Samuel Wales
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ppzoyfvf.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).