Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!ucbvax.berkeley.edu!sam
From: sam@oxford.berkeley.edu (Sam Leffler)
Newsgroups: comp.dcom.fax
Subject: 2-d encoding and padding EOL
Message-ID: <41468@ucbvax.BERKELEY.EDU>
Date: 27 Mar 91 15:38:46 GMT
Sender: nobody@ucbvax.BERKELEY.EDU
Lines: 19

If you're padding the EOL indicator to a byte boundary (say
for a modem or when placing data in a file), does the tag bit
used to signal the type of the next row in 2-d encoded data
go *in the byte*, or after?  That is, should the EOL byte include
the tag bit, or does the tag bit go in the immediately following
byte?  Putting the bit in with the EOL is a lot more convenient,
but it seems like the tag bit is logically part of the line of data
and so belongs after.

TIFF Class F has an option that says to pad EOL's to byte
boundaries, but does not specify which of the two cases is to
be used.  Modem manufacturers that have controls for padding
EOLs to byte boundaries don't seem to acknowledge 2-d encoded
data.  I've looked in the CCITT specs, and they seem to indicate
that the tag bit goes with the row it "modifies".

	Sam

sam@sgi.com