Some updates to the .po files

Presumably these are showing up because either the .po files were edited or because
they were regenerated as a result of changes in the text.

Author: mtiller

text/locale/cn/LC_MESSAGES/behavior/arrays/chem.po

@@ -134,20 +134,6 @@ msgid ""
 "**as a dimension in an array** as follows:"
 msgstr ""
 
-#: ../../source/behavior/arrays/chem.rst:150
-msgid ""
-"Since the ``Species`` type has only three possible values, this means that "
-"the vector ``C`` has exactly three components.  We can then refer to the "
-"individual components of ``C`` as ``C[Species.A]``, ``C[Species.B]`` and "
-"``C[Species.C]``."
-msgstr ""
-
-#: ../../source/behavior/arrays/chem.rst:155
-msgid ""
-"Because it is awkward to constantly prefix each species name with "
-"``Species``, we can define a few convenient constants, we follows:"
-msgstr ""
-
 #: ../../source/behavior/arrays/chem.rst:164
 msgid ""
 "In this way, we can now refer to the concentration of species :math:`A` as "
@@ -169,3 +155,29 @@ msgid ""
 " be used not only to index the array, but also to define one or more "
 "dimensions in the declaration."
 msgstr ""
+
+#: ../../source/behavior/arrays/chem.rst:150
+msgid ""
+"Since the ``Species`` type has only three possible values, this means that "
+"the vector ``C`` has exactly three components.  We can then refer to the "
+"individual components of ``C`` as ``C[Species.A]``, ``C[Species.B]`` and "
+"``C[Species.X]``."
+msgstr ""
+
+#: ../../source/behavior/arrays/chem.rst:155
+msgid ""
+"Because it is awkward to constantly prefix each species name with "
+"``Species``, we can define a few convenient constants as follows:"
+msgstr ""
+
+#~ msgid ""
+#~ "Since the ``Species`` type has only three possible values, this means that "
+#~ "the vector ``C`` has exactly three components.  We can then refer to the "
+#~ "individual components of ``C`` as ``C[Species.A]``, ``C[Species.B]`` and "
+#~ "``C[Species.C]``."
+#~ msgstr ""
+
+#~ msgid ""
+#~ "Because it is awkward to constantly prefix each species name with "
+#~ "``Species``, we can define a few convenient constants, we follows:"
+#~ msgstr ""

text/locale/cn/LC_MESSAGES/behavior/arrays/functions.po

@@ -663,22 +663,10 @@ msgstr ""
 msgid "``skew``"
 msgstr ""
 
-#: ../../source/behavior/arrays/functions.rst:509
-msgid ""
-"The ``skew`` function takes a vector with three components and returns the "
-"following matrix:"
-msgstr ""
-
 #: ../../source/behavior/arrays/functions.rst:523
 msgid "``cross``"
 msgstr ""
 
-#: ../../source/behavior/arrays/functions.rst:528
-msgid ""
-"The ``cross`` function takes two vectors (each with 3 components) and "
-"returns the following scalar:"
-msgstr ""
-
 #: ../../source/behavior/arrays/functions.rst:542
 msgid "Reduction Operators"
 msgstr ""
@@ -1058,3 +1046,25 @@ msgstr ""
 #: ../../source/behavior/arrays/functions.rst:657
 msgid "vectorization"
 msgstr ""
+
+#: ../../source/behavior/arrays/functions.rst:509
+msgid ""
+"The ``skew`` function takes a vector with three components and returns the "
+"following skew-symmetric matrix:"
+msgstr ""
+
+#: ../../source/behavior/arrays/functions.rst:528
+msgid ""
+"The ``cross`` function takes two vectors (each with 3 components) and "
+"returns the following vector (with three components):"
+msgstr ""
+
+#~ msgid ""
+#~ "The ``skew`` function takes a vector with three components and returns the "
+#~ "following matrix:"
+#~ msgstr ""
+
+#~ msgid ""
+#~ "The ``cross`` function takes two vectors (each with 3 components) and "
+#~ "returns the following scalar:"
+#~ msgstr ""

text/locale/cn/LC_MESSAGES/behavior/arrays/oned.po

