Merge pull request #253 from jdeisenberg/cs20

Eliminate Warnings on Build

Author: bnmnetp

pretext/Debugging/BeginningtipsforDebugging.ptx

@@ -3,7 +3,7 @@
   <title>Beginning tips for Debugging</title>
   <p>Debugging a program is a different way of thinking than writing a program.  The process of debugging is much more like being a detective.  Here are a few rules to get you thinking about debugging.</p>
   <p>
-    <ol label="1">
+    <ol marker="1">
       <li>
         <p>Everyone is a suspect (Except Python)!  It's common for beginner programmers to blame Python, but that should be your last resort.  Remember that Python has been used to solve CS1 level problems millions of times by millions of other programmers.  So, Python is probably not the problem.</p>
       </li>

pretext/Debugging/HowtoAvoidDebugging.ptx

@@ -3,7 +3,7 @@
   <title>How to Avoid Debugging</title>
   <p>Perhaps the most important lesson in debugging is that it is <term>largely avoidable</term> &#x2013; if you work carefully.</p>
   <p>
-    <ol label="1">
+    <ol marker="1">
       <li>
         <p><term>Understand the Problem</term>  You must have a firm grasp on <term>what</term> you are trying to accomplish but not
                     necessarily <term>how</term> to do it. You do not need to understand the entire problem. But you must understand

pretext/Debugging/KnowyourerrorMessages.ptx

@@ -1,6 +1,7 @@
 <?xml version="1.0"?>
 <section xml:id="debugging_know-your-error-messages">
   <title>Know Your Error Messages</title>
+  <introduction>
   <p>Many problems in your program will lead to an error message.  For example as I was writing and testing this chapter of the book I wrote the following version of the example program in the previous section.</p>
   <program language="python">
     <input>
@@ -227,10 +228,11 @@ print(final_time_int)
       </li>
     </ul>
   </p>
+  </introduction>
   <subsection xml:id="debugging_parseerror">
     <title>ParseError</title>
     <p>Parse errors happen when you make an error in the syntax of your program.  Syntax errors are like making grammatical errors in writing.  If you don't use periods and commas in your writing then you are making it hard for other readers to figure out what you are trying to say.  Similarly Python has certain grammatical rules that must be followed or else Python can't figure out what you are trying to say.</p>
-    <p>Usually ParseErrors can be traced back to missing punctuation characters, such as parentheses, quotation marks, or commas. Remember that in Python commas are used to separate parameters to functions.  Paretheses must be balanced, or else Python thinks that you are trying to include everything that follows as a parameter to some function.</p>
+    <p>Usually ParseErrors can be traced back to missing punctuation characters, such as parentheses, quotation marks, or commas. Remember that in Python commas are used to separate parameters to functions.  Parentheses must be balanced, or else Python thinks that you are trying to include everything that follows as a parameter to some function.</p>
     <p>Here are a couple examples of Parse errors in the example program we have been using.  See if you can figure out what caused them.</p>
     <exercise>
       <statement/>
@@ -349,7 +351,7 @@ print(time_when_alarm_go_off)
     </hint>
     <p><term>Finding Clues</term>  With name errors one of the best things you can do is use the editor, or browser search function.  Quite often if you search for the exact word in the error message one of two things will happen:</p>
     <p>
-      <ol label="1">
+      <ol marker="1">
         <li>
           <p>The word you are searching for will appear only once in your code, it's also likely that it will be on the right hand side of an assignment statement, or as a parameter to a function.  That should confirm for you that you have a typo somewhere.  If the name in question <term>is</term> what you thought it should be then you probably have a typo on the left hand side of an assignment statement on a line before your error message occurs.  Start looking backward at your assignment statements.  In some cases it's really nice to leave all the highlighted strings from the search function visible as they will help you very quickly find a line where you might have expected your variable to be highlighted.</p>
         </li>
@@ -390,7 +392,7 @@ print(alarm_time)
         <title>Solution</title>
         <p>In this example the error message is about <c>set_time</c> not defined on line 3.  In this case the undefined name is not used in an assignment statement, but is used as a parameter (incorrectly) to a function call.   A search on <c>set_time</c> reveals that in fact it is only used once in the program.  Did the author mean <c>set_alarm</c>?  If we make that assumption we immediately get another error <c>NameError: name 'alarm_time' is not defined on line: 3</c>.  The variable <c>alarm_time</c> is defined on line 4, but that does not help us on line 3.  Furthermore we now have to ask the question is this function call <c>int(present_time, set_alarm, alarm_time)</c> even the correct use of the <c>int</c> function?  The answer to that is a resounding no.  Let's list all of the things wrong with line 3:</p>
         <p>
