On Sat, Oct 23, 2010 at 11:44 AM, Juan Acevedo
wrote:
> Thanks Vafa, working like a charm now
>
> For the common good:
> commenting out the line
>
>
> \...@ifclassloaded{book}{\@ifpackageloaded{flowfram}{}{\input{book-xetex-bidi.def}}}{}
>
> in xetex-bidi.def
>
> seems to solve (at least some) cur
Thanks Vafa, working like a charm now
For the common good:
commenting out the line
\...@ifclassloaded{book}{\@ifpackageloaded{flowfram}{}{\input{book-xetex-bidi.def}}}{}
in xetex-bidi.def
seems to solve (at least some) current conflicts between bidi (via arabxetex)
and titlesec, even with a co
there is a change file for titlesec in bidi but since it is not yet complete
and perfect, it is not loaded. Can you try a minimal file using just bidi
and titlesec, no polyglossia, no arabxetex and see if this issue happens
there too.
--
بسی رنج بردم در این سال سی عَجَم زنده کردم بدین پا
Juan Acevedo wrote:
Hello everyone,
I wonder if anyone has a solution or workaround for the ongoing bidi--titlesec
clash?
I tried it here --- with \setotherlanguage{arabic}, your formatting
(roman, centered, tiny) is overridden by something. My guess is it's in
polyglossia, since that
Hello everyone,
I wonder if anyone has a solution or workaround for the ongoing bidi--titlesec
clash?
I had set a book last year, in English with lots of Arabic, and it was running
fine a few months ago. Now titlesec stops working as soon as I load either
arabxetex or polyglossia+arabic, so I