@@ -49,13 +49,6 @@ msgid ""
 ":math:`i^{th}` section.  We can further describe the mass as:"
 msgstr ""
 
-#: ../../source/behavior/arrays/oned.rst:41
-msgid ""
-"where :math:`\\rho` is the material density and :math:`V_i` is the volume of"
-" the :math:`i^{th}` section.  Finally, we can expression the volume of the "
-":math:`i^{th}` section as:"
-msgstr ""
-
 #: ../../source/behavior/arrays/oned.rst:49
 msgid ""
 "where :math:`A_i` is the cross-sectional area of the :math:`i^{th}` section,"
@@ -321,3 +314,16 @@ msgstr ""
 #: ../../source/behavior/arrays/oned.rst:252
 msgid "array comprehensions"
 msgstr ""
+
+#: ../../source/behavior/arrays/oned.rst:41
+msgid ""
+"where :math:`\\rho` is the material density and :math:`V_i` is the volume of"
+" the :math:`i^{th}` section.  Finally, we can express the volume of the "
+":math:`i^{th}` section as:"
+msgstr ""
+
+#~ msgid ""
+#~ "where :math:`\\rho` is the material density and :math:`V_i` is the volume of"
+#~ " the :math:`i^{th}` section.  Finally, we can expression the volume of the "
+#~ ":math:`i^{th}` section as:"
+#~ msgstr ""

text/locale/cn/LC_MESSAGES/behavior/arrays/state_space.po

@@ -33,14 +33,6 @@ msgid ""
 " but can ultimately be computed from the values of the states and inputs)."
 msgstr ""
 
-#: ../../source/behavior/arrays/state_space.rst:28
-msgid ""
-"There is a particularly interesting special case of these equation when the "
-"functions :math:`\\vec{f}` and :math:`\\vec{g}` depend linearly on "
-":math:`\\vec{x}` and :math:`\\vec{u}`.  In this case, the equations can be "
-"rewritten as:"
-msgstr ""
-
 #: ../../source/behavior/arrays/state_space.rst:38
 msgid ""
 "The matrices in this problem are the so-called \"ABCD\" matrices.  This ABCD"
@@ -219,27 +211,13 @@ msgid ""
 "change accordingly."
 msgstr ""
 
-#: ../../source/behavior/arrays/state_space.rst:203
-msgid ""
-"We can take a similar approach in reformulating the our previous "
-":ref:`mechanical example <mech-example>` into LTI form:"
-msgstr ""
-
 #: ../../source/behavior/arrays/state_space.rst:210
 msgid ""
 "Again, we compute ``A`` from physical parameters.  One thing to note about "
 "this example is the construction of ``A``.  Mathematically, the :math:`A` "
 "matrix is defined as:"
 msgstr ""
 
-#: ../../source/behavior/arrays/state_space.rst:227
-msgid ""
-"One thing we can note about this construction of :math:`A` is that the first"
-" two rows might be easier to express as a matrix of zeros and an identify "
-"matrix.  In other words, it might be simpler to construct the matrix as a "
-"set of sub-matrices, *i.e.,*"
-msgstr ""
-
 #: ../../source/behavior/arrays/state_space.rst:264
 msgid ""
 "In Modelica, we can construct our ``A`` matrix from sub-matrices in this "
@@ -296,3 +274,44 @@ msgstr ""
 #: ../../source/behavior/arrays/state_space.rst:56
 msgid "FMI"
 msgstr ""
