emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [RFC] inline task formatting in odt/doc (was Re: Org-odt fails to export when inline tasks are present)
Date: Tue, 16 Aug 2011 19:09:16 +0200	[thread overview]
Message-ID: <87vctxjnb7.fsf@gnu.org> (raw)
In-Reply-To: <81sjpbhm8o.fsf_-_@gmail.com> (Jambunathan K.'s message of "Mon, 08 Aug 2011 22:30:23 +0530")

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

  parent reply	other threads:[~2011-08-16 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-06 11:41 Org-odt fails to export when inline tasks are present suvayu ali
2011-08-06 15:02 ` Jambunathan K
2011-08-06 17:19   ` Achim Gratz
2011-08-06 20:04   ` suvayu ali
2011-08-08 17:00   ` [RFC] inline task formatting in odt/doc (was Re: Org-odt fails to export when inline tasks are present) Jambunathan K
2011-08-08 18:17     ` suvayu ali
2011-08-16 17:09     ` Bastien [this message]
2011-08-10  9:13   ` Org-odt fails to export when inline tasks are present Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vctxjnb7.fsf@gnu.org \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).