IssueTracker

Issue summary: Customer has been using the HTML translation directly on their website and has been working fine until last 2019.

Input (8 span tags):

<div>
<span>We played it for the first time but the</span>

<span>developers conference in June and</span>

<span>I wanted to open with it this morning because</span>

<span>I think it does such an incredible</span>

<span>job of talking about our values.</span>

<span>It reflects the unique way that Apple creates</span>

<span>what we believe are the very best</span>

<span>products in the world.</span>

</div>

Expected Output (8 span tags):

<div>
<span>Lo jugamos por primera vez, pero la</span>

<span>conferencia de desarrolladores en Junio y</span>

<span>quería abrir con él esta mañana porque</span>

<span>creo que hace un trabajo increíble</span>

<span>al hablar de nuestros valores.</span>

<span> Refleja la forma única en que Apple crea</span>

<span>lo que creemos que son los mejores</span>

<span>productos del mundo.</span>

</div>

Actual Output on the newest release (early 2020)(10 span tags):

<div>
<span>La tocamos por primera vez, pero la</span>

<span>conferencia de desarrolladores en junio y</span>

<span>yo queríamos abrir con ella esta mañana porque</span>

<span>creo que hace un</span>

<span>trabajo</span>

<span>increíble</span>

<span>de hablar de nuestros valores.</span>

<span>Refleja la forma única en que Apple crea</span>

<span>lo que creemos son los mejores</span>

<span>productos en el mundo.</span>

</div>
This new behavior (adding new HTML tags) is causing differences producing missalignments on the customer web page.

It would be really nice to have an option on the Translation API that could maintain the older HTML reconstruction behavior as well as the same context as the original text (something like --nohtmlbreaking).