Re: flexfax: Modem uses only 1-D format

[Ulrich Eckhardt <uli@transcom.de>]

Hi,

i have checked this. My ps2fax generates 2-D encoded files. But the
FaxQueuer
seems to decide not to use 2-D encoding :

Jun  9 09:45:32 henko FaxQueuer[24782]: JOB 28149 (active dest
+4969006071925140 pri 127 tts 0:00 killtime 2:59:00): PREPARE START
Jun  9 09:45:32 henko FaxQueuer[25086]: JOB 28149 (active dest
+4969006071925140 pri 127 tts 0:00 killtime 2:59:00): CONVERT DOCUMENT:
bin/ps2fax -o docq/doc28196.ps;01 -r 196 -w 1728 -l 297 -m 4294967295 -1
docq/doc28196.ps.28149
Jun  9 09:45:33 henko FaxQueuer[24782]: JOB 28149 (active dest
+4969006071925140 pri 127 tts 0:00 killtime 2:58:59): PREPARE DONE
Jun  9 09:45:33 henko FaxQueuer[24782]: JOB 28149 (active dest
+4969006071925140 pri 127 tts 0:00 killtime 2:58:59): CMD START
/usr/local/sbin/faxsend -m ttyS1 sendq/q28149 (PID 25090)
Jun  9 09:46:18 henko FaxQueuer[24782]: JOB 28149 (active dest
+4969006071925140 pri 127 tts 0:00 killtime 2:58:14): CMD DONE: exit
status 0x200
Jun  9 09:46:18 henko FaxQueuer[24782]: JOB 28149 (done dest
+4969006071925140 pri 127 tts 0:00 killtime 2:58:14): SEND DONE: 0:45


Jun  9 09:47:07 henko FaxQueuer[24782]: SUBMIT JOB 28150
Jun  9 09:47:07 henko FaxQueuer[24782]: JOB 28150 (active dest
+4969006071925140 pri 127 tts 0:00 killtime 2:59:00): PREPARE START
Jun  9 09:47:07 henko FaxQueuer[25114]: JOB 28150 (active dest
+4969006071925140 pri 127 tts 0:00 killtime 2:59:00): CONVERT DOCUMENT:
bin/ps2fax -o docq/doc28197.ps;01 -r 196 -w 1728 -l 297 -m 4294967295 -1
docq/doc28197.ps.28150
Jun  9 09:47:08 henko FaxQueuer[24782]: JOB 28150 (active dest
+4969006071925140 pri 127 tts 0:00 killtime 2:58:59): PREPARE DONE
Jun  9 09:47:08 henko FaxQueuer[24782]: JOB 28150 (active dest
+4969006071925140 pri 127 tts 0:00 killtime 2:58:59): CMD START
/usr/local/sbin/faxsend -m ttyS1 sendq/q28150 (PID 25118)
Jun  9 09:47:53 henko FaxQueuer[24782]: JOB 28150 (active dest
+4969006071925140 pri 127 tts 0:00 killtime 2:58:14): CMD DONE: exit
status 0x200
Jun  9 09:47:53 henko FaxQueuer[24782]: JOB 28150 (done dest
+4969006071925140 pri 127 tts 0:00 killtime 2:58:14): SEND DONE:
0:45      

The info file seems ok for this destination, 2DEncoding is yes :

supportsHighRes:yes
supports2DEncoding:yes
supportsPostScript:no
calledBefore:yes
maxPageWidth:2432
maxPageLength:-1
maxSignallingRate:"14400"
minScanlineTime:"0ms"
remoteCSI:"Transcom"
sendFailures:0
dialFailures:0
&pagingProtocol:"ixo"      

Any further hint where i can have a look. Currently i will dig throug
the
sourcecode, if i can find something.

Uli

Glenn Burkhardt wrote:
> 
> Ok, I figured this out.
> 
> Use 0x063b for the trace codes.  In the /var/log/syslog file, you should
> find entries like this:
[..]
> The key is the '-2' in the arguments passed to 'ps2fax' command, listed
> above at 23:13:13.  Here, it's looked in the /var/spool/fax/info/<phone-number>
> file to see if the remote fax will support 2D.
> 
> I still wish the default for a phone number with no info file was 2D,
> but I'll look into that later.
> 
> You can check if your 'ps2fax' command is working properly.  Take some
> small Postscript file, and try
> 
>         ps2fax -1 -o file.1d somefile.ps
>         ps2fax -2 -o file.2d somefile.ps
> 
> The 2D file should be smaller.  With more effort, one could verify that
> the TIFF header says one is 1D encoded, and the other 2D.
> 
> Hope this helps.

-- 
Ulrich Eckhardt       http://people.frankfurt.netsurf.de/uli
Signalgro�tat des wu-ftpd 2,4 (unvollst�ndig?)
Cgi-Sicherheitsbohrung in EWS (regen Sie f�r Webservers auf)
[Translation from an english text to german by AltaVista]