emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Philip Hudson <phil.hudson@iname.com>
To: emacs orgmode-mailinglist <emacs-orgmode@gnu.org>
Subject: ODT export
Date: Sat, 8 Oct 2016 09:10:02 +0100	[thread overview]
Message-ID: <CAJ1MqVF6TLXxBAez+oe80tLFiSfLVOq66ch4vWZr7837r-racQ@mail.gmail.com> (raw)

First time out, very disappointing and confusing results.

Having created a styled example.odt file as per instructions in the manual...

(info "(org) Applying custom styles")

(BTW, the string "Stylist" does not appear anywhere in LibreOffice's
UI; there's more than enough difficulty here without adding impossible
instructions!)

Having torn my hair out en route to discovering that enclosing
double-quotes are mandatory for the #+ODT_STYLES_FILE...

Having finally got an apparently successful run of the exporter using
the styles file...

LaTeX to MathML converter not available.
Formatting LaTeX using verbatim
Wrote /home/phil/tmp/odt-22378aSo/meta.xml
Using schema /usr/share/emacs/etc/org/schema/od-schema-v1.2-os.rnc [2 times]
Saving file /home/phil/tmp/odt-22378aSo/styles.xml...
Wrote /home/phil/tmp/odt-22378aSo/styles.xml
Using vacuous schema
Wrote /home/phil/tmp/odt-22378aSo/mimetype
Using vacuous schema
Saving file /home/phil/tmp/odt-22378aSo/META-INF/manifest.xml...
Wrote /home/phil/tmp/odt-22378aSo/META-INF/manifest.xml
Saving file /home/phil/tmp/odt-22378aSo/content.xml...
Wrote /home/phil/tmp/odt-22378aSo/content.xml
(No changes need to be saved)
Creating ODT file...
Running zip -mX0 Invoice28.odt mimetype
Running zip -rmTq Invoice28.odt .
Created /home/phil/org/Customers/Invoice28.odt
Searching for `odt-22'....

I then open the resulting ODT file and find that a) my customization
of the "title" style does not appear and b) my top-level headline
appears as "Default Style" (in other words, not marked up at all), not
"Heading 1" as expected.

The temp directory ~/tmp/odt-xxxxx is apparently deleted on exit so I
can't examine the various intermediate XML files generated by export.

Help and advice please.


-- 
Phil Hudson                   http://hudson-it.ddns.net
@UWascalWabbit                 PGP/GnuPG ID: 0x887DCA63

             reply	other threads:[~2016-10-08  8:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-08  8:10 Philip Hudson [this message]
2016-10-09  9:33 ` ODT export Philip Hudson
2016-10-11 16:58   ` Eduardo Mercovich
2016-10-12  8:59     ` Christian Moe
     [not found]     ` <f3d70ad741fd459ca272f553e551464a@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-13  7:40       ` Eric S Fraga
2017-07-03  4:02 ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2013-08-12  0:24 Vikas Rawal
2013-08-12  2:59 ` Yagnesh Raghava Yakkala
2013-08-12 13:57   ` Vikas Rawal
2013-08-12 14:31   ` Vikas Rawal

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=CAJ1MqVF6TLXxBAez+oe80tLFiSfLVOq66ch4vWZr7837r-racQ@mail.gmail.com \
    --to=phil.hudson@iname.com \
    --cc=emacs-orgmode@gnu.org \
    /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).