From: "Alex Fu" <alexfu@arcor.de>
To: emacs-orgmode@gnu.org
Subject: Problems exporting literal HTML fragments
Date: Mon, 19 Mar 2007 10:21:23 -0400 [thread overview]
Message-ID: <op.tpfwtxkn1wjnvxafu@pc3> (raw)
Hello all,
When using the #+TEXT:, #+HTML:, or #BEGIN_HTML...#END_HTML directives to
output literal html fragments, the resulting markup is enclosed in a
paragraph with <p> and </p> tags. Whenever I need something else, I am
forced to inhibit their generation in clumsy ways, "cancelling out" the
opening and closing paragraph tags like this:
#+TEXT: @</p>@<p class="marginpar">@<a href="/home.html">Back to
main@</a>@</p>@<p>
or
#+HTML: </p><p class="marginpar"><a href="/home.html">Back to
main</a></p><p>
Thus, I think it would be a good idea *not* to enclose literal html
fragments in a paragraph (<p>...</p>), given that the markup is already
being controlled through these directives.
* * *
Possible bug:
#+BEGIN_HTML...#+END_HTML blocks are not correctly interpreted if they
consist of multiline text. Only 1 line --the one exactly above
#+END_HTML-- is exported literally.
For example:
#+BEGIN_HTML
</p><div id="special"><p><img src="someimage.jpg"/></p></div><p>
#+END_HTML
does right thing (well, almost, because of having to cancel out <p> tags),
producing:
<div id="special"><p><img src="someimage.jpg"/></p></div>
However,
#+BEGIN_HTML
</p><div id="special">
<p><img src="someimage.jpg"/></p>
</div><p>
#+END_HTML
produces:
<p>
</p><div id="special">
<img src="someimage.jpg"/>
</div>
Tested on org 4.68, GNU Emacs 22.0.92.1.
Kind regards.
--
Alex Fu
next reply other threads:[~2007-03-19 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 14:21 Alex Fu [this message]
2007-03-20 12:07 ` Problems exporting literal HTML fragments Carsten Dominik
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=op.tpfwtxkn1wjnvxafu@pc3 \
--to=alexfu@arcor.de \
--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).