From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alex Fu" Subject: Re: Org-mode version 4.68 Date: Mon, 19 Mar 2007 10:21:25 -0400 Message-ID: References: <1c43fad8a5823dc1386f861a4984ae26@science.uva.nl> <87tzwle93o.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 Content-Transfer-Encoding: Quoted-Printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HTIlH-0000gz-NG for emacs-orgmode@gnu.org; Mon, 19 Mar 2007 10:22:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HTIlH-0000gi-5J for emacs-orgmode@gnu.org; Mon, 19 Mar 2007 10:22:59 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HTIlH-0000ge-0E for emacs-orgmode@gnu.org; Mon, 19 Mar 2007 09:22:59 -0500 Received: from wr-out-0506.google.com ([64.233.184.225]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from <120571@gmail.com>) id 1HTIjn-0003gy-UE for emacs-orgmode@gnu.org; Mon, 19 Mar 2007 10:21:28 -0400 Received: by wr-out-0506.google.com with SMTP id 76so1249454wra for ; Mon, 19 Mar 2007 07:21:27 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Dear all, On Fri, 16 Mar 2007 13:08:33 -0400, Carsten Dominik = wrote: >> * Exporting text before the first heading ? >> >> It seems that text before the first heading is not exported. Using= >> #+TEXT: might help, but #+TEXT: does not understand links. Is that= >> intentional ? > > I guess this is not very well though-out, and maybe it would be good > to simply export the text before the first heading. > That TEXT is not HTML processed I would also consider as > a bug, but I know that some have made clever use of this bug > to insert custom HTML into a file. This is now no loger > necessary since you can embed protected HTML with special commands. Note that the #+HTML: and #+BEGIN_HTML...#+END_HTML directives are not = (yet) a replacement for inserting literal html as it can be done using = #+TEXT:. As far as I've noticed, #+TEXT: inserts html (or any other tex= t) = before the first heading (before the

in the resulting html file), = something the #+HTML directives can't do, since the effect of placing it= = before the first heading is null, as it is not exported. I don't expect to use Org as a full-featured publishing engine. Still, = = the following example represents a very specific use of #+TEXT: that I = need for implementing file-specific site navigation (as opposed to = project-specific, which in this case is configured using :preamble in = `org-publish-project-alist'). These are the relevant lines in the org = file: ----- #+TEXT: @

@

@Return t= o = introduction@@

* Sonata for Unaccompanied Achilles ^ will be exported as

after

... ----- AFAIK, I can't use #+HTML: to insert that snippet before the

, or = first level 'org' heading, which is what I need. > Hmmm, not clear to me how exactly this should be done. Should we > cast a vote for exporting text before the first heading? This is my idea: if the text before the first heading were exported and = = that included the #+HTML: directives, it would be one way (out of perhap= s = a handful) to avoid having to use the #+HTML: and #+TEXT: directives for= = the same purpose -- exporting literal html. In the end, for literal htm= l = we'd just use #+HTML: anywhere in the file, while #+TEXT: could be = reserved for a different purpose. Vote: +1 But the final decision should consider other (broader) aspects... Kind regards. -- = Alex Fu