From: Nick Dokos <nicholas.dokos@hp.com>
To: Jordi Inglada <jordi.inglada@cesbio.cnes.fr>
Cc: Jeff Horn <jrhorn424@gmail.com>,
emacs-orgmode@gnu.org, nicholas.dokos@hp.com
Subject: Re: Title page for book latex export
Date: Mon, 18 Oct 2010 17:43:49 -0400 [thread overview]
Message-ID: <12673.1287438229@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from Jordi Inglada <jordi.inglada@cesbio.cnes.fr> of "Mon, 18 Oct 2010 22:19:32 +0200." <19644.43988.128890.607963@goeland.ups-tlse.fr>
Jordi Inglada <jordi.inglada@cesbio.cnes.fr> wrote:
> Hi Jeff,
>
> Thanks for your reply. I actually did that as a first try, but the
> problem is that the org->tex export generates a standard title page
> (title, author, date), then the table of contents, and only after that
> my title page.
>
> So the question would rather be: how to deactivate the standard title
> page and put mine before anything else in the document?
>
> Thank you.
>
> Jordi
>
> Jeff Horn writes:
> > Any code between LaTeX code blocks should execute automatically. For
> > example, I could place an entire .tex source between
> >
> > #+BEGIN_LaTeX
> > [Code goes here]
> > #+END_LaTeX
> >
> > And name the file tex.org and it can be exported to PDF. So, I would
> > just place the normal LaTeX commands you would use to accomplish what
> > you are trying to do in a code block, like above.
> >
> > Good luck,
> > Jeff
> >
> > On Mon, Oct 18, 2010 at 5:39 AM, Jordi Inglada
> > <jordi.inglada@cesbio.cnes.fr> wrote:
> > > Hi all,
> > >
> > > I would like to export to LaTeX using "#+LaTeX_CLASS: book" and use a
> > > title page that I have built using the LaTeX titlepage environment. I
> > > don't know where to put the titlepage environment and how to
> > > deactivate the title page generation by the LaTeX export.
> > >
> > > Thank you for your help.
> > >
> > > Jordi
> > >
<rant>
Instead of saying: "I would like to do such and so", please consider using
something like this:
"I would like to do such and so. This is what I tried:
<contents of org file>
This is what I got when I exported to LaTeX:
<contents of TeX file>
As you can see, I get <description of undesired behavior>, instead of
what I would like to get: <description of desired behavior>.
How do I accomplish that?"
That helps in several ways:
o it helps the submitter of the question:in the process of
explaining the problem you might hit upon the solution.
o it helps the potential helpers: instead of having to deconstruct
the description and construct an example of their own (which
might or might not be related to the original problem), they have
an exact specification of the problem.
o it helps the submitter *and* the potential helpers: instead of me
guessing what the problem is, replying, you pointing out that I
misunderstood, explaining the misunderstanding, etc. etc., we
avoid the extended conversation: the submitter gets a quicker
answer and the helpers can go back to what they were doing
faster. And saying: "I tried that - it didn't work", well,
that's adding insult to injury.
o it helps the list: there is a crisp description of the problem and
(hopefully) a crisp answer. Those who are interested can file it
away faster, those who are not can bypass it faster.
o it helps future org-mode users: searching the archive for answers
is much easier.
Also it places the burden where it should be: it is the submitter who
has the problem; it is only fair that it be the submitter who does most
of the work to get it resolved: so tell me (nay, *show me*) what you've
tried. At the very least, it will save some typing on my part.
In general, the rule of thumb is "more information is better than less."
Act accordingly.
In your case, you mention the titlepage environment. Now sometime in the
distant past, I might have used it but do I remember anything about it?
Nope, not at this point. So the next step is to go do some research to
find out how to use it: oops, I packed away the LaTeX book for the move
next week. Got to go to the web - oops, firefox is wedged, restart it.
Now what? Ah, heck the wireless is having a bad day...
The idea is to make the helper want to continue helping instead of
giving him/her a chance to say "Ah, screw it - it's not worth it,
I have better things to do."
</rant>
OK, now that I've got that off my chest and as a reward for subjecting
you (and everybody else) to the rant, here's a way to do what you
want (I think - unless I've misunderstood the problem...)
,----
| #+LATEX_HEADER: \input{mytitle}
|
| * Foo
| foo
|
| * Bar
| bar
`----
where the file mytitle.tex looks like this:
,----
| \renewcommand\maketitle{\begin{titlepage}%
| FOO
| \end{titlepage}%
| }
`----
and where instead of "FOO", you put your titlepage stuff.
That's how \maketitle is defined in the first place, so
just redefine it.
HTH,
Nick
next prev parent reply other threads:[~2010-10-18 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 9:39 Title page for book latex export Jordi Inglada
2010-10-18 17:44 ` Jeff Horn
[not found] ` <9312871.193.1287423634931.JavaMail.root@zm-cesbio-01>
2010-10-18 20:19 ` Jordi Inglada
2010-10-18 21:43 ` Nick Dokos [this message]
2010-10-19 6:18 ` Carsten Dominik
[not found] ` <28722569.197.1287437982941.JavaMail.root@zm-cesbio-01>
2010-10-19 6:13 ` Jordi Inglada
2010-10-19 14:04 ` Nick Dokos
2010-10-20 2:33 ` Jeff Horn
2010-10-20 4:11 ` Nick Dokos
[not found] ` <AANLkTiks0Om7sdkFfiR5CiJncixhD5AKE2htZcexKLcW@mail.gmail.com>
2010-10-20 4:49 ` Jeff Horn
2010-10-20 5:05 ` Jambunathan K
2010-10-27 22:28 ` Bastien
2010-10-28 9:00 ` Jeff Horn
[not found] ` <493995.8239.1287496847211.JavaMail.root@zm-cesbio-01>
2010-10-19 14:36 ` Jordi Inglada
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=12673.1287438229@alphaville.usa.hp.com \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=jordi.inglada@cesbio.cnes.fr \
--cc=jrhorn424@gmail.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).