Jambunathan K kjambunat...@gmail.com writes:
In the pdf version of Emacs info manuals one typically sees all three of
a Section number AND a Description AND a Page number, something like:
See Section 3.1 [Tropical Storms], page 24.
In Org context, I am wondering whether there is such a
Jambunathan K writes:
When we are typesetting a xref in a backend - I can authoritatively
speak for the ODT backend - we need not be resticted to ONE-OF but can
have ANY-COMBINATION-OF descriptors. What I mean is this:
In the pdf version of Emacs info manuals one typically sees all three
Jambunathan K writes:
The following message is a courtesy copy of an article
that has been posted to gmane.emacs.orgmode as well.
Christian Moe m...@christianmoe.com writes:
You can do cross-references with ordinary links. Have a look at the
manual section 4.2, Internal links. However,
I will respond to other items as I visit them. Meanwhile, I would like
to add the following note for discussion.
Christian Moe m...@christianmoe.com writes:
When headings are not numbered in export (#+options: num:nil), current
ODT export outputs a cross-reference with a descriptive text
Christian Moe m...@christianmoe.com writes:
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
Hi, Dan,
Is this the message you get?
No such file: /[path]/OpenDocument export failed: FIXME?
Does the error always occur when you have my filter set, and never when
you don't?
Does it matter whether you're restricting export to subtrees?
After some more testing, I'm seeing the above error
On Thu, Nov 21, 2013 at 11:34:55AM -0500, Dan Griswold wrote:
On Wed, Nov 20, 2013 at 4:33 PM, Christian Moe m...@christianmoe.comwrote:
Well, here's one way to get those page references, using filters:
(defun my-odt-filter-pagerefs (text backend info)
Make page references, not
Well, as you can see with my exchange with Suvayu I got past the error. Yet
I still have a strange problem. Your solution works on a small test file,
but not on my large (~ 13k words) document. The conversion of text to
page just doesn't happen.
I do have a special style file, so I thought that
Dan Griswold writes:
Well, as you can see with my exchange with Suvayu I got past the error. Yet
I still have a strange problem. Your solution works on a small test file,
but not on my large (~ 13k words) document. The conversion of text to
page just doesn't happen.
Odd. The document I
On Thu, Nov 21, 2013 at 11:38 AM, Suvayu Ali fatkasuvayu+li...@gmail.comwrote:
First I would check the Output buffer. That should have more
information on why the export failed.
Thanks Suvayu. There was no Output buffer, only a few error messages in the
*Messages* buffer (and these are of
On Wed, Nov 20, 2013 at 4:33 PM, Christian Moe m...@christianmoe.comwrote:
Well, here's one way to get those page references, using filters:
(defun my-odt-filter-pagerefs (text backend info)
Make page references, not textual references in ODT export.
(when
Hello,
Dan Griswold dgris...@rochester.rr.com writes:
@text:span text:style-name=HighlightThis 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?
Syntax for Org 8.0
Hi,
@text:span text:style-name=HighlightThis 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
Thank you, Nicolas! This is just what I need.
It seems that my installation of org mode (from orgmode.org/elpa) does not
have its info file updated to reflect that change of syntax.
Dan
On Wed, Nov 20, 2013 at 3:24 PM, Nicolas Goaziou n.goaz...@gmail.comwrote:
Hello,
Dan Griswold
Thank you Christian,
This is very helpful.
I'll do some comparing of the standard way of doing links with the
workaround I've stumbled into.
Cheers,
Dan
On Wed, Nov 20, 2013 at 3:34 PM, Christian Moe m...@christianmoe.comwrote:
Hi,
@text:span text:style-name=HighlightThis is a
Dan Griswold dgris...@rochester.rr.com writes:
It seems that my installation of org mode (from orgmode.org/elpa) does not
have its info file updated to reflect that change of syntax.
I updated the manual. Thank you.
Regards,
--
Nicolas Goaziou
I said:
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
Thank you!
On Wed, Nov 20, 2013 at 4:10 PM, Nicolas Goaziou n.goaz...@gmail.comwrote:
Dan Griswold dgris...@rochester.rr.com writes:
It seems that my installation of org mode (from orgmode.org/elpa) does
not
have its info file updated to reflect that change of syntax.
I updated the
18 matches
Mail list logo
