That works. Thanks!
On 12/08/19 13:09, Adam McCollum wrote:
Hi Nathan,
Others may have more to say, but I happen to have looked around
yesterday due to the same problem and found that putting the line
below in the preamble seems to solve the problem:
\let\aemph\veryundefinedcommand
Best wishes,
Adam
On Aug 18, 2012, at 11:02 PM, Nathan Sidoli wrote:
Is it possible to use polyglossia with arabxetex? It seems that both
of them define the command \aemph. Since they both define it in the
same way, it doesn't really matter, but it would be nice if there
were no error message. Maybe each of them could be made to check if
the command is already defined. Or is there some way to manually
clear the definition before calling in the a later package.
Below is a minimal example.
Thanks,
Nathan
\documentclass[12pt,a4paper]{article}
\usepackage{polyglossia}
\setdefaultlanguage{french}
\usepackage{fontspec}
\setmainfont[Mapping=tex-text]{Junicode}
\usepackage[novoc,fdf2noalif]{arabxetex}
\newfontfamily\arabicfont[Script=Arabic,Scale=1,WordSpace=2]{Amiri}
\newcommand{\A}{\textarabic}
\begin{document}
Nous adoptons {\it al-mu\b ht\=ariq\/} pour les raisons de sens et de
graphie: {\it i\b htaraqa \/} = inventer un mensonge [$\,$Fl\"ugel a
\A{m.hrrq}$\,$; mais une autre lecture serait \A{m_hrrf}$\,$, <<
charlatan~>>$\,$].
\end{document}
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
Adam McCollum, Ph.D.
Skype: adam.bar.yona
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
