Hi Jambunathan,
Jambunathan K writes:
> I am attaching the patch and sample org/odt/doc/html files.
Applied, thanks a lot!
--
Bastien
Hi Nicolas,
Nicolas Goaziou writes:
> Loading org-inlinetask is the user's job. He has to assume weird things
> which will happen when the buffer holds inline tasks without them being
> loaded (but I give him an excuse as inline tasks are completely
> undocumented).
We should fix this -- anyone
> What I think is that, for now, we just should keep the existing facility
> and implement a working default template for HTML (and a new one for
> ODT).
I am attaching the patch and sample org/odt/doc/html files.
I have used the css style suggested by Suvayu Ali for inlinetask (but
with an yell
Jambunathan K writes:
>> As far as I can tell, inline tasks are not designed to be nested.
>
> May be C-c C-x t should throw an error and enforce this.
Done.
> If inlinetasks cannot be nested, may I know how one would use
> org-inlinetask-promote and org-inlinetask-demote.
>
> I understand that
Nicolas
(Sent my mail too early. Resending with additions)
> As far as I can tell, inline tasks are not designed to be nested.
May be C-c C-x t should throw an error and enforce this.
If inlinetasks cannot be nested, may I know how one would use
org-inlinetask-promote and org-inlinetask-demote
Nicolas
> As far as I can tell, inline tasks are not designed to be nested.
May be C-c C-x t should throw an error and enforce this.
If inlinetasks cannot be nested, may I know why one would do a applying
org-inlinetask-promote and org-inlinetask-demote.
Jambunathan K.
Hello,
Jambunathan K writes:
> 1. When org-inlinetask is NOT LOADED, inline tasks are treated as
>regular headlines and are listified. (The "END" of inlinetask appears
>as listified headline though)
Loading org-inlinetask is the user's job. He has to assume weird things
which will happe
Hello Nicolas and Jambu,
On Tue, Aug 9, 2011 at 11:51 PM, Jambunathan K wrote:
>> I see. Contents of inline tasks are meant to be interpreted during
>> export. Thus, paragraphs will be marked as , lists as or
>> whatever...
>>
>> This isn't compatible with the default tag provided. I can see tw
> I see. Contents of inline tasks are meant to be interpreted during
> export. Thus, paragraphs will be marked as , lists as or
> whatever...
>
> This isn't compatible with the default tag provided. I can see two
> possibilities. Come up with a better default value, or provide a way to
> tell to
Hello,
Jambunathan K writes:
> The problem persists. You can put the exported html file in nxml-mode
> and do a C-c C-n to find the validation errors.
The problem is different now.
> I am attaching the two examples and the problematic html segment (marked
> with VALIDATION ERROR) here. Note th
Nicolas Goaziou writes:
> Hello,
>
> Jambunathan K writes:
>
>>> Summary: org-inlinetask produces invalid xhtml
>
> I've pushed a fix. Is it correct now?
The problem persists. You can put the exported html file in nxml-mode
and do a C-c C-n to find the validation errors.
I am attaching the two
Hello,
Jambunathan K writes:
>> Summary: org-inlinetask produces invalid xhtml
I've pushed a fix. Is it correct now?
> Additional Note: I think instead of having templates one could have
> org--format-inlinetask(heading task todo priority whatever)
Not as long as org-inlinetask isn't loaded b
Nicolas,
> Summary: org-inlinetask produces invalid xhtml
>
> The org file and exported html files are included. Org file also
> contains some annotation on the bug.
>
> Food for thought: If inline task entry is seen as a regular "body text"
> even though it is wrapped in to " " element does that
Summary: org-inlinetask produces invalid xhtml
The org file and exported html files are included. Org file also
contains some annotation on the bug.
Food for thought: If inline task entry is seen as a regular "body text"
even though it is wrapped in to " " element does that suggest
a possible wa
14 matches
Mail list logo
