When compiling a latex file containing a postscript figure, viewing the dvi file afterwards with xdvi does not render the postscript figure. That used to be fine with mga6 and our previous version of texlive.
Files attached for checking.
this produces the file test.dvi. Open the file with:
enjoy the missing figure. You can check that the dvi file is correct, if you open it with, for instance "emacs", the figure is properly rendered.
Created attachment 11078 [details]
source latex file
The file to compile with "latex"
Created attachment 11079 [details]
A postscript figure that is included.
Postscript figure that should be in the same directory as the test.tex file before compiling with "latex test.tex"
Assigning to our registered texlive maintainer.
It looks like this is a ghostscript problem:
1) requirement to ghostscript-module-x is added for the future
2) made a few tests, looks like ghostscript is to blame, using ghostscript from mga6, xdvi works as expected.
So as stated by arch linux there is a API change, we use texlive 2018 and gs 9.27, so both should work with the new API.
I know xdvi is a small and handy tool, but maybe some of the desktop tools like evince kdvi, ... are working better.
Nope, that does not seem to be the cause of the bug, ghostscript-module-X is installed, it is indeed 9.27.1mga7 together with texlive 2018.
The bug is opened for mga7 only, I had no issue with mga6 in the past, so there is a breakage with 9.27 and 2018.
as said, xdvi works with "old" ghostscript but not with the newer one. So I guess ghostscript has done some more api changes which not have been adapted to xdvi (2018).
I'll have a look, if a newer version of xdvi fixes this issue.
Ok, I understand what you say. So report it upstream,that's clearly a texlive bug, they do maintain xdvi!
@Chris: for testing purpose, I've built the latest 2019 package, bit still not image in xdvi.
E.g. atril (with atril-xdvi) works as expected.
Thanks for the suggestion of alternatives. I've also tried okular and evince.
It is amazing that none of this new dvi readers are actually as good as xdvi!!!
atril and evince do not support hyperlink...okular does, but it takes like more than 5 secs on my super fast machine (xeon 2 cpu 3.1GHz, 48 cores, 132Gb of RAM) to open a dvi file... no comment :)
did you report this issue upstream? any feedback yet?
Nope, I thought you did... ;) I will then!
Finally, this bug has been fixed upstream, xdvi works again in mga8.
Let's close as wontfix for mga7.