test: avoid unicode characters in the middle of line

Format in OCaml 5.4 is using a better computation for character width.
To avoid backward compatibility problem, this commit remove one unicode
character and move another in the beginning of a paragraph.

test/generators/cases/markup.mli

···
 
     {1 Unicode}
 
-    The parser supports any ASCII-compatible encoding, in particuλar UTF-8.
+    The parser supports any ASCII-compatible encoding.
+
+    In particuλar UTF-8.
 
 
     {1 Raw HTML}

test/generators/cases/section.mli

···
 (** {1 {e This} [section] {b title} {_has} {^markup}}
 
     But links are impossible thanks to the parser, so we never have trouble
-    rendering a section title in a table of contents – no link will be nested
+    rendering a section title in a table of contents - no link will be nested
     inside another link. *)

test/generators/html/Markup.html

···
      </ul>
     </li>
    </ul><h2 id="unicode"><a href="#unicode" class="anchor"></a>Unicode</h2>
-   <p>The parser supports any ASCII-compatible encoding, in particuλar
-     UTF-8.
-   </p><h2 id="raw-html"><a href="#raw-html" class="anchor"></a>Raw HTML</h2>
+   <p>The parser supports any ASCII-compatible encoding.</p>
+   <p>In particuλar UTF-8.</p>
+   <h2 id="raw-html"><a href="#raw-html" class="anchor"></a>Raw HTML</h2>
    <p>Raw HTML can be <input type="text" placeholder="inserted"> as inline
      elements into sentences.
    </p>

test/generators/html/Section.html

···
      <code>section</code> <b>title</b> <sub>has</sub> <sup>markup</sup>
    </h2>
    <p>But links are impossible thanks to the parser, so we never have
-     trouble rendering a section title in a table of contents – no 
-    link will be nested inside another link.
+     trouble rendering a section title in a table of contents - no link
+     will be nested inside another link.
    </p>
   </div>
  </body>

test/generators/latex/Markup.tex

···
 \item{\hyperref[Markup-val-foo]{\ocamlinlinecode{\ocamlinlinecode{foo}}[p\pageref*{Markup-val-foo}]}}\end{itemize}%
 }\end{itemize}%
 \subsection{Unicode\label{unicode}}%
-The parser supports any ASCII-compatible encoding, in particuλar UTF-8.
+The parser supports any ASCII-compatible encoding.
+
+In particuλar UTF-8.
 
 \subsection{Raw HTML\label{raw-html}}%
 Raw HTML can be  as inline elements into sentences.

test/generators/latex/Section.tex

···
 \subsection{within a comment\label{within-a-comment}}%
 \subsubsection{and one with a nested section\label{and-one-with-a-nested-section}}%
 \subsection{\emph{This} \ocamlinlinecode{section} \bold{title} \textsubscript{has} \textsuperscript{markup}\label{this-section-title-has-markup}}%
-But links are impossible thanks to the parser, so we never have trouble rendering a section title in a table of contents – no link will be nested inside another link.
+But links are impossible thanks to the parser, so we never have trouble rendering a section title in a table of contents - no link will be nested inside another link.
 
 
 

test/generators/man/Markup.3o

···
 .in 
 .sp 
 .fi 
-The parser supports any ASCII-compatible encoding, in particuλar UTF-8\.
+The parser supports any ASCII-compatible encoding\.
+.sp 
+In particuλar UTF-8\.
 .nf 
 .sp 
 .in 3

test/generators/man/Section.3o

···
 .in 
 .sp 
 .fi 
-But links are impossible thanks to the parser, so we never have trouble rendering a section title in a table of contents – no link will be nested inside another link\.
+But links are impossible thanks to the parser, so we never have trouble rendering a section title in a table of contents - no link will be nested inside another link\.
 .nf