<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Firedrake is a very happy Sphinx user. Of course our primary language is Python. I’m not sure how wonderful sphinx is if your primary language is C (though support is, I believe, claimed).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">petsc-dev <petsc-dev-bounces@mcs.anl.gov> on behalf of Patrick Sanan via petsc-dev <petsc-dev@mcs.anl.gov><br>
<b>Reply-To: </b>Patrick Sanan <patrick.sanan@gmail.com><br>
<b>Date: </b>Wednesday, 12 June 2019 at 10:10<br>
<b>To: </b>"Smith, Barry F." <bsmith@mcs.anl.gov><br>
<b>Cc: </b>petsc-dev <petsc-dev@mcs.anl.gov><br>
<b>Subject: </b>Re: [petsc-dev] User(s) manual sections field in manual pages?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">(and another potential option is to use a tool to convert the current latex source or rendered pdf to HTML)<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">Am Mi., 12. Juni 2019 um 09:40 Uhr schrieb Patrick Sanan <<a href="mailto:patrick.sanan@gmail.com">patrick.sanan@gmail.com</a>>:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal" style="margin-left:36.0pt">I'm interested to hear more about this plan to refactor the user's manual! In particular, is there a concensus on what's a good alternative to LaTeX?
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">I got to chat with one of the developers of deal.ii yesterday, which was cool - this is of course an example of high quality documentation, and uses Doxygen. We've also discussed Sphinx and Madoko in the past.
It's also not out of the question to avoid heavy dependencies and consider something custom, akin to the current HTML generation approach for the man pages and other docs on the website. <o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">Am Sa., 8. Juni 2019 um 09:33 Uhr schrieb Smith, Barry F. <<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>>:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt">
<br>
This was one of my many dreams. The sections in the users manual would have latex names and each man page would link to appropriate ones. Given the hopelessness of linking inside PDF documents on the web (in theory it is possible but no browsers support it)
I gave up on it. You can remove these. With Jed's plans this summer to refactor the users manual to not use latex this all becomes possible but we'll want some automated way of doing this, not requiring listing links on each manual page.<br>
<br>
Barry<br>
<br>
<br>
> On Jun 8, 2019, at 1:09 AM, Mills, Richard Tran via petsc-dev <<a href="mailto:petsc-dev@mcs.anl.gov" target="_blank">petsc-dev@mcs.anl.gov</a>> wrote:<br>
> <br>
> Colleagues,<br>
> <br>
> I have noticed that we have a "Users manual sections" section in the MatNullSpaceCreate() manual page, and an empty "User manual sections" section (which I suppose should be corrected to "Users manual sections", since it is officially the "PETSc Users Manual").
Those appear to be the only two manual pages that use these headings. Would we like to add these for other manual pages, or, since they appear to be unused, should we eliminate them?<br>
> <br>
> --Richard<o:p></o:p></p>
</blockquote>
</div>
</blockquote>
</div>
</div>
</body>
</html>