Am Freitag, den 21.08.2020, 19:06 +0200 schrieb Kornel Benko: > This version does hang. Switch the commented documentclass, and now > the compilation does not hang.
It boils down to the order of hebrew and farsi (or arabic):
====
\documentclass[
hebrew,% breaks
farsi,% or: arabic
% hebrew,% compiles
english]{article}
\usepackage[LAE,LFE,T1]{fontenc}
\usepackage[cp1255,utf8,latin9]{inputenc}
\usepackage{babel}
\begin{document}
Hello.
\end{document}
====
If Hebrew comes after farsi and arabic, it compiles, if it precedes, it
breaks with the following error (which is only ssen when compiling
manually):
! Argument of \o@everypar has an extra }.
<inserted text>
\par
l.126 \n@everypar\expandafter{\the\o@everypar}
My guess is that arabicore.sty (use by Farsi and Arabic) and
lhbabel.def (used by Hebrew) redefine \everypar in incompatible ways.
What we can do is to assure that hebrew is always output after arabic
and farsi. But this of course only works if Arabic or Farsi are not the
main language.
I can try and file a report, but both Arabi and babel-hebrew don't have
seen updates for a long time.
Jürgen
signature.asc
Description: This is a digitally signed message part
-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
