From: Mehul Sanghvi <mehul.sanghvi@gmail.com>
To: Matt Price <moptop99@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 11:16:19 -0400 [thread overview]
Message-ID: <CAPo9-A9ERmPKMkSRraYo0kYKjJEoyxogggq4LjXh5G6721nrPQ@mail.gmail.com> (raw)
In-Reply-To: <CAN_Dec-rK9miQGWQDyyChA0+rn5NnS0sMnkcFNKnTv91TX6Wdw@mail.gmail.com>
On Wed, Oct 19, 2011 at 10:35, Matt Price <moptop99@gmail.com> wrote:
>
>
> 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
>
>
I will most likely end up it that way and using that as my workflow.
The font thing was
just something coming out from the fact that I do not know or
understand ODT styles.
Something new to learn now :)
Now I just got to figure out the fonts that Latex is using for my
resume and re-use those same ones
in my style and apply them correctly in the ODT styles.
--
Mehul N. Sanghvi
email: mehul.sanghvi@gmail.com
next prev parent reply other threads:[~2011-10-19 15:16 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 [this message]
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=CAPo9-A9ERmPKMkSRraYo0kYKjJEoyxogggq4LjXh5G6721nrPQ@mail.gmail.com \
--to=mehul.sanghvi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=mail@christianmoe.com \
--cc=moptop99@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).