From: Scott Randby <srandby@gmail.com>
To: Grant Rettke <gcr@wisdomandwonder.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: advice please: best way to export to DOC(X) with maths
Date: Mon, 18 Dec 2017 18:45:11 -0500 [thread overview]
Message-ID: <667bfe8e-c2e7-85a0-1194-99c281b182e1@gmail.com> (raw)
In-Reply-To: <CAAjq1mfnd0nj+AR27W-KjyyWPG071g=0BzQa5_FJHE90z5p9og@mail.gmail.com>
On 12/17/2017 10:14 PM, Grant Rettke wrote:
> On Sun, Dec 17, 2017 at 10:55 AM, Scott Randby <srandby@gmail.com> wrote:
>>
>> On 12/15/2017 01:43 PM, Grant Rettke wrote:
>>> Write it in Org. Export to Pandoc file pandoc-A.
>>>
>>> Export Pandoc file pandoc-A to Word file word-A. Send that to your
>>> peers for review.
>>>
>>> Export Word file word-A to Pandoc file pandoc-B.
>>>
>>> Get the Word from your peers, the file with changes from their review,
>>> word-C. Export it to pandoc-C
>>>
>>> Do a diff between pandoc-B and pandoc-C. Integrate the results into
>>> your original Org file.
>>
>> I'm confused. My understanding is that Pandoc converts between file formats, so I don't understand what you mean by a Pandoc file. What is the file format of pandoc-A?
>>
>> Is this what you mean?
>>
>> Pandoc: Org -> word-A
>> Pandoc: word-A -> pandoc-B.org
>> Pandoc: word-C -> pandoc-C.org
>
> Pandoc has their own markup language "Pandoc Markdown". That is what I
> meant by "Pandoc". And that was totally wrong in regards to your
> question. Sorry my mistake.
>
> You said it right, yes. It makes it easy to diff the "reverse
> engineered" Org fils to see what changed from the reviewers.
I appreciate the clarification. Your method is very useful to me since I frequently have to work with people who know nothing but Word and since LibreOffice doesn't deal well with some of the poorly formatted DOCX files I receive. I've been experimenting with some sample files, and your method works great.
I know this is a lost cause, but I dream of the future in which document collaboration is done using only text files.
Scott
>
next prev parent reply other threads:[~2017-12-18 23:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 12:18 advice please: best way to export to DOC(X) with maths Eric S Fraga
2017-12-15 12:58 ` Fabrice Popineau
2017-12-15 13:30 ` Eric S Fraga
2017-12-15 14:54 ` Tim O'Callaghan
2017-12-15 18:15 ` Adonay Felipe Nogueira
2017-12-15 18:43 ` Grant Rettke
2017-12-17 16:55 ` Scott Randby
2017-12-18 3:14 ` Grant Rettke
2017-12-18 23:45 ` Scott Randby [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-15 3:20 edgar
2017-12-15 12:28 ` Eric S Fraga
2017-12-19 5:09 ` edgar
2017-12-21 8:58 ` Tim O'Callaghan
2017-12-26 4:09 ` Adrian Bradd
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=667bfe8e-c2e7-85a0-1194-99c281b182e1@gmail.com \
--to=srandby@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gcr@wisdomandwonder.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).