On Wed, 13 Oct 2021 at 16:35, Pavel Sanda wrote:
> On Wed, Oct 13, 2021 at 03:12:02PM +0200, Thibaut Cuvelier wrote:
> > On Wed, 13 Oct 2021 at 15:07, Pavel Sanda wrote:
> >
> > > On Wed, Oct 13, 2021 at 02:33:47PM +0200, Thibaut Cuvelier wrote:
> > > > The only solution I could find is to use t
On Wed, Oct 13, 2021 at 03:12:02PM +0200, Thibaut Cuvelier wrote:
> On Wed, 13 Oct 2021 at 15:07, Pavel Sanda wrote:
>
> > On Wed, Oct 13, 2021 at 02:33:47PM +0200, Thibaut Cuvelier wrote:
> > > The only solution I could find is to use the existing mechanism to
> > generate
> > > preview images.
On Wed, 13 Oct 2021 at 15:07, Pavel Sanda wrote:
> On Wed, Oct 13, 2021 at 02:33:47PM +0200, Thibaut Cuvelier wrote:
> > The only solution I could find is to use the existing mechanism to
> generate
> > preview images. This way, the LaTeX code is transformed into an
> > intelligible form (i.e. an
On Wed, Oct 13, 2021 at 02:33:47PM +0200, Thibaut Cuvelier wrote:
> The only solution I could find is to use the existing mechanism to generate
> preview images. This way, the LaTeX code is transformed into an
> intelligible form (i.e. an image), while still keeping the original LaTeX
> code if som
Dear list,
Subject: https://www.lyx.org/trac/ticket/12372
In the last few weeks, I've been working on a fix for #12372. Basically,
the user complained that some random LaTeX code is not properly rendered in
the DocBook output. The problem is that this is really arbitrary LaTeX code
quite remote f
