emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mehul Sanghvi <mehul.sanghvi@gmail.com>
To: mail@christianmoe.com
Cc: emacs-orgmode@gnu.org, Jambunathan K <kjambunathan@gmail.com>
Subject: Re: org-odt: specifying fonts
Date: Tue, 18 Oct 2011 17:15:29 -0400	[thread overview]
Message-ID: <CAPo9-A8Mht5q23eSihkzWnfKLSX1kLtJvFv5gPoRh_Y40xYezA@mail.gmail.com> (raw)
In-Reply-To: <4E9DDBB7.5050806@christianmoe.com>


      Thanks for the stopgap measure.  As for fonts, like styles, it
would be easier, simpler and more elegant
to be able to do that without having to edit styles.odt every time.
This is not specific to org-odt.  It should be,
at least I think so for now, to do this with any exporting backend.

If you send me a styles.odt, and I do not like the fonts you are
using, it becomes cumbersome to be editing the styles.odt
for each font and making sure to change it in all possible places
until I settle on a proper font I want to use.

If I could instead specify the font in org file itself, it would be a
matter of changing the header and re-generating the file.

The ODT_STYLE is certainly a good enhancement.

On Tue, Oct 18, 2011 at 16:04, Christian Moe <mail@christianmoe.com> wrote:
> Hi, Mehul, cc: Jambunathan,
> 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
> Jambunathan, please consider this a feature request (if you haven't
> implemented it already, and I've missed it as usual...)
> Many users will want to use different styles files for different kinds of
> document (e.g. report.odt, cv.odt). Customizing org-export-odt-styles-file
> every time they've got a different kind of document to export does not seem
> the best way. There should be a way for each Org file to remember what ODT
> style it wants, parallel to the options that exist for html (#+STYLE) and
> latex (#+LATEX_HEADER).
> As for specifying fonts, etc., in ODT export, that's definitely something
> that should be done through the choice of an external style template. The
> org-odt exporter has done its job if everything you could reasonably want to
> style is exported in a named paragraph or character style that you can apply
> a template to.
> Yours,
> Christian
> PS. Mehul, I do have a stopgap solution for specifying the style template on
> a per-file basis. Place this somewhere in your Org document (e.g. before the
> first heading), and replace "/path/to/template.odt" with the path to your
> styles file.
> #+begin_src emacs-lisp :results silent :exports results
> (setq org-export-odt-styles-file "/path/to/template.odt")
> #+end_src
> On 10/18/11 6:32 PM, Mehul Sanghvi wrote:
>> This may not be specific to org-odt, but maybe applies to Org itself.
>> I have a LaTeX file which I use for my resume at the moment.  The
>> fonts that are being used with it are great for what I want.
>> How do I specify fonts that I want to use, rather then the defaults?
>> Do I have to do that through styles.odt ?
>> If so, is there a specific OPTION for specifying the style file to use
>> ?   That would be a nice enhancement if it is not already there.
>> I may want to use different styles/fonts, etc. and probably do not
>> want to play around with the styles.odt file each time I make
>> changes to the styles.odt file.

Mehul N. Sanghvi
email: mehul.sanghvi@gmail.com

  reply	other threads:[~2011-10-18 21:15 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 [this message]
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
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:

  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=CAPo9-A8Mht5q23eSihkzWnfKLSX1kLtJvFv5gPoRh_Y40xYezA@mail.gmail.com \
    --to=mehul.sanghvi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \
    --cc=mail@christianmoe.com \


* 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


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).