emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Vinh Nguyen <vinhdizzo@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-odt (Applying custom templates)
Date: Thu, 24 Mar 2011 00:43:11 +0530	[thread overview]
Message-ID: <81k4fpejlk.fsf@gmail.com> (raw)
In-Reply-To: <81fwqevzgz.fsf_-_@gmail.com> (Jambunathan K.'s message of "Wed, 23 Mar 2011 17:08:20 +0530")


>> In addition, is there a way to set up a header, or some text, before
>> the title, similar to the attached file (including the image)?  I
>> don't mind if the solution is pasting some raw xml code in the
>> org-mode file, as this part will remain constant.
> What is required is that you extract styles.xml and any images files
>  that it referenced from your odt/ott file and instruct org-odt.el to
>  package these files in the resulting directory. You can do these
>  manually.
> I also have a prototype code (that is not committed yet) that achieves
> the above functionality. 

I pushed a fix to my staging branch.

If you set the variable as below

(setq org-export-odt-styles-file
      '("~/tmp-orgmode/Thu Thong Bao - Trai Ve Nguon XV (2011).odt"
	("styles.xml" "Pictures/10000000000002740000034B83A526F3.png")))

the styles.xml and header images would get copied on to the generated
odt file. 

If the desired styles.xml makes no references to other files (as in the
example above) then the above variable could be set to 

(setq org-export-odt-styles-file
      "~/tmp-orgmode/Thu Thong Bao - Trai Ve Nguon XV (2011).odt")


(setq org-export-odt-styles-file "~/elisp/styles.xml")

In both the case org-odt's native styles file will be replaced by the
one that is specified (implicity or explicitly)

> See the attached output file and you could see that the headers are
> getting repeated on all pages.
> On customization side of things, I am little bit uncertain what would be
> the best way to apply custom styles while also having the user feel
> happy about the document that comes out as a result. (When I apply your
> styles.xml to override my Org's very own styles file, the resulting
> output file is not pleasing to the eye (for example, Headings are
> unstylized) This is because your styles.xml doesn't specify styles for
> 'Heading 2' while for some strange reason - partly because of it's
> ancestry org-odt.el - is emitting Headings from level 2 onwards)
> I am open to hearing what orgers think on this front. I would go very
> slow on the customization side of things unless some consensus or clariy
> emerges.

Jambunathan K.

  reply	other threads:[~2011-03-23 19:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTikW7RiwS79utq2E4hquOLf1+BwfBWG-f_iK85JR@mail.gmail.com>
     [not found] ` <81pqqxyrq5.fsf@gmail.com>
     [not found]   ` <AANLkTik5UzLb-+krHo8dd7j9vux7HmoXP4oL8+QvgCeU@mail.gmail.com>
     [not found]     ` <81ei7cjpuy.fsf@gmail.com>
     [not found]       ` <AANLkTi=u-7mwRYN4CaNk74W0L2HtieSrB++iqnFAy+wn@mail.gmail.com>
     [not found]         ` <AANLkTinXCvCcfT1guBtf=-dcqQrqvX2GOwc_7SapZeCD@mail.gmail.com>
2011-03-23 11:38           ` Jambunathan K
2011-03-23 19:13             ` Jambunathan K [this message]
2011-06-28 19:48             ` Vinh Nguyen
2011-07-09  3:52               ` Jambunathan K

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=81k4fpejlk.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=vinhdizzo@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).