[Infrastructure] Experiment: Recompile using entirely Pandoc

Jos Purvis (jopurvis) jopurvis at cisco.com
Mon Apr 15 09:03:11 MST 2019


Sounds good! I merged in the changes from cabforum/master that incorporate everything up to 1.6.4, and then generated new documents from that, which should properly simulate the 1.6.3 to 1.6.4 update. I’ll send those under separate cover.

 

 

-- 
Jos Purvis (jopurvis at cisco.com)
.:|:.:|:. cisco systems  | Cryptographic Services
PGP: 0xFD802FEE07D19105  | +1 919.991.9114 (desk)

 

 

From: "Dimitris Zacharopoulos (HARICA)" <dzacharo at harica.gr>
Date: Friday, 12 April, 2019 at 17:44 
To: "Jos Purvis (jopurvis)" <jopurvis at cisco.com>, "infrastructure at cabforum.org" <infrastructure at cabforum.org>
Subject: Re: [Infrastructure] Experiment: Recompile using entirely Pandoc

 

I mean, try to create a BR.pdf/BR.docx with -say- BR 1.6.3 and another pair of .pdf, .docx for BR 1.6.4. Send me these files and I will try to diff them so we can get a redline pdf and docx from 1.6.3 to 1.6.4.

You can send those privately so we don't fill up the space in the archive of the list.


Dimitris.

On 12/4/2019 11:35 μ.μ., Jos Purvis (jopurvis) wrote:

You mean, do the same edits for a previous version of the BRs? Or just supply the diff version against the current version? If you want the latter, you could diff my copy (https://github.com/castillar/documents/blob/master/docs/BR.md) against the current version of the BRs (https://github.com/cabforum/documents/blob/master/docs/BR.md) and see how that does? 

 

 

-- 
Jos Purvis (jopurvis at cisco.com)
.:|:.:|:. cisco systems  | Cryptographic Services
PGP: 0xFD802FEE07D19105  | +1 919.991.9114 (desk)

 

 

From: "Dimitris Zacharopoulos (HARICA)" <dzacharo at harica.gr>
Date: Tuesday, 9 April, 2019 at 12:07 
To: "Jos Purvis (jopurvis)" <jopurvis at cisco.com>, "infrastructure at cabforum.org" <infrastructure at cabforum.org>
Subject: Re: [Infrastructure] Experiment: Recompile using entirely Pandoc

 

Jos this is great work! I think you just completed a huge milestone!

If you can send me an example of similar outputs from the previous version of the BRs, I can try to create a red-line for both the word and PDF.

Dimitris.

On 9/4/2019 6:01 μ.μ., Jos Purvis (jopurvis) wrote:

Great feedback! I had a little mini-hackathon the last couple nights, and managed to untangle and clean up the formatting in sections like 5.4.1 and the 7.2.x.x.x.x sections and added page numbers to the Word doc. Results are attached. ☺

 

 

-- 
Jos Purvis (jopurvis at cisco.com)
.:|:.:|:. cisco systems  | Cryptographic Services
PGP: 0xFD802FEE07D19105  | +1 919.991.9114 (desk)

 

 

From: "Dimitris Zacharopoulos (HARICA)" <dzacharo at harica.gr>
Date: Monday, 8 April, 2019 at 02:56 
To: "Jos Purvis (jopurvis)" <jopurvis at cisco.com>, "infrastructure at cabforum.org" <infrastructure at cabforum.org>
Subject: Re: [Infrastructure] Experiment: Recompile using entirely Pandoc

 


Thanks Jos, this looks really promising!

I noticed some issues with the numbering of different levels. For example, take a look at section 5.4.1. Page numbers are also missing from the docx version. We're getting close!


Dimitris.

On 7/4/2019 9:32 μ.μ., Jos Purvis (jopurvis) wrote:

It’s astonishing what you can get done when you’re avoiding other work. ☺ For fun[0], I decided to see how much would need to change in the BRs to get Pandoc to produce a PDF from them, since it can happily take the same source document and also produce DOCX, HTML, and even ODT. Turns out, it wasn’t much:
I removed the funky Kramdown table header lines from the list of ballots and the list of effective dates at the top of the document.
I removed some zero-length Unicode space characters that had crept into one of the 7.2.2.X.X.X sections.
That’s it. Really.

 

>From there, I added a metadata file (“BR.yaml”) that contains some document variables like the title and copyright info, and a template LaTeX document with a nice-looking title page, since that’s what Pandoc uses in the background to produce a PDF. Then I converted the old title block for the document to a ‘Verso’ page so there’s still a title at the top of the Markdown file. The result is attached: I think it looks pretty close to what we were looking for, including an automatically-generated table of contents and a nice title page, and we can use the same toolset to generate all of the output artifacts. From there, next steps would be to generate a similarly nice-looking Word doc (Pandoc will take an existing DOCX as a template and use its formatting styles) and CSS for the other two formats.

 

Note that we don’t need to go this route, but it’s cool to note that a little tinkering with the Markdown generated something that will produce all three outputs pretty easily. If you’re curious, I forked the repo and the changes and artifact output are here:

            https://github.com/castillar/documents

 

            --Jos

 

[0] For interesting values of “fun” that include “avoiding house-cleaning”.

 

 

-- 
Jos Purvis (jopurvis at cisco.com)
.:|:.:|:. cisco systems  | Cryptographic Services
PGP: 0xFD802FEE07D19105  | +1 919.991.9114 (desk)

 





_______________________________________________
Infrastructure mailing list
Infrastructure at cabforum.org
http://cabforum.org/mailman/listinfo/infrastructure












-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/infrastructure/attachments/20190415/e8caffeb/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2095 bytes
Desc: not available
URL: <http://cabforum.org/pipermail/infrastructure/attachments/20190415/e8caffeb/attachment-0001.p7s>


More information about the Infrastructure mailing list