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: Fri, 23 Nov 2012 13:44:05 -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; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:53677) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tc2v0-0003MD-QD for emacs-orgmode@gnu.org; Fri, 23 Nov 2012 18:44:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tc2uz-0000mt-D7 for emacs-orgmode@gnu.org; Fri, 23 Nov 2012 18:44:22 -0500 Received: from oproxy6-pub.bluehost.com ([67.222.54.6]:51260) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1Tc2uz-0000h2-4G for emacs-orgmode@gnu.org; Fri, 23 Nov 2012 18:44:21 -0500 In-Reply-To: (Jonathan Leech-Pepin's message of "Wed, 21 Nov 2012 11:31:33 -0500") 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: Jonathan Leech-Pepin Cc: Nicolas Goaziou , Org-mode 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 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 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 >> >> > 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: > >=20=20=20=20=20 > Nicolas Goaziou writes: >=20=20=20=20=20 > > 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. =C2=A0Back-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. > > >=20=20=20=20=20 > > 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 > =C2=A0 > >=20=20=20=20=20 > > I would be consistent with #+caption[short]: long for other > elements. > > > > > > Regards, >=20=20=20=20=20 >=20=20=20=20=20 > 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). >=20=20=20=20=20 >=20=20=20=20=20 > All the best, > Tom >=20=20=20=20=20 > -- >=20=20=20=20=20 >=20=20=20=20=20 > Thomas S. Dye > http://www.tsdye.com >=20=20=20=20=20 >=20=20=20=20=20 > --=20 Thomas S. Dye http://www.tsdye.com