Re: [RFC] inline task formatting in odt/doc (was Re: Org-odt fails to export when inline tasks are present)

[suvayu ali <fatkasuvayu+linux@gmail.com>]

Hi Jambu,

On Mon, Aug 8, 2011 at 7:00 PM, Jambunathan K <kjambunathan@gmail.com> wrote:
>
> Suvayu / Others
>
>> Looks like I need to create an entry in
>>
>> C-h v org-inlinetask-export-templates.
>
> Are there any opinions/preferences on how inline tasks could be exported
> in to odt format. I think having an ability to quickly navigate through
> all the inline tasks in the exported document would be a
> pre-requisite.
>
> I am thinking of exporting them as "Insert->Comments" and from
> OpenOffice help it seems one can quickly visit such comments in order.
>
> I am unsure how big the inline tasks typically are. From the mailing
> lists it seems that the (unarticulated) expectation is that they are
> simple notes (with mostly no body text or very little text)
>

I tried out the comments feature in OOo. I think it serves the purpose
very well. However I have an observation.

For single heading inlinetasks, you correctly say there is little text
and the comment feature works wonderfully. But for inlinetasks with an
END heading, it is common to find an enclosed list or a longer note.
Something like below.

*************** Some note
                + with a few pointers
                + like these
*************** END

Since comments in OOo don't support things like lists, it might be a
good idea to translate the shorter inlinetasks into comments and the
longer ones into highlighted blocks (as in latex export).

Since the format for inlinetask export templates already provides
support to adapt the template based on the content[1], this might be a
feasible feature request. But then again, I am not doing the work. ;)

> Jambunathan K.
>

I hope this helps.

Footnotes:

[1] org-inlinetask-export-templates is a variable defined in
`org-inlinetask.el'.
    ...
    Moreover, the following special keywords are provided: `todo',
    `priority', `heading', `content', `tags'.  If some of them are not
    defined in an inline task, their value is the empty string.


-- 
Suvayu

Open source is the future. It sets us free.