No problem, I did and pushed the clean-up you have required. There is nothing to move to the French translation, as this was extra material that I had only contributed yet in the French version while doing the translation, and that needed to be propagated to the English version, and to make this easier (like re-finding in the French version the whole context) I had included this text in ignored block in addition to have some comment indicated need for re-alignment.

De : emacs-devel-bounces+vincent.b.1=hotmail.fr@gnu.org <emacs-devel-bounces+vincent.b.1=hotmail.fr@gnu.org> de la part de Eli Zaretskii <eliz@gnu.org>
Envoyé : lundi 1 janvier 2024 17:09
À : Vincent Belaïche <vincent.b.1@hotmail.fr>
Cc : jean.christophe.helary@traductaire-libre.org <jean.christophe.helary@traductaire-libre.org>; stefankangas@gmail.com <stefankangas@gmail.com>; emacs-devel@gnu.org <emacs-devel@gnu.org>; rms@gnu.org <rms@gnu.org>
Objet : Re: SES manual French translation (Re: Where to contribute manual translations ?)

> From: Vincent Belaïche <vincent.b.1@hotmail.fr>
> CC: Eli Zaretskii <eliz@gnu.org>, "stefankangas@gmail.com"
> <stefankangas@gmail.com>, "emacs-devel@gnu.org" <emacs-devel@gnu.org>,
> Richard Stallman <rms@gnu.org>
> Date: Mon, 1 Jan 2024 15:40:57 +0000
>
> >Even if they're tagged as @ignore, I'm not sure that's good practice
> >for potential translators to other languages.
>
> I did it this way, in order to keep both contents aligned and do not
> loose any contributed text, whatever is between « @ignore » … « @end
> ignore » anyway does not go to the output document, this remains only in
> the source code. Note that in addition of the « @ignore » I've put a
> TODO comment for the translator to know that there is some re-alignment
> to do.

I understand, but please don't do that. Please move this to the
French translation, and if you need to copy the English text or have a
reference to it, that's fine. The English source of ses.texi should
not have any text that is specific to some translation of it, it is
incorrect to do that, and we should fix that ASAP.

Thanks.