Hi Jon,
Jonathan Leech-Pepin writes:
> Hello,
>
> On 23 February 2013 18:04, Nicolas Goaziou wrote:
>
>> Hello,
>>
>> [...]
>>
>> I eventually added :OPTIONAL_TITLE: property. Get its parsed value with
>> `org-export-get-optional-title' function.
>>
>> I patched ox-ascii, ox-latex and ox-html s
Hello,
Jonathan Leech-Pepin writes:
> I've replaced the use of :TEXINFO_MENU_TITLE: with :OPTIONAL_TITLE:.
Thank you for looking into it.
Though, please use `org-export-get-optional-title' function instead.
OPTIONAL_TITLE property only contains the raw string. The function will
return the pars
Hello
On 25 February 2013 11:09, Nicolas Goaziou wrote:
> Hello,
>
> Jonathan Leech-Pepin writes:
>
> > I've replaced the use of :TEXINFO_MENU_TITLE: with :OPTIONAL_TITLE:.
>
> Thank you for looking into it.
>
> Though, please use `org-export-get-optional-title' function instead.
> OPTIONAL_TIT
Hello,
On 23 February 2013 18:04, Nicolas Goaziou wrote:
> Hello,
>
> [...]
>
> I eventually added :OPTIONAL_TITLE: property. Get its parsed value with
> `org-export-get-optional-title' function.
>
> I patched ox-ascii, ox-latex and ox-html so they use it when building
> a TOC. I think only ox-o
Hello,
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,
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
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:
>
Nicolas Goaziou writes:
> t...@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
t...@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 va
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Nicolas Goaziou writes:
>>
>>> t...@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
>>>
t...@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou writes:
>
>> t...@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
Nicolas Goaziou writes:
> t...@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 poss
t...@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
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> An Org manual convention uses title case for the main menu and sentence
>> case for chapter heads, e.g., the chapter "Document structure" shows up
>> in the main menu as "Document Structure".
>>
>> I haven't been abl
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> An Org manual convention uses title case for the main menu and sentence
> case for chapter heads, e.g., the chapter "Document structure" shows up
> in the main menu as "Document Structure".
>
> I haven't been able to get the texinfo exporter to do t
Aloha all,
An Org manual convention uses title case for the main menu and sentence
case for chapter heads, e.g., the chapter "Document structure" shows up
in the main menu as "Document Structure".
I haven't been able to get the texinfo exporter to do this.
Perhaps org-e-texinfo--generate-menu-it
16 matches
Mail list logo
