From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Leech-Pepin Subject: Re: [org-e-texinfo] generate menu items Date: Wed, 21 Nov 2012 11:31:33 -0500 Message-ID: References: <87vcd4m5cm.fsf@gmail.com> <87ip94lytq.fsf@gmail.com> <877gpjn9l5.fsf@gmail.com> <87sj87xozu.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=20cf300e4bef34434404cf03e27d Return-path: Received: from eggs.gnu.org ([208.118.235.92]:56664) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TbDDE-00066t-Gq for emacs-orgmode@gnu.org; Wed, 21 Nov 2012 11:31:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TbDD4-0002Vv-PQ for emacs-orgmode@gnu.org; Wed, 21 Nov 2012 11:31:44 -0500 Received: from mail-qa0-f41.google.com ([209.85.216.41]:63508) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TbDD4-0002Vh-Id for emacs-orgmode@gnu.org; Wed, 21 Nov 2012 11:31:34 -0500 Received: by mail-qa0-f41.google.com with SMTP id c26so2052854qad.0 for ; Wed, 21 Nov 2012 08:31:33 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Thomas S. Dye" Cc: Org-mode , Nicolas Goaziou --20cf300e4bef34434404cf03e27d Content-Type: text/plain; charset=UTF-8 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 wrote: > Nicolas Goaziou writes: > > > tsd@tsdye.com (Thomas S. Dye) writes: > > > >> Nicolas Goaziou 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 > > --20cf300e4bef34434404cf03e27d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello Tom, Nicolas,

I've just pushed a change that should provid= e the desired results.

The optional title for the menu entries (as w= ell as associated node
headings) can be set using the :TEXINFO_MENU_TITL= E: property.

On 18 November 2012 11:22, Thomas S. Dye <tsd@t= sdye.com> wrote:
Nicolas Goaziou <n.goaziou@gmail.com> writes:

> tsd@tsdye.com (Thomas S. Dye) wri= tes:
>
>> Nicolas Goaziou <n.goazi= ou@gmail.com> writes:
>
>>> That's a bit of work, because, so far, node-property value= s are not
>>> parsed. So it would require to define a new class of node-prop= erties:
>>> those with a parsed value. But then, how to decide which prope= rties have
>>> their value parsed are parsed and which have not?
>
>> Thanks for the information and explanation. =C2=A0Back-end-specifi= c
>> 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 prop= erties I can then adjust the texinfo
exporter to use the generic TOC/Opt= ional title property rather than a
backend specific one.


Regards,

--
Jon
=C2=A0
> I would be consistent with #+caption[short]: long for other elements.<= br> >
>
> Regards,

I'm biased by LaTeX, which uses the optional argument for t= he 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=


--20cf300e4bef34434404cf03e27d--