virtio-msg: replace non-ASCII punctuation in transport text (Bill Mills)

Bill Mills noted that transport-msg.tex still contained non-ASCII
punctuation.

Replace sentence-interrupting Unicode dashes with commas, convert
numeric ranges to the single ASCII hyphen form used elsewhere in the
virtio spec, and normalize the remaining 0--31/32--63 range to that
same style.

Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>

Author: bertrand-marquis

transport-msg.tex

@@ -313,8 +313,8 @@ \subsubsection{Device Numbers and Enumeration}
         might inform the bus of available device numbers and their properties.
 \end{itemize}
 
-Once a bus confirms that a device number is valid—regardless of the discovery
-method—it normally issues \msgref{GET_DEVICE_INFO} to retrieve the device and
+Once a bus confirms that a device number is valid, regardless of the discovery
+method, it normally issues \msgref{GET_DEVICE_INFO} to retrieve the device and
 vendor IDs before registering the device with the host OS so the usual Virtio
 driver binding process can begin.
 
@@ -326,8 +326,8 @@ \subsubsection{Device Numbers and Enumeration}
         immediately after a device is removed, to reduce race conditions with
         delayed messages associated with the removed device.
   \item A bus implementation SHOULD provide the driver with sufficient
-        information—either via \busref{GET_DEVICES} or equivalent platform
-        data—to discover each valid device number.
+        information, either via \busref{GET_DEVICES} or equivalent platform
+        data, to discover each valid device number.
 \end{itemize}
 
 \subsubsection{Configuration Semantics Profiles}
@@ -413,7 +413,7 @@ \subsubsection{Feature Negotiation Blocks}
 
 \begin{itemize}
   \item \textbf{Block Index}: The starting block (e.g., block 0 for
-        features 0--31, block 1 for features 32--63, etc.).
+        features 0-31, block 1 for features 32-63, etc.).
   \item \textbf{Number of Blocks}: How many blocks the driver wishes to retrieve
         or modify in a single message.
   \item \textbf{Feature Data}: The 32-bit values representing the supported (or
@@ -1876,7 +1876,7 @@ \subsubsection{Overview}
 
 Example: a request with \field{offset}=0, \field{count}=16 might produce
 \field{bitmap}=0b00100101 00000000 and \field{next_offset}=16. That indicates
-devices 0, 2, and 5 are present within the 0–15 window and suggests continuing
+devices 0, 2, and 5 are present within the 0-15 window and suggests continuing
 at device number 16.
 
 \paragraph{Intended usage}
@@ -1952,8 +1952,8 @@ \subsubsection{Overview}
 \hline
 DEVICE\_BUS\_STATE\_ADDED    & 0x0001 & Device is present and ready. \\
 DEVICE\_BUS\_STATE\_REMOVED  & 0x0002 & Device is no longer present. \\
-Reserved                    & 0x0003–0x7FFF & Reserved for standard use. \\
-Implementation-defined      & 0x8000–0xFFFF & MAY be used by the bus implementation. \\
+Reserved                    & 0x0003-0x7FFF & Reserved for standard use. \\
+Implementation-defined      & 0x8000-0xFFFF & MAY be used by the bus implementation. \\
 \hline
 \end{tabular}