+
+#: ../../source/behavior/arrays/state_space.rst:28
+msgid ""
+"There is a particularly interesting special case of these equations when the"
+" functions :math:`\\vec{f}` and :math:`\\vec{g}` depend linearly on "
+":math:`\\vec{x}` and :math:`\\vec{u}`.  In this case, the equations can be "
+"rewritten as:"
+msgstr ""
+
+#: ../../source/behavior/arrays/state_space.rst:203
+msgid ""
+"We can take a similar approach in reformulating our previous "
+":ref:`mechanical example <mech-example>` into LTI form:"
+msgstr ""
+
+#: ../../source/behavior/arrays/state_space.rst:227
+msgid ""
+"One thing we can note about this construction of :math:`A` is that the first"
+" two rows might be easier to express as a matrix of zeros and an identity "
+"matrix.  In other words, it might be simpler to construct the matrix as a "
+"set of sub-matrices, *i.e.,*"
+msgstr ""
+
+#~ msgid ""
+#~ "There is a particularly interesting special case of these equation when the "
+#~ "functions :math:`\\vec{f}` and :math:`\\vec{g}` depend linearly on "
+#~ ":math:`\\vec{x}` and :math:`\\vec{u}`.  In this case, the equations can be "
+#~ "rewritten as:"
+#~ msgstr ""
+
+#~ msgid ""
+#~ "We can take a similar approach in reformulating the our previous "
+#~ ":ref:`mechanical example <mech-example>` into LTI form:"
+#~ msgstr ""
+
+#~ msgid ""
+#~ "One thing we can note about this construction of :math:`A` is that the first"
+#~ " two rows might be easier to express as a matrix of zeros and an identify "
+#~ "matrix.  In other words, it might be simpler to construct the matrix as a "
+#~ "set of sub-matrices, *i.e.,*"
+#~ msgstr ""

text/locale/cn/LC_MESSAGES/behavior/discrete/bouncing.po

@@ -106,11 +106,6 @@ msgid ""
 " ``time``."
 msgstr ""
 
-#: ../../source/behavior/discrete/bouncing.rst:89
-msgid ""
-"do the referenced variables have to be continuous to make a state event?"
-msgstr ""
-
 #: ../../source/behavior/discrete/bouncing.rst:91
 msgid ""
 "As such, the simulation proceeds assuming the ball is in free fall until it "
@@ -276,3 +271,7 @@ msgid ""
 "later in this chapter when we talk about the important differences between "
 ":ref:`if-vs-when`."
 msgstr ""
+
+#~ msgid ""
+#~ "do the referenced variables have to be continuous to make a state event?"
+#~ msgstr ""

text/locale/cn/LC_MESSAGES/behavior/discrete/cooling.po

@@ -65,34 +65,10 @@ msgid ""
 "model for one second, we get the following temperature trajectory:"
 msgstr ""
 
-#: ../../source/behavior/discrete/cooling.rst:50
-msgid ""
-"As you can see in these results, the ambient temperature does indeed start "
-"to decrease after half a second.  In studying the dynamic response of the "
-"temperature itself, we see two distinct phases.  The first phase is the "
-"initial transient response toward equilibrium (to match the ambient "
-"temperature).  The second phase is the tracking of the ambient temperature "
-"as it increases."
-msgstr ""
-
 #: ../../source/behavior/discrete/cooling.rst:58
 msgid "Initial Transients"
 msgstr ""
 
-#: ../../source/behavior/discrete/cooling.rst:60
-msgid ""
-"It is worth noting that this is a very common issue in modeling. Frequently,"
-" you wish to model the systems response to some disturbance (like the "
-"ambient temperature increase in this case).  However, if you don't start "
-"your system in some kind of equilibrium state, the system response will also"
-" include some kind of initial transient (like the one shown here).  In order"
-" to distinguish these two responses clearly, we want to avoid any overlap "
-"between them.  **The simplest way to do that is to start the simulation in "
-"an equilibrium condition** (as discussed previous in our discussion of :ref"
-":`steady-state`).  This avoids the initial transient altogether and allows "
-"us to focus entirely on the disturbance that we are interested in."
-msgstr ""
-
 #: ../../source/behavior/discrete/cooling.rst:72
 msgid ""
 "As we learned during our discussion of :ref:`initialization`, we can solve "
@@ -223,3 +199,49 @@ msgstr ""
 #: ../../source/behavior/discrete/cooling.rst:115
 msgid "max"
 msgstr ""
