Bug fixes in Office 2008 12.1.2

[etcstgo]

Go back command not working after an application restart: not fixed.

Tabbing incorrectly closing the Preferences panel: not fixed.

Deletion of text incorrectly leaving paragraphs marks behind: not
fixed.

AutoCorrect smart button displaying in spite of preference not to: not
fixed.

Display of recent fonts in font menus not surviving an application
restart: not fixed.

Entries in the custom dictionary selection window deselecting
themselves: not fixed.

Spanish Custom dictionary getting nuked by an attempt to add to it:
not fixed.

Focus randomly passing from Find & Replace window to document window:
not fixed.

Patricio Mason
Santiago, Chile

 

[John McGhie]

So? What does this have to do with us fellow users?

Where did Microsoft say that they WERE fixed?

Most of these are not bugs, they are the way it's designed to work.

If you send this in as feedback, someone at Microsoft will look at it. I
don't see the point in putting it in here?

Cheers

Go back command not working after an application restart: not fixed.

Tabbing incorrectly closing the Preferences panel: not fixed.

Deletion of text incorrectly leaving paragraphs marks behind: not
fixed.

AutoCorrect smart button displaying in spite of preference not to: not
fixed.

Display of recent fonts in font menus not surviving an application
restart: not fixed.

Entries in the custom dictionary selection window deselecting
themselves: not fixed.

Spanish Custom dictionary getting nuked by an attempt to add to it:
not fixed.

Focus randomly passing from Find & Replace window to document window:
not fixed.

Patricio Mason
Santiago, Chile

--

Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Nhulunbuy, NT, Australia. mailto:[email protected]

 

[Phillip Jones]

I guess the fellow knew of these bugs, sent them to feedback *expected*
them to be fixed. Obviously because someone told him they were to be
fixed in next patch and noting they didn't fix them that's all.

True it won't do us any good because we are not able to fix them.

But he was just letting us know what wasn't fixed, if we expected them
to be fixed. ;-)

So? What does this have to do with us fellow users?

Where did Microsoft say that they WERE fixed?

Most of these are not bugs, they are the way it's designed to work.

If you send this in as feedback, someone at Microsoft will look at it. I
don't see the point in putting it in here?

Cheers

--
------------------------------------------------------------------------
Phillip M. Jones, CET |LIFE MEMBER: VPEA ETA-I, NESDA, ISCET, Sterling
616 Liberty Street |Who's Who. PHONE:276-632-5045, FAX:276-632-0868
Martinsville Va 24112 |[email protected], ICQ11269732, AIM pjonescet
------------------------------------------------------------------------

If it's "fixed", don't "break it"!

mailto[email protected]

<http://www.kimbanet.com/~pjones/default.htm>
<http://www.kimbanet.com/~pjones/90th_Birthday/index.htm>
<http://www.kimbanet.com/~pjones/Fulcher/default.html>
<http://www.kimbanet.com/~pjones/Harris/default.htm>
<http://www.kimbanet.com/~pjones/Jones/default.htm>

<http://www.vpea.org>

 

[Elliott Roper]

I guess the fellow knew of these bugs, sent them to feedback *expected*
them to be fixed. Obviously because someone told him they were to be
fixed in next patch and noting they didn't fix them that's all.

True it won't do us any good because we are not able to fix them.

But he was just letting us know what wasn't fixed, if we expected them
to be fixed. ;-)

That's right up *your* alley Phillip. A slight change on your sig is
all we need:

If it's "broken", don't "fix" it!

John, I don't see any of Patricio's list that could be described as "as
designed" unless exhibiting brain-damage was a design goal. I don't
blame him for venting here. Most of his observations were included in
the long list of backward moving things that has caused me to give up
on 2008 until it is raised to merchantable quality. (Except for the
Spanish dictionary - I wish I could swear fluently in Spanish about
this poor excuse for an 'upgraded' version of Office)

 

[The Netherlands Ingrid]

If anyone can PROVE that the Spanish Dictionary was designed ON PURPOSE as not to work, making the program INACCESSIBLE and VOID to a particular group of people as to EXCLUDE them from using it, that would be a clear reason to indict MS Corp at the International Court of Justice, on grounds of a breach of the
International Convention on the Elimination of All Forms of Racial Discrimination
Adopted and opened for signature and ratification byGeneral Assembly resolution 2106 (XX) of 21 December 1965;entry into force 4 January 1969, in accordance with Article 19

<http://www.unhchr.ch/html/menu3/b/d_icerd.htm>

 

[John McGhie]

Hi Elliot:

1, 2, 3, 5, 6, and 8 are all "as designed".

I was careful not to comment on the quality of the design or implementation
-- I said all that to them in person in April

Cheers

That's right up *your* alley Phillip. A slight change on your sig is
all we need:

If it's "broken", don't "fix" it!

