emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Mehul Sanghvi <mehul.sanghvi@gmail.com>
Cc: emacs-orgmode@gnu.org, Jambunathan K <kjambunathan@gmail.com>
Subject: Re: org-odt: specifying fonts
Date: Wed, 19 Oct 2011 21:37:51 +0200	[thread overview]
Message-ID: <4E9F270F.5030102@christianmoe.com> (raw)
In-Reply-To: <CAPo9-A8Mht5q23eSihkzWnfKLSX1kLtJvFv5gPoRh_Y40xYezA@mail.gmail.com>

Hi, Mehul,

It's not that I would be opposed to a fonts option, of course, but I 
don't see it as a priority or even necessary. As long as org-odt 
handles the document structure and semantics right, and allows 
attaching an external stylesheet, I think it's done its job.

There are other developments I'm more keen on, like a finalized set of 
documented header options for images (those often need to be set on a 
per-image basis), or the table styles Jambunathan's been experimenting 
with (OpenOffice, eat your heart out!), or simply the definitive 
integration of the odt exporter into core Org.

On 10/18/11 11:15 PM, Mehul Sanghvi wrote:
> 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.

Some would say tinkering with fonts is a distraction from writing that 
having Your Life In Plain Text allows you to get away from. And the 
consistent use of styles and templates is anyway good word-processing 

But sure, this is possible in other backends. For html export (which I 
know better than latex), one can simply include a header like:

   #+STYLE: <style> * { font-family: Gentium; } </style>

to make every element use the Gentium font if available. If I need 
more than 2-3 STYLE headers to get a job done, though, I find it 
easier, simpler and more elegant to link to an external stylesheet.

HTML comes with the breathtaking power and simplicity of CSS styling; 
LaTeX comes with breathtaking power and ... well, at least it's in 
plain text that Org can pass on to the relevant backend. ODT is a 
slightly different story. Its styles are in XML that was not really 
meant to be hand-edited.

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

You'd still need to do the cumbersome work of making sure to change it 
in all possible places, though. Changing the Default paragraph style 
will typically change e.g. the linked Text Body style, too , but not 
the headings (they're linked with Heading). So at a minimum, you'd 
need options to modify both. And once fonts can be specified, users 
will want sizes, weights, colors, borders, etc. Sure, there could be 
an extensive options vocab a la:

   #+ODT_STYLE: "Default" :type para :font "Gentium" :size 12pt
   #+ODT_STYLE: "Heading" :type para :font "Arial" :size 16pt :weight 
bold :color blue :borders ...etc. etc. ...

But is it needed? While Latex, HTML and DocBook users should never be 
required to sully their hands with a GUI, when we use ODT we can 
reasonably be expected to open up an office application now and again 
to modify our templates.

Okay, #+END_RANT...


  parent reply	other threads:[~2011-10-19 19:34 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 [this message]
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=4E9F270F.5030102@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \
    --cc=mehul.sanghvi@gmail.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).