emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: "Sébastien Vauban" <zthjwsqqafhv@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Export as HTML
Date: Mon, 30 Mar 2009 14:28:41 +0200	[thread overview]
Message-ID: <871vsfgpom.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <874oxbwedd.fsf@mundaneum.com> ("Sébastien Vauban"'s message of "Mon, 30 Mar 2009 11:26:22 +0200")


Could you describe here what's the problem with the <div> element?

This was put in recently on a users request. If you don't want to use it
for you're CSS styling, just don't.

One way to gear the export results to your needs exactly might be the
usage of XSL (which you could use with the XHTML or DocBook export).




Since the ideas about layout differ so much, I think it's not worth it
to change the XHTML export, but to put more effort into creating a
template based export instead. Or into what was already called the
`generic exporter' here, and I think some people are already working on
it.



   Sebastian










Sébastien Vauban <zthjwsqqafhv@spammotel.com> writes:
> Hi Roc Lee,
>
> Roc lee wrote:
>> 2009/3/30 roc lee <roc.lee.80@gmail.com>
>>>> Could you remove that line, and its closing tag from `(insert
>>>> "\n</div>\n</body>\n</html>\n"))' (in function `org-export-as-html') so
>>>> that we have a completely naked BODY, that the user can fill at its own
>>>> freedom via the preamble/postamble?
>>
>> There is no such a div on my exported files. The version I am using is
>> 6.17a.
>
> See lines 3584:
>
>
> <div id=\"content\">
>
> and line 4205:
>
>
> (insert "\n</div>\n</body>\n</html>\n"))
>
> in my Org-mode version 6.24trans.
>
> Seb

  reply	other threads:[~2009-03-30 12:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30  8:55 Export as HTML Sébastien Vauban
2009-03-30  9:03 ` roc lee
2009-03-30  9:10   ` roc lee
     [not found]     ` <bdfccab30903300210h7a683ae4hc4e4a655ce7327c6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-30  9:26       ` Sébastien Vauban
2009-03-30 12:28         ` Sebastian Rose [this message]
2009-03-30 12:46           ` Matthew Lundin
2009-03-30 13:11             ` Carsten Dominik
2009-03-30 14:45               ` Matthew Lundin
2009-03-30 17:45                 ` Carsten Dominik
     [not found]                   ` <1E2E8AB7-274B-4283-AC02-631D165C06E1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-03-30 19:07                     ` Sébastien Vauban
2009-03-30 19:55                   ` Sebastian Rose
2009-03-30 21:06                     ` Carsten Dominik
2009-03-30  9:53 ` Carsten Dominik
     [not found]   ` <61ECBCBA-4963-4435-82BD-BAA37A03FC50-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-03-30 11:23     ` Sébastien Vauban
2009-03-30 11:59       ` roc lee
2009-03-30 13:48       ` Sebastian Rose

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=871vsfgpom.fsf@kassiopeya.MSHEIMNETZ \
    --to=sebastian_rose@gmx.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=zthjwsqqafhv@spammotel.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).