[08:43] <dholbach> davidcalle, https://github.com/thejimbirch/GoogleDoc2Html/ looks nice
[08:43] <davidcalle> dholbach: is the result ok?
[08:44] <dholbach> still looking at it :)
[08:46] <dholbach> not 100%, no
[08:48] <dholbach> davidcalle, https://developer.ubuntu.com/en/snappy/guides/security-whitepaper/
[08:48] <dholbach> (not published)
[08:48] <dholbach> it doesn't get the footnotes, nor the code blocks
[08:49] <dholbach> maybe another option would be to ask Jamie and Tyler if they could imagine editing this in a separate repo somewhere and we can stay with .md? :-)
[08:53] <davidcalle> dholbach: I'm wondering if there is an online repo somewhere that deals with md footnotes
[08:54] <dholbach> can you explain?
[08:57] <dholbach> davidcalle, ^
[09:00] <davidcalle> eg. https://stackedit.io/editor supports footnotes, maye we could host it there. It seems to generate clean html.
[09:00] <davidcalle> This would allow us to stay with a clean md, a clean html, and a convenient editor for the sec team
[09:01] <davidcalle> GitHub works as well, but footnotes will look weird :)
[09:04] <dholbach> that looks very nice
[09:04] <dholbach> I'm just not sure what the workflow should look like...
[09:06] <davidcalle> I know :)
[09:07] <dholbach> to me it seems to be right now: 1) the guys edit it in gdoc and we live with very suboptimal html, or try to optimise it somehow or 2) we set up another repo, leave the markdown in there and import it
[09:07] <dholbach> that's at least two workflows I can easily understand :)
[09:09] <davidcalle> dholbach: I'm all for 2), but the downside is that they won't have a proper view of a document using footnotes.
[09:11] <davidcalle> Therefore, the way I see it, let's have a good way to clean 1). It will also be useful for the SDK team, as they are publishing things raw from gdoc and I have to clean it up when it's posted.
[09:13] <dholbach> ok
[13:11] <davidcalle> dholbach: I'm on what I think is a good solution for ^, can I send you a prototype later today?
[13:11] <dholbach> yes, please
[13:11] <dholbach> I started looking into it myself
[13:11] <dholbach> but I'm sure I didn't get as far as you did :-P
[13:13] <davidcalle> dholbach: I have a tool that downloads the doc in html and pdf, with html images still hosted on gdrive, and a parser that does a bit of cleaning.
[13:13] <dholbach> wow
[13:57] <dholbach> davidcalle, can we land https://code.launchpad.net/~dholbach/developer-ubuntu-com/fix-consistency-command/+merge/295718 later on today maybe? :)
[13:59] <dholbach> I can check my backlog to see if I can still do it... if you want
[14:00] <davidcalle> Oh, thanks, I was going to talk to you about this just after what I'm doing, so +1
[14:01] <davidcalle> I'll do it asap
[14:02] <dholbach> maybe you can share your bash history with me again? :)
[14:04] <davidcalle> dholbach: too late, deploying :)
[14:04] <dholbach> no worries
[14:04] <dholbach> shall I land it in trunk?
[14:04] <davidcalle> dholbach: let's test it on the staging db, because I had the exact same traceback this morning, without this fix
[14:04] <dholbach> ok
[14:05] <davidcalle> dholbach: gdoc cleaner: the only issue I have is that code blocks are not handled (because gdoc doesn't actually use the code format, or at least it wasn't used in this doc).
[14:11] <dholbach> that's absolutely acceptable :)
[15:15] <davidcalle> dholbach: check your email, you have the cleaner prototype
[15:15] <dholbach> yep, saw the mail
[15:16] <dholbach> thanks a lot
[15:16] <davidcalle> np :) You'll still need to extract and only paste what's inside the body tag but, 99% of the cruft is out.
[15:18] <dholbach> davidcalle, is that in clean.html?
[15:18] <davidcalle> dholbach: glad it worked :D yes
[15:18] <dholbach> there's a lot of <span> items still
[15:19] <dholbach> is that expected?
[15:20] <davidcalle> dholbach: part of the 1% remaining cruft, but it shouldn't be an issue, the CMS will clean empty ones
[15:20] <dholbach> ok
[15:20] <dholbach> fair enough
[15:23] <dholbach> davidcalle, https://developer.ubuntu.com/en/snappy/guides/security-whitepaper/ - qu'est-ce que tu pense?
[15:24] <dholbach> je l'aime beaucoup
[15:24] <dholbach> maybe just add the .pdf at the top (Read this in .pdf format.) or something?
[15:25] <davidcalle> dholbach: :) Maybe let's get rid of the TOC for now, it doesn't look great without indentation. And needs some code blocks. I can do it in a moment if you need to run :) The rest wfm :)
[15:26] <dholbach>  I'll remove it from the page
[15:29] <dholbach> davidcalle, can I attach files to pages in the cms or will the world explode?
[15:33] <davidcalle> dholbach: never tried to attach files (other than images), maybe we should host it on a people.ubuntu.com or a people.canonical.com thing
[15:33] <dholbach> sure
[15:36] <davidcalle> (but as I said, I don't mind doing it later today)
[15:37] <dholbach> davidcalle, https://developer.ubuntu.com/en/snappy/guides/security-whitepaper/ - looks ok to you?
[15:43] <davidcalle> At least three code blocks missing, but don't worry, you can tell Jamie it will be cleaned up by tomorrow if you want.
[15:43] <dholbach> ok cool
[15:43] <dholbach> will do