From: Ethan Ligon <ligon@are.berkeley.edu>
To: emacs-orgmode@gnu.org
Subject: [Bug] Problem with html export of description list items
Date: Wed, 6 Apr 2011 00:07:42 +0000 (UTC) [thread overview]
Message-ID: <loom.20110406T011110-551@post.gmane.org> (raw)
I've just stumbled across what I regard as a bug in the html export of
description list items.
The problem has to do with whether the specification of a description
list includes a trailing space or not; i.e., whether "- Item ::" is
treated the same way as "- Item :: ". LaTeX export treats these as
identical. Html export gets confused about what the description list
item is, and winds up generating a "???" for the description.
Here's an example.
#+begin_src org
* Illustration of bug in html export
- Has a space after the colons :: so will work in latex and html
- No space after the colons ::so won't work in html
- Has a terminating space ::
- So it works in both html and latex export!
- Even though it's difficult to distinguish from the next example.
- Lacks a terminating space ::
- *Doesn't* work in html export, does in latex.
#+end_src
The relevant bit of the html export
#+begin_src html
<div id="outline-container-1" class="outline-2">
<h2 id="sec-1"><span class="section-number-2"></span> Illustration of bug in
html export </h2>
<div class="outline-text-2" id="text-1">
<dl>
<dt>This has a space after the colons</dt><dd>so will work
</dd>
<dt>???</dt><dd>This doesn't have a space after the colons ::so won't work
</dd>
<dt>Has a terminating space</dt><dd>
<ul>
<li>So it works in both html and latex export!
</li>
<li>Even though it's difficult to distinguish from the next example.
</li>
</ul>
</dd>
<dt>???</dt><dd>Lacks a terminating space ::
<ul>
<li><b>Doesn't</b> work in html export, does in latex.
</li>
</ul>
</dd>
</dl>
</div>
</div>
#+end_src
The relevant bit of the latex export looks like this:
#+begin_src latex
\vspace*{1cm}
\section{Illustration of bug in html export}
\label{sec-1}
\begin{description}
\item[This has a space after the colons] so will work
\item[This doesn't have a space after the colons] so won't work
\item[Has a terminating space]
\begin{itemize}
\item So it works in both html and latex export!
\item Even though it's difficult to distinguish from the next example.
\end{itemize}
\item[Lacks a terminating space]
\begin{itemize}
\item \textbf{Doesn't} work in html export, does in latex.
\end{itemize}
\end{description}
#+end_src
Thanks for any help!
-Ethan Ligon
next reply other threads:[~2011-04-06 0:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 0:07 Ethan Ligon [this message]
2011-04-06 0:38 ` [PATCH] Problem with html export of description list items Ethan Ligon
2011-04-07 12:51 ` Nicolas Goaziou
2011-04-07 21:52 ` Ethan Ligon
2011-04-08 11:53 ` Nicolas Goaziou
2011-04-08 17:46 ` [PATCH] Fix for html & docbook " Ethan Ligon
2011-04-09 3:19 ` [PATCH] Problem with html " Ethan Ligon
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=loom.20110406T011110-551@post.gmane.org \
--to=ligon@are.berkeley.edu \
--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).