Am Sonntag, dem 02.04.2023 um 13:21 +0200 schrieb Jürgen Spitzmüller:
> This needs some effort. For the time being, I think we will be better
> off with this rather harmless info message.
Possible approach attached.
--
Jürgen
diff --git a/src/Paragraph.cpp b/src/Paragraph.cpp
index c43421b376..4
Am Mittwoch, dem 22.03.2023 um 23:21 + schrieb Udicoudco:
> > > I attached a possible patch, it only fix the lstlisting case when
> > > polyglossia is used, since babel-hebrew does not have an
> > > equivalent
> > > to \begin{RTL}...\end{RTL} (or there is one?) and babel with
> > > luatex
> > >
On Wed, Mar 22, 2023 at 10:28 PM Udicoudco wrote:
>
> > I attached a possible patch, it only fix the lstlisting case when
> > polyglossia is used, since babel-hebrew does not have an equivalent
> > to \begin{RTL}...\end{RTL} (or there is one?) and babel with luatex
> > does not need this kind of w
> I attached a possible patch, it only fix the lstlisting case when
> polyglossia is used, since babel-hebrew does not have an equivalent
> to \begin{RTL}...\end{RTL} (or there is one?) and babel with luatex
> does not need this kind of wrappers.
I've added line breaks to the LaTeX code for
readabi
On Wed, Mar 22, 2023 at 2:22 PM Scott Kostyshak wrote:
>
> On Wed, Mar 22, 2023 at 01:13:27PM +0100, Jürgen Spitzmüller wrote:
> > Am Mittwoch, dem 22.03.2023 um 12:54 +0200 schrieb Udicoudco:
> > > I think in the case of where forceLTR insets will have multiple
> > > paragraphs, it is better to u
On Wed, Mar 22, 2023 at 01:13:27PM +0100, Jürgen Spitzmüller wrote:
> Am Mittwoch, dem 22.03.2023 um 12:54 +0200 schrieb Udicoudco:
> > I think in the case of where forceLTR insets will have multiple
> > paragraphs, it is better to use
> > \begin{RTL}...\end{RTL}, which basically only issues \par a
Am Mittwoch, dem 22.03.2023 um 12:54 +0200 schrieb Udicoudco:
> I think in the case of where forceLTR insets will have multiple
> paragraphs, it is better to use
> \begin{RTL}...\end{RTL}, which basically only issues \par and sets
> the
> RTL related conditionals
> to be false.
Thanks for the deta
Slight correction, the lines
>
> \@RTLfalse\beginL{
> \begin{lstlisting}
> Hello
> \end{lstlisting}
> }\endL
>
should be
{\@RTLfalse\beginL
\begin{lstlisting}
Hello
\end{lstlisting}
}\endL
and the lines
>
> \@RTLfalse\beginL{
> \par
> Hello
> \par
> }\endL
>
should be
{\@RTLfalse\beginL
On Tue, Mar 21, 2023 at 9:40 PM Scott Kostyshak wrote:
>
> On Tue, Mar 21, 2023 at 12:50:06PM +0100, Jürgen Spitzmüller wrote:
> > Am Dienstag, dem 21.03.2023 um 11:27 + schrieb Udicoudco:
> > > Hello all,
> > >
> > > Attached a LyX file and its export to LaTeX code.
> > > When compiling with
On Tue, Mar 21, 2023 at 12:50:06PM +0100, Jürgen Spitzmüller wrote:
> Am Dienstag, dem 21.03.2023 um 11:27 + schrieb Udicoudco:
> > Hello all,
> >
> > Attached a LyX file and its export to LaTeX code.
> > When compiling with XeLaTeX the exported code
> > I get the warning:
> >
> > \endL o
Am Dienstag, dem 21.03.2023 um 11:27 + schrieb Udicoudco:
> Hello all,
>
> Attached a LyX file and its export to LaTeX code.
> When compiling with XeLaTeX the exported code
> I get the warning:
>
> \endL or \endR problem (0 missing, 1 extra) in paragraph at lines
> 26--27
Interestingly,
Hello all,
Attached a LyX file and its export to LaTeX code.
When compiling with XeLaTeX the exported code
I get the warning:
\endL or \endR problem (0 missing, 1 extra) in paragraph at lines 26--27
If I replace
\LRE{
\begin{lstlisting}
Hello
\end{lstlisting}
}
With
\begin{LTR}
\begin{ls
12 matches
Mail list logo
