On May 16, 8:35=A0pm, CyberTaz <onlygeneralt...@[EMAIL PROTECTED]
> wrote:
> I'm not seeing anything of the sort here (G5 Dual 2 GHz, 1.5 MB, OS X
> 10.4.11) regardless of whether the page breaks are natural or manual.
Have=
> also included Section Breaks & graphics in the printed selection.
I'm seeing it on an Intel Macbook (1st Gen), 10.5.2, Word 12.1.0.
After more investigation, I can only reproduce in one do***ent. See
below for more.
> Have you recently checked to see if there is an update for your
printer's
> driver software? Have you repaired permissions & restarted your Mac
since
> applying the update?
Yes.
> What's the nature of the content you're trying to print? Does it happen
wi=
th
It's a 27 page do***ent, no tracked changes, some comments, an
embedded ToC, lost of autonumbered headings, some footnotes.
> *every* do***ent or just a certain one? Is it just a certain ****tion of
a
> certain doc, or regardless of what ****tion of any doc? Any
One do***ent, doesn't seem to matter where, but the selection does
need to straddle a page boundary.
problems with
> other print jobs or printing from other programs in a similar fa****on?
Wha=
t
No.
> if you print to PDF or click the Preview button - even while the
> responsiveness is occurring?
Nothing happens - Word just locks up.
> It helps if you provide complete details including specific OS X version
-=
> especially when peripherals are involved - Word (as is the case with any
> program) has little to do with printing, saving, etc. other than calling
f=
or
> the service. It's up to the OS & device driver to carry the ball from
ther=
e.
Hope the above info helps. Anything else I can try?
> Regards |:>)
> Bob Jones
> [MVP] Office:Mac
>
> On 5/16/08 1:53 AM, in article
> 60233979-7c97-4c4c-a0f1-7638bf686...@[EMAIL PROTECTED]
>
> "ATreloar" <andrew.trel...@[EMAIL PROTECTED]
> wrote:
> > I have just upgraded to Word 12.1.0. Now, if I select a chunk of text
> > that spans a page boundary, and do a File->Print, as soon as I tick
> > "Selected Text", the CPU usage of Word climbs to over 100% (dual CPU
> > machine, obviously) and it becomes unresponsive. I have to Force Quit
> > it. If I select a chunk of text *within* a page boundary, it is fine.
>
>
|
