From: Luca Ferrari <fluca1978@gmail.com>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: from org to openoffice presentations (or make org looks like openoffice)
Date: Wed, 24 Jul 2019 13:42:11 +0200 [thread overview]
Message-ID: <CAKoxK+6Fb1kTcHa8+Sgf4De6gqUP8fL+Y2PRozR3cD6rtAq25w@mail.gmail.com> (raw)
In-Reply-To: <877e87rhl3.fsf@ucl.ac.uk>
Thanks all for the quick replies!
On Wed, Jul 24, 2019 at 9:56 AM Fraga, Eric <e.fraga@ucl.ac.uk> wrote:
> #+latex_header: \usebackgroundtemplate{\includegraphics[width=\paperwidth]{<your_fig>}}
>
Yes, this is what I'm doing so far. The problems I see are:
1) the image contains a footer, and LaTeX does not anything about such
footer so sometimes text can overlap with the footer. If I isolate the
footer as a separate image, how can I specify to place it to the
bottom of each slide and have beamer not placing controls and other
text on the slides?
2) I usually provide two sets of slides, one dark and one light
(printable), and therefore I suspect to provide two different
backgrounds and duplicate my org file for each theming accordingly.
Any better idea? If I can isolate the footer (which is what makes the
slides look like what is requested), is there a way to apply say a
color as background and do a "variable"-based export to beamer
choosing the color as option?
By the way, things were even worst of how I described them: the
template was Microsoft Office (not even Open Office)!
Thanks,
Luca
next prev parent reply other threads:[~2019-07-24 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 7:13 from org to openoffice presentations (or make org looks like openoffice) Luca Ferrari
2019-07-24 7:36 ` Marcin Borkowski
2019-07-24 7:56 ` Fraga, Eric
2019-07-24 11:42 ` Luca Ferrari [this message]
2019-07-24 12:12 ` Fraga, Eric
2019-07-25 7:53 ` Luca Ferrari
2019-07-25 9:16 ` Fraga, Eric
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=CAKoxK+6Fb1kTcHa8+Sgf4De6gqUP8fL+Y2PRozR3cD6rtAq25w@mail.gmail.com \
--to=fluca1978@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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).