Re: [O] [BUG] Various problems with org-odt export

[Christian Moe]

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