From: Carsten Dominik <carsten.dominik@gmail.com>
To: Detlef Steuer <steuer@unibwh.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: HTML export without all <div ...> tags
Date: Fri, 25 Sep 2009 14:45:06 +0100 [thread overview]
Message-ID: <D72BCC93-EB47-4844-A296-EDCFD422538D@gmail.com> (raw)
In-Reply-To: <20090925150010.0250f077@gaia>
On Sep 25, 2009, at 2:00 PM, Detlef Steuer wrote:
> Hi!
>
> I'm in the process of adapting cmsimple (www.cmsimple.dk) to use our
> university's corporate design. Cmsimple in its core is a php script,
> which takes _one_
> html file and creates the complete layout of a site on the fly while
> splitting the file apart at h[123] levels.
>
> Now I want to create that one html file with org-mode. What else?
>
> If I could get org-mode to export pure html without all the <div>
> tags I think I am done. But how to explain to orgmode to be dumb?
>
> The variable Org-Export-Html-Style-Include-Default ist set to nil,
> so no definitions included. Nevertheless the way divs are grouped
> around headlines seems to disturb cmsimple and its layout.
> At least, if I remove all divs the layout is just fine.
>
> Is there a way to get rid of all div tags in exported html?
I guess the easiest would be to just post-process the html file
produced by Org. For example with perl (untested):
perl -ap -e 's/<div [^>]*>//g' orgoutput.html > simple.html
HTH
- Carsten
next prev parent reply other threads:[~2009-09-25 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 13:00 HTML export without all <div ...> tags Detlef Steuer
2009-09-25 13:32 ` Matt Lundin
2009-09-25 13:53 ` R: " Giovanni Ridolfi
2009-09-25 13:45 ` Carsten Dominik [this message]
2009-09-25 14:06 ` Matt Lundin
2009-09-25 14:15 ` scripting challenge (was: Re: HTML export without all <div ...> tags) Giovanni Ridolfi
2009-09-25 14:19 ` Carsten Dominik
2009-09-25 14:32 ` scripting challenge Bernt Hansen
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=D72BCC93-EB47-4844-A296-EDCFD422538D@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=steuer@unibwh.de \
/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).