From: Carsten Dominik <dominik@science.uva.nl>
To: Rasmus Pank Roulund <rasmus.pank@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug and feature request in HTML export
Date: Tue, 10 Feb 2009 23:53:23 +0100 [thread overview]
Message-ID: <8A8BB431-CFF6-4F82-99FA-C2B84AF4C067@uva.nl> (raw)
In-Reply-To: <82wsbyatnj.fsf@gmail.com>
On Feb 10, 2009, at 10:06 PM, Rasmus Pank Roulund wrote:
> Hello,
> There seems to be a bug in HTML export.
> I am using Org for making a (fancy) web site.
> I define the top menu via a list which is made fancy via CSS.
>
> The Org file looks like this:
>
> #+HTML: <div id="topbar">
>
> - [[file:index.org][Forside]]
> - [[file:eksempler.org][Eksempler]]
>
> #+HTML: </div>
Org cannot know that you do want to end the list here, the HTML
insertion might be part of the list.
I do not know how to fix this.
>
> I also have a couple of feature request/bug reports for html export:
>
> First: it would be nice if one could specify the location of the title
> similar to the [TABLE-OF-CONTENTS] option. At the moment it seems to
> always be placed in the top of the page, which might not be desirable.
It seems to me quite reasonable to put it at the top of the page.
Don't forget that Org is not a full HTML editor, it just tried to do
a good job at converting your file.
> Second: I do not know if this is a feature, but * Heading (i.e. a
> first
> level heading) is marked as a <h2> heading. It should probably be
> <h1>. At least one should be able to define it as a <h1> heading.
See `org-export-html-toplevel-nlevel', and also see
http://orgmode.org/worg/org-tutorials/org-customize.php
> Third (bug): Sometimes links are rendered wrong:
> [[http://etext.library.adelaide.edu.au/k/keynes/john_maynard/k44g/k44g.html
> ]]
> is rendered as <a href="http://etext.library.adelaide.edu.au/k/keynes/john_maynard/k44g/k44g.html
> ">http://etext.library.adelaide.edu.au/k/keynes/john<sub>maynard</
> sub>/k44g/k44g.html</a>
> notice the <sub>-tags!
You do not have a recent version of Org-mode. Please always
try the latest version before reporting bugs.
> Forth: Sometimes it is desirable to be able to #+HTML in links and
> titles. This is not possible.
> For example:
> #+TITLE: #+HTML: <span class="latex">T<sub>E</sub>X</span>
> or
> [[http://scripts.sil.org/xetex][
> #+HTML: <span class="latex">X<sub>Ǝ</sub>T<sub>e</sub>X</span>
> ]]
This is not supported currently, and I am not sure we will get there.
For this specific case you will get away with
#+TITLE: @<span class="latex">T@<sub>E@</sub>X@</span>
However, if you need this much or more control, maybe Muse
will be a better option.
- Carsten
next prev parent reply other threads:[~2009-02-10 22:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 21:06 Bug and feature request in HTML export Rasmus Pank Roulund
2009-02-10 22:53 ` Carsten Dominik [this message]
2009-02-10 23:17 ` Rasmus Pank Roulund
2009-02-11 0:51 ` Sebastian Rose
2009-02-12 18:17 ` Rasmus Pank Roulund
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=8A8BB431-CFF6-4F82-99FA-C2B84AF4C067@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus.pank@gmail.com \
/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).