LyX ⇒ Problem with including lyx documents in Farsi
Problem with including lyx documents in Farsi
I am using XeTex for writing Farsi language documents in Lyx. Everything works fine as long as I have all my text within one document. But as soon as I include another Lyx file as a child document, I get an error:
\textFR
{%
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.
I exported the latex (XeTex) code from Lyx and when I look at it I see Lyx adds a \textFR{% command at the beginning of the included file. This is where the error message comes from.
All I need is a way to prevent Lyx from adding \textFR at the beginning of Farsi child documents.
I would appreciate it if somebody can help me to resolve this issue.
NEW: TikZ book now 40% off at Amazon.com for a short time.
And: Currently, Packt sells ebooks for $4.99 each if you buy 5 of their over 1000 ebooks. If you choose only a single one, $9.99. How about combining 3 LaTeX books with Python, gnuplot, mathplotlib, Matlab, ChatGPT or other AI books? Epub and PDF. Bundle (3 books, add more for higher discount): https://packt.link/MDH5p
- Stefan Kottwitz
- Site Admin
- Posts: 10335
- Joined: Mon Mar 10, 2008 9:44 pm
Problem with including lyx documents in Farsi
welcome to the forum!
For
\textFR
you would need to install and to use the arabi package.Alternatively, if you just would like to deactivate it, you could define in your preamble
Code: Select all
\let\textFR\relax
Code: Select all
\newcommand{\textFR}[1]{#1}
Re: Problem with including lyx documents in Farsi

-
- Site Moderator
- Posts: 542
- Joined: Sat Sep 01, 2012 6:38 am
Re: Problem with including lyx documents in Farsi
can you please make a bug report on http://www.lyx.org/trac with a minimal example that shows the problem? I know that this would take some of your time to produce, but it would help us a lot since we do not have a lot of feedback from users of Farsi so there are bugs that we just don't know about and thus can't fix. I think this is one of them.
I'm glad you got a solution to the problem!
scott