A
Afoldo
Greetings!
I believe I have identified a bug with Office XP's Brazilian Portuguese
spell checker, as given by the following error message:
"AppName: winword.exe AppVer: 10.0.5815.0 ModName: mssp3pb.dll ModVer:
7.0.0.27 Offset: 0000c288", or
"AppName: excel.exe AppVer: 10.0.5815.0 ModName: mssp3pb.dll ModVer:
7.0.0.27 Offset: 0000c288".
It occurs with the latest Office Updates as of December 28, 2003, and
can also be made to happen in other Office applications that use the common
spell checker. To reproduce it, one must simply run a spell check over any
one of the following lines of text (without the quotation marks):
"n.o"
"a.i"
"a.o"
etc...
It seems that a general formula for the trigger would be
letter-period-letter, and probably other similar variations with the period.
It does not occur with all letter combinations, though. I have seen or
heard this error reported by other people, but there seems to be no official
patch as of yet implemented by Microsoft. An obvious workaround is to
disable automatic spellchecking until all similar strings are removed from
the document.
Nevertheless, I'd like to hear what is Microsoft's official standing on
this issue.
Afoldo
I believe I have identified a bug with Office XP's Brazilian Portuguese
spell checker, as given by the following error message:
"AppName: winword.exe AppVer: 10.0.5815.0 ModName: mssp3pb.dll ModVer:
7.0.0.27 Offset: 0000c288", or
"AppName: excel.exe AppVer: 10.0.5815.0 ModName: mssp3pb.dll ModVer:
7.0.0.27 Offset: 0000c288".
It occurs with the latest Office Updates as of December 28, 2003, and
can also be made to happen in other Office applications that use the common
spell checker. To reproduce it, one must simply run a spell check over any
one of the following lines of text (without the quotation marks):
"n.o"
"a.i"
"a.o"
etc...
It seems that a general formula for the trigger would be
letter-period-letter, and probably other similar variations with the period.
It does not occur with all letter combinations, though. I have seen or
heard this error reported by other people, but there seems to be no official
patch as of yet implemented by Microsoft. An obvious workaround is to
disable automatic spellchecking until all similar strings are removed from
the document.
Nevertheless, I'd like to hear what is Microsoft's official standing on
this issue.
Afoldo