From mboxrd@z Thu Jan 1 00:00:00 1970 From: tsd@tsdye.com (Thomas S. Dye) Subject: Re: [org-e-texinfo] generate menu items Date: Sun, 18 Nov 2012 06:22:11 -1000 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: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:47949) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ta7dn-0000RE-Je for emacs-orgmode@gnu.org; Sun, 18 Nov 2012 11:22:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ta7dk-0000Z5-Gk for emacs-orgmode@gnu.org; Sun, 18 Nov 2012 11:22:39 -0500 Received: from oproxy9.bluehost.com ([69.89.24.6]:35201) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1Ta7dk-0000Yl-79 for emacs-orgmode@gnu.org; Sun, 18 Nov 2012 11:22:36 -0500 In-Reply-To: <87sj87xozu.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 18 Nov 2012 10:02:45 +0100") 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: Nicolas Goaziou Cc: Org-mode 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. > > 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