From: edgar@openmail.cc
To: emacs-orgmode@gnu.org
Subject: Exporting ODT to Org [was Re: General advice beyond Org]
Date: Sun, 20 May 2018 04:56:32 +0000 [thread overview]
Message-ID: <95c864b38f22f6ebd27c75beb4673a40@openmail.cc> (raw)
In-Reply-To: <CAJcAo8u2pkNgO=sgZbg374DxNYsbRFHhy_k71skgRRN8J6gSmA@mail.gmail.com>
On 2018-05-20 01:24, Samuel Wales wrote:
> perhaps we can start thinking about improving registration between
> formats?
I don't really know what this means.
> if you export org [you posted to org mailng list] to a foreign format,
> you want your collaborator to be able to edit, save, send back without
> raising a sweat.
Not really, although it would be nice--and possibly titanic to do.
> now you have to integrate the changes. you want to do this without
> annoyance.
>
> suppose you export comments in the foreign format that contain the
> equivalent of persistent markers. you might or might not be willing
> to put org id or custom id on every heading, but there might be
> workarounds that are not so intrusive. maybe your source can contain
> comments with markers. dunno.
Every great project had to start somewhere (this sounds like that).
However, if I am going to devote time to such a gigantic task, I would
rather spend it trying to convert others to free software rather than
doing favours to a closed format. I am not saying that it wouldn't be
nice to have it.
> if your exported document is a subtree within a huge org file that you
> edit all the time, registration allows your software to identify that
> subtree, so you're not trying to change anything outside that subtree.
> that alone is a win.
This sounds like a project for people in LibreOffice or Pandoc. I think
I will contact them to see if they are interested.
>
> but maybe we can do more. the markers can register sections or even
> paragraphs if you're doing intensive collaboration. the tricky part
> might be getting standard tools to understand that the mapping of
> markers takes precedence over everything else.
Yes, big project.
>
> details of this handwavey and possibly impossible brainstorm are left
> as an exercise for the reader.
LooooL! you remind me of books with notes such as "after deriving the
equation one arrives to the following expression" :P !
Thank you.
-------------------------------------------------
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
next prev parent reply other threads:[~2018-05-20 4:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 0:28 General advice beyond Org edgar
2018-05-18 1:52 ` Peter Neilson
2018-05-18 7:12 ` S. Champailler
2018-05-18 8:10 ` edgar
2018-05-18 11:44 ` Diego Zamboni
2018-05-18 14:21 ` Aaron Ecay
2018-05-18 22:31 ` Stefan Monnier
2018-05-18 10:54 ` Yuri Khan
2018-05-18 11:10 ` S. Champailler
2018-05-18 13:50 ` Kevin Buchs
2018-05-18 13:50 ` hymie!
2018-05-19 7:18 ` Marcin Borkowski
2018-05-18 19:57 ` Adonay Felipe Nogueira
2018-05-19 7:17 ` Marcin Borkowski
2018-05-20 1:24 ` Samuel Wales
2018-05-20 4:56 ` edgar [this message]
2018-06-05 19:52 ` Adonay Felipe Nogueira
2018-06-06 8:58 ` Marco
2018-06-15 16:24 ` Grant Rettke
[not found] <mailman.15.1526832003.3852.help-gnu-emacs@gnu.org>
2018-05-20 19:34 ` Exporting ODT to Org [was Re: General advice beyond Org] edgar
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=95c864b38f22f6ebd27c75beb4673a40@openmail.cc \
--to=edgar@openmail.cc \
--cc=emacs-orgmode@gnu.org \
/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).