Additional Properties for Export

Additional Properties for Export

[Peter Jones]

As you can tell from my recent questions, I've been doing a lot of
exporting from Org lately.  Here are a few things I'd like some
feedback on.

I would like to be able to set a TITLE property for a sub-tree, and
when I export just that sub-tree, the document title will be taken
from that property instead of the file global #+TITLE:.

Right now, when I export a sub-tree, I need to manually change the
#+TITLE: line so that the exported document will have an appropriate
title.

It would also be nice to have an OPTIONS property (or maybe
EXPORT_OPTIONS) where I could override the #+OPTIONS line for each
sub-tree.

Does this seem generally useful?

Here is an example document:

#+TITLE: Client Work

* Client A
** Project Foo Requirements
   :PROPERTIES:
   :ID:       a-foo
   :TITLE:    Foo Application Requirements
   :COLUMNS:  %50ITEM(Task) %5Effort(Effort Estimate){:} %5TODO(State)
   :END:
*** DONE Feature 1
*** TODO Feature 2
** Project Bar Requirements
   :PROPERTIES:
   :ID:       a-bar
   :TITLE:    Bar Application Requirements
   :COLUMNS:  %50ITEM(Task) %5Effort(Effort Estimate){:}
   :END:
*** TODO Feature 1
*** TODO Feature 2

-- 
Peter Jones, pmade inc.
http://pmade.com

Re: Additional Properties for Export

[Carsten Dominik]

Hi Peter, how do you export a single subtree?  If you do it by  
selecting the subtree as the region, then the headling of the subtree  
will become the title for export. - - - Actually, I just tried, and  
that does not work.  Bug is fixed now, in the git-repo.

However, an EXPORT_TITLE property is a good idea, and I have added  
that, too.

The EXPORT_OPTIONS property is a lot harder, can you motivate why and  
how you would want it?

- Carsten

On May 20, 2008, at 12:28 AM, Peter Jones wrote:
> As you can tell from my recent questions, I've been doing a lot of
> exporting from Org lately.  Here are a few things I'd like some
> feedback on.
>
> I would like to be able to set a TITLE property for a sub-tree, and
> when I export just that sub-tree, the document title will be taken
> from that property instead of the file global #+TITLE:.
>
> Right now, when I export a sub-tree, I need to manually change the
> #+TITLE: line so that the exported document will have an appropriate
> title.
>
> It would also be nice to have an OPTIONS property (or maybe
> EXPORT_OPTIONS) where I could override the #+OPTIONS line for each
> sub-tree.
>
> Does this seem generally useful?
>
> Here is an example document:
>
> #+TITLE: Client Work
>
> * Client A
> ** Project Foo Requirements
>   :PROPERTIES:
>   :ID:       a-foo
>   :TITLE:    Foo Application Requirements
>   :COLUMNS:  %50ITEM(Task) %5Effort(Effort Estimate){:} %5TODO(State)
>   :END:
> *** DONE Feature 1
> *** TODO Feature 2
> ** Project Bar Requirements
>   :PROPERTIES:
>   :ID:       a-bar
>   :TITLE:    Bar Application Requirements
>   :COLUMNS:  %50ITEM(Task) %5Effort(Effort Estimate){:}
>   :END:
> *** TODO Feature 1
> *** TODO Feature 2
>
> -- 
> Peter Jones, pmade inc.
> http://pmade.com
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Additional Properties for Export

[Peter Jones]

Carsten Dominik <c.dominik@uva.nl> writes:
> Hi Peter, how do you export a single subtree?  If you do it by
> selecting the subtree as the region, then the headling of the subtree
> will become the title for export. - - - Actually, I just tried, and
> that does not work.  Bug is fixed now, in the git-repo.

I narrow to the subree.  I do wish it were a little easier to export a
subtree, because I have to ensure that nothing is folded after I
narrow to the subtree.

Thanks for adding EXPORT_TITLE.

> The EXPORT_OPTIONS property is a lot harder, can you motivate why and
> how you would want it?

A simple use case is the table of contents.  When exporting the entire
file I want a TOC.  When exporting a subtree, however, I don't.  This
feature isn't as important as the EXPORT_TITLE is.  If you want, I can
see if I can come up with a patch for it.

-- 
Peter Jones, pmade inc.
http://pmade.com

Re: Re: Additional Properties for Export

[Carsten Dominik]

On May 20, 2008, at 9:41 PM, Peter Jones wrote:

> Carsten Dominik <c.dominik@uva.nl> writes:
>> Hi Peter, how do you export a single subtree?  If you do it by
>> selecting the subtree as the region, then the headling of the subtree
>> will become the title for export. - - - Actually, I just tried, and
>> that does not work.  Bug is fixed now, in the git-repo.
>
> I narrow to the subree.  I do wish it were a little easier to export a
> subtree,


C-c @                ; to select the subtree
C-c C-e              ; to export

> because I have to ensure that nothing is folded after I
> narrow to the subtree.
>
> Thanks for adding EXPORT_TITLE.
>
>> The EXPORT_OPTIONS property is a lot harder, can you motivate why and
>> how you would want it?
>
> A simple use case is the table of contents.  When exporting the entire
> file I want a TOC.  When exporting a subtree, however, I don't.  This
> feature isn't as important as the EXPORT_TITLE is.  If you want, I can
> see if I can come up with a patch for it.

The reason why it i non-trivial is because of the way how
the options parsing is implemented.  It does not parse from the string,
but from a buffer.  I'll put it on my ist.

- Carsten

Re: Re: Additional Properties for Export

[Carsten Dominik]

On May 20, 2008, at 9:41 PM, Peter Jones wrote:

> Carsten Dominik <c.dominik@uva.nl> writes:
>> Hi Peter, how do you export a single subtree?  If you do it by
>> selecting the subtree as the region, then the headling of the subtree
>> will become the title for export. - - - Actually, I just tried, and
>> that does not work.  Bug is fixed now, in the git-repo.
>
> I narrow to the subree.  I do wish it were a little easier to export a
> subtree, because I have to ensure that nothing is folded after I
> narrow to the subtree.
>
> Thanks for adding EXPORT_TITLE.
>
>> The EXPORT_OPTIONS property is a lot harder, can you motivate why and
>> how you would want it?
>
> A simple use case is the table of contents.  When exporting the entire
> file I want a TOC.  When exporting a subtree, however, I don't.  This
> feature isn't as important as the EXPORT_TITLE is.  If you want, I can
> see if I can come up with a patch for it.

OK, EXPORT_OPTIONS and EXPORT_TEXT work now as well.  Don't forget that
you can also set EXPORT_FILE_NAME.

- Carsten