Path: utzoo!utgpu!watserv1!watmath!att!cbnewsi!hrs1 From: hrs1@cbnewsi.att.com (herman.r.silbiger) Newsgroups: comp.std.internat Subject: Re: [comp.std.internat] CCITT Group 3 question: "early" EOL Summary: Yes, EOLs Message-ID: <1990Aug30.200521.11175@cbnewsi.att.com> Date: 30 Aug 90 20:05:21 GMT References: <1990Aug29.200555.21009@math.lsa.umich.edu> Organization: AT&T Bell Laboratories Lines: 22 In article <1990Aug29.200555.21009@math.lsa.umich.edu>, andrea@sdd.hp.com (Andrea K. Frankel) writes: > > Here's a question I hope someone reading this group can answer: > > CCITT Group 3 encoding has explicit end-of-line codes. Some implementations > (hardware and software) appear to require all lines to be the same > length, fully encoded up to the row width (which must be specified in > some way external to the encoded file), or else they fail. > > - Is this a valid, conforming implementation? > > - Or should a robust implementation be able to decode > Group 3 files where some rows are ended "early" with an EOL > (in which case presumably the rest of the row is white)? The line length is specified in T.4, and has to be maintained. Therefore, no short lines. Even in T.6, where there are no EOLs, the number of pels/line is fixed. Herman Silbiger hsilbiger@attmail.com