emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: Carsten Dominik <dominik@uva.nl>,
	emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: footnote export fails if footnote indented
Date: Fri, 16 Apr 2010 12:07:15 -0700	[thread overview]
Message-ID: <x2z20524da71004161207n1702e44l9870313e40b44086@mail.gmail.com> (raw)
In-Reply-To: <87ochji6oa.fsf@stats.ox.ac.uk>

On 2010-04-16, Dan Davison <davison@stats.ox.ac.uk> wrote:
> Samuel Wales <samologist@gmail.com> writes:
>
>> Here are 2 test cases for footnotes.  Perhaps they can be put in a
>> test directory somewhere if they are useful.
>
> Hi Samuel,
>
> Thanks. You have obviously thought about this a lot more carefully than
> me. Is there any chance you could run your test files with Carsten's
> patch, with the footnote definitions tab indented away from the left
> margin, and report on whether the patch introduces any new problems? I
> did quickly try exporting your file but I wasn't sure how to interpret
> the output.

For health reasons, I cannot at this time.

>
> Dan
>
>>
>> My old relatively thorough test case with 11 specific documented
>> points to test for:
>>
>> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg10877.html
>>
>> And my recent one, sloppily put together and reproduced here:
>>
>> * top
>> *** an article
>> sadfkaj sdnfklaj nsfklandsf
>> asd flkajnd sfa
>> *** an article.  exporting this to ascii does not export anonymous
>> footnotes
>> I sometimes[fn:3] mix regular[fn:1] footnotes and inline
>> [fn:: There are issues here.  For example, I have to type
>> them in manually.  You cannot leave empty; it won't accept
>> it.  Maybe it has to do with my ido setup.  Exporting this
>> to ASCII seems to silent fail.  I tried "fn:: text" and
>> "fn::text".] ones[fn:2].
>>
>> ===
>>
>> [fn:1] ordinary.  note that if you put point here and do c-c
>> c-c, you will get sent to the next article, which is
>> disconcerting.  i expected it to go up to the thing that
>> points to it.  this situation, where you have duplicate
>> footnote numbers in the same file, but different org
>> entries, is very common when you refile an article.
>> \par
>> don't know how to separate paragraphs in a footnote in
>> a way that fill-paragraph with filladapt will understand.
>> would be nice if a way were possible, imo.
>>
>> [fn:2] another
>>
>> [fn:3] a third
>> # a comment
>> *** another article
>> ordinary [fn:1], inline[fn:This is a test.], and
>> regular[fn:2] footnotes.
>>
>> ===
>>
>> [fn:1] regular
>>
>> [fn:2] usual
>> *** another article
>> asdfj alkdfn akljdn fklajdf
>> askdfn al;ksjnf lajdnf klajdnf
>> skjdhflakjdnf klajnf [fn:1]
>>
>> [fn:1] test
>> *** another article
>> asdknf lakjdnf ak
>> asdkjfn aldjf
>>
>>
>> On 2010-04-16, Dan Davison <davison@stats.ox.ac.uk> wrote:
>>> I hadn't forgotten about this but I have been conscious that I wasn't
>>> giving it the testing it deserved. I don't export with footnotes that
>>> much, and when I do it tends to be to HTML. So I haven't noticed any
>>> problems, but perhaps some others who use footnotes more seriously than
>>> me could test out this patch for a bit? Sorry, I know I should have sent
>>> this email ages ago!
>


-- 
Q: How many CDC "scientists" does it take to change a lightbulb?
A: "You only think it's dark." [CDC has denied a deadly disease for 25 years]
==========
Retrovirus: http://www.wpinstitute.org/xmrv/index.html

      reply	other threads:[~2010-04-16 19:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 21:37 footnote export fails if footnote indented Dan Davison
2010-01-13 10:51 ` Carsten Dominik
2010-04-14 14:50   ` Carsten Dominik
2010-04-16 16:53     ` Dan Davison
2010-04-16 18:11       ` Samuel Wales
2010-04-16 18:38         ` Dan Davison
2010-04-16 19:07           ` Samuel Wales [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=x2z20524da71004161207n1702e44l9870313e40b44086@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=davison@stats.ox.ac.uk \
    --cc=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.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.
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).