Org-odt fails to export when inline tasks are present

Org-odt fails to export when inline tasks are present

[suvayu ali]

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

Hi Jambunathan,

Exporting to org-odt fails if my org file has inline tasks and
org-inlinetask is already loaded. To reproduce the bug with the attached
org file you can do the following:

1. In a minimal org-mode setup (without requiring org-inlinetask),
   export the attached file to odt. It will be done without problems.
2. Now repeat the same thing but after requiring org-inlinetask.

The second fails and gives me the following errors. I shortened some
really long text and errors from the debugger output. I can post the
complete error if you think it would help.

I hope this report helps.

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  format(nil)
  eval((format format-str))
  org-inlinetask-export-handler()
  run-hooks(org-export-preprocess-before-backend-specifics-hook)
  org-export-preprocess-string(..)

  [...]

  org-lparse("odt" "odt" nil nil nil nil nil nil)
  org-export-as-odt(nil)
  call-interactively(org-export-as-odt)
  org-export(nil)
  call-interactively(org-export nil nil)


-- 
Suvayu

Open source is the future. It sets us free.

[-- Attachment #2: odt-export-bug.org --]
[-- Type: text/plain, Size: 581 bytes --]



* B oscillations

B lifetime oscillations is a purely QM effect. It has the functional
form of an exponential decay function modulated by oscillatory phases
due to interference b/w heavy and light states (cos, sin, cosh and
sinh functions related to the mass and decay width differences (Δm and
ΔΓ) b/w the two eigenstates).

_Questions_:
*************** Detector effects 					 :Qn:
1. How is the Gaussian used for smearing of proper
   time resolution derived?
2. Why is the proper time error PDF needed? Why is
   smearing of time resolution not enough?
*************** END

Re: Org-odt fails to export when inline tasks are present

[Jambunathan K]

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]


Hello Suvayu

> Hi Jambunathan,
>
> Exporting to org-odt fails if my org file has inline tasks and
> org-inlinetask is already loaded. To reproduce the bug with the attached
> org file you can do the following:

Looks like I need to create an entry in

C-h v org-inlinetask-export-templates.

Till such time as that happens, the attached patch would strip inline
tasks from odt export. i.e., the exporter will behave as though
org-inlinetask-export is set to nil for the purpose of odt export.

NOTE TO THE MAINTAINERS: git diff is forcibly creating the first hunk in
the attached diff even though I haven't made any modifications as
suggested by it. (I think it is getting confused by the presence of the
"special non-ascii A") 


[-- Attachment #2: 0001-Check-org-inlinetask-export-templates-before-exporti.patch --]
[-- Type: text/x-patch, Size: 1562 bytes --]

From 8bd8dcc2dae59034bfc8e07a4cd43f26941f68a8 Mon Sep 17 00:00:00 2001
From: Jambunathan K <kjambunathan@gmail.com>
Date: Sat, 6 Aug 2011 20:04:35 +0530
Subject: [PATCH] Check org-inlinetask-export-templates before exporting inline tasks

* lisp/org-inlinetask.el (org-inlinetask-export-handler): Don't export
inline tasks if the current backend has provided no entries in
org-inlinetask-export-templates.
---
 lisp/org-inlinetask.el |    8 +++++---
 1 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/lisp/org-inlinetask.el b/lisp/org-inlinetask.el
index 7a52d6b..a990bd3 100644
--- a/lisp/org-inlinetask.el
+++ b/lisp/org-inlinetask.el
@@ -119,9 +119,9 @@ When nil, they will not be exported."
 	   '((unless (eq todo "") (format "%s%s " todo priority))
 	     heading
 	     (unless (eq content "")
-	       (format "\n         ¦ %s"
+	       (format "\n         ¦ %s"
 		       (mapconcat 'identity (org-split-string content "\n")
-				  "\n         ¦ ")))))
+				  "\n         ¦ ")))))
     (docbook "<variablelist>
 <varlistentry>
 <term>%s%s</term>
@@ -333,7 +333,9 @@ Either remove headline and meta data, or do special formatting."
       ;; Remove the task.
       (goto-char beg)
       (delete-region beg end)
-      (when org-inlinetask-export
+      (when (and org-inlinetask-export
+		 (assq org-export-current-backend
+		       org-inlinetask-export-templates))
 	;; Format CONTENT, if appropriate.
 	(setq content
 	      (if (not (and content (string-match "\\S-" content)))
-- 
1.7.2.3


[-- Attachment #3: Type: text/plain, Size: 5 bytes --]


-- 

Re: Org-odt fails to export when inline tasks are present

[Achim Gratz]

Jambunathan K <kjambunathan@gmail.com> writes:
> NOTE TO THE MAINTAINERS: git diff is forcibly creating the first hunk in
> the attached diff even though I haven't made any modifications as
> suggested by it. (I think it is getting confused by the presence of the
> "special non-ascii A") 

There is no such character in the original file, just the "broken pipe"
symbol.  The problem likely is that you are probably reading and
obviously saving that file in a different coding system (should be
utf-8).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html

Re: Org-odt fails to export when inline tasks are present

[suvayu ali]

Hi Jambu,

On Sat, Aug 6, 2011 at 5:02 PM, Jambunathan K <kjambunathan@gmail.com> wrote:
>
> Hello Suvayu
>
>> Hi Jambunathan,
>>
>> Exporting to org-odt fails if my org file has inline tasks and
>> org-inlinetask is already loaded. To reproduce the bug with the attached
>> org file you can do the following:
>
> Looks like I need to create an entry in
>
> C-h v org-inlinetask-export-templates.
>
> Till such time as that happens, the attached patch would strip inline
> tasks from odt export. i.e., the exporter will behave as though
> org-inlinetask-export is set to nil for the purpose of odt export.
>

Yes it works as you describe, thanks. :)

-- 
Suvayu

Open source is the future. It sets us free.

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

[Jambunathan K]

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)

Jambunathan K.

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

[suvayu ali]

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.

Re: Org-odt fails to export when inline tasks are present

[Nicolas Goaziou]

Hello,

Jambunathan K <kjambunathan@gmail.com> writes:

> Till such time as that happens, the attached patch would strip inline
> tasks from odt export. i.e., the exporter will behave as though
> org-inlinetask-export is set to nil for the purpose of odt export.

I have applied the patch, correcting the coding issue.

Regards,

-- 
Nicolas Goaziou

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

[Bastien]

Hi Jambunathan,

Jambunathan K <kjambunathan@gmail.com> writes:

> 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 don't use inline tasks myself, so I don't have a strong opinion about
this.

> I am thinking of exporting them as "Insert->Comments" and from
> OpenOffice help it seems one can quickly visit such comments in
> order. 

These sounds like a reasonable choice, assuming we can find a solution
for the problem Suvayu has been pointing at.  If the solution we try to
implement first is not the best one, we can always improve it afterwards.

Thanks in advance for implementing this!

-- 
 Bastien