From: mb21 <mauro.bieg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Google Docs workflow via pandoc?
Date: Sun, 11 Jan 2015 07:18:21 -0800 (PST) [thread overview]
Message-ID: <24d0ebc4-2e52-4883-8420-13dc0da9aa29@googlegroups.com> (raw)
In-Reply-To: <0f7ab0a4-9b9e-4406-a46b-d9d206ff72d7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1945 bytes --]
I've used https://stackedit.io and liked it a lot. To enable collaboration:
in the left sidebar: "Google Drive" -> "Export" -> "Options..." -> tick
"Create a real time collaborative document". Then in Google Drive, invite
your collaborators.
On Friday, January 9, 2015 at 4:47:45 AM UTC+1, Benjamin Slade wrote:
>
> I was curious if anyone has come up with a workflow for working with
> Google Docs in another editor (say, Emacs). I played around a bit with:
> with google-cl one can get or edit Google Docs documents in various
> formats, docx, odt, rtf, html, txt. Txt format would obviously be easiest,
> but it strips out all formatting from the original document (and so is
> destructive). The markup of Google Docs' rtf and html formats are really
> unreadable, so unfortunately one can't work with them directly in Emacs in
> any reasonable way. I was wondering if anyone had developed a workflow for
> downloading Google Docs docs in some format, converting them via pandoc to
> some text-editor-manageable format, and then reconvert them back to the
> original format. And, if so, how well this works.
>
> The reason I'm curious about this is that Google Docs is very convenient
> for collaboration, especially with people of varying levels of technical
> expertise, but it would be great if I wasn't stuck working in a
> word-processor.
>
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/24d0ebc4-2e52-4883-8420-13dc0da9aa29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2561 bytes --]
prev parent reply other threads:[~2015-01-11 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 3:47 Benjamin Slade
[not found] ` <0f7ab0a4-9b9e-4406-a46b-d9d206ff72d7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-11 15:18 ` mb21 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24d0ebc4-2e52-4883-8420-13dc0da9aa29@googlegroups.com \
--to=mauro.bieg-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).