[forgot to cc: the list] Sébastien Vauban <wxhgmqzgw...@spammotel.com> wrote:
> Hi Avdi, > > Nick Dokos wrote: > > Avdi Grimm <a...@avdi.org> wrote: > >> On Wed, Apr 27, 2011 at 5:41 PM, Nick Dokos <nicholas.do...@hp.com> wrot= > e: > >> > Just star them by hand in the tex file after exporting for the last > >> > time: it'll take two seconds. You may be able to do it from Org by > >> > writing a custom function (C-h v org-export-latex-classes <RET> for > >> > details) but I suspect that the effort is just not worth it. > >>=20 > >> Ugh. This is a (somewhat) living document; manually tweaking the .tex > >> after export isn't really an option. > >>=20 > >> I was hoping there was a tag or property that I could set on a section > >> indicating it is frontmatter/backmatter. > > > > I don't know of an easy way within Org - somebody else might have better > > ideas. > > > > If I were in your position, I'd probably write a simple Makefile to produ= > ce > > the PDF and incorporate a simple post-processing awk script to do the > > transformation. Or write an elisp function to run as part of > > org-export-latex-final-hook perhaps. > > What about just inserting > > #+LaTeX: \backmatter{} > > and the like where applicable in the Org file? > >From a quick read of the description of \frontmatter, it is not clear to me that it is going to work the way the OP wants, but it is indeed worth trying: I forgot about that completely. [trying it...] I just ran a quick test: \frontmatter seems to be undefined in the report class - it's only defined in the book class. Thanks, Nick