Inkscape. error rendering latex equation

FroL_Onn · 2017-03-20 10:26:22

Hello!

I've just installed Arch and have encountered a problem with inkscape extention for latex rendering.
When I try to render a formula the error message appears:

Traceback (most recent call last):
  File "eqtexsvg.py", line 160, in <module>
    e.affect()
  File "/usr/share/inkscape/extensions/inkex.py", line 283, in affect
    self.effect()
  File "eqtexsvg.py", line 154, in effect
    svg_open(self, svg_file)
  File "eqtexsvg.py", line 81, in svg_open
    doc = inkex.etree.parse(filename)
  File "src/lxml/lxml.etree.pyx", line 3427, in lxml.etree.parse (src/lxml/lxml.etree.c:81117)
  File "src/lxml/parser.pxi", line 1811, in lxml.etree._parseDocument (src/lxml/lxml.etree.c:117848)
  File "src/lxml/parser.pxi", line 1837, in lxml.etree._parseDocumentFromURL (src/lxml/lxml.etree.c:118195)
  File "src/lxml/parser.pxi", line 1741, in lxml.etree._parseDocFromFile (src/lxml/lxml.etree.c:117107)
  File "src/lxml/parser.pxi", line 1138, in lxml.etree._BaseParser._parseDocFromFile (src/lxml/lxml.etree.c:111653)
  File "src/lxml/parser.pxi", line 595, in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:105109)
  File "src/lxml/parser.pxi", line 706, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:106817)
  File "src/lxml/parser.pxi", line 635, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:105671)
  File "/tmp/inkscape-HqOPrw/eq.svg", line 1
lxml.etree.XMLSyntaxError: Document is empty, line 1, column 1

Am I the only one affected?
I've reported a bug HERE.

mraggi · 2017-03-30 13:50:15

I can confirm, I have the same bug.

positronik · 2017-03-30 14:38:47

Are you sure that this is an Arch problem?

BTW I use textext [aur] to render latex formulae in inkscape.
Give that a try in the meantime!

nullgeppetto · 2017-10-17 12:32:00

I just encountered a similar problem trying to instert a LaTeX expression in Inkscape. The bug reported above does not seem to provide any insight on how to solve the problem. Is this a pstoedit, python2-lxml. problem? Is it my configuration that causes the problem, or is it a bug? I also tried to use textext but it doen't work either.

 *** WARNING - the DELAYBIND command has been deprecated, and will be

               removed in the next version. For now you can restore

               the behaviour by using -dREALLYDEALYBIND but if you

               require continued use of this command you should contact

               the Ghostscript developers. Commercial customers of

               Artifex should email their support contact, free users

               are encouraged to talk to us on the #ghostscript IRC

               channel on irc.freenode.net.


Unrecoverable error: undefined in DELAYBIND

PostScript/PDF Interpreter finished. Return status 65280 executed command : /usr/bin/gs -I/home/geppetto/.fonts -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS "/tmp/psinMRKmv5"

The interpreter seems to have failed, cannot proceed !

Traceback (most recent call last):
  File "eqtexsvg.py", line 160, in <module>
    e.affect()
  File "/usr/share/inkscape/extensions/inkex.py", line 283, in affect
    self.effect()
  File "eqtexsvg.py", line 154, in effect
    svg_open(self, svg_file)
  File "eqtexsvg.py", line 81, in svg_open
    doc = inkex.etree.parse(filename)
  File "src/lxml/etree.pyx", line 3441, in lxml.etree.parse
  File "src/lxml/parser.pxi", line 1834, in lxml.etree._parseDocument
  File "src/lxml/parser.pxi", line 1860, in lxml.etree._parseDocumentFromURL
  File "src/lxml/parser.pxi", line 1764, in lxml.etree._parseDocFromFile
  File "src/lxml/parser.pxi", line 1161, in lxml.etree._BaseParser._parseDocFromFile
  File "src/lxml/parser.pxi", line 598, in lxml.etree._ParserContext._handleParseResultDoc
  File "src/lxml/parser.pxi", line 709, in lxml.etree._handleParseResult
  File "src/lxml/parser.pxi", line 638, in lxml.etree._raiseParseError
  File "/tmp/inkscape-NrMMAD/eq.svg", line 1
lxml.etree.XMLSyntaxError: Document is empty, line 1, column 1

Using textext leads to the following error:

Traceback (most recent call last):
  File "textext.py", line 210, in cb_ok
    self.callback(self.text, self.preamble_file, self.scale_factor)
  File "textext.py", line 369, in <lambda>
    converter_cls, old_node))
  File "textext.py", line 387, in do_convert
    new_node = converter.convert(text, preamble_file, scale_factor)
  File "textext.py", line 751, in convert
    self.pdf_to_svg()
  File "textext.py", line 849, in pdf_to_svg
    + pstoeditOpts)
  File "textext.py", line 596, in exec_command
    % (' '.join(cmd), p.returncode, out + err))
