Wow, nice community: lots of hints here in the past few messages.
Please forgive my elaborate writing in this post: I do this merely to help other users in the future who tend to search for solutions, to make this story absolutely not vague.
hulf2012 wrote:If you look at the INX file of that extension,you will recognize the path to the dependencies. Maybe there is the mistake, or the dependencies path changed.
As expected, the inx file of both textext as well as the builtin plugin refer simply to programs that are either in the extensions directory or on the path. Example for the
eqtexsvg builtin:
Code: Select all
<_name>LaTeX formula</_name>
<id>org.inkscape.effect.eqtexsvg</id>
<dependency type="executable" location="extensions">eqtexsvg.py</dependency>
<dependency type="executable" location="extensions">inkex.py</dependency>
<dependency type="executable" location="path">latex</dependency>
<dependency type="executable" location="path">dvips</dependency>
<dependency type="executable" location="path">pstoedit</dependency>
And I assume that location="path" implies that the $PATH variable will be searched (both on Linux as well as Windows with its path). So it's still unclear why inkscape 0.48.3.1 says those dependencies are not present, when they are.
That being said, on an another machine (Linux Mint Debian Edition (3.11-2-amd64 #1 SMP Debian 3.11.8-1 (2013-11-13) x86_64 GNU/Linux)) which has a slightly higher version of inkscape ("Inkscape 0.48.4 r9939 (Aug 16 2013)", from the default repositories), the built-in extension
does work, provided I change my default interpreter to python2, even though it generates an information message easily interpreted for an error message:
Inkscape has received additional data from the script executed. The script did not return an error, but this may indicate the results will not be as expected.
Summary: it works fine on that machine.
hulf2012 wrote:I understand that you have LaTeX distribution (TexLive?), installed on your machine. Maybe there is something I'm missing but It's better to install the distribution package than parts of that (pstoedit,Latex, dvi, etc).
Correct, I have texlive installed from the default repositories, which of course took care of the dependencies for me. So there's no issue there.
hulf2012 wrote:If you solve your problem (or a workaround) let us know
My workaround was to install textext on the first machine and ensure that python2.x was the default interpreter (the current version of textext uses several python2.x constructs that will generate SyntaxErrors in python3). However, for that Ubuntu machine, there's an easier solution if one really wants to go with the built-in plugin, as mentioned by Moini in his post here:
That seems like a good idea on my Ubuntu machine. Won't try it on my LMDE though, since it wasn't made for that and problems can be expected in that case. When this problem popped up in the past week, I hadn't found out about this PPA yet.
... a few minutes later...
Checked! Using that PPA, I now have Inkscape 0.91 r (Jan 30 2015), on which the default plugin works just fine (note that no extra packages were installed, so the dependencies listed in my first post were still where they were normally, i.e. on the path. Problem solved.
brynn wrote:One last suggestion for getting the LaTex capability, would be to install the last stable version, which is 0.48.5 (or whatever is the last one where it worked). You would not have to uninstall 0.91. Just install the other version in a different directory.
Well, as mentioned above, a slightly later version works fine, but it's an install on a different machine (LMDE vs Ubuntu 12.04). All I can say is that the "eqtexsvg.inx" file is identical on both machines, so it's kind of peculiar that one install generates path-related errors in the "extension-errors.log" as both distros have the required packages on their path. Perhaps it's a bug that got ironed out when transitioning from 0.48.3.1 to 0.48.4 r9939. Of course, your suggestion and that of Moini are the best: simply get the latest available package, and after 10 or so years on Linux, I should have known that too. It just didn't occur to me.
brynn wrote:I would suggest contacting developers about making extensions python3-ready. Can do either via mailing list (devel or user)
https://inkscape.org/en/download/ or via IRC channel
https://inkscape.org/en/community/discussion/.
I suspect that any work you can contribute to the project will be warmly and happily welcomed.....Unless there is some technical issue with python3, which I'm not aware of (because I'm generally not very technically aware, and not because I have some particular idea that there might be some issue).
Good suggestions, thanks for the pointer. I'll follow up on it, would be happy to contribute a bit to the open-source community.
Thank you for the link. I'm not familiar yet with the wealth of information for inkscape online, so it would have taken me some time to find it. Much appreciated.