Change some hyphens to em-dashes

chapters/annotations.tex

@@ -662,7 +662,7 @@ \subsection{Connections}\doublelabel{connections1}
 The optional Text-primitive defines a text that will be written on the
 connection line. It has the following definition (\emph{it is not equal
 to the Text-primitive as part of graphics --- the differences are marked as bold lines}):
-% NOTE: Technically just the names - not the entire lines are marked in bold
+% NOTE: Technically just the names -- not the entire lines are marked in bold
 \begin{lstlisting}[language=modelica]
 record Text
   extends GraphicItem;
@@ -877,10 +877,8 @@ \subsubsection{Text}\doublelabel{text}
 A zero-width \lstinline!extent! is convenient for handling texts where the width is unknown.
 \end{nonnormative}
 
-If the string \lstinline!fontName! is empty, the tool may choose a font. The font
-names \lstinline!"serif"!, \lstinline!"sans-serif"!, and \lstinline!"monospace"! shall be recognized. If
-possible the correct font should be used - otherwise a reasonable match,
-or treat as if font-name was empty.
+If the string \lstinline!fontName! is empty, the tool may choose a font.  The font names \lstinline!"serif"!, \lstinline!"sans-serif"!, and \lstinline!"monospace"! shall be recognized.  If possible
+the correct font should be used --- otherwise a reasonable match, or treat as if \lstinline!fontName! was empty.
 
 The style attribute \lstinline!textStyle! specifies variations of the font.
 
@@ -1153,7 +1151,7 @@ \section{Annotations for the Graphical User Interface}\doublelabel{annotations-f
 a message indicating the recommended action.
 This annotation is not inherited, the assumption is that if a class uses
 an obsolete class (as a base-class or as the class of one of the components)
-that shall be updated - ideally without impacting users of the class.
+that shall be updated --- ideally without impacting users of the class.
 If that is not possible the current class can have also have an obsolete-annotation.
 
 A declaration may have the following annotations:

chapters/arrays.tex

@@ -575,15 +575,10 @@ \subsection{Array Constructor with Iterators}\doublelabel{array-constructor-with
 IDENT in array_expression
 \end{lstlisting}
 
-the loop-variable, \lstinline!IDENT!, is in scope inside expression in the array
-construction. The loop-variable may hide other variables, as in
-for-clauses. The loop-variable has the same type as the type of the
-elements of array\_expression; and can be simple type as well as a
-record type. The loop-variable will have the same type for the entire
-loop - i.e.\ for an array\_expression \{1,3.2\} the iterator will have
-the type of the type-compatible expression (Real) for all iterations.
-For deduction of ranges, see \autoref{implicit-iteration-ranges}; and for using types as
-range see \autoref{types-as-iteration-ranges}.
+the loop-variable, \lstinline!IDENT!, is in scope inside expression in the array construction.  The loop-variable may hide other variables, as in for-clauses.  The loop-variable has the same type as
+the type of the elements of \lstinline!array_expression!; and can be simple type as well as a record type.  The loop-variable will have the same type for the entire loop --- i.e., for an
+\lstinline!array_expression! \lstinline!{1, 3.2}! the iterator will have the type of the type-compatible expression (\lstinline!Real!) for all iterations.  For deduction of ranges, see
+\autoref{implicit-iteration-ranges}; and for using types as range see \autoref{types-as-iteration-ranges}.
 
 \subsubsection{Array Constructor with One Iterator}\doublelabel{array-constructor-with-one-iterator}
 

chapters/introduction.tex

@@ -38,7 +38,7 @@ \section{Scope of the Specification}\doublelabel{scope-of-the-specification}
 the resulting system of equations can be transformed to state space form
 (at least locally numerically), i.e., a hybrid DAE of index zero. In
 order to allow this structural analysis, a tool may reject simulating a
-model if parameters cannot be evaluated during translation - due to
+model if parameters cannot be evaluated during translation --- due to
 calls of external functions or initial equations/initial algorithms for
 fixed=false parameters. Accepting such models is a quality of
 implementation issue. The Modelica specification does not define how to

chapters/synchronous.tex

@@ -666,7 +666,7 @@ \subsection{Sub-clock conversion operators}\doublelabel{sub-clock-conversion-ope
 Clock.  (The operators can operate on all types of clocks.)  If
 u is a clocked expression, the operator returns a clocked variable that
 has the same type as the expression. If u is an expression of type
-Clock, the operator returns a Clock - except for noClock where it is an error.
+Clock, the operator returns a Clock --- except for noClock where it is an error.
 
 The optional input arguments \lstinline!factor! (default=0, min=0), and \lstinline!resolution!
 (default=1, min=1) are parameter expressions of type Integer.

preamble.tex

@@ -338,7 +338,7 @@
 \end{center}
 ~\\[2\baselineskip]
 \fi
-Modelica\textsuperscript\textregistered - A Unified Object-Oriented Language for Systems
+Modelica\textsuperscript\textregistered --- A Unified Object-Oriented Language for Systems
 Modeling\\[2\baselineskip]
 Language Specification\\[2\baselineskip]
 Version 3.5-dev}