RE: Lots of undefined control sequences when using Arabic Babel

This doesn't correct the UTF-8 errors. This is supposed to correct them or only ensuring compilation upon recovery of errors?
________________________________
De : David Carlisle <[email protected]>
Envoyé : dimanche 12 mai 2024 15:56
À : outlook user <[email protected]>
Cc : [email protected] <[email protected]>
Objet : Re: Lots of undefined control sequences when using Arabic Babel

\beginR is a xetex (tex-xet) command: it is not expected to be defined in luatex. Also as commented on your other message
you seem to have somehow forced xetex processing with lualatex as the inputenc error you showed should
only have occurred with xetex. If you use \usepackage{babel} \babelprovide{arabic} things should go more smoothly.

David


On Sun, 12 May 2024 at 14:43, outlook user <[email protected]<mailto:[email protected]>> wrote:
> The compiler is having trouble understanding a command you have used. Check that the command is  spelled correctly. If the command is part of a package, make sure you have included the package in your preamble using \usepackage{...}.
> Learn more
> \Arabi@rl@everypar ...setbox \z@ \lastbox \beginR
>                                                    \usebox \z@ }\fi
> l.1452 -
>       --
> The control sequence at the end of the top line
> of your error message was never \def'ed. If you have
> misspelled it (e.g., `\hobx'), type `I' and the correct
> spelling (e.g., `I\hbox'). Otherwise just continue,
> and I'll forget about whatever was undefined.


On version 1.16.0 of LuaHBTeX from TeX Live distribution version 2023 using LUALaTeX 2023.8.28. It appears when `\usepackage{babel}` is modified to `\usepackage[arabic]{babel}`

It seems like he expects all commands to be written in Arabic, or maybe he has lost TeX definitions and don't know any commands anymore, or is misinterpreting anything. Anyway, many classic La/TeX commands are interpreted as unknown control sequences