|
From: | Carsten Dominik |
Subject: | Re: [Orgmode] Org-mode version 4.68 |
Date: | Tue, 20 Mar 2007 13:14:17 +0100 |
On Mar 19, 2007, at 15:21, Alex Fu wrote:
Dear all,On Fri, 16 Mar 2007 13:08:33 -0400, Carsten Dominik <address@hidden> 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 <h2> 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: <a href="...">unprocessed HTML code</a> #+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
[Prev in Thread] | Current Thread | [Next in Thread] |