From: Christian Moe <mail@christianmoe.com>
To: Dan Griswold <dgriswol@rochester.rr.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: tricky odt export needs
Date: Wed, 20 Nov 2013 21:34:13 +0100 [thread overview]
Message-ID: <m2vbzmsth6.fsf@vpn-client193.uio.no> (raw)
In-Reply-To: <CAGO+QKtxt_PK7L2A6-Dy_tRs8rHWJfMxBV9qedh_JF0oUdiU4Q@mail.gmail.com>
Hi,
> @<text:span text:style-name="Highlight">This is a
> highlighted text@</text:span>. But this is a
> regular text.
>
> doesn't work. That is, the resulting .odt file shows the text above with
> the @ symbols. Am I missing something?
No, the manual is. My bad, sort of; I meant to fix it a week ago but
never got around to it.
With the new exporter, the syntax is:
@@odt:<text:span text:style-name="Highlight">@@This is a highlighted
text@@odt:</text:span>@@. But this is a regular text.
The raw ODT is now wrapped in double @@'s, not preceded by a single @,
and you need to specify the backend after the leading @@'s.
> It would be nice to know how I can get embedded odt tags to work as
> described in the manual. But what's more important, and may make the odt
> tag question moot, is to be able to mark places in the document as labels
> and page references. Even if I could get just the first part of that going
> (marking certain places as labels or cross reference sources) then I'd be
> further along.
You can do cross-references with ordinary links. Have a look at the
manual section 4.2, "Internal links". However, what you get out of the
box is textual references to e.g. section headings, not page
references. You can change that for each reference individually by
right-clicking on them in LibreOffice. There should be a way to get page
references by default, but off the cuff, I'm not sure how.
Yours,
Christian
next prev parent reply other threads:[~2013-11-20 20:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 19:13 tricky odt export needs Dan Griswold
2013-11-20 20:24 ` Nicolas Goaziou
2013-11-20 20:37 ` Dan Griswold
2013-11-20 21:10 ` Nicolas Goaziou
2013-11-20 21:34 ` Dan Griswold
2013-11-20 20:34 ` Christian Moe [this message]
2013-11-20 20:40 ` Dan Griswold
2013-11-20 21:33 ` Christian Moe
2013-11-21 16:34 ` Dan Griswold
2013-11-21 16:38 ` Suvayu Ali
2013-11-21 20:19 ` Dan Griswold
2013-11-21 21:02 ` Christian Moe
2013-11-21 20:52 ` Dan Griswold
2013-11-21 21:16 ` Christian Moe
2013-12-20 6:29 ` Jambunathan K
2013-12-20 9:25 ` Christian Moe
2013-12-21 7:09 ` Jambunathan K
2013-12-22 10:25 ` Christian Moe
2014-02-15 6:24 ` 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:
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=m2vbzmsth6.fsf@vpn-client193.uio.no \
--to=mail@christianmoe.com \
--cc=dgriswol@rochester.rr.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).