[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] [org-e-texinfo] generate menu items

From: Jonathan Leech-Pepin
Subject: Re: [O] [org-e-texinfo] generate menu items
Date: Wed, 21 Nov 2012 11:31:33 -0500

Hello Tom, Nicolas,

I've just pushed a change that should provide the desired results.

The optional title for the menu entries (as well as associated node
headings) can be set using the :TEXINFO_MENU_TITLE: property.

On 18 November 2012 11:22, Thomas S. Dye <address@hidden> wrote:
Nicolas Goaziou <address@hidden> writes:

> address@hidden (Thomas S. Dye) writes:
>> Nicolas Goaziou <address@hidden> writes:
>>> That's a bit of work, because, so far, node-property values are not
>>> parsed. So it would require to define a new class of node-properties:
>>> those with a parsed value. But then, how to decide which properties have
>>> their value parsed are parsed and which have not?
>> Thanks for the information and explanation.  Back-end-specific
>> properties should work nicely in this case.
>> I'll wait to see what Jonathan thinks about the original query.
> one, :EXPORT_TOC_ENTRY: (?), will be the only ones being parsed, I can
> give it a try.

If you do include these node properties I can then adjust the texinfo
exporter to use the generic TOC/Optional title property rather than a
backend specific one.


> I would be consistent with #+caption[short]: long for other elements.
> Regards,

I'm biased by LaTeX, which uses the optional argument for the TOC and
running heads. Since the back-ends are free to use this optional entry
as they please, and not only for the TOC, perhaps :EXPORT_SHORT_ENTRY:
(because that is its usual function), or :EXPORT_OPTIONAL_ENTRY:
(because the back-end has the option to use it where appropriate).

All the best,

Thomas S. Dye

reply via email to

[Prev in Thread] Current Thread [Next in Thread]