John, I don't see any of Patricio's list that could be described as "as
designed" unless exhibiting brain-damage was a design goal. I don't
blame him for venting here. Most of his observations were included in
the long list of backward moving things that has caused me to give up
on 2008 until it is raised to merchantable quality. (Except for the
Spanish dictionary - I wish I could swear fluently in Spanish about
this poor excuse for an 'upgraded' version of Office)

--

Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Nhulunbuy, NT, Australia. mailto:[email protected]

 

[etcstgo]

Hi Elliot:

1, 2, 3, 5, 6, and 8 are all "as designed".

I was careful not to comment on the quality of the design or implementation
-- I said all that to them in person in April

This is astonishing. What you've just revealed here is dynamite.

Until now many users thought that the functionality that was missing
from Word 2008 were unintended bugs.

But if functionality has been taken away by design, I can only
conclude that the inmates have taken over the insane asylum.

And there we were, believing your harangues about reporting bugs to
Microsoft.

I'll bet the media will want to look into your claims.

Patricio Mason
Santiago, Chile

 

[CyberTaz]

Hello Patricio -

My experience here differs a bit on some points;

Go back command not working after an application restart: not fixed.

Confirmed - it appears that this has not changed. Oddly enough if I have a
..doc open then open a .docx & key Shift+F5 it brings the .doc window to the
fore at the previously edited location... Go Figure‽

Tabbing incorrectly closing the Preferences panel: not fixed.

I've not been able to get this to happen since applying the 12.1.2 update.
Tabbing through Preferences no longer causes the panel to go back to the
main panel.

Deletion of text incorrectly leaving paragraphs marks behind: not
fixed.

I've never seen this nor do I recall a post to that effect prior to this.

AutoCorrect smart button displaying in spite of preference not to: not
fixed.

Actually none of the features in *AutoCorrect* itself trigger the SmartTag -
it's actually the AutoFormat As You Type features that do - and yes, that
continues to be the case.

Display of recent fonts in font menus not surviving an application
restart: not fixed.

Confirmed - can't comment on "fixed" because I honestly don't know whether
it's intended to be that way or not.

There are 2 sides to the coin - I can understand how it may be convenient
for some users to have their recently used fonts clustered in a tight shot
group whenever they launch the program, but by the same token those who use
a vast array of fonts might be even more distraught once the accumulation of
"recently used" approximates the actual number of installed fonts. Where
should the line be drawn? 5 most recently used... 10... 20? It seems to me
that such a "feature" would be a poor substitute for proper font management
& avoidance of direct formatting in the first place & would contribute
negatively to what many consider "bloat".

Entries in the custom dictionary selection window deselecting
themselves: not fixed.

Can't comment

Spanish Custom dictionary getting nuked by an attempt to add to it:
not fixed.

Can't comment

Focus randomly passing from Find & Replace window to document window:
not fixed.

Although I did witness this when we discussed it some 6 weeks ago I have not
been able to force it since applying 12.1.2 in either .doc or .docx files.

Patricio Mason
Santiago, Chile

Thanks for following up on these issues.

Regards |:>)
Bob Jones
[MVP] Office:Mac

 

[Elliott Roper]

This is astonishing. What you've just revealed here is dynamite.

Until now many users thought that the functionality that was missing
from Word 2008 were unintended bugs.

But if functionality has been taken away by design, I can only
conclude that the inmates have taken over the insane asylum.

I have no inside knowledge, but I suspect that "inmate" should be spelt
"accountant".
The whole product smells of something rushed out the door to a fixed
date and fixed budget. Most of those "as designed" things were probably
the result of design decisions of the form "Too hard!" and "No Time"

To be a tiny bit even-handed, they *did* have to run very fast to stand
still. I think 2004 was all built using Code Warrior, and they had to
port everything to x-code before anything would work native on Intel.
It looks like they disturbed as little as possible in the process.

Me, I would have stayed on Rosetta for another couple of years while
doing a proper port to Cocoa and chucking away some of the
barnacle-encrusted PC-alike mess that no-one remembers how it works.
But then MS is the world's richest software company and mine went bust.
So what do I know?

I like your attitude (and that of "The Netherlands Ingrid"). Someone
has to deal with the driver asleep at the wheel in Redmond.

Me, I voted with my wallet. I also asked them to rip my MVP badge off
me, and so far they can't even do that properly.

Ingrid, I bet the European courts have had it up the *Here* with
Microsoft.

And there we were, believing your harangues about reporting bugs to
Microsoft.

I'll bet the media will want to look into your claims.

I'll bet they won't.
Media method: 1. Inspect bread. 2. Observe butter.

 

[etcstgo]

Hello Patricio -

I've not been able to get this to happen since applying the 12.1.2 update..
Tabbing through Preferences no longer causes the panel to go back to the
main panel.

Still happening here, every time.

I've never seen this nor do I recall a post to that effect prior to this.

No doubt I wasn't clear. It's right here; you took part in the
discussion yourself:
http://groups.google.com/group/micr...d/b76faa14311dc431/e78911572839d321?lnk=gst&q.

