http://bugzilla.suse.com/show_bug.cgi?id=925371 Johannes Meixner 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 --- 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 #3 from Johannes Meixner --- 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 #5 from Johannes Meixner --- 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 Dr. Werner Fink 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 #10 from Dr. Werner Fink --- 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 #12 from Johannes Meixner --- 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.