I have the same problem. I don't understand how MS could make such an obvious mistake and, six months after its release, not have a fix for it yet. It makes the presenter, which is usually somebody in a business presenting internally or to people outside of their company, look sloppy.
I also don't understand why, with all of the "MVPs" crawling all over this site, there isn't an answer for this yet.
In 22 years of using MS products, the company has never missed a chance to underwhelm. This bug and the failure to fix it is another classic example.
> I have the same problem. I don't understand how MS could make such an obvious mistake and, six months after its release, not have a fix for it yet. It makes the presenter,
which is usually somebody in a business presenting internally or to people outside of
their company, look sloppy.
> I also don't understand why, with all of the "MVPs" crawling all over this site, there isn't an answer for this yet.
We're not MS employees. It's perhaps a bit easier for us to bring problems to
Microsoft's attention, but we have about as much ability to get problems fixed as you
do.
Less if we take "you" in the aggregate. Please ... everyone ...if you haven't already
done so, use the item on the Help menu to contact MS and describe the problem. That's
a vote for a fix.
================================================
Steve Rindsberg, PPT MVP
PPT FAQ: www.pptfaq.com
PPTools: www.pptools.com
================================================
CyberTaz - 27 Jul 2008 22:36 GMT
On 7/27/08 4:48 PM, in article VA.000041dc.11188567@localhost.com, "Steve
Rindsberg" <abuse@localhost.com> wrote:
>> I have the same problem. I don't understand how MS could make such an obvious
>> mistake
[quoted text clipped - 24 lines]
> PPTools: www.pptools.com
> ================================================
Extending on what Steve posted:
Most issues similar to what is referred to in this thread have been
addressed by the updates so far released. It is also a fact that problems
can seldom be corrected unless they can be replicated, and the subject here
is apparently not universal. I have Office 2008 on 2 separate Macs - one
PPC, one Intel - one running Tiger, the other Leopard - and have not seen
anything similar to this occur since applying the 12.0.1 update. Neither
have I been able to force it to occur no matter what fonts or other changes
I make to files from previous versions including ones going back to Office
2000 on the PC.
All who have contributed to this thread might do well to review the posts
within and ask themselves what they've offered by way of details... I see
very little but gripes & moans. Nobody has included version specifics for OS
X or Office, nobody has offered any detailed information with regard to
fonts or font versions, there's nothing with regard to any other formatting
effects used where the problem is being seen... There has been virtually
nothing offered of any substance that would assist in resolution of the
problem that obviously does exist for some users. Without something more
substantive than demands & derisive comments about MS those willing to help
can't reproduce the issue & if it can't be repro'd it's just about
impossible to resolve. There may not be a solution or it may actually be
something faulty in the software, but without facts nobody stand a fighting
chance.
Do you want to just continue bellyaching or do you want to participate in an
effort to get it resolved?
Regards |:>)
Bob Jones
[MVP] Office:Mac