Actually none of the features in *AutoCorrect* itself trigger the SmartTag -
it's actually the AutoFormat As You Type features that do - and yes, that
continues to be the case.

I didn't say it was the features in AutoCorrect. I said the
"AutoCorrect smart button", which is the terminology used in the
application. There is no such thing as an *AutoFormat* smart button.

Can't comment
http://groups.google.com/group/micr...d/256c9d57503d9b3c/dc904d913cd4be33?lnk=gst&q


Can't comment
http://groups.google.com/group/micr...d/e15548143c0a6945/fae47b1c856e7fe1?lnk=gst&q


Although I did witness this when we discussed it some 6 weeks ago I have not
been able to force it since applying 12.1.2 in either .doc or .docx files..

Still happening here, very reliably.

Patricio Mason
Santiago, Chile

 

[CyberTaz]

Thanks for the reminder - the current message just didn't "click"

No doubt I wasn't clear. It's right here; you took part in the
discussion yourself:
http://groups.google.com/group/microsoft.public.mac.office.word/browse_thread/
thread/b76faa14311dc431/e78911572839d321?lnk=gst&q.

Do you find that the problem persists if you simply begin typing after
selecting, rather than pressing delete first?

Regards |:>)
Bob Jones
[MVP] Office:Mac

 

[etcstgo]

Thanks for the reminder - the current message just didn't "click"

Do you find that the problem persists if you simply begin typing after
selecting, rather than pressing delete first?

Re: Deletion of selected text incorrectly leaving paragraphs marks
behind:

I don't use Word 2008 anymore, but I started it up to check your
suggestion.

At least in my very quick test (three times, three different
paragraphs), this does seem to make a difference.

Not that it matters a whole lot , but care to expand on what you
know/suspect about the reason for this?

Patricio Mason
Santiago, Chile

 

[CyberTaz]

Re: Deletion of selected text incorrectly leaving paragraphs marks
behind:

I don't use Word 2008 anymore, but I started it up to check your
suggestion.

At least in my very quick test (three times, three different
paragraphs), this does seem to make a difference.

Not that it matters a whole lot , but care to expand on what you
know/suspect about the reason for this?

Patricio Mason
Santiago, Chile

Just a guess, but Word creates files based on paragraphs as the smallest
unit of content. The default behavior if you delete a sentence, for example,
is that the space following the sentence is deleted as well but the space
preceding the sentence is retained so that the following text doesn't close
up inappropriately. The focus is on the preservation of a well formed
paragraph. It stands to reason that the same concept should extend to a
paragraph when there are 2 consecutive ¶s that one would be retained.

I also noted that if you do the same spanning only one ¶ that it will be
retained, but if you actually type content instead it "bridges the gap" &
the 2 ¶s join to become one.

That's the point I failed to make clear in the previous discussion

Regards |:>)
Bob Jones
[MVP] Office:Mac

 

[John McGhie]

Which they wouldn't be able to do. What a silly thing to say....

If anyone can PROVE that the Spanish Dictionary was designed ON PURPOSE as not
to work, making the program INACCESSIBLE and VOID to a particular group of
people as to EXCLUDE them from using it, that would be a clear reason to
indict MS Corp at the International Court of Justice, on grounds of a breach
of the
International Convention on the Elimination of All Forms of Racial
Discrimination
Adopted and opened for signature and ratification byGeneral Assembly
resolution 2106 (XX) of 21 December 1965;entry into force 4 January 1969, in
accordance with Article 19

<http://www.unhchr.ch/html/menu3/b/d_icerd.htm>

--

Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Nhulunbuy, NT, Australia. mailto:[email protected]

 

[John McGhie]

Hi Patricio:

Nonsense Those six issues are working as designed. That does not mean
that Microsoft, or the designer, or the coder, likes the design. In some
cases they probably don't.

Any software product has multiple components and functions that its maker
"wished would work differently". However, usually for very good reasons, it
doesn't.

You and I might consider the design to be buggy, but since the software is
working the way the specification said it should, there is no likelihood of
it changing.

If you put in a report, with quantified justification, they might change the
design for the next version. If you don't put in a report, there would
normally be no change at all.

I am utterly certain that the media have no interest at all in looking into
these claims -- I am a journalist [I do not practice as one very often
these days, but I am a qualified journalist.] Any journalist trying to make
a name for themselves who DOES look into these claims will either
misunderstand and embarrass themselves, or spend several weeks of work
trying to understand the situation, then realise they have been left without
a story.

Cheers

This is astonishing. What you've just revealed here is dynamite.

Until now many users thought that the functionality that was missing
from Word 2008 were unintended bugs.

But if functionality has been taken away by design, I can only
conclude that the inmates have taken over the insane asylum.

And there we were, believing your harangues about reporting bugs to
Microsoft.

I'll bet the media will want to look into your claims.

Patricio Mason
Santiago, Chile

--

Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Nhulunbuy, NT, Australia. mailto:[email protected]