From: Jambunathan K <kjambunathan@gmail.com>
To: mail@christianmoe.com
Cc: emacs-orgmode@gnu.org, Mehul Sanghvi <mehul.sanghvi@gmail.com>
Subject: Re: org-odt: specifying fonts
Date: Wed, 19 Oct 2011 23:24:38 +0530 [thread overview]
Message-ID: <81d3dslvdt.fsf@gmail.com> (raw)
In-Reply-To: <4E9DDBB7.5050806@christianmoe.com> (Christian Moe's message of "Tue, 18 Oct 2011 22:04:07 +0200")
> I agree with Mehul it would be great to have an option to specify a
> styles file on a per-file basis. Something like:
>
> #+ODT_STYLE: ~/org/odt-templates/cv.odt
I have gone with `#+ODT_STYLES_FILE: '[1]. Refer the docstring below for a
sample setting.
,----[ C-h v org-export-odt-styles-file RET ]
| org-export-odt-styles-file is a variable defined in `org-odt.el'.
| Its value is nil
|
| Documentation:
| Default styles file for use with ODT export.
| Valid values are one of:
| 1. nil
| 2. path to a styles.xml file
| 3. path to a *.odt or a *.ott file
| 4. list of the form (ODT-OR-OTT-FILE (FILE-MEMBER-1 FILE-MEMBER-2
| ...))
|
| [snip]
|
| Use "#+ODT_STYLES_FILE: ..." directive to set this variable on
| a per-file basis. For example,
|
| #+ODT_STYLES_FILE: "/path/to/styles.xml" or
| #+ODT_STYLES_FILE: ("/path/to/file.ott" ("styles.xml" "image/hdr.png")).
|
| You can customize this variable.
`----
Hope it is OK.
Footnotes:
[1] The name of the option is same as the upcased custom variable name
with `org-export-' prefix stripped. The same convention can be used for
any "future" per-file odt settings.
--
next prev parent reply other threads:[~2011-10-19 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 16:32 org-odt: specifying fonts Mehul Sanghvi
2011-10-18 20:04 ` Christian Moe
2011-10-18 21:15 ` Mehul Sanghvi
2011-10-19 14:35 ` Matt Price
2011-10-19 15:16 ` Mehul Sanghvi
2011-10-19 15:32 ` Jambunathan K
2011-10-19 15:39 ` Jambunathan K
2011-10-19 15:37 ` Jambunathan K
2011-10-19 19:37 ` Christian Moe
2011-10-19 17:54 ` Jambunathan K [this message]
2011-10-19 18:15 ` Mehul Sanghvi
2011-10-19 18:30 ` Christian Moe
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=81d3dslvdt.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.com \
--cc=mehul.sanghvi@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).