-          <ol label="1">
+          <ol marker="1">
             <li>
               <p><c>set_time</c> is not defined and never used, the author probably meant <c>set_alarm</c>.</p>
             </li>

pretext/Dictionaries/Exercises.ptx

@@ -59,7 +59,7 @@ for char in sorted(keys):
     <p>Give the Python interpreter's response to each of the following from a
                     continuous interpreter session:</p>
     <p>
-      <ol label="a">
+      <ol marker="a">
         <li>
           <program language="python">
             <input>

pretext/Exceptions/05_exceptions_syntax.ptx

@@ -1,8 +1,10 @@
 <?xml version="1.0"?>
 <section xml:id="exceptions_exceptions-syntax">
   <title>Exceptions Syntax</title>
+  <introduction>
   <p>There are many variations on the code that catches exceptions. Here is a
             brief summary, but other code variations are possible.</p>
+        </introduction>
   <subsection xml:id="exceptions_catch-all-exceptions">
     <title>Catch All Exceptions</title>
     <p>Catch all exceptions, regardless of their type. This will prevent

pretext/Functions/Exercises.ptx

@@ -122,7 +122,7 @@ drawPoly(tess, 8, 50)
   <exercise label="ex_5_5">
     <statement>
       <p>The two spirals in this picture differ only by the turn angle.  Draw both.</p>
-      <image source="Functions/Figures/tess_spirals.png" width="50%" height="240"/>
+      <image source="Functions/Figures/tess_spirals.png" width="50%"/>
     </statement>
     <program interactive="activecode" language="python" xml:id="ex_5_5_editor">
       <input>

pretext/Functions/Functionscancallotherfunctions.ptx

@@ -139,7 +139,7 @@ wn.exitonclick()
             new functions. Actually, there are a lot of reasons, but this example
             demonstrates two:</p>
   <p>
-    <ol label="1">
+    <ol marker="1">
       <li>
         <p>Creating a new function gives you an opportunity to name a group of
                     statements. Functions can simplify a program by hiding a complex computation

pretext/Functions/ProgramDevelopment.ptx

@@ -131,7 +131,7 @@ test.testEqual(distance(0,0, 1,1), 1.41)
             to chunk music &#x2014; from indvidual notes to chords, bars, phrases, and so on.</p>
   <p>The key aspects of the process are:</p>
   <p>
-    <ol label="1">
+    <ol marker="1">
       <li>
         <p>Make sure you know what you are trying to accomplish. Then you can write appropriate unit tests.</p>
       </li>

pretext/Functions/TheAccumulatorPattern.ptx

@@ -1,6 +1,7 @@
 <?xml version="1.0"?>
 <section xml:id="functions_the-accumulator-pattern">
   <title>The Accumulator Pattern</title>
+  <introduction>
   <video xml:id="function_accumulator_pattern" youtube="aqhREpceEMI" width="auto"/>
   <p>In the previous example, we wrote a function that computes the square of a number.  The algorithm we used
             in the function was simple: multiply the number by itself.
@@ -60,6 +61,7 @@ squareResult = square(toSquare)
 print("The result of", toSquare, "squared is", squareResult)
     </input>
   </program>
+</introduction>
   <subsection xml:id="functions_the-general-accumulator-pattern">
     <title>The General Accumulator Pattern</title>
     <program language="python">

pretext/Functions/UnitTesting.ptx

@@ -1,6 +1,7 @@
 <?xml version="1.0"?>
 <section xml:id="functions_unit-testing">
   <title>Unit Testing</title>
+  <introduction>
   <p>A <term>test case</term> expresses requirements for a program, in a way that can be checked automatically. Specifically, a test
             asserts something about the state of the program at a particular point in its execution. A <term>unit test</term> is an automatic
             procedure used to validate that individual units of code are working properly. A function is one form of a unit.
@@ -99,6 +100,7 @@ assert type(9.0//5) == int
       </choice>
     </choices>
   </exercise>
+</introduction>
   <subsection xml:id="functions_assert-with-for-loops">
     <title><c>assert</c> with <c>for</c> loops</title>
     <p>Why would you ever want to write a line of code that can never compute anything useful for you, but sometimes causes