Re: okular "cannot find latex executable"
On Thursday, April 19, 2018 9:38:57 PM CEST you wrote:
> inkbottle ha scritto:
> > On Thursday, April 19, 2018 3:22:26 PM CEST Lisandro Damián Nicanor Pérez
> >
> > Meyer wrote:
> >> El miércoles, 18 de abril de 2018 16:38:37 -03 Luigi Toscano escribió:
> >>> Lisandro Damián Nicanor Pérez Meyer ha scritto:
> >>>> El miércoles, 18 de abril de 2018 12:31:28 -03 inkbottle escribió:
> >>>>> However the resulting Okular behavior is far from satisfactory:
> >>>>> The inline note shows only the latex code: in order to see the result
> >>>>> of
> >>>>> it, one has to first double click the inline note, and then to click
> >>>>> on
> >>>>> "render latex code"; which is far from providing an immediate and
> >>>>> intuitive view of the formulas.
> >>>>>
> >>>>> However, again, that could be use to compensate that poppler's utf8
> >>>>> related
> >>>>> bug: https://bugs.freedesktop.org/show_bug.cgi?id=65956
> >>>>>
> >>>>> Provided one possibly modify
> >>>>> https://github.com/KDE/okular/blob/2aa006fa87240a89ff8446744ccd9f86a48
> >>>>> c
> >>>>> 8d
> >>>>> d0/ ui/latexrenderer.cpp through the addition of latex packages to
> >>>>> render
> >>>>> desired fonts;
> >>>>> not sure it is so easy, but is is probably easier than fixing a 5
> >>>>> years
> >>>>> old
> >>>>> poppler's bug.
> >>>>
> >>>> Maybe suggesting this to upstream?
> >>>
> >>> It would not fix the bug anyway: you don't want to strictly depend on a
> >>> (huge deployment of) latex for this.
> >>
> >> Indeed, this is true.
> >
> > So it boils done to a functionality: not very useful, not working very
> > well, and enabling it could clutter the system.
> >
> > Which lead to a very straightforward bug reporting course of action: doing
> > noting. I like it.
>
> What I don't like it is when someone reads what I didn't write.
> I didn't say that that adding an optional dependency on latex is a problem.
> I wrote that this is not *the* solution, because most of the deployments
> don't, won't and can't have latex.
There might have been some misunderstanding; surely nothing improper was
meant.
But you made your point about that a LaTeX deployment cannot be assumed
generally speaking.
At the end of the day I don't see there is much ground for a bug report,
either on debian side or upstream; but then I might be mistaken.
Reply to: