Re: Manual duplex printing requires each finished page to be flipp

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Daiya,

As I said in the original post:
"For example, the first sheet in the stack will have PAGE 2 on SIDE A and
PAGE 1 on SIDE B; the second sheet will have PAGE 4 on SIDE A and PAGE 3 on
SIDE B. This means that if you thumbed through the output stack, you would
see pages 2, 4, 6, 8.... in sequence, rather than the desired pages 1, 3, 5,
7...

The pages come out in the hopper face down, and go back in face down so that
the reverse side is printed.

I think the problem is that the Word routine is printing the odd sides
first, and then the even sides. This leaves you with page 2 on the top of
the stack.

I've tried using the Reverse flag, and although it should have corrected the
problem, it did not.

If I do this all semi-manually (printing just the odd pages and then just
the even pages) I can get it right, but my aim was to use Microsoft's "Manual
Duplex" feature to save some effort....but to no avail.

"Daiya Mitchell" wrote:

> What *is* the sequence of page images that Word is sending to the printer?
> In the first pass and the second pass?
>
> I'm not sure exactly what Word 2003 Manual Duplex does, but I assume you
> print all the odd pages, then all the even pages. Might printing all the
> even pages, then all the odd pages, work? (or vice versa, switch whatever is
> currently being done) You might have to add an extra fake page to make sure
> the last page is even, though, not sure.
>
>
> On 7/7/05 10:25 AM, "Larry" wrote:
>
> > I'd have to disagree. This is "manual duplex" so I'm using Word's software to
> > print the pages in the sequence that Word decides...I only provide the labor
> > of taking the output out of the printer and reinserting it for the second
> > pass. The problem is in the sequence of the page images that Word is
> > outputting.
> >
> > But thanks for responding nonetheless.
> >
> > "Larry" wrote:
> >
> >> In Word 2003, using the Manual Duplex printing feature, I get accurate
> >> two-sided printing with one problem: I must flip each sheet of the finished
> >> output as it appears in the output stack. For example, the first sheet in the
> >> stack will have PAGE 2 on SIDE A and PAGE 1 on SIDE B; the second sheet will
> >> have PAGE 4 on SIDE A and PAGE 3 on SIDE B. This means that if you thumbed
> >> through the output stack, you would see pages 2, 4, 6, 8.... in sequence,
> >> rather than the desired pages 1, 3, 5, 7...
> >>
> >> For large jobs, flipping each sheet individually is a real nuisance. I
> >> cannot seem to find a sequence of steps and combination of settings that
> >> avoid this problem. Any advice?
>
>
.



Relevant Pages

  • Re: C to Forth converter?
    ... stack operations to get a lot of stack parameters just right. ... CREATE DOES> SWAP CELLS +; ... ARRAY SEQUENCE #TURNS CELLS ALLOT ... gives you 371 which is the sequence NIP ROT DROP ...
    (comp.lang.forth)
  • Re: Statement on Schildt submitted to wikipedia today
    ... However, what Schildt described was not an abstract stack, but a specific ... but not true -- many compilers will ... support the contention that the standard was designed "to protect profits". ... "Sequence points" were designed to protect profits, ...
    (comp.lang.c.moderated)
  • Re: locating special recurrences
    ... [An awk script to determine whether a sequence of tokens between two ... sentinels tokens is repeated between the second sentinel ... of sequence, split on 11, and compare subsequences" approach. ... do (push (nreverse stack) accum) ...
    (comp.unix.shell)
  • Re: Recursion versus looping.
    ... You claim no stack is needed, but is there no implicit stack ... The coprime sequence is generated in bit-reversed order with no stack. ...
    (comp.lang.forth)
  • Re: Set Up To Print Book, 2 Sides, L & R Margins Alternate-Pagination
    ... chapter a new section which starts on odd page. ... Printing might be more interesting. ... Place the output stack back in the input hopper ... The result is a duplex stack in the ...
    (microsoft.public.mac.office.word)