[Bug 925371] New: Results of the device eps2write are not usable in EndPage procedure even with the same ghostscript
http://bugzilla.suse.com/show_bug.cgi?id=925371 Bug ID: 925371 Summary: Results of the device eps2write are not usable in EndPage procedure even with the same ghostscript Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: werner@suse.com QA Contact: qa-bugs@suse.de CC: chcao@suse.com, don.raboud@ualberta.ca, jsmeix@suse.com, ulrich.deiters@uni-koeln.de Depends on: 912398 Found By: Community User Blocker: --- +++ This bug was initially created as a clone of Bug #912398 +++
Created attachment 621196 [details] LaTeX file + 2 EPS files
Eps2write is positively not a good replacement for epswrite! The attached zip > archive contains 2 EPS files. hdr_KDK.eps is the original letter background. I > created hdr_KDK2.eps with
gs -sDEVICE=eps2write -sOutputFile=hdr_KDK2.eps hdr_KDK.eps
hdr_KDK2.eps seems OK when one looks at it with okular, gv, etc. But when the > LaTeX document is compiled,
latex doc dvips -t a4 -o doc.ps doc
the resulting PS file is damaged: Okular shows a blank page, and gs gives the error message "%%[ Error handled by opdfread.ps : undefined; OffendingCommand: end92 ]%%"
Compare also with https://stackoverflow.com/questions/28917496/is-it-possible-to-use-eps-file-... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Results of the device |latex or dvips wrongly |eps2write are not usable in |include "gs |EndPage procedure even with |-sDEVICE=eps2write" output |the same ghostscript | --- Comment #1 from Johannes Meixner <jsmeix@suse.com> --- I do not understand the current bug subject "not usable in EndPage procedure" because there is no EndPage procedure in any of your files. Regardless whether or not there is a EndPage procedure, I think plain "gs -sDEVICE=eps2write" output works when it is included "as is" in a PostSCript file but it seems latex or dvips somehow wrongly includes "gs -sDEVICE=eps2write" output. In doc.ps I removed manually the therein included hdr_KDK2 i.e. from the line %%BeginDocument: $HOME/Error2/hdr_KDK2.eps up to includeing the line %%EOF The remaining doc.without-hdr_KDK2.ps results no errors in "gs". Then I manually included hdr_KDK2.eps unchanged as is into doc.without-hdr_KDK2.ps at exactle the palkce where I had before removed the hdr_KDK2 stuff. The resulting doc.with-hdr_KDK2.ps results no errors in "gs". To verify that the hdr_KDK2 is falsely included in doc.ps I removed in doc.ps all lines from the beginning up to including %%BeginDocument: $HOME/Error2/hdr_KDK2.eps and from the next line %%EOF up to the last line so that the remaining stuff is the included hdr_KDK2 in doc.ps i.e. hdr_KDK2-extracted-from-doc.ps and that one results the same error in "gs" as the whole doc.ps. Accordingly my conclusion is that latex or dvips wrongly include "gs -sDEVICE=eps2write" output. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 --- Comment #2 from Johannes Meixner <jsmeix@suse.com> --- Created attachment 629566 --> http://bugzilla.suse.com/attachment.cgi?id=629566&action=edit doc.with-hdr_KDK2.ps doc.with-hdr_KDK2.ps with manually included hdr_KDK2.eps that results no errors in "gs". -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 --- Comment #3 from Johannes Meixner <jsmeix@suse.com> --- Created attachment 629568 --> http://bugzilla.suse.com/attachment.cgi?id=629568&action=edit hdr_KDK2-extracted-from-doc.ps hdr_KDK2-extracted-from-doc.ps is the included hdr_KDK2 manually extracted from doc.ps that results the same error in "gs" as the whole doc.ps. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 --- Comment #4 from Johannes Meixner <jsmeix@suse.com> --- FYI: Since yesterday there is the newest Ghostscript 9.16 available in the openSUSE build service development project "Printing". I used Ghostscript 9.16 on my openSUSE 13.2 system for my above tests. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 --- Comment #5 from Johannes Meixner <jsmeix@suse.com> --- FYI: For me diff -u hdr_KDK2.eps hdr_KDK2-extracted-from-doc.ps | tr -c '[:graph:] \t\n' '?' does not show anything meaningful. It looks as if latex or dvips change encoded "stream" content while including "gs -sDEVICE=eps2write" output? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 --- Comment #6 from Dr. Werner Fink <werner@suse.com> --- Ahmmm ... AFAIK the eps2write is the replacment of epswrite that is it should work out of the box without changing anything. Or in other words: esp2write outpout should be compatible with the old epswrite output. What is the reason for ghostscript upstream to break existing programs. Do you know what Linus Torvalds does in such cases? AFAIK Linus does not accept any change in the kernel which break user space programs. I'd like to see the same behaviour in the ghostscript PostScript kernel world. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|latex or dvips wrongly |Ghostscript device |include "gs |eps2write is not compatible |-sDEVICE=eps2write" output |with device epswrite -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 --- Comment #7 from Dr. Werner Fink <werner@suse.com> --- Btw: Do have read the link in the initial comment? There is no latex nor dvips involved. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 --- Comment #8 from Dr. Werner Fink <werner@suse.com> --- Hmmm ... if I remove the $HOME/Error2 from the tex file as shown here: /tmp/test-dvips> unzip -p ~/Downloads/doc3.zip doc.tex | diff -u doc.tex - --- doc.tex 2015-04-01 13:19:27.101058935 +0200 +++ - 2015-04-01 13:22:49.063249212 +0200 @@ -53,8 +53,7 @@ \selectlanguage{german} \sffamily\mdseries\upshape\normalsize \setlength{\baselineskip}{13.200000pt} -\special{psfile=$HOME/Error2/hdr_KDK2.eps hoffset=0 voffset=-708} +%%\special{psfile=hdr_KDK.eps hoffset=0 voffset=-708} +\special{psfile=hdr_KDK2.eps hoffset=0 voffset=-708} \setlength{\leftskip}{10.5cm} \vspace*{3.5cm} then anything works as it should. /tmp/test-dvips> latex doc.tex [...] Output written on doc.dvi (1 page, 672 bytes). Transcript written on doc.log. /tmp/test-dvips> dvips doc.dvi This is dvips(k) 5.993 Copyright 2013 Radical Eye Software (www.radicaleye.com) ' TeX output 2015.04.01:1326' -> doc.ps </usr/share/texmf/dvips/base/tex.pro> </usr/share/texmf/fonts/enc/dvips/base/8r.enc> </usr/share/texmf/dvips/base/texps.pro> </usr/share/texmf/dvips/base/special.pro> </usr/share/texmf/dvips/base/color.pro>. </usr/share/texmf/fonts/type1/urw/helvetic/uhvr8a.pfb> </usr/share/texmf/fonts/type1/urw/helvetic/uhvb8a.pfb>[1<./hdr_KDK2.eps>] /tmp/test-dvips> gv doc.ps This look more like a problem os using $HOME within a tex file. Also using the full path works flawless. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #9 from Dr. Werner Fink <werner@suse.com> --- With ${PWD}/hdr_KDK2.eps it works also /tmp/test-dvips> grep hdr_KDK2.eps doc.tex doc.ps doc.tex:\special{psfile=${PWD}/hdr_KDK2.eps hoffset=0 voffset=-708} doc.ps:%%BeginDocument: ${PWD}/hdr_KDK2.eps /tmp/test-dvips> gv doc.ps -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 --- Comment #10 from Dr. Werner Fink <werner@suse.com> --- Test was done on openSUSE Factory with ghostscript 9.15 and TeXLive 2013 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 --- Comment #11 from Johannes Meixner <jsmeix@suse.com> --- The difference in the encoded "stream" content is only regarding those characters: 0x04 EOT (end of transmission) 0x0D CR '\r' (carriage ret) When I replace in both hdr_KDK2.eps and hdr_KDK2-extracted-from-doc.ps all '\r' with '\n' (using " tr '\r' '\n' " ) and when I also remove in both files all EOT (using " tr -d '\004' " ) then both resulting remainder files are identical. Accordingly it seems when including "gs -sDEVICE=eps2write" output latex or dvips somehow mess up things with EOT and CR characters. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 --- Comment #12 from Johannes Meixner <jsmeix@suse.com> --- Might this have something to do with "locale" settings? In particular because of the '\r' versus '\n' thing? FYI: To make this once and for all clear: I never was and I am not at all in any way an author or any kind of decision maker for Ghostscript upstream. FWIW: AFAIK systemd is the replacment of SysVinit that is it should work out of the box without changing anything. Or in other words: systemd should be compatible with the old SysVinit. What is the reason for systemd upstream to break existing stuff. Do you know what Linus Torvalds does in such cases? http://www.theregister.co.uk/2014/04/05/torvalds_sievers_dust_up/ Or in other words: People who live in glass houses shouldn't throw stones. and Let he who is without sin cast the first stone. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=925371 --- Comment #13 from Johannes Meixner <jsmeix@suse.com> --- FWIW: I got the same results with Ghostscript 8.62 in SLE11-SP3. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com