Open dflipo opened 1 year ago
Thanks for your bug report. Sure, I will certainly look into this but I'm afraid that will not be anytime soon as I am occupied by other things currently.
May be this post is answer?
https://github.com/kvafa/bidi/issues/13#issuecomment-1915377726
This lettrine-xetex-bidi.def in texmf-local/tex/xelatex/bidi
solve this problem for me.
NO, this file is incompatible with the current version of lettrine.sty [2024/01/20 v.2.60]. Lettrine.sty is aware of bidi now. Please consider replacing lettrine-xetex-bidi.def by the appended (zipped) version. lettrine-xetex-bidi.zip
Patching an internal command of lettrine.sty (which is liable to change) is definitely not the way to go.
Thank you!
Yes, it was some kind of "dirty hacking" - I had to compile my task urgently.
Brief outline of the issue
lettrine-xetex-bidi.def patches an old definition of the internal command \@lettrine of the lettrine package leading to issues with the current implementation.
Rather than updating the patched definition in lettrine-xetex-bidi.def, I suggest to include the RTL flag mechanism for the \parshape command in the original definition of \@lettrine. I have an experimental version of lettrine.sty, appended here. Please let me know lettrine.sty.gz if something like that would enable to get rid of lettrine-xetex-bidi.def?
Check/indicate
xepersian
packagebidi
package issue tracker has been searched for similar issues?xepersian
package issue tracker has been searched for similar issues?Minimal example showing the issue
Expected behavior
Log and PDF files
! Undefined control sequence.