Reassigned to Ulf.

FYI the problem still exists in build 641.

BTW, I have a feature request (not sure if this is where it belongs,
if not can you forward?).  It would be nice to preview .eps graphics
along with the other formats (jpeg, etc.)  Currently, print preview
doesn't show them, just a frame.  Ultimately, it would be nice to view
all graphics in line (as you type) instead of just showing frames.

Thanks, and keep up the good work

Taz

Joost->Ken: please provide a sample document (in sxw format) to have a
chance to reproduce it. In the moment I just can guess...maybe it's a
ghostscript bug

Hi Folks,
I'm pretty sure that this is the same problem as
http://www.openoffice.org/issues/show_bug.cgi?id=2810 .Please verify
it. Easiest way to find out is to try the workaround posted there.
Best regards, Peter

This is supposed to be fixed in the next build.  I will close it once
its verified [when is the next build anyway?]

I just tried 642, the problem is still not fixed

Still doesn't work in 641D.  Help!  I really need this.  SO5.2 prints
out the file correctly, but OO doesn't.  Neither did SO6.0beta.  I am
not a code, so I am sending it back to the subcomponent owner.

thanks

Reassigned to Hasan.

As Joost allreasdy said, please give us a sample where we can download
such document.

Created attachment 2017 [details]
The Attachment from Ken

HI->PL: The attachment includes 3 files:
- OOtest.sxw = the file
- c1focus.eps = the graphic
- junk.ps = Output of print to file
I can't reproduce the crash with OO1.0
The amazing is I can't see the graphic on the document but I can see
it when I look the print to file result.
What's going up there?

Sorry, i can't see a problem with the attached files. GhostScript
shows the file including the EPS perfectly. I see, that gv does not
work correctly (doesn't crash in my case, but neither does it show
anything), but don't you think that is more gv's problem than
OpenOffice.org's considering that GhostScript has no problem working
with it ?

The summary says that printing fails; if so, with what kind of printer
? If you use ghostscript as renderer for your printer, do you still
use version 5 ? There are problems with that version.

Regarding your feature request: EPS graphics are shown in the document
if they contain a preview graphic.

I agree that EPS shows the graphic perfectly.  I appreciate the info
about the EPS required to have its own thumbnail, too bad we cant
generate a thumbnail for graphics without one, oh well, maybe that
should be a feature request.  As for ghostview, it doesn't crash for
me either, it just doesn't print anything and I get the hourglass and
I also get two pages (0 and 1) even though there is just one page.

When I try ghostscript (vs ghostview 3.5.8) it does work--weird
because I thought gv just called gs...  As I played with gv, I found
that the "respect DSC" switch in the gv options dialog is the culprit.
 If I don't respect DSC (document structuring convention...thank you
man pages!) then I see the document but without the page numbers on
the right quick select.  As for the question of is this a gv or an oo
bug, I think oo.  I can work around it now (thank you very much), but
oo is generating broken postscript in that its implementation of DSC
seems to have picked up a bug between 5.2 and now.  If you have
versioning, it started doing this almost immediately after 5.2, maybe
that will make it easier to find.

As for printing, I have a HP LJ4050.  It is a postscript printer, but
"lpr junk.ps" makes my data light flash but nothing happens.  I am not
sure how to turn off the DSC.  More man page reading I guess. 

The most interesting/frustrating thing about this is everything works
just fine in SO 5.2

Thanks again for helping me find a work around, but I still think
there is a bug here, especially since it used to work.

Ken

LJ4050 is a PostScript printer AFAIK. With the additional info that it
is probably the DSC i think i can do something about that. In the
meantime (while there is no fix for this) perhaps you could use
ghostscript to render PCL to your LaserJet. This is obviously not the
best method to feed a native PostScript printer, but should at least work.

BTW: the printing since 5.2 was completely changed; 5.2 used a
commercial print solution that Sun naturally could not make
OpenSource; also it did not work with TrueType fonts and did not
support asian languages (not to speak of CTL languages like arabic or
even thai)

This may be fixed together with issue 7262 which fixes some DSC
compliance issues.

Since the original problem was caused by DSC features (see issue
7262), this is definitely fixed by the fixes for issue 7262 and issue
4529.

closing