+
+#: ../../source/behavior/discrete/cooling.rst:50
+msgid ""
+"As you can see in these results, the ambient temperature does indeed start "
+"to decrease after half a second.  In studying the dynamic response of the "
+"temperature itself, we see two distinct phases.  The first phase is the "
+"initial transient response toward equilibrium (to match the ambient "
+"temperature).  The second phase is the tracking of the ambient temperature "
+"as it decreases."
+msgstr ""
+
+#: ../../source/behavior/discrete/cooling.rst:60
+msgid ""
+"It is worth noting that this is a very common issue in modeling. Frequently,"
+" you wish to model the systems response to some disturbance (like the "
+"ambient temperature decrease in this case).  However, if you don't start "
+"your system in some kind of equilibrium state, the system response will also"
+" include some kind of initial transient (like the one shown here).  In order"
+" to distinguish these two responses clearly, we want to avoid any overlap "
+"between them.  **The simplest way to do that is to start the simulation in "
+"an equilibrium condition** (as discussed previous in our discussion of :ref"
+":`steady-state`).  This avoids the initial transient altogether and allows "
+"us to focus entirely on the disturbance that we are interested in."
+msgstr ""
+
+#~ msgid ""
+#~ "As you can see in these results, the ambient temperature does indeed start "
+#~ "to decrease after half a second.  In studying the dynamic response of the "
+#~ "temperature itself, we see two distinct phases.  The first phase is the "
+#~ "initial transient response toward equilibrium (to match the ambient "
+#~ "temperature).  The second phase is the tracking of the ambient temperature "
+#~ "as it increases."
+#~ msgstr ""
+
+#~ msgid ""
+#~ "It is worth noting that this is a very common issue in modeling. Frequently,"
+#~ " you wish to model the systems response to some disturbance (like the "
+#~ "ambient temperature increase in this case).  However, if you don't start "
+#~ "your system in some kind of equilibrium state, the system response will also"
+#~ " include some kind of initial transient (like the one shown here).  In order"
+#~ " to distinguish these two responses clearly, we want to avoid any overlap "
+#~ "between them.  **The simplest way to do that is to start the simulation in "
+#~ "an equilibrium condition** (as discussed previous in our discussion of :ref"
+#~ ":`steady-state`).  This avoids the initial transient altogether and allows "
+#~ "us to focus entirely on the disturbance that we are interested in."
+#~ msgstr ""

text/locale/cn/LC_MESSAGES/behavior/discrete/decay.po

@@ -31,12 +31,6 @@ msgstr ""
 msgid "Consider the following almost trivial model:"
 msgstr ""
 
-#: ../../source/behavior/discrete/decay.rst:21
-msgid ""
-"If we attempt to simulate this model for 5 seconds, we fine that the "
-"simulation terminates after about 2 seconds with the following trajectory:"
-msgstr ""
-
 #: ../../source/behavior/discrete/decay.rst:27
 msgid ""
 "Again, numerical issues creep in.  Even though mathematically it should not "
@@ -311,3 +305,14 @@ msgid ""
 "integration error is introduced and this, in turn, depends on the numerical "
 "tolerances used."
 msgstr ""
+
+#: ../../source/behavior/discrete/decay.rst:21
+msgid ""
+"If we attempt to simulate this model for 5 seconds, we find that the "
+"simulation terminates after about 2 seconds with the following trajectory:"
+msgstr ""
+
+#~ msgid ""
+#~ "If we attempt to simulate this model for 5 seconds, we fine that the "
+#~ "simulation terminates after about 2 seconds with the following trajectory:"
+#~ msgstr ""

text/locale/cn/LC_MESSAGES/behavior/functions/interpolation.po

@@ -33,12 +33,6 @@ msgstr ""
 msgid "Function Definition"
 msgstr ""
 
-#: ../../source/behavior/functions/interpolation.rst:18
-msgid ""
-"For this example, we assume that we interpolation data in the following "
-"form:"
-msgstr ""
-
 #: ../../source/behavior/functions/interpolation.rst:22
 msgid "Independent Variable, :math:`x`"
 msgstr ""
@@ -461,3 +455,13 @@ msgstr ""
 #: ../../source/behavior/functions/interpolation.rst:152
 msgid "ExternalObject"
 msgstr ""
+
+#: ../../source/behavior/functions/interpolation.rst:18
+msgid ""
+"For this example, we assume that we interpolate data in the following form:"
+msgstr ""
+
+#~ msgid ""
+#~ "For this example, we assume that we interpolation data in the following "
+#~ "form:"
+#~ msgstr ""