kvafa / bidi

Bidirectional typesetting in plain TeX and LaTeX, using XeTeX
https://ctan.org/pkg/bidi
6 stars 1 forks source link

lettrine-xetex-bidi.def outdated #31

Open dflipo opened 1 year ago

dflipo commented 1 year ago

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

Minimal example showing the issue

% !TEX TS-program = XeLaTeX
% !TEX encoding = UTF-8 Unicode

\documentclass{article}            % or some other class

  % Any packages other than the bidi package must be loaded here
\usepackage{lettrine}

  % The bidi package must be loaded as the last package
\usepackage{bidi}

  % Any preamble code goes here

\begin{document}

 \lettrine{V}{oici} un exemple 

\end{document}

Expected behavior

Log and PDF files

! Undefined control sequence.

\LettrineFont \L@initial
kvafa commented 11 months 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.

EliseyP commented 6 months ago

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.

dflipo commented 6 months ago

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.

EliseyP commented 6 months ago

Thank you!
Yes, it was some kind of "dirty hacking" - I had to compile my task urgently.