emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Price <moptop99@gmail.com>
To: Mehul Sanghvi <mehul.sanghvi@gmail.com>
Cc: emacs-orgmode@gnu.org, mail@christianmoe.com,
	Jambunathan K <kjambunathan@gmail.com>
Subject: Re: org-odt: specifying fonts
Date: Wed, 19 Oct 2011 10:35:53 -0400	[thread overview]
Message-ID: <CAN_Dec-rK9miQGWQDyyChA0+rn5NnS0sMnkcFNKnTv91TX6Wdw@mail.gmail.com> (raw)
In-Reply-To: <CAPo9-A8Mht5q23eSihkzWnfKLSX1kLtJvFv5gPoRh_Y40xYezA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]

On Tue, Oct 18, 2011 at 5:15 PM, Mehul Sanghvi <mehul.sanghvi@gmail.com>wrote:

> Christian,
>
>      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.
>
> I think the problem here, Mehul, is that odt export works with styles, not
fonts.  So to do what you want, the exporter would need to be able to tweak
the styles manually(so, I guess, first run some kind of xml transform on the
stylesheet, then apply the stylesheet itself).  If there are hidden
inconsistencies in the original stylesheet, you may end up with
difficult-to-diagnose breakage. I'd definitely suggest just modifying hte
stylesheet and saving it somewhere safe.
m

[-- Attachment #2: Type: text/html, Size: 1632 bytes --]

  reply	other threads:[~2011-10-19 14:36 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 [this message]
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:
  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=CAN_Dec-rK9miQGWQDyyChA0+rn5NnS0sMnkcFNKnTv91TX6Wdw@mail.gmail.com \
    --to=moptop99@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \
    --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).