From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Xiha <xiha@laposte.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Questions about exporting: subtitle, level formating, custom highlight markers error
Date: Mon, 27 Jul 2015 09:34:41 +0100 [thread overview]
Message-ID: <87egjugfry.fsf@ucl.ac.uk> (raw)
In-Reply-To: <55B4DAEC.7030805@laposte.net> (xiha@laposte.net's message of "Sun, 26 Jul 2015 15:04:44 +0200")
On Sunday, 26 Jul 2015 at 15:04, Xiha wrote:
> 2) I have #+OPTIONS: H:9 num:9 because explicit level structure is
> important for this document. I would like to have more control over
For LaTeX export, this will not work (AFAIK) as LaTeX only supports 4 or
so levels of headings.
> how this is exported, e.g. by setting heading font size as well as
> left-margin widths per level, for a staircase-like effect similar to
> that obtained with org-indent-mode in Org itself. (How) can this be
> done?
If you want this kind of control, you should ensure that the LaTeX uses
the scrartcl (koma-script) article class which is highly
configurable. However, you will have to do the LaTeX configuration
yourself directly using #+latex: and #+latex_header: org directives in
your org document.
For HTML export, you will need to define the appropriate CSS
specifications to achieve the stair case effect. I have no idea how
this would be done...
> 3) I forget through which command/menu, but I set custom markers that
> 'highlight' the words they surround, within Org itself. I'm using the
> 'leuven' theme which makes them stand out with a yellow background -
> useful for passages that need work etc. But now when I try to export
> to HTML or PDF, it fails with "Unknown marker at 10497". Is there a
> way to get the highlighting in the exported document? Alternatively,
> can I tell the exporter to ignore the custom markers, i.e. treat them
> as regular characters?
Could you maybe post a small example file? I have no idea what you are
describing unfortunately.
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-1293-g985420
next prev parent reply other threads:[~2015-07-27 8:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 13:04 Questions about exporting: subtitle, level formating, custom highlight markers error Xiha
2015-07-26 18:44 ` Rasmus
2015-07-27 8:34 ` Eric S Fraga [this message]
2015-07-27 13:55 ` Xiha
2015-07-27 15:02 ` Eric S Fraga
2015-07-28 7:24 ` Sebastien Vauban
2015-07-28 8:20 ` Eric S Fraga
2015-07-28 11:38 ` Xiha
2015-07-28 12:05 ` Eric S Fraga
2015-07-28 13:47 ` Xiha
2015-07-28 15:19 ` John Kitchin
2015-07-29 19:32 ` Xiha
2015-07-29 19:51 ` Marcin Borkowski
2015-07-28 12:25 ` Nick Dokos
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=87egjugfry.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=xiha@laposte.net \
/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).