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.