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

[tsd@tsdye.com (Thomas S. Dye)]

Aloha Jon,

Thanks very much for these changes, which appear to work nicely with the
draft Org manual.

What do you think about the various macro commands defined in org.texi?
How to put them in the Org file and then get them into the texinfo
output? The org.texi file has them between @finalout and @copying. I
don't know if they have to be there, but I assume they were put there
for a reason.

All the best,
Tom

Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:

> 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 <tsd@tsdye.com> wrote:
>
>> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>>
>> > tsd@tsdye.com (Thomas S. Dye) writes:
>> >
>> >> Nicolas Goaziou <n.goaziou@gmail.com> 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.
>> >
>> > Assuming :EXPORT_TITLE:, :EXPORT_AUTHOR:, :EXPORT_DATE: and this
>> > 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.
>
>
> Regards,
>
> --
> Jon
>
>
>> > 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,
>> Tom
>>
>> --
>> Thomas S. Dye
>> http://www.tsdye.com
>>
>>
> 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 <tsd@tsdye.com> wrote:
>
>     
>     Nicolas Goaziou <n.goaziou@gmail.com> writes:
>     
>     > tsd@tsdye.com (Thomas S. Dye) writes:
>     >
>     >> Nicolas Goaziou <n.goaziou@gmail.com> 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.
>     >
>     > Assuming :EXPORT_TITLE:, :EXPORT_AUTHOR:, :EXPORT_DATE: and this
>     > 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.
>
>
> Regards,
>
> --
> Jon
>  
>
>     
>     > 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,
>     Tom
>     
>     --
>     
>     
>     Thomas S. Dye
>     http://www.tsdye.com
>     
>     
>

-- 
Thomas S. Dye
http://www.tsdye.com