<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
On Thursday March 14th, after the end of the regular CA/B Forum
sessions, we had a short hands-on session in an attempt to improve
the automated output from Markdown to HTML/PDF. It was a very
educative session in which Ryan went over the internals of the build
process.<br>
<br>
The currently produced PDF is fairly good but could use some
improvements as listed below:<br>
<ul>
<li>Cover page<br>
</li>
<li>Table of Contents that might include page numbers. We already
added a ToC but due to the fact that an html version is created
first, it is not very trivial to include page numbers in an html
document<br>
</li>
<li>Section 7.1.2 is using 6 levels down creating a problem that
displays "boxes" around that text. This should probably be
corrected in the BRs.<br>
</li>
<li>Add a .docx extension by creating a symlink or copying the
.html to .docx<br>
</li>
<li>Use monospace for pseudocode (not critical)</li>
</ul>
<p>We also talked about the following:<br>
</p>
<ul>
<li>Release tagging per stable version of the documents. Pull
requests will be maintained but intermediate branches can be
deleted after the pull request is merged to master.<br>
</li>
<li>There is a need for automatically produced HTML diff to create
PDF red-lines</li>
<li>If we allow (in the future) only a diff to be included in a
ballot, the external link that will point to a red-line must be
immutable and must not allow future commits to alter the ballot.</li>
</ul>
<p>I think once we complete these improvements we will be in a much
better position to propose specific change procedures to certain
documents that utilize GitHub as the canonical version.</p>
<p><br>
</p>
<p>Thanks,</p>
<p>Dimitris.<br>
</p>
</body>
</html>