emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Html export suggestion (use of <div>)
Date: Wed, 17 Oct 2007 11:40:07 +0100	[thread overview]
Message-ID: <87odeynhx4.fsf@bzg.ath.cx> (raw)
In-Reply-To: <b54e49f3abeed2b2b9a657364cac02e9@science.uva.nl> (Carsten Dominik's message of "Wed, 17 Oct 2007 11:13:08 +0200")

Hi Carsten,

Carsten Dominik <dominik@science.uva.nl> writes:

> I now see why it can be useful to preserve the outline
> structure in the HTML export, and if Bastien remains the
> only voice against it, I will put these <div>s in.

I didn't pronounced myself "against" it at all.  I really like the idea
of having <div>s in Org :)

I only raised concerns about the fact that having <div>s will perhaps
lead to a full templating system for the HTML output, and should be
thought carefully (what structure? what classes? what ids?)

Just for the record, here are the relevant parts of the (private) email
I sent on this topic:

,----
| i don't want to jump into the « Dive-in-<div>-or-die » discussion, but
| just to give you my very first impression on this: having <div> is nice
| but you will surely end up trying to implement "templates" for the HTML
| exporter.
| 
| The choice for good class/id defaults might also be tricky: should a
| <div> for a section have a class attribute like class="section" or an id
| attribute like id="section1"?  Org will of course chose the class=""
| option, for the sake of both simplicity and genericity.  But I can bet
| you will soon be under pressure for more and more options...
`----

Again: I'm not against <div>s, I'm just curious on how it could develop!

-- 
Bastien

next prev parent reply	other threads:[~2007-10-17  9:40 UTC|newest]

Thread overview: 12+ 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
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 [this message]
2007-10-18 13:00       ` cezar
  -- strict thread matches above, loose matches on Subject: below --
2007-10-10 13:31 cezar
2007-10-10 14:36 ` cezar

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=87odeynhx4.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --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

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).