From: Fabrice Popineau <fabrice.popineau@supelec.fr>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Exporting to multiple files
Date: Thu, 13 Mar 2014 14:11:06 +0100 [thread overview]
Message-ID: <CAFgFV9Piy6_9+JcePe_stjH4in=dBYpao9BeqfBqiABHsTZ5Qg@mail.gmail.com> (raw)
In-Reply-To: <20140309103453.24010dae@aga-netbook>
[-- Attachment #1: Type: text/plain, Size: 1830 bytes --]
You could have a look at o-blog for example. It does something which is not
too far from what you want (IIUC).
It does it in a way similar to what you describe.
Regards,
Fabrice
2014-03-09 10:34 GMT+01:00 Marcin Borkowski <mbork@wmi.amu.edu.pl>:
> Dnia 2014-03-09, o godz. 02:34:09
> Marcin Borkowski <mbork@wmi.amu.edu.pl> napisał(a):
>
> > Hi all,
> >
> > I'd like to export an Org-mode file to /multiple/ HTML files. For
> > instance, I might want to convert all first and second level headings
> > to files, and third-level headings to <h1>, fourth-level ones to <h2>
> > inside these files etc. Is that possible? I looked into the docs,
> > but didn't find anything like this.
> >
> > Of course, there's an issue of /naming/ these files. Basing the names
> > on the text of the heading would be the best thing to have, but it's
> > not strictly necessary for me - numbers or (as a /very last/ resort)
> > some kind of SHA hashes might do as well.
> >
> > (In fact, I'd like to write a custom HTML exporter based on the HTML
> > one, so that I'd be fine with some Elisp to do this as opposed to just
> > setting some variables.)
>
> It occurred to me that I could just walk through the file, creating
> temporary buffers with my subtrees, demote them and export them one by
> one to HTML. This seems doable (and even not too complicated), but is
> there a better/simpler way, or has someone already invented that wheel?
>
> Best,
>
> --
> Marcin Borkowski
> http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
> Adam Mickiewicz University
>
>
--
Fabrice Popineau
-----------------------------
SUPELEC
Département Informatique
3, rue Joliot Curie
91192 Gif/Yvette Cedex
Tel direct : +33 (0) 169851950
Standard : +33 (0) 169851212
------------------------------
[-- Attachment #2: Type: text/html, Size: 2644 bytes --]
next prev parent reply other threads:[~2014-03-13 13:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 1:34 Exporting to multiple files Marcin Borkowski
2014-03-09 9:34 ` Marcin Borkowski
2014-03-13 11:59 ` Bastien
2014-03-15 11:11 ` Marcin Borkowski
2014-03-13 13:11 ` Fabrice Popineau [this message]
2014-03-13 17:38 ` Richard Lawrence
2014-03-15 11:13 ` Marcin Borkowski
2014-04-06 20:45 ` Sacha Chua
2014-04-07 13:45 ` Iannis Zannos
2014-09-30 23:46 ` Marcin Borkowski
2014-10-01 3:20 ` Eric Abrahamsen
2014-10-01 12:44 ` Nicolas Goaziou
2014-10-01 14:07 ` Marcin Borkowski
2014-10-01 15:00 ` Nicolas Goaziou
2014-10-01 17:17 ` Eric Abrahamsen
2014-10-01 19:12 ` Nicolas Goaziou
2014-10-02 3:22 ` Eric Abrahamsen
2014-10-01 9:25 ` Rasmus
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='CAFgFV9Piy6_9+JcePe_stjH4in=dBYpao9BeqfBqiABHsTZ5Qg@mail.gmail.com' \
--to=fabrice.popineau@supelec.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
/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).