<html xmlns:v="urn:schemas-microsoft-com:vml" 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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Consolas;
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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=en-DE link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-family:Consolas;mso-fareast-language:EN-US'>Hi Bill,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:Consolas;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:Consolas;mso-fareast-language:EN-US'>That would call for something like Pygments. Especially, if we already require a Python installation, Pygments can be a powerful replacement for listings.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:Consolas;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:Consolas;mso-fareast-language:EN-US'>Kind regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:Consolas;mso-fareast-language:EN-US'> -michael<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:Consolas;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> mpi-forum <mpi-forum-bounces@lists.mpi-forum.org> <b>On Behalf Of </b>William Gropp via mpi-forum<br><b>Sent:</b> Montag, 6. September 2021 16:51<br><b>To:</b> Main MPI Forum mailing list <mpi-forum@lists.mpi-forum.org><br><b>Cc:</b> William Gropp <wgropp@illinois.edu><br><b>Subject:</b> Re: [Mpi-forum] Questions on MPI Standard formatting<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On the MPI_Waitsome/MPI_Wait - this is a bug in the lstlisting package. We had lots of trouble with this in the Using MPI books when we switched, but were usually able to get it to work through various hacks. Long term, it might be better to move the highlighting out of LaTeX and process it as part of the “render” step.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Bill<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal><span style='color:black'>William Gropp<br>Director, NCSA<br>Thomas M. Siebel Chair in Computer Science<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>University of Illinois Urbana-Champaign<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>IEEE-CS President-Elect<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p></div><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On Sep 5, 2021, at 3:23 AM, Martin Schulz via mpi-forum <<a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal><span lang=EN-US>Hi Bill, all,</span><o:p></o:p></p></div><div><p class=MsoNormal><span lang=EN-US> </span><o:p></o:p></p></div><div><p class=MsoNormal><span lang=EN-US>I also agree with what has been said so far and I also agree with the statement that if we don’t find a good solution for tables, leaving it off there is not a big problem (lines should be easily identified there.</span><o:p></o:p></p></div><div><p class=MsoNormal><span lang=EN-US> </span><o:p></o:p></p></div><div><p class=MsoNormal><span lang=EN-US>As for the syntax highlighting – I personally don’t mind it sticking out, but I can also see Joseph’s point – perhaps something between the two version would work.</span><o:p></o:p></p></div><div><p class=MsoNormal><span lang=EN-US> </span><o:p></o:p></p></div><div><p class=MsoNormal><span lang=EN-US>One question, though: in the example that goes over two pages, the “MPI_Waitsome” call is only bold for “MPI_Wait” and not bold for “some” – is this an annotation bug or a problem with the package of not detecting prefixes correctly?</span><o:p></o:p></p></div><div><p class=MsoNormal><span lang=EN-US> </span><o:p></o:p></p></div><div><p class=MsoNormal><span lang=EN-US>Thanks!</span><o:p></o:p></p></div><div><p class=MsoNormal><span lang=EN-US> </span><o:p></o:p></p></div><div><p class=MsoNormal><span lang=EN-US>Martin</span><o:p></o:p></p></div><div><p class=MsoNormal><span lang=EN-US> </span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><div><p class=MsoNormal><span lang=EN-US>-- </span><span lang=EN-US style='font-size:10.5pt;font-family:"Helvetica",sans-serif'><br>Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems<br>Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching<br>Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ)<br>Email:<span class=apple-converted-space> </span><a href="mailto:schulzm@in.tum.de">schulzm@in.tum.de</a></span><o:p></o:p></p></div><div><div><p class=MsoNormal><span lang=EN-US> </span><o:p></o:p></p></div></div></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><div><p class=MsoNormal><b><span style='font-size:12.0pt'>From:<span class=apple-converted-space> </span></span></b><span style='font-size:12.0pt'>mpi-forum <<a href="mailto:mpi-forum-bounces@lists.mpi-forum.org">mpi-forum-bounces@lists.mpi-forum.org</a>> on behalf of "Jeff Squyres (jsquyres) via mpi-forum" <<a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a>><br><b>Reply-To:<span class=apple-converted-space> </span></b>Main MPI Forum mailing list <<a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a>><br><b>Date:<span class=apple-converted-space> </span></b>Saturday, 4. September 2021 at 19:33<br><b>To:<span class=apple-converted-space> </span></b>MPI Forum list <<a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a>><br><b>Cc:<span class=apple-converted-space> </span></b>"Jeff Squyres (jsquyres)" <<a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a>><br><b>Subject:<span class=apple-converted-space> </span></b>Re: [Mpi-forum] Questions on MPI Standard formatting</span><o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><p class=MsoNormal>I am in agreement with all that has been said so far -- generally, this is great. Minor tweaks (already cited by George and Joseph) would be nice improvements.<span class=apple-converted-space> </span><o:p></o:p></p></div><div><div><p class=MsoNormal> <o:p></o:p></p></div><div><div><p class=MsoNormal><br><br><br><o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal>On Sep 3, 2021, at 5:46 PM, Gropp, William D via mpi-forum <<a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a>> wrote:<o:p></o:p></p></div></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><div><div><div><p class=MsoNormal>One option is to use a different font; the one I used in the first examples has a strong bold. Here’s the same page with a different font with a less bold look. In some ways, this may go too far in the other direction - the bold text is a little heavier, but the difference is slight.<span class=apple-converted-space> </span><o:p></o:p></p></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal>One advantage of this choice is that the code text is not quite as wide as with the font choice for the previous example, which works better with the current code examples.<o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal>Let me know your preference. It is easy to change, modulo the issue of needing to wrap a few lines of code.<o:p></o:p></p></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal>Bill<o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div></div></div><div><div><div><div><p class=MsoNormal> <o:p></o:p></p></div><div><div><div><div><p class=MsoNormal>William Gropp<br>Director, NCSA<br>Thomas M. Siebel Chair in Computer Science<o:p></o:p></p></div></div><div><div><p class=MsoNormal>University of Illinois Urbana-Champaign<o:p></o:p></p></div></div><div><div><p class=MsoNormal>IEEE-CS President-Elect<o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div></div><p class=MsoNormal style='margin-bottom:12.0pt'> <o:p></o:p></p></div><div><div><p class=MsoNormal><br><br><br><o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal>On Sep 3, 2021, at 1:40 PM, Joseph Schuchart via mpi-forum <<a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a>> wrote:<o:p></o:p></p></div></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><div><div><p class=MsoNormal>I am OK with leaving out line numbers in tables. Maybe that will be solved in the future.<br><br>One comment I had was on the code formatting. While I definitely prefer the lstlistings formatting over the verbatim we have so far, I find the bold highlighting somewhat distracting. I find it hard to focus on the surrounding code pieces. Would it be possible to tone down the highlighting somewhat (slightly thinner, maybe grey)?<br><br>Thanks<br>Joseph<br><br>On 9/3/21 2:36 PM, William Gropp via mpi-forum wrote:<br><br><br><o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>Thanks, George. On the line numbering, unfortunately, this is very difficult to fix (and is a known problem). My proposal instead is to not use the line numbers in these cases; in the rare cases where we need to identify the location, we can count rows in the table or otherwise identify the line. There are some alternatives, but they are awkward and IMHO ugly, and don’t add much.<br><br>Bill<br><br>William Gropp<br>Director, NCSA<br>Thomas M. Siebel Chair in Computer Science<br>University of Illinois Urbana-Champaign<br>IEEE-CS President-Elect<br><br><br><br><br><br><br><o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-bottom:12.0pt'>On Sep 3, 2021, at 12:19 PM, George Bosilca <<a href="mailto:bosilca@icl.utk.edu">bosilca@icl.utk.edu</a><span class=apple-converted-space> </span><<a href="mailto:bosilca@icl.utk.edu">mailto:bosilca@icl.utk.edu</a>>> wrote:<br><br>Bill,<br><br>These PDFs looks great, a clear leap forward in improving the readability and cleanness of the MPI standard.<br><br>The only issue I noticed (and that was pinpointed in your email) was about the multi-page tabular where the numbering is done consecutively for the entire tabular environment despite the fact that the table is split across multiple pages, and the numbers are placed on the same side as the first page on all pages. If we can fix this to have the line numbers per page and on the correct side for all environments, that would be great.<br><br>Thanks,<br> George.<br><br>On Thu, Sep 2, 2021 at 11:03 Gropp, William D via mpi-forum <<a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a><span class=apple-converted-space> </span><<a href="mailto:mpi-forum@lists.mpi-forum.org">mailto:mpi-forum@lists.mpi-forum.org</a>>> wrote:<br><br> I’ve been experimenting with updating the MPI Forum document<br> formatting, and in particular, modernizing the use of LaTeX and<br> reducing the custom LaTeX in the document. Attached are a few<br> pages from my tests. These show:<br><br> 1) Use of the lineno package to label each line of text - this<br> replaces the ruler currently used, and means that text is more<br> accurately labeled, but “boxes”, including tables, figures, and<br> captions may not have line numbers. All of the attached pages<br> show the line numbers in the margins.<br> 2) Use of the lstlisting package, with syntax and MPI routine<br> highlighting. This also sets a background to gray to help the<br> code examples standout. The approach used in MPI 4.0 creates a<br> box with a border; because of the box, in that approach, the<br> individual lines of code are not numbered. Hence this change in<br> how code examples are marked off. The attached examples show both<br> one page and a code example that spans two pages.<br> 3) There is a way to include numbering for tabular environments<br> (and some others). However, this can lead to some odd labeling,<br> because of how the labeling is implemented within the various<br> LaTeX packages. I’ve included some examples which show both the<br> expected behavior (consecutive numbering) and the unexpected (and<br> nearly impossible to fix) non-consecutive numbering.<br> 4) I’ve also switched from the book to the srcbook document<br> class. This is a more modern and powerful document class, and has<br> allowed me to remove some of the custom LaTeX code.<br><br> I’d like feedback on these. I’d like to adopt some of these for<br> the next version. In particular:<br><br> 1) Use srcbook instead of book<br> 2) Use lstlisting in code examples as shown here<br> 3) For tabular environments, do NOT use line numbers for tabular<br> environments used within a table (or other floating) environment.<br> This is where the weird line numbering can happen (e.g., see the<br> attached page 32). For inline tabular environments, use edtable<br> to get line numbers (this is what was used in these examples, and<br> it has worked well in other parts of the document)<br><br> If you have suggestions for improvements or alternatives, please<br> let me know.<br><br> Bill<br><br><br> William Gropp<br> Director, NCSA<br> Thomas M. Siebel Chair in Computer Science<br> University of Illinois Urbana-Champaign<br> IEEE-CS President-Elect<br><br><br><br><br> _______________________________________________<br> mpi-forum mailing list<br> <a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a><span class=apple-converted-space> </span><<a href="mailto:mpi-forum@lists.mpi-forum.org">mailto:mpi-forum@lists.mpi-forum.org</a>><br> <a href="https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi-forum__;!!DZ3fjg!rX65ncURBYvC7HZUZt7_GihcXnt489vlz7HBN630c59pdHc7EaItJ-sh7U7fkRDrnw$">https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mpi-forum__;!!DZ3fjg!rX65ncURBYvC7HZUZt7_GihcXnt489vlz7HBN630c59pdHc7EaItJ-sh7U7fkRDrnw$</a><span class=apple-converted-space> </span> <<a href="https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi-forum__;!!DZ3fjg!ocG0YkYjZCIg26wHqY9ROpnb8nHCQTM8tYRtSx_Yw7RsjsMy5TL85BlU7F6wBdHXnA$">https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mpi-forum__;!!DZ3fjg!ocG0YkYjZCIg26wHqY9ROpnb8nHCQTM8tYRtSx_Yw7RsjsMy5TL85BlU7F6wBdHXnA$</a>><o:p></o:p></p></blockquote><div><p class=MsoNormal><br><br>_______________________________________________<br>mpi-forum mailing list<br><a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a><br><a href="https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi-forum__;!!DZ3fjg!rX65ncURBYvC7HZUZt7_GihcXnt489vlz7HBN630c59pdHc7EaItJ-sh7U7fkRDrnw$">https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mpi-forum__;!!DZ3fjg!rX65ncURBYvC7HZUZt7_GihcXnt489vlz7HBN630c59pdHc7EaItJ-sh7U7fkRDrnw$</a><o:p></o:p></p></div></blockquote><div><p class=MsoNormal><br>_______________________________________________<br>mpi-forum mailing list<br><a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a><br><a href="https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi-forum__;!!DZ3fjg!rX65ncURBYvC7HZUZt7_GihcXnt489vlz7HBN630c59pdHc7EaItJ-sh7U7fkRDrnw$">https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mpi-forum__;!!DZ3fjg!rX65ncURBYvC7HZUZt7_GihcXnt489vlz7HBN630c59pdHc7EaItJ-sh7U7fkRDrnw$</a><o:p></o:p></p></div></div></div></blockquote></div><div><p class=MsoNormal> <o:p></o:p></p></div></div></div></div></div><div><p class=MsoNormal><mpi40-report-9-3-code.pdf>_______________________________________________<br>mpi-forum mailing list<br><a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a><br><a href="https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi-forum__;!!DZ3fjg!sWL8x6fmEjhYAcQs2aDtwTgiva1_CDyY7lPx0kbepp3EC0PgIL-v1qGAn2CPjIoJ5Q$">https://lists.mpi-forum.org/mailman/listinfo/mpi-forum</a><o:p></o:p></p></div></div></blockquote></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><div><div><p class=MsoNormal><span style='font-size:15.0pt;font-family:"Helvetica",sans-serif'><br>-- </span><o:p></o:p></p></div></div><div><div><p class=MsoNormal><span style='font-size:15.0pt;font-family:"Helvetica",sans-serif'>Jeff Squyres</span><o:p></o:p></p></div></div><div><div><p class=MsoNormal><span style='font-size:15.0pt;font-family:"Helvetica",sans-serif'><a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a></span><o:p></o:p></p></div></div><div><div><p class=MsoNormal><span style='font-size:15.0pt;font-family:"Helvetica",sans-serif'> </span><o:p></o:p></p></div></div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><p class=MsoNormal> <o:p></o:p></p></div></div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>_______________________________________________<br>mpi-forum mailing list<br></span><a href="mailto:mpi-forum@lists.mpi-forum.org"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>mpi-forum@lists.mpi-forum.org</span></a><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><br></span><a href="https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi-forum__;!!DZ3fjg!sWL8x6fmEjhYAcQs2aDtwTgiva1_CDyY7lPx0kbepp3EC0PgIL-v1qGAn2CPjIoJ5Q$"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mpi-forum__;!!DZ3fjg!sWL8x6fmEjhYAcQs2aDtwTgiva1_CDyY7lPx0kbepp3EC0PgIL-v1qGAn2CPjIoJ5Q$</span></a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>