Hi Dominik, Thanks for your offer. I could indeed surely use some help with document conversion.
Let me tell you what I did so far, and you can decide then. My goal is automatically download and convert the documentation from Google Docs, in a repeatable way. (I don't really want to move away from it as the pristine source--I have an idea for another way to avoid its shortfalls. Even any case, even in the unlikely case this ended up being a final conversion, it would be best automated.) So what I've done is wrote a script against the API to download the various available conversions of it, and then tried various conversions to Markdown using different tools. Some sparse notes here: https://bitbucket.org/blais/beancount/src/5987cd6616df03acba98142c1939ae0ff2842451/experiments/docs/convert/compare_download_formats.txt?at=default&fileviewer=file-view-default A basic download-and-convert script here: https://bitbucket.org/blais/beancount/src/5987cd6616df03acba98142c1939ae0ff2842451/experiments/docs/convert/compare_download_formats.py?at=default&fileviewer=file-view-default In short, the result of this experiment is that it looks like "docx" is the downloadable format which yields the most structured information. However, it is missing some crucial elements, so the final conversion method will have to combine informations extracted from multiple formats and/or conversions. Moreover, I have found it difficult to produce the "code blocks" in a way that preserves indentation. So I was thinking of writing a script that would do three things for each document: - Combine the various elements from the different exported formats - Fixup some of the invalid converted syntax - Automatically recover the code blocks using heuristics to reindent them in order to produce something that would render really nice to Markdown. I should download all the formats and make them available somewhere as I'm not sure if you can run this script on the API. It should be possible - and faster anyway - to write code against all the files exported to the file system. To be fair, I haven't spent a whole lot of time on this yet. Also, I'm a bit of a perfectionist; you could feel free to drive this more scrappy and pragmatically if you like, it might be a better way to get this done. Let me know if you'd like a download of all the static exports. On Mon, Aug 7, 2017 at 1:03 AM, Dominik Aumayr <domi...@aumayr.name> wrote: > > I'd like to automate this conversion and publish a copy of Dominik > Aumayr's static docs with the gdocs embedded in them. > > If you need help with that, or if I should update/modify the static docs > to better suit your needs and the transition, just let me know. Happy to > help! > > - Dominik > > > > Am 07.08.2017 um 05:54 schrieb Martin Blais <bl...@furius.ca>: > > > > On Sun, Aug 6, 2017 at 3:40 PM, Stefano Zacchiroli <z...@upsilon.cc> > wrote: > > On Sun, Aug 06, 2017 at 01:52:31PM -0400, Martin Blais wrote: > > > So for now I've made the docs read-only. > > > If you need to comment, I think there might be a way to request comment > > > access. > > > Otherwise, try the mailing-list... > > > > So, this makes me wonder: given the main argument for having > > documentation on Google Docs was the ease of submitting and receiving > > user contributions, would you be open to reconsider that decision now? > > > > I've been trying to automatically convert the gdocs to a Markdown file, > but so far my efforts have failed to produce something that looks good > enough. I'd like to automate this conversion and publish a copy of Dominik > Aumayr's static docs with the gdocs embedded in them. To be fair I haven't > had much time to fiddle open source lately (new role at work and all my > free time is now going toward that and related reading). > > > > > > -- > > You received this message because you are subscribed to the Google > Groups "Beancount" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to beancount+unsubscr...@googlegroups.com. > > To post to this group, send email to email@example.com. > > To view this discussion on the web visit https://groups.google.com/d/ > msgid/beancount/CAK21%2BhMJxvRS2g%3D5T55s0%2B9H8iz% > 2B5O%2BtEsZADDd3wG1Y1spTxw%40mail.gmail.com. > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Beancount" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beancount+unsubscr...@googlegroups.com. > To post to this group, send email to firstname.lastname@example.org. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/beancount/36421676-D136-4297-9EEC-D79846A49864%40aumayr.name. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to beancount+unsubscr...@googlegroups.com. To post to this group, send email to email@example.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhO9OLefKJQr5vosfatogqdEhpga%2Bm5hxuQUEEYr1UziFw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.