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

[Nicolas Goaziou <n.goaziou@gmail.com>]

tsd@tsdye.com (Thomas S. Dye) writes:

> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> tsd@tsdye.com (Thomas S. Dye) writes:
>>
>>> Agreed.  Perhaps a new property, OPTIONAL_TITLE?  The texinfo back-end
>>> could use this in menus and the latex back-end could pass it to the
>>> sectioning command, e.g., \chapter[optional]{title} (if this isn't
>>> already possible).
>>
>> Back-ends can indeed use specific properties (Beamer back-end does it
>> with "BEAMER_ENV" and so on). Though, I suggest to prefix the property
>> name with the name of the backend: "TEXINFO_OPTIONAL_TITLE" (perhaps
>> a bit verbose).
>>
>> Then, one can access to it from the headline translator with:
>>
>>   (org-element-property :texinfo-optional-title headline)
>>
>> Anyway, Jonathan Leech-Pepin will decide what to do about that.
>
> I looked in org-e-latex.el but didn't find a way to set the optional
> argument to a sectioning command.  Is there currently a way to set this
> argument?

No there isn't.

I had overlooked the fact that you wanted the property to be effective
across back-ends. So, it would define how the entry should appear in the
table of contents in every back-end where it makes sense.

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?


Regards,

-- 
Nicolas Goaziou