Re: okular "cannot find latex executable"
On Wednesday, April 18, 2018 8:09:57 AM CEST Andrey Rahmatullin wrote: > On Wed, Apr 18, 2018 at 04:07:21AM +0200, inkbottle wrote: > > But then, what happens for me, even though I've installed the "suggested" > > texlive-binaries, and rebooted in between, is that I get a message saying > > "cannot find latex executable". > > Well, texlive-binaries doesn't install latex. You probably need > texlive-latex-base. I installed texlive-latex-base as you suggested; which btw is not in any dependency chain with Okular; and rebooted, one is never too sure. Now I've got a different error message: "A problem occurred during the execution of the 'latex' command" The text in my inline note is: hello $$a$$. When I click on "details", there are no additional details.
Re: okular "cannot find latex executable"
On Wednesday, April 18, 2018 4:30:23 PM CEST you wrote:
> On Wednesday, April 18, 2018 8:09:57 AM CEST Andrey Rahmatullin wrote:
> > On Wed, Apr 18, 2018 at 04:07:21AM +0200, inkbottle wrote:
> > > But then, what happens for me, even though I've installed the
> > > "suggested"
> > > texlive-binaries, and rebooted in between, is that I get a message
> > > saying
> > > "cannot find latex executable".
> >
> > Well, texlive-binaries doesn't install latex. You probably need
> > texlive-latex-base.
>
> I installed texlive-latex-base as you suggested; which btw is not in any
> dependency chain with Okular; and rebooted, one is never too sure.
>
> Now I've got a different error message:
> "A problem occurred during the execution of the 'latex' command"
>
> The text in my inline note is:
> hello $$a$$.
>
> When I click on "details", there are no additional details.
Following:
https://github.com/KDE/okular/blob/master/ui/annotwindow.cpp
I get:
https://github.com/KDE/okular/blob/2aa006fa87240a89ff8446744ccd9f86a48c8dd0/ui/latexrenderer.cpp
tempStream << "\
\\documentclass[" << fontSize << "pt]{article} \
\\usepackage{color} \
\\usepackage{amsmath,latexsym,amsfonts,amssymb,ulem} \
\\pagestyle{empty} \
\\begin{document} \
{\\color[rgb]{" << textColor.redF() << "," << textColor.greenF() << "," <<
textColor.blueF() << "} \
\\begin{eqnarray*} \
" << latexFormula << " \
\\end{eqnarray*}} \
\\end{document}";
So I searched for the packages (latex's); I thought I did the search with sid,
but re-reading myself shows different.
https://packages.debian.org/stretch/texlive-latex-base [amsmath.sty,
latexsym.sty, color.sty]
https://packages.debian.org/stretch/texlive-base [amsfont.sty]
https://packages.debian.org/stretch/texlive-generic-recommended [ulem.sty]
https://packages.debian.org/stretch/texlive-base [amssymb.sty]
After the install of that I get:
"Cannot find dvipng executable"
There is a package of that name, so I installed it.
And Voilà!
Therefore, for the one thing it might be suitable to put those 5 packages in
suggested dependencies of Okular; possibly through a "metapackage", for
simplification, and ease of removal.
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/2aa006fa87240a89ff8446744ccd9f86a48c8dd0/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.
Re: okular "cannot find latex executable"
El miércoles, 18 de abril de 2018 12:31:28 -03 inkbottle escribió:
> On Wednesday, April 18, 2018 4:30:23 PM CEST you wrote:
> > On Wednesday, April 18, 2018 8:09:57 AM CEST Andrey Rahmatullin wrote:
> > > On Wed, Apr 18, 2018 at 04:07:21AM +0200, inkbottle wrote:
> > > > But then, what happens for me, even though I've installed the
> > > > "suggested"
> > > > texlive-binaries, and rebooted in between, is that I get a message
> > > > saying
> > > > "cannot find latex executable".
> > >
> > > Well, texlive-binaries doesn't install latex. You probably need
> > > texlive-latex-base.
> >
> > I installed texlive-latex-base as you suggested; which btw is not in any
> > dependency chain with Okular; and rebooted, one is never too sure.
> >
> > Now I've got a different error message:
> > "A problem occurred during the execution of the 'latex' command"
> >
> > The text in my inline note is:
> > hello $$a$$.
> >
> > When I click on "details", there are no additional details.
>
> Following:
> https://github.com/KDE/okular/blob/master/ui/annotwindow.cpp
>
> I get:
> https://github.com/KDE/okular/blob/2aa006fa87240a89ff8446744ccd9f86a48c8dd0/
> ui/latexrenderer.cpp
>
> tempStream << "\
> \\documentclass[" << fontSize << "pt]{article} \
> \\usepackage{color} \
> \\usepackage{amsmath,latexsym,amsfonts,amssymb,ulem} \
> \\pagestyle{empty} \
> \\begin{document} \
> {\\color[rgb]{" << textColor.redF() << "," << textColor.greenF() << "," <<
> textColor.blueF() << "} \ \\begin{eqnarray*} \
> " << latexFormula << " \
> \\end{eqnarray*}} \
> \\end{document}";
>
> So I searched for the packages (latex's); I thought I did the search with
> sid, but re-reading myself shows different.
>
> https://packages.debian.org/stretch/texlive-latex-base [amsmath.sty,
> latexsym.sty, color.sty] https://packages.debian.org/stretch/texlive-base
> [amsfont.sty]
> https://packages.debian.org/stretch/texlive-generic-recommended [ulem.sty]
> https://packages.debian.org/stretch/texlive-base [amssymb.sty]
>
> After the install of that I get:
> "Cannot find dvipng executable"
>
> There is a package of that name, so I installed it.
>
> And Voilà!
>
> Therefore, for the one thing it might be suitable to put those 5 packages in
> suggested dependencies of Okular; possibly through a "metapackage", for
> simplification, and ease of removal.
First of all, thanks *a lot* for doing the research. For the above please file
a bug so the maintainer can take note.
> 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/2aa006fa87240a89ff8446744ccd9f86a48c8dd0/
> 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?
--
My favourite poem is the one that starts 'Thirty days hath September' because
it actually tells you something.
-- Groucho Marx
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.
Re: okular "cannot find latex executable"
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/2aa006fa87240a89ff8446744ccd9f86a48c8dd0/ >> 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. -- Luigi
