From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Org-mode version 4.68 Date: Tue, 20 Mar 2007 13:14:17 +0100 Message-ID: References: <1c43fad8a5823dc1386f861a4984ae26@science.uva.nl> <87tzwle93o.fsf@bzg.ath.cx> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HTdFr-0005jQ-24 for emacs-orgmode@gnu.org; Tue, 20 Mar 2007 08:15:55 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HTdFq-0005jE-Kt for emacs-orgmode@gnu.org; Tue, 20 Mar 2007 08:15:54 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HTdFq-0005jB-Dq for emacs-orgmode@gnu.org; Tue, 20 Mar 2007 07:15:54 -0500 Received: from korteweg.uva.nl ([146.50.98.70]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HTdEG-0002YO-WC for emacs-orgmode@gnu.org; Tue, 20 Mar 2007 08:14:17 -0400 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: Alex Fu Cc: emacs-orgmode@gnu.org On Mar 19, 2007, at 15:21, Alex Fu wrote: > 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 > text) 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. This will change. In the future, #+TEXT: lines will be fully processed like any other buffer line, I consider that fact that is was not processed so far as a bug. On the other hand, constructs like the following will be allowed: #+TEXT: Processed text iwth *bold* words #+TEXT: #+BEGIN_HTML #+TEXT: unprocessed HTML code #+TEXT: #+END_HTML #+TEXT: /This/ will be processed again There will also be an option to export the text before the first headline, in which case the #+TEXT prefix is not necessary. - Carsten