Corrupted outgoing faxes (linejumps)

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

Christian Jung wrote:
> I Have a strange problem that caused a lot of frustration to my. As usual I
> reviewed the docs, the mailinglist-archives and the webpages but to no
> avial :-(
> 
> The problem:
> I generate a PS-File by printing a Word 7.0 (Win95) document to a Apple
> Laserwriter (which actually does not exist :) ) and redirect the
> priontoutput to a file (maybe fax.ps)
> I then 'faxspool <number> fax.ps' and the magic happens. GS complains
> abount long lines in the file (think itīs GS ?!) but promisses to have that
> fixed up. File has been spooled successfully.

g3cat is the one that's complaining. The postscript files created by
windoze contain control commands that confuse ghostscript, and make it
create G3 files with the wrong line width.

> [BTW there is an output of gs during spooling (only with Win95-originated
> ps-files) -> %%Page1%% or similar - is that normal? ]

That's Win95 crap.

> The received fax on the remote station is corrupted. At two or three
> positions, the fax breaks and continous without any space inbetween with
> the faximage a few lines before...uhh..you canīt see what i mean - right?
> In other words: line1,line 2 and line 3 are printed, the suddenly line 2
> appears again, then line 3 and so on. Like a little backwardsjump in the
> datastream.

Huh? This is very weird. Does that happen with other receiving machines
as well?

Actually, I thought that I finally closed that issue, making g3cat fix
these problems "on the fly", but it seems that some faxes can't accept
a *black* run-length of 0 pixels, and do some "bad things". I will
rework that fix...

Anyway, for the time being, you can fix your G3 files by piping them
through:
 g3topbm file-in.g3 | pgm2g3 > file-out.g3

gert
-- 
USENET is *not* the non-clickable part of WWW!
           //www.muc.de/~gert/
Gert Doering - Munich, Germany      gert@greenie.muc.de
fax: +49-89-3545980     gert.doering@physik.tu-muenchen.de
.