I really think this could work.
I've downloaded the JSONs for all the current Beancount docs here:
https://bitbucket.org/blais/beancount-jsondocs/src/default/
There's a little Python script in there you can just run, I hacked on this
for a half hour, just kicking the tires.
If anyone would like to have a go at it, this is a good place to start.
It will run its incomplete parser on all the docs in the current dir.
e.g. run it like this:
./convert_docs_json_to_markdown.py .
I think there's enough information in the JSON files to make a really good
conversion.



On Sun, Feb 17, 2019 at 4:04 PM Martin Blais <[email protected]> wrote:

> I just tried it, this API provides enough detail to do a much better job
> at converting to Markdown.
> I could easily and reliably identify code blocks with it.
>
>
> On Sun, Feb 17, 2019 at 3:51 PM Martin Blais <[email protected]> wrote:
>
>> That looks nice and promising indeed, you get access to their structure
>> of the document:
>> https://developers.google.com/docs/api/concepts/structure
>> Thanks for sending a pointer to this. I hadn't noticed this release.
>>
>> I haven't done any work with this yet.
>> It looks like it could potentially work.
>>
>>
>>
>>
>>
>> On Fri, Feb 15, 2019 at 2:03 PM <[email protected]> wrote:
>>
>>> Google recently released the API for Docs [1]. This should make the
>>> export process easier. Has anyone looked at it? Is anyone working on this?
>>>
>>> [1]
>>> https://developers.google.com/docs/api/reference/rest/v1/documents#Document
>>>
>>> On Wednesday, November 28, 2018 at 8:00:24 PM UTC-8, Martin Blais wrote:
>>>>
>>>> On Tue, Nov 27, 2018 at 10:24 PM Oon-Ee Ng <[email protected]> wrote:
>>>>
>>>>> On Thu, May 10, 2018 at 11:29 AM Martin Blais <[email protected]> wrote:
>>>>>
>>>>>> On Wed, May 9, 2018 at 8:29 AM, Martin Michlmayr <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>> * Martin Blais <[email protected]> [2018-03-24 00:35]:
>>>>>>> > BTW, here's what the current automated conversion results looks
>>>>>>> like in
>>>>>>> > your static skeleton:
>>>>>>> > http://furius.ca/tmp/beancount-docs/
>>>>>>>
>>>>>>> http://furius.ca/tmp/beancount-docs/users/installation.html has some
>>>>>>> formatting issues.  It seems ReST links are created for links in
>>>>>>> verbatim elements, see e.g. section "Where to Get It"
>>>>>>>
>>>>>>> What's needed to make these docs official?
>>>>>>>
>>>>>>
>>>>>> There are number of quirks like that.
>>>>>> Finding a way - even a kludgey solution - to fixup all those quirks
>>>>>> automatically is what I'm looking for.
>>>>>> Your contribution in that department would be highly appreciated.
>>>>>> I would suggest first making sure you can run the whole conversion
>>>>>> process yourself, and then if  you want, add some Python to address the
>>>>>> quirks one by one, patches welcome.
>>>>>> The source code is here:
>>>>>> https://bitbucket.org/blais/beancount/src/tip/experiments/docs_rst/
>>>>>>
>>>>>> Please ignore the docs-related scrips under tools/, I need to remove
>>>>>> them.
>>>>>>
>>>>>
>>>>> Can I assume this is on-hold/pause currently?
>>>>>
>>>>
>>>> I haven't worked on it.
>>>> Too busy.
>>>>
>>>>
>>>> I'm finally getting round to implementing some imports after using
>>>>> beancount for more than a year, and I think the 'Importing External Data'
>>>>> section could use some sprucing up, wondering how I would suggest changes
>>>>> now that the Google Doc suggest edits route is no longer open.
>>>>>
>>>>
>>>> I opened up for comments for you. If you need comment access on any
>>>> other doc, let me know.
>>>> Thank you,
>>>>
>>>>
>>>>
>>>> --
>>>>> 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 [email protected].
>>>>> To post to this group, send email to [email protected].
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/beancount/CAGQ70et9_UsxVWo2N%2B%3DWK-r3x9dC00-SUnEt_wbtmNqG-1Nftw%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/beancount/CAGQ70et9_UsxVWo2N%2B%3DWK-r3x9dC00-SUnEt_wbtmNqG-1Nftw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> 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 [email protected].
>>> To post to this group, send email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beancount/0df8f70c-45e3-4c70-8bea-dec310694b85%40googlegroups.com
>>> <https://groups.google.com/d/msgid/beancount/0df8f70c-45e3-4c70-8bea-dec310694b85%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> 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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/CAK21%2BhMvy%2Bs0a-PpoW75hP-Wnt6gMk4q9QA%3DoAQY68MVczyj%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to