Re: [hylafax-users] 11x17 Log as requested

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

On 2003.12.17 15:18 Jayson Henkel wrote:
> Lee,
>
> Here is the log you requested. I believe this is what you want.

> Dec 16 12:42:34.35: [  228]: RECV/CQ: Bad 1D pixel count, row 3115,
> got 0, expected 2048
> Dec 16 12:42:34.35: [  228]: RECV/CQ: Adjusting for RTC found at row
> 3110
> Dec 16 12:42:37.07: [  228]: RECV FAX (00000003): from <UNSPECIFIED>,
> page 1 in 1:27, INF, 7.7 line/mm, 1-D MR, 14400 bit/s

So we got an image sized 2048 (B4 page width) x 3110 at a resolution of 
204 pel/inch x 196 line/inch ... making it 10 x 16.  In other words, 
the sender is choosing B4 page width when it could choose (in theory) 
A3 page width and get the full width in.

> The
> image is only cropped by about 1/2" as you suggested.

I made a reading mistake before and so I made an incorrect statement 
about A3 cropping horizontally for 11x17.  It's actually cropping 1" 
according to the log you sent because it's using B4 page width.  It 
wouldn't have to crop anything for 11x17 if the sender actually 
selected A3 page width, but it isn't.

> Is there
> anywhere
> where I can examine the T.30 spec? I'll need this ammo to back up my
> findings.

http://www.itu.int/

You can get free copies of specs from:

http://www.itu.int/publications/bookshop/how-to-buy.php#free

Specifically you'll want to examine and refer to the page width 
settings discussed in Table 2.

> Re the Debian issue, I'd prefer not to have to package it myself. So,
> I
> guess this is a call to anyone that has encountered the same issue.
> The
> CVS version sounds like exactly what I need, anyone have it packaged?

I have RPMs available.  I don't know if anyone on -devel yet uses 
Debian.

Lee.

____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxxxxx*