[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
Re: File that won't print to the end
- Subject: Re: File that won't print to the end
- From: "J. R. Fox" jr_fox@xxxxxxxxxx
- Date: Thu, 21 Oct 2004 12:46:45 -0800
Paul Breeze wrote:
> So, I imagine that there is
> something astray in the file itself. When you talk of Hex 1A amidships or errant and extra Ascii
> 12s, what am I looking for and how do I identity them?
I don't know if Xy's Expanded View would be sufficient -- for the Ascii-12, it should be. A lot of
DOS programs and util.s simply treated one of these as meaning (immediate) End of Page | Eject the
page, whether it actually was the end or not. (I recognize that this was not exactly your problem.)
This is basic stuff, so I _should_ recall it better than I do (like a lot of things . . . ), but I
just don't remember if Xy was primed to react that way. I mean, Xy used its own ≪PG≫ code for
that. Normally what I would do in this case is to examine the file in ZTree's dual Hex | Ascii
view,
which is going to show you everything. O.K., I just did a minimal test file:
blah
blah
and blah
«PG»
and I see two CR/LF pairs following the chevroned PG. Is that the equivalent of the Ascii-12, or is
the PG uniquely interpreted by Xy ? Anyway, I think you said that your results indicate the
behavior
is confined to printing from Xy. That limits the possibilities right there.
Tell you what -- if the file in question contains nothing of a confidential nature, why not send it
to
one or more of us, to run our own scan of it and print test. I must confess to being middling at
best
when it comes to parsing Xy printer files. (Of course, the printer is apt to be different, so
that's
one inconstant variable . . . . ) I'd volunteer for this, but will be away shortly.
Jordan