From: Christian Moe <mail@christianmoe.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: Bastien <bzg@altern.org>, emacs-orgmode@gnu.org
Subject: Re: [BUG] Various problems with org-odt export
Date: Mon, 12 Dec 2011 21:54:38 +0100 [thread overview]
Message-ID: <4EE66A0E.9010107@christianmoe.com> (raw)
In-Reply-To: <81aa6xsy1q.fsf@gmail.com>
Hi,
Thanks, the problem was indeed with setup and not with org-odt as
such, so I'm really sorry about the noise. But I'm wondering if
something needs to be done about the Makefile to make sure etc/styles
installs.
Background: I'm in the habit of compiling and installing Org each time
I pull, and as I'm on a Mac, that means changing a couple of
installation paths in the Makefile so as to install into Emacs.app.
All this probably puts me in a small minority of users.
The lisp files got installed all right, including the up-to-date
org-odt.el and org-odt.elc.
And yes, I did for some reason have an older org-odt.el in my loadpath
that was interfering. Very embarrassing. But after I got rid of that,
I was definitely running the new org-odt.
However, things still did not work, and the reason seems to be that
the etc/styles directory did not get installed into the appropriate
etc directory in Emacs.app. Because the directory was missing,
org-odt-styles-dir never got set; it kept throwing an error that it
couldn't find the factory styles.
I copied the etc/styles dir manually over into Emacs.app, and now
everything seems to work.
Could it be that, because there hasn't been anything to install from
the etc directory before, the Org-mode Makefile doesn't take care of
it? The only reference to "etc/" I've found in the Makefile is in
connection with ELPA, which I don't use.
Yours,
Christian
On 12/12/11 2:46 PM, Jambunathan K wrote:
>
> Christian
>
>> Hi,
>>
>> Either something's gone wrong with my setup, or there are a number of
>> issues to straighten out after org-odt moved to core.
>>
>> Here's what I have so far (with Org 7.7 pulled this morning, Emacs
>> 23.3.1, on a Mac). Issues 1 and 3 look urgent.
>>
>> 1. The org-export-odt-styles-file variable
>>
>> still points to
>> "~/src/base/org-mode/contrib/odt/styles.xml"
>> as the default style template. The defcustom comes with a FIXME note,
>> and that has become urgent, as the lack of a default styles file in
>> the default place would cause Org-odt export to fail out of the box
>> for most users. I'm not sure where this should point, but I assume it
>> should not point to anything in contrib any longer.
>
> The default style files have been moved from contrib/odt/styles to
> etc/styles.
>
> Make sure that you are loading the right version of org-odt with M-x
> locate-library.
>
> Also the following variables:
>
> C-h v org-odt-lib-dir => "~/src/org-mode/lisp/"
> C-h v org-odt-styles-dir => "~/src/org-mode/etc/styles/"
>
> The first variable says wherefrom org-odt is loaded.
>
> The second variable -- which was newly introduced a 2-3 days ago --
> should tell where the default style files come from.
>
> If you are unable to find the second variable, then it most postively
> suggests that it is the old org-odt that is loaded.
>
>> 2. The #+ODT_STYLES_FILE directive
>>
>> does not seem to work. It's ignored and the value of
>> org-export-odt-styles-file is used instead.
>
> May be related to (1).
>
> Is everything OK when there is *no* ODT_STYLES_FILE and
> org-export-odt-styles-file is *reset* to nil?
>
>> 3. Current backend not set to 'odt?
>>
>> During ODT export, org-export-format-source-code-or-example
>> fails while trying to load a file called "org-nil". So apparently
>> org-export-current-backend fails to be passed the value 'odt on ODT
>> export.
>>
>> The latter problem could also explain why, trying to export a file
>> with verse environments, I got LaTeX mixed in with the ODT XML...
>
> I hope org-odt loads fine...
> Does M-x load-library RET org-odt RET report any errors?
>
>> Yours,
>> Christian
>>
>>
>>
>
next prev parent reply other threads:[~2011-12-12 20:49 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 17:22 The Org->ODT exporter is now in Org's core (latest git) Bastien
2011-12-11 0:27 ` Herbert Sitz
2011-12-11 12:29 ` Bastien
2011-12-11 16:30 ` Thomas
2011-12-11 16:36 ` Thomas
2011-12-11 17:15 ` Bastien
2011-12-11 17:06 ` Herbert Sitz
2011-12-11 17:13 ` Bastien
2011-12-11 0:52 ` suvayu ali
2011-12-11 2:17 ` Mehul Sanghvi
2011-12-11 8:01 ` Christian Moe
2011-12-11 16:46 ` Manish
2011-12-11 19:37 ` Christian Moe
2011-12-11 19:56 ` Manish
2011-12-11 23:20 ` Bastien
2011-12-12 12:28 ` [BUG] Various problems with org-odt export Christian Moe
2011-12-12 13:46 ` Jambunathan K
2011-12-12 20:54 ` Christian Moe [this message]
2011-12-15 7:48 ` Jambunathan K
2011-12-13 17:37 ` The Org->ODT exporter is now in Org's core (latest git) Eric S Fraga
2011-12-13 19:23 ` Christian Moe
2011-12-14 8:57 ` Eric S Fraga
2011-12-14 11:10 ` Christian Moe
2011-12-14 14:15 ` Nick Dokos
2011-12-14 16:41 ` Eric S Fraga
2011-12-14 18:48 ` Gary Oberbrunner
2011-12-15 7:19 ` Jambunathan K
2011-12-16 12:37 ` Eric S Fraga
2011-12-15 7:01 ` Jambunathan K
2011-12-16 12:42 ` Eric S Fraga
2011-12-14 20:28 ` Dave Marquardt
2011-12-14 21:35 ` suvayu ali
2011-12-14 21:56 ` Alan L Tyree
2011-12-14 23:20 ` suvayu ali
2011-12-15 0:27 ` Alan L Tyree
2011-12-15 7:16 ` Jambunathan K
2011-12-15 7:26 ` Jambunathan K
2011-12-15 8:58 ` Christian Moe
2011-12-15 10:11 ` Alan L Tyree
2011-12-15 11:20 ` suvayu ali
2011-12-15 10:07 ` Alan L Tyree
2011-12-15 13:59 ` Dave Marquardt
2011-12-15 7:24 ` Jambunathan K
2011-12-15 14:03 ` Dave Marquardt
2011-12-15 16:56 ` Dave Marquardt
2011-12-15 17:06 ` suvayu ali
2011-12-15 17:08 ` Dave Marquardt
2011-12-16 9:02 ` Achim Gratz
2011-12-20 23:18 ` Bastien
2011-12-20 23:24 ` Dave Marquardt
2011-12-21 8:50 ` 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=4EE66A0E.9010107@christianmoe.com \
--to=mail@christianmoe.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@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).