RuntimeError: Command pstoedit -f plot-svg /tmp/tmp8Xro0J/tmp.pdf /tmp/tmp8Xro0J/tmp.svg -dt -ssp -psarg -r9600x9600 failed (code 1): pstoedit: version 3.70 / DLL interface 108 (built: Jul 15 2017 - release build - g++ 7.1.1 20170630 - 64-bit) : Copyright (C) 1993 - 2014 Wolfgang Glunz

 *** WARNING - the DELAYBIND command has been deprecated, and will be
               removed in the next version. For now you can restore
               the behaviour by using -dREALLYDEALYBIND but if you
               require continued use of this command you should contact
               the Ghostscript developers. Commercial customers of
               Artifex should email their support contact, free users
               are encouraged to talk to us on the #ghostscript IRC
               channel on irc.freenode.net.

Unrecoverable error: undefined in DELAYBIND
PostScript/PDF Interpreter finished. Return status 65280 executed command : /usr/bin/gs -I/home/geppetto/.fonts -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS -r9600x9600 "/tmp/psin37Swos"
The interpreter seems to have failed, cannot proceed !

Last edited by nullgeppetto (2017-10-17 15:26:01)

kifuna · 2017-10-17 17:25:18

I have the same problem. As a temporary workaround I downgrade ghostscript to version 9.21 every time when I want to use LaTeX in Inkscape and afterwards revert it back to the current version 9.22. Not very convenient, I admit, but at least it re-enables LaTeX rendering in Inkscape.The problem seems to be the way the new ghostscript version handles the -dDELAYBIND flag. I guess that this needs to be fixed in pstoedit (which seems to call gs with this flag)?

nullgeppetto · 2017-10-17 18:41:50

kifuna wrote:

I have the same problem. As a temporary workaround I downgrade ghostscript to version 9.21 every time when I want to use LaTeX in Inkscape and afterwards revert it back to the current version 9.22. Not very convenient, I admit, but at least it re-enables LaTeX rendering in Inkscape.The problem seems to be the way the new ghostscript version handles the -dDELAYBIND flag. I guess that this needs to be fixed in pstoedit (which seems to call gs with this flag)?

I see, good to know that it works by downgrading a specific package. By the way, is there any open bug concerning this?

aristocrates · 2017-11-02 08:23:19

I am experiencing the same problem and I have reported a bug at https://bugs.archlinux.org/task/56202, seems like the issue might be upstream though.

cfr · 2017-11-04 04:09:37

If somebody has isolated the problem to pstoedit, that should be in the bug report. Right now, it is just reported against ghostscript and/or inkscape, but it sounds as if the issue is not with those. (And if it is an upstream problem, it should be reported upstream.)

aristocrates · 2017-11-04 04:58:08

I suppose the question is, which upstream? Nominally this is a pstoedit bug, but if we look here, pstoedit hasn't had any development since 2015. Perhaps this is an inkscape issue, and they should look into using a different backend for this feature (mentioned below: pdf2svg, also has not been actively developed for a while but according to a commenter on the textext aur package it doesn't call Ghostscript with -dDELAYBIND) or remove it. Or should this be reported to the Ghostscript developers to ask them to "undeprecate" this flag?

It seems from the error message that patching pstoedit to use -dREALLYDELAYBIND might fix this for now (although it is obviously bad going forward to depend on deprecated behavior); would a band-aid like this be considered an acceptable patch for Arch to apply, or would this violate packaging standards?

If we look at https://aur.archlinux.org/packages/textext/, it seems like textext can use a different backend to render latex.

I had this textext installed with pstoedit, but there appears to be a bug in how pstoedit calls Ghostscript. The -dDELAYBIND flag has been deprecated.
Installing pdf2svg allows textext to work around this issue by not using the pstoedit backend.

Last edited by aristocrates (2017-11-04 21:51:46)

Arch Linux

#1 2017-03-20 10:26:22

Inkscape. error rendering latex equation

#2 2017-03-30 13:50:15

Re: Inkscape. error rendering latex equation

#3 2017-03-30 14:38:47

Re: Inkscape. error rendering latex equation

#4 2017-10-17 12:32:00

Re: Inkscape. error rendering latex equation

#5 2017-10-17 17:25:18

Re: Inkscape. error rendering latex equation

#6 2017-10-17 18:41:50

Re: Inkscape. error rendering latex equation

#7 2017-11-02 08:23:19

Re: Inkscape. error rendering latex equation

#8 2017-11-04 04:09:37

Re: Inkscape. error rendering latex equation

#9 2017-11-04 04:58:08

Re: Inkscape. error rendering latex equation

Board footer