First time tried using the autotranslate.
Added API key and enabled, went to record and triggered the auto translation.
Mostly the entry was translated without issue, but the RTE field (redactor) was translated but inherited spurious returns.

Source text:

<p>Nuestros expertos en Magento, Prestashop, Wordpress y WooCommerce 
están a tu disposición, para que no tengas que preocuparte de problemas 
técnicos y puedas centrarte en tareas más productivas para tu negocio.</p>
<ul>
                        <li> <strong>Te complementamos: </strong>Nuestros
 técnicos son programadores especializados que pueden encargarse del 
soporte a tus clientes y otras tareas técnicas que te interese delegar. 
No pierdas tu valioso tiempo con problemas técnicos, caídas, ataques de 
hackers, etc.</li>
                        <li> <strong>Tú mandas: </strong>Tú
 decides si nuestros técnicos hablan directamente con tus clientes o 
gestionamos todo a través de tu agencia. Nos adaptamos a tus 
instrucciones.</li>
                        <li> <strong>Contacta por la vía que prefieras: </strong>Estamos
 disponibles por email, chat y teléfono, también con servicio de 
emergencias. Todo el apoyo que necesitas para que un problema técnico no
 te amargue el día ni te haga perder clientes.</li>
                    </ul>

The translated version ended up like this:

<p>Our Magento, Prestashop, Wordpress and WooCommerce experts are at your disposal, so you don't have to worry about problems.
are at your disposal, so that you don't have to worry about technical
technical issues and you can focus on more productive tasks for your business.
</p>
<ul>
                        <li> <strong>We complement you:</strong>Our
 technicians are specialized programmers who can take care of customer support and
support to your customers and other technical tasks that you want to delegate.
Do not waste your valuable time with technical problems, crashes, hacker attacks, etc..
hacker attacks, etc.</li> <li>
                        <br></li><li> <strong>You're in charge:</strong>You
 decide if our technicians talk directly with your customers or if we manage everything
we manage everything through your agency. We adapt to your
instructions.</li> <li>
                        <br></li><li> <strong>Contact us by the way you prefer: </strong>We are available by email, chat and phone.
 available by email, chat and phone, also with emergency service.
emergencies. All the support you need so that a technical problem does not make your day or
 make your day bitter or make you lose customers.</li>.
                    </ul>

You will see that the translated version has added
fields.

I have worked with DeepL on similar issues with my own Auto-Translate add-on and if I recall rightly this is an issue within DeepL’s API but can be controlled via the settings used to initiate the translation. However, without diving into your code I am not sure whether similar fixes can work with your setup.

Anyhow - as it stands this is an issue / bug - grateful for any guidance you can give on how it might be resolved.

Currently working on a Laravel Valet local host, so cannot provide remote access to the server - but if this is necessary to resolve let me know and I’ll move it onto a staging server you can access. However, if it is the bug I think it is, you should be able to replicate / its a DeepL issue…

Thanks!

PS - separate point - on Firefox (105) on macOS 12.6 this page renders with black background colour making the location of all content fields impossible to see - need to click around to find the fields. Not sure if this is a bug or style choice, but not helpful.