emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tony Day <tonyday567@gmail.com>
To: Julian Burgos <julian@hafro.is>
Cc: emacs-orgmode@gnu.org
Subject: Re: collaborating between org-mode and MS Word users
Date: Mon, 31 Dec 2012 11:26:15 +1100	[thread overview]
Message-ID: <m2vcbj12zc.fsf@gmail.com> (raw)
In-Reply-To: <57278.46.239.234.92.1356615218.squirrel@www.hafro.is> (Julian Burgos's message of "Thu, 27 Dec 2012 13:33:38 -0000 (GMT)")


"Julian Burgos" <julian@hafro.is> writes:

> - Is there a better way to have a non-org mode use to edit/correct a
> org-mode document and then bring back the corrections to an org-mode
> document?

If MS Word users can't tolerate plain text org-mode files then I can't
think of many shortcuts. This works well when bringing a docx back into
emacs:

#+begin_src emacs-lisp
 (add-to-list 'auto-mode-alist '("\\.docx\\'" . docx2txt))

(defun docx2txt ()
  "Run docx2txt on the entire buffer."
  (shell-command-on-region (point-min) (point-max) "docx2txt.pl" t t))
#+end_src

> - What is the best way to compare org-mode nodes/branches (like in the
> above example the Version 1 and Version 2 nodes?). Can I use ediff within
> an org-mode file? Or should I keep separate versions on separate
> documents?

ediff-regions-linewise might get the job done.  Within
that process, org-mark-subtree and C-u C-c C-w to quickly jump to the
relevant subtrees are great speed ups.

More generally, re-builder is a godsend for working out the regular back and
forth transformations you'll be doing.

      parent reply	other threads:[~2012-12-31  0:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-27 13:33 collaborating between org-mode and MS Word users Julian Burgos
2012-12-27 15:09 ` Eric Schulte
2012-12-29 18:31 ` Karl Voit
2012-12-31  0:26 ` Tony Day [this message]

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=m2vcbj12zc.fsf@gmail.com \
    --to=tonyday567@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=julian@hafro.is \
    /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).