From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Richard Lawrence <richard.lawrence@berkeley.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Footnotes break iCalendar export [8.0.1 (release_8.0.1 @ /home/rwl/src/org-mode/lisp/)]
Date: Sun, 21 Apr 2013 23:48:02 +0200 [thread overview]
Message-ID: <87y5cbmu7h.fsf@gmail.com> (raw)
In-Reply-To: <87li8c9a6f.fsf@berkeley.edu> (Richard Lawrence's message of "Sat, 20 Apr 2013 14:14:32 -0700")
Hello,
Richard Lawrence <richard.lawrence@berkeley.edu> writes:
> I've been trying to get iCalendar export working with my agenda files
> again since upgrading to 8.0, and I've found that footnotes break the
> agenda export to .ics. The problem is that a plain text version of the
> footnotes in the file ends up in the output "floating loose"---not
> wrapped by VEVENT tags or any other tags---resulting in an unparseable
> .ics file (at least according to Google Calendar).
>
> Here's a sample Org file to illustrate:
>
> * Entry 1
> This entry has some text with an inline footnote[fn:: which isn't
> very interesting]
> * Entry 2
> This entry has some text with an external footnote[fn:1]
> * Appointment with Someone
> <2013-04-20 Sat 15:00>
> * Footnotes
> [fn:1] which still isn't very interesting
This should be fixed. Thank you for the report.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2013-04-21 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 21:14 Bug: Footnotes break iCalendar export [8.0.1 (release_8.0.1 @ /home/rwl/src/org-mode/lisp/)] Richard Lawrence
2013-04-21 13:11 ` Bastien
2013-04-21 18:52 ` Richard Lawrence
2013-04-21 19:12 ` [PATCH] tiny fixes in ox-ascii.el [was: Re: Bug: Footnotes break iCalendar export] Richard Lawrence
2013-04-21 21:53 ` Nicolas Goaziou
2013-04-21 21:49 ` Bug: Footnotes break iCalendar export [8.0.1 (release_8.0.1 @ /home/rwl/src/org-mode/lisp/)] Nicolas Goaziou
2013-04-21 22:12 ` Bastien
2013-04-21 21:48 ` Nicolas Goaziou [this message]
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=87y5cbmu7h.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=richard.lawrence@berkeley.edu \
/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).