emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suhail Shergill <suhailshergill@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-html: subtree specific footnote references
Date: Tue, 10 Jul 2012 05:03:18 +0000	[thread overview]
Message-ID: <87bojoryw9.fsf@chaos.shergill.su> (raw)
In-Reply-To: <81bojogrhh.fsf@gmail.com> (Jambunathan K.'s message of "Tue, 10 Jul 2012 10:08:50 +0530")

Jambunathan K <kjambunathan@gmail.com> writes:

> Suhail Shergill <suhailshergill@gmail.com> writes:
>> Jambunathan K <kjambunathan@gmail.com> writes:
>>>>> running org-export-as-html on a subtree is currently problematic if
>>>>> the result is to be merged into a document which contains html-ized
>>>>> versions of other subtrees: the footnote references and definitions
>>>>> get clobbered.
>>> Do the subtrees come from the same org file?
>> that is the use case, yes.
> Try marking the subtrees with :export: tag.  Lookup the following in the
> mailing list, worg or the info manual.
>      #+EXPORT_SELECT_TAGS:   Tags that select a tree for export
>      #+EXPORT_EXCLUDE_TAGS:  Tags that exclude a tree from export
> With this, do footnotes come out along the expected lines?

*if* you were to generate the entire file again, things will be fine yes. i'm
talking about a scenario where for one reason or another you may not want to do
that, but may instead only want to export the most recent subtree which has been
added (since the last time it was exported). earlier when you tried to do that,
the footnote links would no longer work because of name attribute
collisions. this patch provides a way to prevent that.

>>> Won't it look odd and confusing to a reader, when there are two
>>> different footnote definitions with the same number. 
>> yes i agree that would be very confusing. but why, pray tell, would
>> there be two different definitions with the same number?
> <a>you haven't modified the description have you?</a>

no, i haven't. also, you could look at the patch. the code is pretty

>>> Confusion is like to be pronounced, if the reader chooses to also print out
>>> the document as a pdf or into paper.
>> the *only* behavioural change that this effects is that the links (and backlinks
>> from the definitions to references) will continue to work properly even in the
>> event the user decides to merge the result of multiple subtree exports into one
>> single document.
> Links are visible when stuff is printed out on paper.  Is it?

not sure what you mean by this. are links visible when you print them? yes,
unless you're using invisible ink. the patch (if you cared to look) modifies the
name attribute of the a tags in question (footnote definition and footnote
references). the text within the a tag (the bit that is actually rendered on
screen/print) is unchanged.


  reply	other threads:[~2012-07-10  5:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-07 20:00 org-html: subtree specific footnote references Suhail Shergill
2012-07-07 20:16 ` Suhail Shergill
2012-07-10  3:48   ` Jambunathan K
2012-07-10  4:18     ` Suhail Shergill
2012-07-10  4:38       ` Jambunathan K
2012-07-10  5:03         ` Suhail Shergill [this message]
2012-07-10  5:20           ` Jambunathan K
2012-07-10  5:54           ` Jambunathan K
2012-07-16 17:31             ` Suhail Shergill
2012-08-02 16:26               ` Bastien
2012-08-04  0:17                 ` Suhail Shergill

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:

  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=87bojoryw9.fsf@chaos.shergill.su \
    --to=suhailshergill@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).