emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "William Henney" <whenney@gmail.com>
To: "cezar@mixandgo.ro" <cezar@mixandgo.ro>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Html export suggestion (use of <div>)
Date: Mon, 8 Oct 2007 16:04:40 -0500	[thread overview]
Message-ID: <41c818190710081404u235dca46vb2c53915240631f4@mail.gmail.com> (raw)
In-Reply-To: <874ph4wsyr.fsf@myhost.localdomain>

On 10/6/07, cezar@mixandgo.ro <cezar@mixandgo.ro> wrote:
> Mike Newman <mike@newmanfamily.me.uk> writes:
>
> > I had wondered if there was any value in wrapping the html export in
> > <div> </div> sections to match the structure of the org file.
> >

[ snip ]

> I have not yet used this feature, but I am working with html/css all
> day, so here is my opinion:
>
> 1. You shouldn't use more divs than you need to, and you don't need
> them.
>

The trouble is, it is currently not possible to wrap a section in a
<div> when you _do_ need it. At least, I tried to do this with @<div>
... @</div> and it produces incorrectly nested tags for the case when
an org heading is mapped onto an html list item (e.g., <div
class="foo"><li>Contents of org section</div></li>). This is because
the closing </div> is interpreted as being inside the section, rather
than outside it.

> 2. You shouldn't use divs for presentation's sake. Why not make each
> subsection a different class or sumthin.
>

How would that work without divs? The problem is (I think) that
sometimes an org section is represented in html as a header plus
following text:

<h3>HEADER TEXT</h3>
<p>BODY TEXT</p>
<p>MORE BODY TEXT</p>

whereas sometimes it is represented as a list item:

<li>HEADER TEXT<br>BODY TEXT</li>.

So, in the first case one cannot apply a class to the whole section,
since there is no enclosing HTML element. In the second place, you
don't have that problem, but now it is impossible to apply a class to
just the header.

What would be nice would be if there was an option for (some) tags to
be applied as classes in the exported html.

Cheers

Will

-- 

  Dr William Henney, Centro de Radioastronomía y Astrofísica,
  Universidad Nacional Autónoma de México, Campus Morelia

  parent reply	other threads:[~2007-10-08 21:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 20:57 Html export suggestion (use of <div>) Mike Newman
2007-10-06  8:25 ` cezar
2007-10-08 20:00   ` Mike Newman
2007-10-09  7:56     ` cezar
2007-10-08 21:04   ` William Henney [this message]
2007-10-09  8:03     ` cezar
2007-10-08 13:05 ` Dmitri Minaev
2007-10-15 22:08 ` Mike Newman
2007-10-17  9:13   ` Carsten Dominik
2007-10-17 10:40     ` Bastien
2007-10-18 13:00       ` cezar
  -- strict thread matches above, loose matches on Subject: below --
2007-10-10 13:31 cezar
2007-10-15 18:45 ` 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=41c818190710081404u235dca46vb2c53915240631f4@mail.gmail.com \
    --to=whenney@gmail.com \
    --cc=cezar@mixandgo.ro \
    --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).