Updated a test related to issue #251.

 - Legacy-Id: 1434

cli/tests/input/section.xml

@@ -295,8 +295,12 @@
 	  to Mrs. Smith and Messrs. Costeau & Filou.  We might also
 	  look at some other examples, e.g. (without the correct comma following
 	  the final dot) military titles like Lt. Anderson, and others,
-	  viz. Prof. Foo and Dr. Barbara. We also should test things like
-	  Anon Y. Name. End of test.
+	  viz. Prof. Foo and Dr. Barbara.  We have however been requested to
+	  generate end-of-sentence spacing for things like this sentence:
+	  OCB encryption protects the confidentiality of P and the authenticity
+	  of A, N, and P.  This is obviously in conflict with the correct
+	  rendering of Anon Y. Name, so a workaround for that case, with
+	    will have to be used for correct rendering.  End of test.
 	  </t>
 
        </section>

cli/tests/valid/section.exp.xml

@@ -136,4 +136,4 @@
 
 <p id="rfc.section.3.1.1.p.4">MRCPv2 clients and servers MUST support the 'multipart/mixed' media type. This is the appropriate media type to use when providing a mix of URI and inline speech data. Embedded within the multipart content block, there MAY be content for the 'text/uri-list', 'application/ssml+xml', and/or 'text/plain' media types. The character set and encoding used in the speech data is specified according to standard media type definitions. The multipart content MAY also contain actual audio data. Clients may have recorded audio clips stored in memory or on a local device and wish to play it as part of the SPEAK request. The audio portions MAY be sent by the client as part of the multipart content block. This audio is referenced in the speech markup data that is another part in the multipart content block according to the 'multipart/mixed' media type specification.</p>
 
-<p id="rfc.section.3.1.1.p.5">Here are some tests for various things which are not sentence endings, and should not be fixed up with double spaces: Some titles (which actually shouldn't all have a final dot according to some grammar rules, but nevermind...): Mr. Jones said hello to Mrs. Smith and Messrs. Costeau &amp; Filou.  We might also look at some other examples, e.g. (without the correct comma following the final dot) military titles like Lt. Anderson, and others, viz. Prof. Foo and Dr. Barbara. We also should test things like Anon Y. Name. End of test.  </p>
+<p id="rfc.section.3.1.1.p.5">Here are some tests for various things which are not sentence endings, and should not be fixed up with double spaces: Some titles (which actually shouldn't all have a final dot according to some grammar rules, but nevermind...): Mr. Jones said hello to Mrs. Smith and Messrs. Costeau &amp; Filou.  We might also look at some other examples, e.g. (without the correct comma following the final dot) military titles like Lt. Anderson, and others, viz. Prof. Foo and Dr. Barbara.  We have however been requested to generate end-of-sentence spacing for things like this sentence: OCB encryption protects the confidentiality of P and the authenticity of A, N, and P.  This is obviously in conflict with the correct rendering of Anon Y. Name, so a workaround for that case, with &amp;nbsp; will have to be used for correct rendering.  End of test.  </p>

cli/tests/valid/section.html

@@ -136,4 +136,4 @@ <h1 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1.</a> Synthesizer S
 
 <p id="rfc.section.3.1.1.p.4">MRCPv2 clients and servers MUST support the 'multipart/mixed' media type. This is the appropriate media type to use when providing a mix of URI and inline speech data. Embedded within the multipart content block, there MAY be content for the 'text/uri-list', 'application/ssml+xml', and/or 'text/plain' media types. The character set and encoding used in the speech data is specified according to standard media type definitions. The multipart content MAY also contain actual audio data. Clients may have recorded audio clips stored in memory or on a local device and wish to play it as part of the SPEAK request. The audio portions MAY be sent by the client as part of the multipart content block. This audio is referenced in the speech markup data that is another part in the multipart content block according to the 'multipart/mixed' media type specification.</p>
 
-<p id="rfc.section.3.1.1.p.5">Here are some tests for various things which are not sentence endings, and should not be fixed up with double spaces: Some titles (which actually shouldn't all have a final dot according to some grammar rules, but nevermind...): Mr. Jones said hello to Mrs. Smith and Messrs. Costeau &amp; Filou.  We might also look at some other examples, e.g. (without the correct comma following the final dot) military titles like Lt. Anderson, and others, viz. Prof. Foo and Dr. Barbara. We also should test things like Anon Y. Name. End of test.  </p>
+<p id="rfc.section.3.1.1.p.5">Here are some tests for various things which are not sentence endings, and should not be fixed up with double spaces: Some titles (which actually shouldn't all have a final dot according to some grammar rules, but nevermind...): Mr. Jones said hello to Mrs. Smith and Messrs. Costeau &amp; Filou.  We might also look at some other examples, e.g. (without the correct comma following the final dot) military titles like Lt. Anderson, and others, viz. Prof. Foo and Dr. Barbara.  We have however been requested to generate end-of-sentence spacing for things like this sentence: OCB encryption protects the confidentiality of P and the authenticity of A, N, and P.  This is obviously in conflict with the correct rendering of Anon Y. Name, so a workaround for that case, with &amp;nbsp; will have to be used for correct rendering.  End of test.  </p>

cli/tests/valid/section.nroff

@@ -302,4 +302,9 @@ grammar rules, but nevermind...): Mr. Jones said hello to Mrs. Smith
 and Messrs. Costeau & Filou.  We might also look at some other
 examples, e.g. (without the correct comma following the final dot)
 military titles like Lt. Anderson, and others, viz. Prof. Foo and Dr.
-Barbara.  We also should test things like Anon Y. Name.  End of test.
+Barbara.  We have however been requested to generate \%end-of-sentence
+spacing for things like this sentence: OCB encryption protects the
+confidentiality of P and the authenticity of A, N, and P.  This is
+obviously in conflict with the correct rendering of Anon Y.  Name, so
+a workaround for that case, with   will have to be used for
+correct rendering.  End of test.

cli/tests/valid/section.raw.txt

@@ -257,4 +257,9 @@
    and Messrs. Costeau & Filou.  We might also look at some other
    examples, e.g. (without the correct comma following the final dot)
    military titles like Lt. Anderson, and others, viz. Prof. Foo and Dr.
-   Barbara.  We also should test things like Anon Y. Name.  End of test.
+   Barbara.  We have however been requested to generate end-of-sentence
+   spacing for things like this sentence: OCB encryption protects the
+   confidentiality of P and the authenticity of A, N, and P.  This is
+   obviously in conflict with the correct rendering of Anon Y.  Name, so
+   a workaround for that case, with   will have to be used for
+   correct rendering.  End of test.

cli/tests/valid/section.txt

@@ -257,4 +257,9 @@
    and Messrs. Costeau & Filou.  We might also look at some other
    examples, e.g. (without the correct comma following the final dot)
    military titles like Lt. Anderson, and others, viz. Prof. Foo and Dr.
-   Barbara.  We also should test things like Anon Y. Name.  End of test.
+   Barbara.  We have however been requested to generate end-of-sentence
+   spacing for things like this sentence: OCB encryption protects the
+   confidentiality of P and the authenticity of A, N, and P.  This is
+   obviously in conflict with the correct rendering of Anon Y.  Name, so
+   a workaround for that case, with   will have to be used for
+   correct rendering.  End of test.