From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: About exporting
Date: Wed, 31 Mar 2021 07:49:33 +1100 [thread overview]
Message-ID: <87wntoibx0.fsf@gmail.com> (raw)
In-Reply-To: <86tuosdfh6.fsf@login.ifi.uio.no>
Martin Steffen <msteffen@ifi.uio.no> writes:
>
> There is one case where I do _NOT_ use org for such documents (though I
> use org basically most things I do), and that is
>
> collaborative editing,
>
> working together on a document (maybe shared by git), at least with a
> document of some amount of complexity and typesetting requirement.
>
Yes, this is still the big unresolved challenge. The sad truth is people
think editing using word and 'track changes' is a good way to do
collaborative documents. I found it was actually pretty bad once you had
more than 2 people working on the document. It really only worked well
if the collaborators worked in serial i.e. one after the other and you
had a single file which just had track changes on it.
My 'solution', which wasn't great, but which I still preferred to
fighting word and track changes, was to send out the document exported
as ascii from org, to each collaborator and told them 'just edit it,
don't worry about formatting, I'll fix that'.
I would then use diff on the returned ascii files to combine them back
into a single ascii file, convert that back to ork and then export the
final form in whatever format was required. This had a couple of
advantages and disadvantages -
Advantages were I had control over the final document. Was actually
useful to release PDFs stamped with 'draft' until agreement was reached
and then issue a single final document. It is amazing how much confusion
can exist in large organisations because multiple versions of some
document are floating around and people lose track of which was the
final version.
Other advantage was I simply didn't have to deal with word. Even doing
all the diff combining (using Emacs of course!) and re-formatting was
faster for me with org than fighting with word and trying to get a good
looking final word document which contains heaps of conflicting styles
etc. (dig into the metadata for a Word document which has been shred and
edited by multiple people and you will know what I mean!).
Disadvantages included some people just not being able to deal with
editing a plain ascii document - just too use to word processing and
found the whole process frustrating. Also, in some situations, people
hated giving up control of the document.
The other somewhat ironic disadvantage was that the organisation was use
to ugly and badly formatted word documents which had a heap of
organisation format 'policy' which you had to comply with (type of font,
font size, margins, line spacing etc. I had to 'uglify' the latex output
in order to make the documents look like other documents produced in the
organisation. This took a bit of effort, but at least once it was done,
I could re-use the setup.
Funny thing was, whenever I produced a document which was just produced
with un-uglified Latex, I would typically get comments about what a nicely formatted
document it was. Nobody ever said that with documents which complied
with the organisation's 'policy'!
--
Tim Cross
next prev parent reply other threads:[~2021-03-30 21:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.51.1617033608.26133.emacs-orgmode@gnu.org>
2021-03-29 19:37 ` About exporting Ypo
2021-03-29 20:15 ` William Denton
2021-03-29 20:46 ` autofrettage
2021-03-29 21:39 ` Samuel Wales
2021-03-29 21:31 ` Juan Manuel Macías
2021-03-29 22:06 ` Tim Cross
2021-03-30 6:17 ` Eric S Fraga
2021-03-30 8:01 ` Colin Baxter
2021-03-30 8:13 ` Detlef Steuer
2021-03-30 10:15 ` Eric S Fraga
2021-03-30 11:40 ` Joost Kremers
2021-03-30 8:17 ` Eric S Fraga
2021-03-30 11:04 ` Juan Manuel Macías
2021-03-29 22:26 ` Thomas S. Dye
2021-03-30 4:47 ` Greg Minshall
2021-03-30 11:54 ` Martin Steffen
2021-03-30 12:44 ` autofrettage
2021-03-30 14:35 ` Martin Steffen
2021-03-30 14:44 ` autofrettage
2021-03-30 15:44 ` Juan Manuel Macías
2021-03-31 9:59 ` Eric S Fraga
2021-03-31 18:28 ` Martin Steffen
2021-04-01 6:52 ` Eric S Fraga
2021-04-01 7:00 ` Tim Cross
2021-04-01 7:29 ` Eric S Fraga
2021-04-01 8:50 ` Timothy
2021-04-01 11:33 ` Eric S Fraga
2021-04-01 13:25 ` Timothy
2021-04-02 14:06 ` Eric S Fraga
2021-04-01 14:21 ` Juan Manuel Macías
2021-03-30 20:49 ` Tim Cross [this message]
2021-03-31 18:56 Juan Manuel Macías
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=87wntoibx0.fsf@gmail.com \
--to=theophilusx@gmail.com \
--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).